Saturday, December 16th 2017, 4:32am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

prattmic

Beginner

Date of registration: Oct 17th 2012

Posts: 7

1

Monday, November 5th 2012, 3:41am

Debugging second core in OMAP4430

I am unclear how to access the second core of the TI OMAP4430 with the JLink. I am using the provided JLink script and can debug the first core fine, however I would like to switch to the second core. Does the script somehow set up the ability to switch between the cores from the GDB server? The following line from the script seems to indicate that the first core is hard coded in. Is it at least possible to change the script to access the second core?

C/C++ Source code

1
CORESIGHT_CoreBaseAddr = 0xD4140000;       // Set base address of the debug registers of the first Cortex-A9 core. (The OMAP4430 incorporates two Cortex-A9 cores)


Thanks

prattmic

Beginner

Date of registration: Oct 17th 2012

Posts: 7

2

Saturday, November 17th 2012, 10:53pm

Has there been any update on this? I am still unclear how to tell the JLink to switch cores.

42BS

Beginner

Date of registration: May 23rd 2011

Posts: 7

3

Saturday, November 24th 2012, 10:07pm

Hi, I am also interested to know how to debug both A9 cores.
(Not to speak of the two M3 cores).

Any news, info?

SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 366

4

Monday, November 26th 2012, 12:07pm

Hi,

You can modify the JLinkScript to connect to the second core by changing the Core Base Address at the following lines:

Source code

1
2
Line 121: DbgRegBaseAddr = 0xD4142000; // Core0: 0xD4140000; Core1: 0xD4142000;
Line 297: CORESIGHT_CoreBaseAddr = 0xD4142000; // Core0: 0xD4140000; Core1: 0xD4142000;


To access both cores at the same time create one JLinkScript for each core and start two instances of JLink GDB Server passing one script file and a port to listen on to it.
Following an example batch file to start JLink GDB Server twice:

Source code

1
2
start "GDBServer Core0" "JLinkGDBServer.exe" -scriptfile "C:\Work\OMAP4430\Core0.JLinkScript" -port 1895
start "GDBServer Core1" "JLinkGDBServer.exe" -scriptfile "C:\Work\OMAP4430\Core1.JLinkScript" -port 1935



Best regards
Johannes

42BS

Beginner

Date of registration: May 23rd 2011

Posts: 7

5

Thursday, November 29th 2012, 8:45pm

Works. Thank you very much.

Edit: Ok, works only half. I use IAR C-Spy with a above mentioned script. But I cannot achieve to debug both cores at the same time.
When ever I launch a C-SPY it reset the board.

Is it a C-Spy problem or do I have to modify something else in the script?

2ndEdit:
Same problem as with C-Spy, starting the 2nd server resets the board and the 1st one loose connection.

BTW: JlinkGDBServer of V457d does not accept -port!

This post has been edited 2 times, last edit by "42BS" (Nov 29th 2012, 9:23pm)


SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,514

6

Friday, November 30th 2012, 9:04am

Hi,

Quoted

BTW: JlinkGDBServer of V457d does not accept -port!

It does accept the command, but it does not work properly. Will be fixed today/ on monday.


Best regards
Alex

42BS

Beginner

Date of registration: May 23rd 2011

Posts: 7

7

Friday, November 30th 2012, 7:22pm

Correct, it accepts it :-) (No error: illegal option). I should be more exact. (Anyway, it is a beta version.)

Anyway, the reset problem is somewhat more disturbing.

Also, how about Xilinx Zynq. Is there an automatic detection or also some TAP-woodoo needed?
Kind regards

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,514

8

Monday, December 3rd 2012, 12:29pm

Hi,

The Xilinx Zynq can be auto-detected (the number of devices for which this can be done is definitely decreasing...).

reset problem: JLinkGDBServer will not perform a reset at connect if it is not told to do.


Best regards
Alex

42BS

Beginner

Date of registration: May 23rd 2011

Posts: 7

9

Monday, December 3rd 2012, 12:48pm

Hi,

The Xilinx Zynq can be auto-detected (the number of devices for which this can be done is definitely decreasing...).
This sounds good.

Hi,
reset problem: JLinkGDBServer will not perform a reset at connect if it is not told to do.
I tried -noreset option, but whenever one of the JLinkScript run it did reset the cpu.
I could see it because the installed bootloader run again.