Difference between revisions of "I.MX6DQ"

From SEGGER Wiki
Jump to: navigation, search
((by NTG) (by NTG))
m (Erik moved page IMX6DQ to I.MX6DQ)
(3 intermediate revisions by one other user not shown)
Line 6: Line 6:
 
It is the responsibility of the user to execute this first step.
 
It is the responsibility of the user to execute this first step.
   
  +
{{plainlist|
 
* A9 Core 0: Can be debugged without a script file, just select "Cortex-A9" as device.
+
A9 Core 0: Can be debugged without a script file, just select "Cortex-A9" as device.<br>
  +
The following commander file can be used to activate Cores 1-3.
* A9 Core 1:[[File:NXP_iMX6DQ_Core1.JLinkScript]]
 
  +
The file serves as an example and may be altered for specific use cases.<br>
* A9 Core 2:[[File:NXP_iMX6DQ_Core2.JLinkScript]]
 
* A9 Core 3:[[File:NXP_iMX6DQ_Core3.JLinkScript]]
+
A9 Core 0: [[File:NXP_iMX6DQ_Activate4Cores.jlink]]<br>
  +
A9 Core 1: [[File:NXP_iMX6DQ_Core1.JLinkScript]]<br>
}}
 
  +
A9 Core 2: [[File:NXP_iMX6DQ_Core2.JLinkScript]]<br>
  +
A9 Core 3: [[File:NXP_iMX6DQ_Core3.JLinkScript]]
   
   
Line 18: Line 20:
   
 
Startup procedure is:
 
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
+
1) Start debug session that connects to Core 0 and activate the other cores. <br>This can be done by passing the following parameters to J-Link Commander:<br> -commanderscript PATHTOFILE/iMX6DQ_Activate4Cores.jlink -jtagconf -1,-1
 
2) Start debug session that connects to Core 1, 2 or 3 by using the respective provided script file
 
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
 
3) Start debug session that connects to Core 1, 2 or 3 by using the respective provided script file if required

Revision as of 10:18, 26 October 2018

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.
The following commander file can be used to activate Cores 1-3. The file serves as an example and may be altered for specific use cases.
A9 Core 0: File:NXP iMX6DQ Activate4Cores.jlink
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 activate the other cores. 
This can be done by passing the following parameters to J-Link Commander:
-commanderscript PATHTOFILE/iMX6DQ_Activate4Cores.jlink -jtagconf -1,-1 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