cowpaul wrote:Is there any way to trigger it from within the startup script or shall I just run it within the post compilation step within Build Steps
There's no way to do it inside the startup script.
phoenix2000 wrote:I can flash this way too. but this not a way I like. so let me explain the procedure so then you can reproduce it.
I made a project for stm32f429 discovery board, with stm32cubemx which initialized all peripherals with their default setting. that's it, without coding anything more. in other words, my project has just some init function call and then a forever loop.
after compiling with the true studio, I opened the "Configure Debug", chose the project and then click on "Search Project..." so it can find the elf file.
but unfortunately, after these attempts, the debug fails and apparently as the warning says it's because of "load" command in the startup scripts.
I tried it again but I don't get the error, perhaps we're not doing the exact same process? Also, I use a STM32F4DISCOVERY board, not sure if it's the exact same?
Anyway, here is what I do:
1. Create a project for the board and initialize all peripherals with their default settings (I'm using stand alone, perhaps that is different?)
2. Generate the project directly into my workspace and for TrueSTUDIO
3. Import the project (existing projects into workspace) through TrueSTUDIO
4. Build it
5. Debug it, no need pointing out .elf since it finds it on its own
Am I doing anything differently from you?