Illustration of JLINK debugging experience under ADS

The article is written for LPC2148, but it is also applicable to Samsung's 44B0 chip. You only need to select S3C44B0 for the corresponding CPU when selecting.

JLINK debugging experience under ADS

Two days ago, a customer used jlink to debug LPC2148 in ADS and always reported an error. I also encountered this error before when debugging LPC2200. Later, the problem was solved and I would like to share it with you.

1. Add JLINK under AXD

Select ConfigTarget under OpTIons, as shown in the figure below:

Click the Add button and add jlinkRDI.dll (make sure you have installed the driver provided by segger company, this instruction installs 3.80a), as shown in the figure below:

After the addition is completed, it will appear as shown in the figure below:

2. Configure JLINK

Continuing from the above, after the addition is completed, click Configure, and the JLINK settings dialog box will appear. Here we mainly select the processor we want to debug, as shown in the following figure:

After selecting, click OK to complete the settings.

If JLINK has been connected to the development board and is powered on, information about the JLINK connection to the processor will appear in the log information, as shown in the following figure:

3. Debugging

After adding JLINK and configuring it, you can start debugging.

After starting debugging, once we single-step or set breakpoint debugging, we will encounter such a problem, as shown in the following figure:

The result cannot be debugged. To solve this problem, we need to modify the settings of ADS and select ConfigureProcessor under Options, as shown in the figure below:

The following dialog box appears:

The problem can be solved by removing the check mark in front of SemihosTing, as shown in the figure below:

Click OK, exit AXD, and re-Debug. This time you can step or set breakpoints at will.