Difference between revisions of "I.MX6DQ"
(Initial commit (by NTG) (by NTG)) |
|||
| (12 intermediate revisions by 5 users 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. |
||
| − | 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]] |
||
| + | 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. |
||
| + | The file serves as an example and may be altered for specific use cases.<br> |
||
| + | 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]] |
||
How to use script files: |
How to use script files: |
||
| Line 16: | Line 19: | ||
Startup procedure is: |
Startup procedure is: |
||
| − | 1) Start debug session that connects to Core 0 and |
+ | 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 |
||
| Line 22: | Line 25: | ||
x) Close all debug session(s) that connect to Core 1, 2 or 3. |
x) Close all debug session(s) that connect to Core 1, 2 or 3. |
||
x + 1) Close debug session that connects to Core 0 |
x + 1) Close debug session that connects to Core 0 |
||
| + | |||
| + | == Tracing on NXP MCIMX6U6 == |
||
| + | |||
| + | ==== Minimum requirements ==== |
||
| + | In order to use trace on the NXP MCIMX6U6 MCU devices, the following minimum requirements have to be met: |
||
| + | * J-Link software version V7.00a or later |
||
| + | * Ozone V3.22e or later (if streaming trace and / or the sample project from below shall be used) |
||
| + | * J-Trace PRO for Cortex-M HW version V1.0 or later for streaming trace |
||
| + | * J-Link Plus V10 or later for TMC/ETB trace |
||
| + | To rebuild the project our IDE Embedded Studio can be used. The recommended version to rebuild the projects is V6.30. But the examples are all prebuild and work out-of-the box with Ozone, so rebuilding is not necessary. |
||
| + | |||
| + | ==== Trace buffer (ETB) ==== |
||
| + | '''Example Project:''' [[Media:NXP_MCIMX6U6_TraceBuffer.zip | NXP_MCIMX6U6_TraceBuffer.zip]] |
||
| + | |||
| + | ==== Streaming Trace ==== |
||
| + | Supported. Example project not available due to lack of eval boards with trace pins. But implementation is straightforward as explained [https://wiki.segger.com/How_to_configure_JLinkScript_files_to_enable_tracing here]. |
||
| + | In order to rebuild the sample project, [https://www.segger.com/embedded-studio.html SEGGER Embedded Studio] can be used. But the examples are all pre-build and work out-of-the box with Ozone, so rebuilding is not necessary. |
||
| + | |||
| + | ==== Tested Hardware ==== |
||
| + | [[File:board_14_1666.jpg|none|thumb|Freescale MCIMXABASEV1 + MCIMX6xAICPU2]] |
||
Latest revision as of 15:53, 15 August 2023
Contents
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
Tracing on NXP MCIMX6U6
Minimum requirements
In order to use trace on the NXP MCIMX6U6 MCU devices, the following minimum requirements have to be met:
- J-Link software version V7.00a or later
- Ozone V3.22e or later (if streaming trace and / or the sample project from below shall be used)
- J-Trace PRO for Cortex-M HW version V1.0 or later for streaming trace
- J-Link Plus V10 or later for TMC/ETB trace
To rebuild the project our IDE Embedded Studio can be used. The recommended version to rebuild the projects is V6.30. But the examples are all prebuild and work out-of-the box with Ozone, so rebuilding is not necessary.
Trace buffer (ETB)
Example Project: NXP_MCIMX6U6_TraceBuffer.zip
Streaming Trace
Supported. Example project not available due to lack of eval boards with trace pins. But implementation is straightforward as explained here. In order to rebuild the sample project, SEGGER Embedded Studio can be used. But the examples are all pre-build and work out-of-the box with Ozone, so rebuilding is not necessary.
