Forum: ARM programming with GCC/GNU tools How to stop breaking at reset

Author: Alan Rouse (Company: XC Comms Ltd) (rousey)
Posted on:

Rate this post
0 useful
not useful
I am developing a number of projects for STM32 processors using Eclipse, 
gcc, gdb and an Olimex ARM-USB-OCD jTag dongle.

All works well, but every time I relaunch the project in debug mode the 
code stops at address 0x08000000.  The debug window displays 'No source 
available for "g_pfnVectors() " '. I can run the program to proceed to 
the next breakpoint, but it is a minor annoyance that this always 
happens.  Furthermore I suspect it is using up one of the 6 breakpoints 
provided by the STM32, which restricts debugging.

I launch gdb with the following commands:

target remote localhost:3333
monitor reset init
monitor reset init
break main

The first breakpoint it should hit is therefore at main(), which is 
where it stops after breaking at 0x08000000.  If I add 'continue' at the 
end of the gdb commands it doesn't break at 0x08000000, nor at main(), 
and not even at any other breakpoints I may have manually added!

Any ideas would be welcomed

Author: jrmymllr jrmymllr (jrmymllr)
Posted on:

Rate this post
0 useful
not useful
That happens to me too on Stellaris.  I think I'm just too tolerant of 
minor annoyances that take longer to fix than to simply work around.


Entering an e-mail address is optional. If you want to receive reply notifications by e-mail, please log in.

Rules — please read before posting

  • Post long source code as attachment, not in the text
  • Posting advertisements is forbidden.

Formatting options

  • [c]C code[/c]
  • [avrasm]AVR assembler code[/avrasm]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]

Bild automatisch verkleinern, falls nötig
Note: the original post is older than 6 months. Please don't ask any new questions in this thread, but start a new one.