Add instructions for using stlink utility in Linux for flashing MCUs#78
Add instructions for using stlink utility in Linux for flashing MCUs#78gregoster wants to merge 4 commits intoRappetor:mainfrom
Conversation
|
Thanks, I will give it a try somewhere this week and see what's possible (especially flashing the mcu's from the printer itself). Think we will have to add some more clear instructions on how to install (what package to get, how to install this via the command line etc) since we have to assume probably most users have limited to no experience with this. Hopefully it will just install and work without too many dependencies or issues. If it works (also with the single digit clones), and I can make an automated script for it, I might just exchange the whole section with this solution. So worth checking out for sure! 😄 |
|
For what it's worth, I've used the stlink from the printer itself when debugging the MCUs and it worked. I did a bunch of flashing. The package is called stlink-tools. Just make sure not to connect the 3V. I don't think GND is needed either but I didn't check for continuity. Actually, if there are two GPIOs available from the SoC no stlink is needed at all. Only two wires. Flashing can be done with OpenOCD and linuxgpiod similar to this: That guide uses bcm2835gpio where we would want to use linuxgpiod instead. I haven't found any schematics for the mainboard though so don't know if any gpios are available directly from the SoC. |
|
there is problematic issue with this instruction at In my case, for the mainboard I notice STM32Cube reporting 512k memory so I used that and the resulting file was identical to that of STM32Cube |
Some (initial?) wording on how to use the stlink utilities (st-info, st-flash, etc.) to read/erase/write firmware to the MCUs. Feel free to use as little or much of this as you prefer.