AnsweredAssumed Answered

SDK_2.2_MCIM6ULL: App starting issues through 'JLinkGDBServer.exe'

Question asked by DJ Regan on Nov 30, 2017
Latest reply on Dec 11, 2017 by Carlos_Musich

Hello,

 

Using a mx6ull evk with 'SDK_2.2_MCIM6ULL', we were able to follow through the getting started documentation: '\SDK_2.2_MCIM6ULL\docs\Getting Started with MCUXpresso SDK for i.MX 6ULL Derivatives.pdf'.

 

However, after successfully building the 1st demo app, and attempting to run the app on the mx6ull evk, through Segger's "JLinkGDBServer.exe"... 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

Outcomes