ST-LINK debug

[kvresto]

Posted on November 05, 2016 at 04:49

Hi

I have been using my F3discovery to build an application, which is now finished, so I designed a new user PCB and after assembling and running my application all went well, until I tried to start the debugger with mu new PCB.

I get the following error:

Error in final launch sequence

Failed to execute MI command: load D:\\emb\\ARM\\ST\\SW4STM32\\F3\\work\\DAQ\\DAQv2\\Debug\\DAQv2.elf

Error message from debugger back end:

Error erasing flash with vFlashErase packet Error erasing flash with vFlashErase packet

I think its because ST-LINK utility is trying to use the F3discovery config file to start the debugger.

Can someone help me understand how to create a custom config file.

I'm using ST-LINK /V2 ICD tool. I have 5 JTAG connections on my board:

TMS, TCK, TDO, TDI, NRST.

Thanks

kvresto

[kvresto]

Posted on November 05, 2016 at 05:42

Also why is it when I debug the F3discovery board, the debugger jumps around all over the place, and I cant tell which instruction I'm executing. I have not programed for any timer interrupts.

thanks

[Tesla DeLorean]

Posted on November 05, 2016 at 07:43

..the debugger jumps around all over the place..

Turn off optimization, there is frequently not a one-to-one relationship between C source lines, and the assembler code, and the optimizer can change the linear flow.

[kvresto]

Posted on November 06, 2016 at 22:44

Thanks Clive, now I can step through the code.

I noticed you have changed your profile, what revolution are you referring to?

kvresto

[Tesla DeLorean]

Posted on November 07, 2016 at 00:49

I'm expecting one to start on November 8th.... but I perceive there are larger things afoot...

[kvresto]

Posted on November 07, 2016 at 01:00

Viva la revolución (i think) 🙂