Difference between revisions of "NXP LPC43xx series"
(Created page with "=Dual Core Debugging on LPC4350 with Embedded Studio= This article describes how to setup dual core debugging with SEGGER Embedded Studio. == Required soft- and hardware ==...") |
|||
Line 1: | Line 1: | ||
+ | __TOC__ |
||
+ | |||
=Dual Core Debugging on LPC4350 with Embedded Studio= |
=Dual Core Debugging on LPC4350 with Embedded Studio= |
||
This article describes how to setup dual core debugging with SEGGER Embedded Studio. |
This article describes how to setup dual core debugging with SEGGER Embedded Studio. |
||
Line 42: | Line 44: | ||
=Triple Core Debugging on LPC4367 with Embedded Studio= |
=Triple Core Debugging on LPC4367 with Embedded Studio= |
||
+ | |||
+ | This article describes how to setup triple core debugging with SEGGER Embedded Studio. |
||
+ | |||
+ | == Required soft- and hardware == |
||
+ | |||
+ | The sample project has been tested with the following components: |
||
+ | |||
+ | *J-Link |
||
+ | *NXP LPCXpresso43xx (OM13088) evaluation board |
||
+ | *J-Link software beta version V6.01f or later |
||
+ | *SEGGER Embedded Studio V3.10 |
||
+ | |||
+ | == Running the sample project == |
||
+ | |||
+ | Every core increments a 32bit counter in a shared shared memory area (0x10001F00 - 0x10001FFF). |
||
+ | |||
+ | To run the sample project at first compile and start the project M4 within LPC4367_Multicore with Embedded Studio. Then open a second instance of Embedded Studio with the project M0APP within LPC4367_Multicore. Compile and start the second project. Then open a third instance of Embedded Studio with the project M0SUB within LPC4367_Multicore. Compile and start the third project. |
||
+ | Now you can independently run, halt and step all three cores. Please note that starting the Cortex-M4 will issue a system reset and affect all cores, so the Cortex-M4 always has to be started before the Cortex-M0 cores. |
||
+ | |||
+ | == Included files == |
||
+ | {| class="wikitable" |
||
+ | |- |
||
+ | ! Filename !! Content |
||
+ | |- |
||
+ | | '''Readme.txt''' || Readme file with instructions for debugging |
||
+ | |- |
||
+ | | '''LPC4367_Multicore\LPC4367_Multicore.emProject''' || Project file with M0/M4 projects |
||
+ | |- |
||
+ | | '''LPC4367_Multicore\M0APP\*''' || Cortex M0 APP core project source files |
||
+ | |- |
||
+ | | '''LPC4367_Multicore\M0SUB\*''' || Cortex M0 SUB core project source files |
||
+ | |- |
||
+ | | '''LPC4367_Multicore\M4\*''' || Cortex M4 core project source files |
||
+ | |- |
||
+ | |} |
||
+ | |||
+ | == NXP LPC4350 Embedded Studio Projects == |
||
+ | [[File:LPC4367_TripleCore_Debug_SES.zip]] |
Latest revision as of 10:23, 16 May 2019
Contents
Dual Core Debugging on LPC4350 with Embedded Studio
This article describes how to setup dual core debugging with SEGGER Embedded Studio.
Required soft- and hardware
The sample project has been tested with the following components:
- J-Link
- Arrow LPC-4350-DB1 Rev.B evaluation board
- J-Link software version V6.32g or later
- SEGGER Embedded Studio V3.40
Running the sample project
The Cortex-M4 simply sends a defined command to the Cortex-M0 using shared memory and waits for the response before it resumes execution. The Cortex-M0 waits for command reception from the Cortex-M4 and simply sends back a "received-response" using shared memory.
To run the sample project at first compile and start the project LPC4350_CortexM4_SES with Embedded Studio. Then open a second instance of Embedded Studio with the project LPC4350_CortexM0_SES. Compile and start the second project. Now you can independently run, halt and step both cores. Please note that starting the Cortex-M4 will issue a system reset and affect both cores, so the Cortex-M4 always has to be started before the Cortex-M0.
Included files
Filename | Content |
---|---|
Readme.txt | Readme file with instructions for debugging |
LPC4350_CortexM0_SES\LPC4350_CortexM0_SES.emProject | Cortex M0 core project file |
LPC4350_CortexM0_SES\Src\* | Cortex M0 core project source files |
LPC4350_CortexM4_SES\LPC4350_CortexM4_SES.emProject | Cortex M4 core project file |
LPC4350_CortexM4_SES\Src\* | Cortex M4 core project source files |
Ozone_Multicore_LPC4350_CM0.jdebug | Cortex M0 Ozone project |
Ozone_Multicore_LPC4350_CM4.jdebug | Cortex M4 Ozone project |
NXP LPC4350 Embedded Studio Projects
LPC4350_DualCore_Debug_ES340_Ozone.zip
Triple Core Debugging on LPC4367 with Embedded Studio
This article describes how to setup triple core debugging with SEGGER Embedded Studio.
Required soft- and hardware
The sample project has been tested with the following components:
- J-Link
- NXP LPCXpresso43xx (OM13088) evaluation board
- J-Link software beta version V6.01f or later
- SEGGER Embedded Studio V3.10
Running the sample project
Every core increments a 32bit counter in a shared shared memory area (0x10001F00 - 0x10001FFF).
To run the sample project at first compile and start the project M4 within LPC4367_Multicore with Embedded Studio. Then open a second instance of Embedded Studio with the project M0APP within LPC4367_Multicore. Compile and start the second project. Then open a third instance of Embedded Studio with the project M0SUB within LPC4367_Multicore. Compile and start the third project. Now you can independently run, halt and step all three cores. Please note that starting the Cortex-M4 will issue a system reset and affect all cores, so the Cortex-M4 always has to be started before the Cortex-M0 cores.
Included files
Filename | Content |
---|---|
Readme.txt | Readme file with instructions for debugging |
LPC4367_Multicore\LPC4367_Multicore.emProject | Project file with M0/M4 projects |
LPC4367_Multicore\M0APP\* | Cortex M0 APP core project source files |
LPC4367_Multicore\M0SUB\* | Cortex M0 SUB core project source files |
LPC4367_Multicore\M4\* | Cortex M4 core project source files |