Closed jerryneedell closed 6 years ago
This is reproducible - 2.x loads and boots consistently. 3.0 does not . Dotstar turns blue and nothing happens. I tried connecting it to a Mac with same result. Also force it to create a new File system - no change in results.
I may have seen some strangeness with 3.0 on the bitsy but I was under the impression that @tannewt recently fixed something with the flash for it that had been causing issues. I'll test again and report back.
I am changing it with the DMA work so I'll take a look at it after.
It works for me with the changes from #663
Doesn't seem to work for me with the changes you mentioned
@siddacious and @jerryneedell can you send me the text from the top of the flash chip? We may have different ones. Feel free to send a picture of the board.
Sure, but It’ll be late tonight or more likely tomorrow before I can. I have not tried the latest version yet an will do that as well.
No rush! Thanks for the help!
On Mon, Mar 12, 2018 at 1:33 PM jerryneedell notifications@github.com wrote:
Sure, but It’ll be late tonight or more likely tomorrow before I can. I have not tried the latest version yet an will do that as well.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/adafruit/circuitpython/issues/655#issuecomment-372452759, or mute the thread https://github.com/notifications/unsubscribe-auth/AADNqVm1JDowA8vwCfKimlZPLFSs2SVBks5tdtuBgaJpZM4SZPVU .
I think some FS weirdness was introduced with the latest ASF with 9b4477e1dc088d18127838310b828514cb33edea. I'm looking into it now.
My ItsyBitsy_m0_espress works fine with the latest build:
Adafruit CircuitPython 3.0.0-alpha.2-17-g9d928b5-dirty on 2018-03-12; Adafruit Itsy Bitsy M0 Express with samd21g18
>>>
Even the dotstar works! trying to read the flash chip markings....
is this the right chip? 
Yup! I think so. I'll need to compare with the datasheets tomorrow.
I think it may actually be a code bug too. If you have time, try with commit 9c5a9e34118532bd54d92c9f968534ad9f9409ae (before the latest asf4 update).
Built BOARD=itsybitsy_m0 (old name) from commit 9c5a9e34118532bd54d92c9f968534ad9f9409ae
This version fails - no FS mounted - dotstar turns green for a few seconds then turns off - repeats.
Restored current master - working fine.
@jerryneedell thats weird! I expected 9c5a9e3 to work and current master to not work. Going heads down on usb shortly to see what I find.
This version does not work for me - itsybitys just goes to a solid blues dotstar - no FS mount as before:
[443568.884692] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[443591.740704] usb 3-3.2: USB disconnect, device number 47
[443591.823432] FAT-fs (sdc): unable to read boot sector to mark fs as dirty
do you want to reopen this one or should I create a new issue.
I am finding that when I flash CP 3.0 to my itsybitsy_m0 _express, my Ubuntu linux system is not recognizing the FS.
It works fine if I flash CP 2.x
dmesg output when FS fails with 3.0
On failed boot the Dotstar turns BLue which should indicate "Circuit python is starting up".....