Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filesystem initialization issues with TinyUF2 bootloader-only #136

Closed
brentru opened this issue Aug 25, 2021 · 4 comments
Closed

Filesystem initialization issues with TinyUF2 bootloader-only #136

brentru opened this issue Aug 25, 2021 · 4 comments
Labels
bug Something isn't working filesystem provisioning

Comments

@brentru
Copy link
Member

brentru commented Aug 25, 2021

Boards loaded with the tinyuf2 bootloader-only (never loaded with CircuitPython) seem to be not initially mounting the filesystem correctly.

First - what doesn't work:
- On Linux, using esptool-3.1, erase flash, write Fun House bootloader
- On Windows, confirm default demo works
- "Double-click" reset button to get into bootloader
- Copy Beta 5 WipperSnapper firmware
- Board auto-resets, presents red DotStars
- Press reset button
- Open secrets.json in Notepad++ and the file is full of garbage as per similar reports

I didn't exhaustively try to get the above to work, but taking the board after that last step to my Linux box, the file opens just fine. No clue what's going on there, but I suspect it's something in the filesystem code of the firmware, based on what I found gets me a repeatable, good result.

What works:
- On Linux, using esptool-3.1, erase flash, write Fun House bootloader
- On Windows, confirm default demo works
- "Double-click" reset button to get into bootloader
- Copy CP 6.3.0 firmware to HOUSEBOOT drive
- Confirm default CP environment loads
- "Double-click" reset button to get to bootloader
- Copy Beta 5 of WipperSnapper firmware
- Board auto-resets, but doesn't preset red DotStars - instead, presents purple DotStars
- Drive is still named CIRCUITPY, but the secrets.json and wipper_boot_out.txt files are there, along with .fseventd directory, .metadata_never_index and .Trashes files
- Editing secrets.json file works as normal (ie, not filled with garbage)
- Reset board, and IO dashboard (https://io.adafruit.com/docmollo/wippersnapper) shows my Fun House as online
- If I unplug the board and move it to my Linux box, the drive still shows up as CIRCUITPY, but things work fine and the files are there and fine
- Move the board back to my Windows box and secrets.json is still readable.
@brentru
Copy link
Member Author

brentru commented Aug 25, 2021

Brent Replication steps for ESP32-S2

  • Erase flash
  • Load Funhouse TinyUF2 Combo
  • Boot into HOUSEBOOT
  • Drag WipperSnapper UF2 over
  • Device starts up with red dotstars. Serial is not available/mounted, no drive is mounted.
  • Press reset button device starts up again with secrets.json (differs from report because not on beta.5 anymore, json is written)

@brentru
Copy link
Member Author

brentru commented Aug 25, 2021

Brent Replication steps for SAMD51

Erase flash via SPIFlash "Flash Erase Express" sketch
Boot into HOUSEBOOT
Drag WipperSnapper UF2 over
Device starts up with red dotstars. Serial is not available/mounted, no drive is mounted.
Press reset button device starts up again with secrets.json (differs from report because not on beta.5 anymore, json is written)

@brentru
Copy link
Member Author

brentru commented Aug 27, 2021

Closed via #141

@brentru brentru closed this as completed Aug 27, 2021
@brentru
Copy link
Member Author

brentru commented Aug 31, 2021

Customer feedback:

This worked perfectly the first time!! I didn't have time to do extensive testing this weekend, but I had a bit of time this evening to at least run through an erase, flash with default firmware, connect to Windows, bootloader mode, copy BETA 8 and reboot. I really like the idea of the flashing yellow DotStars to indicate you need to edit the secrets.json file!

I should have some time this weekend to run this through some more tests and poking to see if I can break it. Oh - and before I forget, I didn't get the red DotStars after editing the secrets.json file and resetting....it really all did work just as expected with having to do an extra reset here or there.

You rock, dude - great job! 🤘

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working filesystem provisioning
Projects
None yet
Development

No branches or pull requests

1 participant