JTAG debugging source level debugging of arm bare board debugging

Catalog

1 Prerequisites for source level debugging

​2 Use the command line for source level debugging

3 Use eclipse Source level debugging

4 summary

---

1 Prerequisites for source level debugging

Source level debugging has 3 Prerequisites

  Because when debugging at the source level , Our program is already located at his link address , That is, it has been repositioned , Then we need to change the previous procedure , We need to comment out the code of initialization memory and relocation in the previous program , So who class initializes our SDRAM, Who can download the program to the link address , This is by openOCD To do the .

2 Use the command line for source level debugging

  Here's just an experience , Because this program is not suitable for debugging .

  As we said before, the premise of debugging is that it has been initialized and relocated , So here we first download one init The program completes initialization , Then debug our program ,

  Then we found our SDRAM It's ready to write , Then download the code , our arm-elf-gdb With our openOCD Link .

Then start debugging ,si(step instruction)

It is still inconvenient to debug with commands ,  Next we use eclipse, It's right gdb Another layer of packaging .

3 Use eclipse Source level debugging

 

   Let's order debug I went to debug ,load Direct load , But we need to initialize the memory first ,

  And then again debug.

  Report errors

Because Chinese directories are not supported , Delete and rebuild the project , Copy the program to a non Chinese Directory , Then repeat the above steps , Recreate project .

  Then you can debug in the window ,

4 summary