• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 350 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.

Could not update children for some modules in kernel objew view

Khor
Intellectual 375 points

 

Hi,

I encountered trouble reading some memory block when opening TIBIOS kernel object view for OMAP1710. Some modules could not update the children. Anybody has any idea what causing this and the way to solve it?

This are the error messages

Error: Error 0x00000002/-2130 Error during: Memory,  Cannot access memory address at 0x0074FFE0 
Trouble Reading Memory Block at 0xa2d818 on Page 0 of Length 0x2c9: Error 0x80000002/-1143 Fatal Error during: Memory,  The memory at 0x00A2D818 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should  still be able to access memory and CPU registers. System state has been altered.  It is strongly advised that the processor should be reset before resuming execution, 
Trouble Reading Memory Block at 0x385f36 on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory,  The memory at 0x0070BE6C continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should  still be able to access memory and CPU registers. System state has been altered.  It is strongly advised that the processor should be reset before resuming execution, 
Trouble Reading Memory Block at 0x385f38 on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory,  The memory at 0x0070BE70 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should  still be able to access memory and CPU registers. System state has been altered.  It is strongly advised that the processor should be reset before resuming execution, 
Trouble Reading Memory Block at 0x386dde on Page 1 of Length 0x40: Error 0x80000002/-1143 Fatal Error during: Memory,  The memory at 0x0070DBBC continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should  still be able to access memory and CPU registers. System state has been altered.  It is strongly advised that the processor should be reset before resuming execution, 
Trouble Reading Memory Block at 0x385f3a on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory,  The memory at 0x0070BE74 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should  still be able to access memory and CPU registers. System state has been altered.  It is strongly advised that the processor should be reset before resuming execution, 
Trouble Reading Memory Block at 0x385f36 on Page 1 of Length 0x4: Error 0x80000002/-1143 Fatal Error during: Memory,  The memory at 0x0070BE6C continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should  still be able to access memory and CPU registers. System state has been altered.  It is strongly advised that the processor should be reset before resuming execution, 
Trouble Reading Memory Block at 0x385f38 on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory,  The memory at 0x0070BE70 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should  still be able to access memory and CPU registers. System state has been altered.  It is strongly advised that the processor should be reset before resuming execution, 

  • 0
    TI__Mastermind 20805 points

    Can you check your memory map to see if that memory is a valid address?   Open a memory window and see if you can read that memory via raw memory window.   Unfortunately, KOV does not check to make sure addresses are valid before trying to read them.  If that address is invalid, then you probably have a bug in the target code that is corrupting one of the BIOS data structures and yielding this memory reference.  The new ROV in CCSv4 checks the memory map before doing memory reads.  It will output a better error message.

    -Karl-