2025-11-20 10:55 AM - edited 2025-11-20 11:52 AM
So i'm following along with this video
* https://www.youtube.com/watch?v=usQ_f6Swpok&list=PLTJzs51NlEICI7ARAHOyUqMhTgJE0UFv0&index=5
I have the same
* STM32N6-DK board
This is my build command for the GPIO_IO_Toggle application.
* /opt/st/stm32cubeide_1.18.1/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.linux64_2.2.100.202412061334/tools/bin/STM32_SigningTool_CLI -bin GPIO_IOToggle_FSBL.bin -nk -of 0x80000000 -t fsbl -o GPIO_IOToggle_FSBL-Trusted.bin -hv 2.3 -dump GPIO_IOToggle_FSBL-Trusted.bin
I tried this on 2 different boards and the same thing happened
Bellow is the results from trying to program it.
My output from generating the signed bin
Solved! Go to Solution.
2025-11-25 3:39 AM
So i was programming
* 0x07000000
* 0x70000000 - which is the address i should have been programming
So after you program the flash. It goes into being locked. Then you just flip boot 1 back to 0 and hit reset and it should work
2025-11-24 9:16 AM - edited 2025-11-24 9:33 AM
Well i guess my bigger question is this permanent or not? If not how do i unlock it?
I can still program it in Debug mode. So boot 0 -> gnd and boot1 pin to -> high. Just i can't seem to flash the chip. So i can't test larger applications.
2025-11-25 3:39 AM
So i was programming
* 0x07000000
* 0x70000000 - which is the address i should have been programming
So after you program the flash. It goes into being locked. Then you just flip boot 1 back to 0 and hit reset and it should work