Closed astrelsky closed 4 years ago
Hi Astrelsky thank you for testing this. Current main branch works for me ( I usually use zero w v 1.1).
Here is a screenshot of the layout of my sd card.
it seems good. Does config.txt has the line kernel=firmware.img
?
it blinks a couple times, turns off pauses and then quickly blinks and stays off. This appears to be the behavior when it fails to boot the .img file.
Yeah I agree with you.
To test whether your environment executes firmware.img
or not, could you build an bare-metal Raspberry Pi program and replace firmware.img
with it?
An example of bare-matal program is here:
https://github.com/boochow/bare_matal_rpi_zero/tree/master/led_blynk
This is a simple code which blinks LED eternaly.
it seems good. Does config.txt has the line
kernel=firmware.img
?
Yes.
To test whether your environment executes
firmware.img
or not, could you build an bare-metal Raspberry Pi program and replacefirmware.img
with it?An example of bare-matal program is here:
https://github.com/boochow/bare_matal_rpi_zero/tree/master/led_blynk
This is a simple code which blinks LED eternaly.
Compiling and executing the provided sample works without a problem. I changed the main.py above to now set GPIO47 to LOW but it still doesn't appear to work. Is there a way to know if micropython is able to access main.py?
Is there a way to know if micropython is able to access main.py?
While booting you’ll see a message “mounting SD card...done”( or “failed”) on UART. If you do not have UART interface module, I strongly recommend to get one.
There may be compatibility problems between SD cards and the card reader driver, so using an other vendor’s SD card could solve the problem.
Is there a way to know if micropython is able to access main.py?
While booting you’ll see a message “mounting SD card...done”( or “failed”) on UART. If you do not have UART interface module, I strongly recommend to get one.
There may be compatibility problems between SD cards and the card reader driver, so using an other vendor’s SD card could solve the problem.
I see. I'll hook up the uart connections to an arduino to monitor the status. If that is the case I'll close this.
So I get nothing over uart. However I am receiving information when I have NOOBS on the sd card and I get output when using the bare-metal uart example.
I had to set VERBOSE to 1 in sd.c. I'm debugging it now.
If you connected UART with 9600 bps, please re-configure it to 115200, 8bit for MicroPython.
If you connected UART with 9600 bps, please re-configure it to 115200, 8bit for MicroPython.
Here is the output I received. It does indeed start micropython so it may be related to the sd card drivers. I can look into updating them if necessary.
TypeError: argument num/types mismatch
continues to loop infinitely.
@boochow it appears to be fully functional as I got a 'hello world' script working. The TypeError appears to be coming from the example main.py script in the last release (It is because the sd card cannot be mounted). Thank you for your assistance!
@astrelsky I am very happy to hear that! I appreciate your information.
@astrelsky I am very happy to hear that! I appreciate your information.
No problem. Just to make everything 100% clear. Micropython itself works, the sd card driver doesn't. I'll work around that or pre compile it though.
Is this supposed to be functional? I've compiled the current branch and installed it as described in the readme. I have also tried the release distribution and I get the same result. Running on raspberry pi zero V1.3. I've tried raspbian and that works just fine so I know the board is at least functional. I had also tried the release about a year ago, uncommented the lines in main.py and was always presented with a bunch of random colors on the screen.
Here is a screenshot of the layout of my sd card.![root](https://user-images.githubusercontent.com/46897303/73141633-5bcfd880-4054-11ea-8dee-03ebe5224202.PNG)
This is the contents of main.py. Everything else remains unchanged.
I would expect the led to turn on and remain on. However, it blinks a couple times, turns off pauses and then quickly blinks and stays off. This appears to be the behavior when it fails to boot the
.img
file.