-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
STM32 Nucleo F4x1 boards support #989
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
Comments
The Nucleo board is lacking in a USB connector and SD card slot, so that really limits its utility. You'd need to use UART for the REPL (not so bad), but the filesystem would be just the internal one, and there'd be no way to access it from the PC (since there is no USB, so no MSD). So from this point of view I don't think it's worth supporting this hardware (otherwise people are going to ask many questions about how to get the filesystem working, etc). What is your motivation for using the Nucleo board? The pyboard is a better option :) |
Hi Damien, |
You could probably write this in Python itself, a Python function that receives using the xmodem protocol. |
Of course, also send the file could be made from an IDE, avoiding the user to perform the command by hand... |
@nuraci did you get something working for the F401? |
@dpgeorg 8000 e yes, some things work and pass the tests, I am currently trying to use the REPL_RAW feature in order to obtain the "Run" functionality through an IDE. |
Is it something we can merge into this repository? |
I'd love to, but I should probably talk to you before about some choices I took (1) and how to address some issues(2). |
As long as it mostly fits the stmhal framework we should merge it. We can provide macro options for RTC, ADC, timer etc differences. |
I agree and happy to hear this, could you help me in order to go ahead? |
Can MicroPython run as an app on top of the mbed OS? Mbed alpha 1 is -- Charlie On Sun, Dec 21, 2014 at 2:02 PM, Nunzio Raciti notifications@github.com
|
Sorry to revive the old thread. Is the nucleo support working yet. Or the os is not picking up the micropython fs.
Dmesg logs:
|
Hi, are you sure that the file you have copied was the firmware.bin? (see in attach). Nunzio 2015-04-01 1:18 GMT+02:00 aniljava notifications@github.com:
|
I retried the whole process, was able to access over serial console but could not mount fatfs.
DMESG AFTER CONNECTING NUCLEO
COPIED THE FIRMWARE
ACCESS OVER THE SERIAL CONSOLE AND VERIFY THE /flash exists with files
AFTER RESET / RECONNECTION :
I also tried 0 and 1 for , |
@nuraci I recently added support for the F401 and F411 MCUs so maybe this helps you? |
Any updates on this ticket? Proposed closing it, forum can be used for further communications, patches can be submitted to patch tracker when ready. |
We could perhaps merge the board config file from: https://github.com/cnoviello/micropython/tree/master/stmhal/boards/STM32F4NUCLEO . @cnoviello is that ready to merge? |
Yes. It's ready, Feel free to merge. |
Anyone got a NUCLEO F746 board running? |
@mikeredbike the F746 discovery board is (partially) supported. The nucleo version would be very similar. Please discuss this at forum.micropython.org if you want further info/help. |
@cnoviello's board config files for the STM32F401NUCLEO board have been merged in 3d42aa0. His original commits were used but they were all squashed together. |
Hi all,
I'm trying to run (with lots of fun) MicroPython on the STM32F401RE, some things are already good, but there is still much work to do (obviously), the big challenge is, from my point of view, how the user can manage easily the internal file system...
Another little issue is related to the build system as the "Nucleo" approach uses almost the same "stmhal" source tree but with a different point of view and with different CPUs.
Let me know if there is interest in this porting :)
Anyway, I will publish soon my work here: https://github.com/nuraci/micropython
Thank you Damien, your MicroPython is great!!
Hoping is the right place for write this....
Regards,
Nunzio
The text was updated successfully, but these errors were encountered: