Display the specific FS error using LED blink codes

[prochazkaml]

My Pico just kept blinking no matter what (tried flashing different firmware versions, erasing the "built-in" memory card file & replacing it with an empty one several times) and I wanted to know why it was failing, so I implemented simple blink error codes:

1 flash = FS mount error 2 flashes = File open error 3 flashes = File read error

Turns out my Pico is failing with 3 flashes, so it cannot read the file properly, meaning the file on the internal FS is smaller than expected. Not sure why that is happening, as the file I uploaded is exactly 131072 bytes (I used the empty memory card example which is provided in this repo).

I figured it might be useful to others for diagnosing such issues.

[dangiu]

Good idea! I would ask you to change 2 things:

• Could you make it so that the number of time the led is blinked is a parameter of the function blink_led()? This way there are no loops repeating arbitrary amounts of time in the code
• Could you change the base branch to "development"?

[prochazkaml]

Thank you!

In order to switch the base branch, do I have to create a new pull request, or is it changeable somewhere? (I can see that I can change the destination branch on your repo, but I cannot change the source branch from my repo...)

[prochazkaml]

Okay, well that appeared to break everything. Should I just start over and submit a new pull request directly from my development branch?

[dangiu]

Ok. Create a new branch from development named something like "feature/LED-status" with the proposed changes, then ask to merge it into development :)

[prochazkaml]

Alright, thank you! 👍