Open S4WRXTTCS opened 3 years ago
I can confirm this issue, V7.0.0 doesn't appear to function. V6.3.0 does:
soft reboot
Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
Hello World!
Code done running.
Press any key to enter the REPL. Use CTRL-D to reload.
Adafruit CircuitPython 6.3.0 on 2021-06-01; NUCLEO STM32H743 with STM32H743
>>>
This might be a bit outside the scope of this bug report, but it doesn't look like either the STM32F7 or the STM32H7 parts will have much support within CircuitPython for the foreseeable future. So should someone like me who is experimenting with Python on those parts shift focus to MicroPython? I created board files for both of my boards using MicroPython and it seems to work just fine.
I don't see any STM32F7/STM32H7 boards from Adafruit so I don't see much reason for Adafruit to support them.
I tend to use CircuitPython first as I like how adafruit has CircuitPython libraries for most of the sensors/lcd/etc that it sells. But, I do see tutorials on how to use those libraries with Micropython so it might not be that big of deal to go that route.
This might be a bit outside the scope of this bug report, but it doesn't look like either the STM32F7 or the STM32H7 parts will have much support within CircuitPython for the foreseeable future. So should someone like me who is experimenting with Python on those parts shift focus to MicroPython? I created board files for both of my boards using MicroPython and it seems to work just fine.
I don't see any STM32F7/STM32H7 boards from Adafruit so I don't see much reason for Adafruit to support them.
I'd love to see the F7/H7 support working and would love to help you find and fix the issue. However, as you say, Adafruit funded folks, like myself, tend to focus our work on platforms that are on Adafruit created hardware.
Since this is an issue with USB I'd suggest testing the latest version of TinyUSB. 7.0.0 updated TinyUSB and that may have caused the issue. Updating TinyUSB further may hopefully fix the issue.
I tend to use CircuitPython first as I like how adafruit has CircuitPython libraries for most of the sensors/lcd/etc that it sells. But, I do see tutorials on how to use those libraries with Micropython so it might not be that big of deal to go that route.
I'd love to help you jump into fixing CircuitPython. The Discord chat is a good place to get quick help: https://adafru.it/discord
Hi, I just tested pre-build CP firmware ver 8.2.9 and 9.0.0 Alpha 6 on nucleo-h743zi2. This problem still exists.
I understand the reason why it is lacking the support from Adafruit, but I think you should remove the download page or the download button at least on CP website if it is no longer working. Doing so to prevent someone like me who wants to purchased a more powerful "supported" board and realized it is actually not later. As suggested above, I will try the Blinka on MicroPython for now.
I understand the reason why it is lacking the support from Adafruit, but I think you should remove the download page or the download button at least on CP website if it is no longer working. Doing so to prevent someone like me who wants to purchased a more powerful "supported" board and realized it is actually not later. As suggested above, I will try the Blinka on MicroPython for now.
Please file an issue here: https://github.com/adafruit/circuitpython-org I don't agree that it should be removed, but we should make it clear that it is alpha quality. (per the release notes)
CircuitPython version
Code/REPL
Behavior
N/A
Description
The STM32H743 Nucleo board doesn't seem to connect to via either the USB Serial or Mass Storage connection to the host using the Circuit Python 7.0.0 bin image off the website or an image built from the CircuitPython GitHub repository.
I verified the board works fine using the latest version of MicroPython.
I've also used CircuitPython V7.0.0 with a couple STM32F405 boards without any issue.
I'm going to test out some earlier builds of CircuitPython to see if those work.
Additional information
No response