AnsweredAssumed Answered

Anyone gotten the SDK_2.2_MCIM6ULL demo applications to work?

Question asked by Kevin Cronn on Aug 16, 2017
Latest reply on Aug 17, 2017 by Yuri Muhin

I am using the evkmcimx6ull development board with the SDK 2.2. I cannot get the demo apps to work with the Segger J-Link Plus on Windows following the armgcc directions in the Getting Started Guide. I have tried the hello_world and the power_mode_switch examples. Both compile with no problems. But the hello_world example does not run, poking around with GDB it looks as if it dies on the first instruction (cpsid i) and the cpu status register says it's an invalid instruction. I get the following output from the SEGGER J-Link GDB Server window when I try to run the power_mode_switch example. When I type "monitor go" it says: ERROR: Could not start CPU core. (ErrorCode: -1).

 

Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00000000 (Data = 0xE59FF01C)
Received monitor command: reset
WARNING: CPU not halted after Reset, halting using Halt request
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x00002E94)
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x00002E94)
Downloading 60 bytes @ address 0x80002000 - Verify failed
Downloading 4096 bytes @ address 0x80002040 - Verify failed
Downloading 4096 bytes @ address 0x80003040 - Verify failed
Downloading 4096 bytes @ address 0x80004040 - Verify failed
Downloading 4096 bytes @ address 0x80005040 - Verify failed
Downloading 4096 bytes @ address 0x80006040 - Verify failed
Downloading 4096 bytes @ address 0x80007040 - Verify failed
Downloading 4096 bytes @ address 0x80008040 - Verify failed
Downloading 4096 bytes @ address 0x80009040 - Verify failed
Downloading 4096 bytes @ address 0x8000A040 - Verify failed
Downloading 4096 bytes @ address 0x8000B040 - Verify failed
Downloading 4096 bytes @ address 0x8000C040 - Verify failed
Downloading 4096 bytes @ address 0x8000D040 - Verify failed
Downloading 4096 bytes @ address 0x8000E040 - Verify failed
Downloading 624 bytes @ address 0x8000F040 - Verify failed
Downloading 8 bytes @ address 0x8000F2B0 - Verify failed
Downloading 4 bytes @ address 0x8000F2B8 - Verify failed
Downloading 4 bytes @ address 0x8000F2BC - Verify failed
Downloading 136 bytes @ address 0x8000F2C0 - Verify failed
Downloading 4096 bytes @ address 0x8000F348 - Verify failed
Downloading 4096 bytes @ address 0x80010348 - Verify failed
Downloading 4096 bytes @ address 0x80011348 - Verify failed
Downloading 4096 bytes @ address 0x80012348 - Verify failed
Downloading 4096 bytes @ address 0x80013348 - Verify failed
Downloading 4096 bytes @ address 0x80014348 - Verify failed
Downloading 4096 bytes @ address 0x80015348 - Verify failed
Downloading 4096 bytes @ address 0x80016348 - Verify failed
Downloading 4096 bytes @ address 0x80017348 - Verify failed
Downloading 3800 bytes @ address 0x80018348 - Verify failed
Writing register (PC = 0x80002400)
WARNING: Failed to read memory @ address 0x80002400
WARNING: Failed to read memory @ address 0x80002400
Received monitor command: go
Starting target CPU...
ERROR: Could not start CPU core. (ErrorCode: -1)
GDB closed TCP/IP connection

 

Has anyone else tried these demo apps?

Outcomes