Difference between revisions of "I.MX6DQ"

From SEGGER Wiki
Jump to: navigation, search
((by NTG) (by NTG))
((by NTG) (by NTG))
Line 8: Line 8:
   
 
A9 Core 0: Can be debugged without a script file, just select "Cortex-A9" as device.<br>
 
A9 Core 0: Can be debugged without a script file, just select "Cortex-A9" as device.<br>
A9 Core 1:[[File:NXP_iMX6DQ_Core1.JLinkScript]]<br>
+
A9 Core 1: [[File:NXP_iMX6DQ_Core1.JLinkScript]]<br>
A9 Core 2:[[File:NXP_iMX6DQ_Core2.JLinkScript]]<br>
+
A9 Core 2: [[File:NXP_iMX6DQ_Core2.JLinkScript]]<br>
A9 Core 3:[[File:NXP_iMX6DQ_Core3.JLinkScript]]
+
A9 Core 3: [[File:NXP_iMX6DQ_Core3.JLinkScript]]
   
   

Revision as of 12:11, 11 January 2017

Multi-core support for iMX6DQ (DualCore / QuadCore Cortex-A9)

J-Link script files are necessary to connect to the different A9 cores of the device. As a first step, it is mandatory to connect to the first A9 core (Core 0) and enable any other A9 core (Core 1-3) which the user would like to debug. It is the responsibility of the user to execute this first step.


A9 Core 0: Can be debugged without a script file, just select "Cortex-A9" as device.
A9 Core 1: File:NXP iMX6DQ Core1.JLinkScript
A9 Core 2: File:NXP iMX6DQ Core2.JLinkScript
A9 Core 3: File:NXP iMX6DQ Core3.JLinkScript


How to use script files: Please refer to J-Link User Guide (UM08001), chapter 5.10 "J-Link script files"

Startup procedure is:

1)     Start debug session that connects to Core 0 and let it run the application to the point that enables the other Cores
2)     Start debug session that connects to Core 1, 2 or 3 by using the respective provided script file
3)     Start debug session that connects to Core 1, 2 or 3 by using the respective provided script file if required
[...]
x)     Close all debug session(s) that connect to Core 1, 2 or 3.
x + 1) Close debug session that connects to Core 0