Hello,
We are developing with a NXP mx6ull evk (has IMX6ULL processor), and attempting to perform some 'bare metal' development with the Segger JLink Plus.
NXP supports such development with a SDK called 'SDK_2.2_MCIM6ULL', which can be downloaded from NXP's site here...
nxp.com/webapp/Download?colCod…ype=license&location=null
Folks following instructions from this SDK are given instructions for installing required toolchains are provided within this download at path:
'\SDK_2.2_MCIM6ULL\docs\Getting Started with MCUXpresso SDK for i.MX 6ULL Derivatives.pdf'.
After successfully installing the armgcc toolchain path -> we are getting a message from Segger's "JLinkGDBServer.exe"... where we observe failure to start the core, with exact message through the GDB server console: "ERROR: Could not start CPU core. (ErrorCode: -1)".
And so, my question is... Has anyone else observed issues initiating a "monitor go" response through the GDB Server console?
Other information...
- Demo app being tested is ''\SDK_2.2_MCIM6ULL\boards\evkmcimx6ull\demo_apps\hello_world\"
- From 'GNU ARM Embedded Toolchain in Launchpad' we are using the latest version build '5.4 2016q3'.
- The full GDB server console session is attached (see file: 'gdb_debug_hello_world.elf.txt'.
- The 'hello_world.elf' file resulting from executing the 'build_ddr_debug.bat' is in attached file 'hello_world.zip'.
Thoughts? Troubleshooting ideas?
Thanks much,
--DJ Regan
We are developing with a NXP mx6ull evk (has IMX6ULL processor), and attempting to perform some 'bare metal' development with the Segger JLink Plus.
NXP supports such development with a SDK called 'SDK_2.2_MCIM6ULL', which can be downloaded from NXP's site here...
nxp.com/webapp/Download?colCod…ype=license&location=null
Folks following instructions from this SDK are given instructions for installing required toolchains are provided within this download at path:
'\SDK_2.2_MCIM6ULL\docs\Getting Started with MCUXpresso SDK for i.MX 6ULL Derivatives.pdf'.
After successfully installing the armgcc toolchain path -> we are getting a message from Segger's "JLinkGDBServer.exe"... where we observe failure to start the core, with exact message through the GDB server console: "ERROR: Could not start CPU core. (ErrorCode: -1)".
And so, my question is... Has anyone else observed issues initiating a "monitor go" response through the GDB Server console?
Other information...
- Demo app being tested is ''\SDK_2.2_MCIM6ULL\boards\evkmcimx6ull\demo_apps\hello_world\"
- From 'GNU ARM Embedded Toolchain in Launchpad' we are using the latest version build '5.4 2016q3'.
- The full GDB server console session is attached (see file: 'gdb_debug_hello_world.elf.txt'.
- The 'hello_world.elf' file resulting from executing the 'build_ddr_debug.bat' is in attached file 'hello_world.zip'.
Thoughts? Troubleshooting ideas?
Thanks much,
--DJ Regan
The post was edited 2 times, last by djregan42 ().