Jlink debugging method

Technorati labels: ok6410, jlink, debugging

Step 1

For details about how to install realview Developer Suite v2.2, see the readme.txt file in the rvds2.2directory. After the installation is successful, the following error occurs:

Program-> 〉Arm->Realview Developer Suite v2.2

Step 2

Install setup_jlinkarm_vpolici.zip on the Optical Disk

Note::Fixed installation4.10Version.The latest on the official website4.14The version cannot be properly debugged.6410.

Step 3

After correctly installing rds2.2, two debuggers will appear. Axd debugger v1.31 and realview debugger v1.8

The following uses axd debugger as an example to describe how to use jlink V8.

(1)Correctly connect the Development Board andJlink. Power on the Development Board

Open axd debugger v1.31

Add select Step 2Jlinkrdi. dll

Step 4

Burn the U-BOOT used under linux2.6.28 to NAND. Then, set the dial switch to the NAND startup mode. For the writing method, refer to "te6410 Development Board linux2.6.28 User Manual"

Note: Burn writeBootloaderThe purpose is to enablePLL, DDR RAM. To add the programLoad to the memory for debugging.

Step 5

After all preparations are completed, you can start normal debugging. Power on the Development Board,

Open axd,

File-> load image: select the. axf file to be debugged.

Note: When you use RDS for program compilation, jlink does not support MMU because of the RO base option settings on the realview linker tab, no matter whether the U-boot you have written has MMU address ing, RO base must use the real address. For example, you can select Ro base as 0x50200000 (Initi6410OfDDR RAMThe address is fromStarting from 0x50000000!)

Jlink debugging method