MicroPython Forum (Archive)

Hi Forum

I have a STM32F411 Nucleo Board, and I'm running Win11. I want to use STM32CubeProgrammer to upload Micropython via the ST-LINK attached programmer. I can successfully connect with STM32CubeProgrammer and USB to the attached ST-LINK board. I can find the NUCLEO_F411RE-20220618-v1.19.1.hex file in the STMCubeProgrammer, and it seems to download successfully to the board.

However, when I look at the memory (on my system, the D: drive), I don't see main.py, boot.py etc. as I would see on a pyboard.
It doesn't appear that I can use a *.dfu file with the STM32CubeProgrammer, so I think the .hex file is what I should be using.

Can anyone offer guidance?

Thanks
Andy

I usually use the .hex file with stlink on stm32f417 and stm32f746 and it works well .
Maybe you should upgrade the stlink to the version which support the mass storage and try then to upload the .hex file to your board .

Thanks for your advice. I had thought STMCubeProgrammer would be most straightforward, but there doesn't seem to be any clear path with this tool. I had found this ST-LINK tool on ST website, but it says it is replaced by STMCubeProgrammer:
https://www.st.com/en/development-tools ... nk004.html

Or by stlink, do you mean this project?:
https://github.com/stlink-org/stlink

I have very little experience with STM32 boards, but I seem to remember something to the effect of that the USB drive (and serial console) presented by MicroPython will be on a different USB port than the one presented by the ST-LINK. You may need to attach a USB connector to the respective pins of your board if it doesn’t have one already.

Andrew1234 wrote: ↑

Fri Jul 29, 2022 2:09 pm

Or by stlink, do you mean this project?:
https://github.com/stlink-org/stlink

Maybe I didn´t explain it well , it´s my fault sorry . What I meant is the use of the stlink utility , when you have the .hex file you can upload it to your controller using the stlink utility , you should have the latest version of the stlink because it supports the VCP and the mass storage .