Arduino for STM32

Implementing a serial bootloader and bootloader check , the best way to do this is have them as two parts, bootloader/program and maintain as such. In the bootloader you need to decide on your check, You can look for a single magic value in the memory , bear in mind you could possibly end in boot lo...

Hi, When you say it worked on 5-6 programs , I assume you mean the board accepted 5 - different .bin files and flashed them and they booted (be it blink or what ever) but when you upload your code it wont function, I assume then yes there is a conflict, i would start by putting serial.print right at...

The USB boot loader need to be flashed first and at a different location of memory, e.g bootloader start address 0x0000000 user code start address 0x00005000 also depending on which ide you are using you will have to change programming type. i use platformio and Black Magic probe( the stm32 jatg sof...

if you see this post https://github.com/stm32duino/Arduino_Core_STM32/issues/669 you will see you can setup spi_2 class with the line #define MOSI2 PB15 #define MISO2 PB14 #define SCLK2 PB13 #define SS2 PB12 //SPIClass(uint8_t mosi, uint8_t miso, uint8_t sclk, uint8_t ssel) SPIClass SPI_2(MOSI2, MIS...

I have recently developed a bootloader for the stm32f4xx series and I can say that clocks and setup varies in each build environment, some set them up fully and others require input and without such input will default to values that can cause issues later on. Heres some tips I have learned along the...

Maybe try this guide,
https://bootlin.com/blog/building-a-lin ... lications/

darkspr1te

It could be a module in arduino being enabled (eg usb) that might be conflicting with the bootloader , that is just a assumption thought.

Are you stuck in that environment? as you can build both in platformio/vscode and have a lot more control over the build but thats my personal preference.
beyond what i've mentioned in prior post I can offer no more advice yet



darkspr1te

At this point the things I would do to diagnose this issue is add a Hardfault handler to your source code ( see bootloader for a example ) and then use SWD debug to see where the program is once the bootloader has handed over and see if any output on uart. Are you able to provide me with a test bin ...

Please also note that in the bootloader itself you must also change the bootvect address
to

darkspr1te