• Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 1751 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

GEL_Reset()

Pragnesh Patel
Intellectual 935 points

I have custom board with LM3S5R31 CPU on board. With CCSv4 studio, I am getting following messages,

 

"

CORTEX_M3_0: GEL: Error while executing OnTargetConnect(): Could not read memory at 0x400FE100: Execution state prevented access.
CORTEX_M3_0: GEL: Error while executing GEL_Reset(): A reset is not allowed at this time when calling the function GEL_Reset().
CORTEX_M3_0: Can't Run Target CPU: Target is not halted or failed to halt after step.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c024 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c000 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c018 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c020 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c028 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c02c on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c030 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c000 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c018 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c020 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c024 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c028 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c02c on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c000 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c000 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c018 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c020 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c024 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c028 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c02c on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c000 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c018 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c020 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c024 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c028 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c02c on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c000 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c000 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c004 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c018 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c020 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c024 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c028 on Page 0 of Length 0x4: Debug Port error occurred.
CORTEX_M3_0: Trouble Reading Memory Block at 0x4000c02c on Page 0 of Length 0x4: Debug Port error occurred.

"

 

I am using ICDI interface. JTAG Debugging works, but every time, I have to reconfigure break points. As well some time it directly go to IntDefaultHandler(void). Resetting CPU core and soft reset brings back the CPU at start of main() in healthy condition.

  • TI__Guru**** 171439 points

    Hi,

    I am not quite sure what is your question, but when exactly does this happen? Is it during a debug session or just after you connect to the target for the first time? 

    These messages indicate that the emulator cannot get control of the device (Execution state prevented access) or the IDE lost communication with the target board (Trouble reading Memory).

    The first scenario may be related to a power glitch on the device or even the application blocking the CPU by waiting for a peripheral or an external memory device.

    The second scenario can also be related to a power glitch, a connection failure between the ICDI and the device, or the application inadvertently resetting the device.

    I suggest checking all power supplies, the status of the device (if it is being held in reset after powering the board) and the emulator cable integrity.

    Hope this helps,

    Rafael