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

DM6437 Segmentation and Memory Faults

Bandeg
Expert 1140 points

Hi

Are there any utilties/support for debugging segmentation faults/ memory faults on a DM6437 program built in RELEASE mode running under DSP/BIOS.

For instance, can we have the debugger stop when we write to an unexpected memory area, (e.g, program memory) and give the line code that is writing there?

Otherwise what is the best way to debug these conditions?

Regards,

--B

  • TI__Mastermind 20805 points

    Bendeg --

    The DM6437 has a memory protection logic block that provides ability to mark on-chip memory as 'rwx' properties (read, write, execute).  An exception will occur for invalid accesses.  You need to carefully place your code and data in your linker and then set up the addresses in the memory protection unit.  This is supported by the DSP/BIOS MPC module.  Unfortunately, this only works for on-chip memory and cannot be used to tag external memory as rwx.

    Some devices have an emulation feature that allows you to halt for read/write of specific addresses.   If you know which address is being trashed, then you can set a watchpoint to halt for any write to that address.  I'm not sure if the DM6437 has this feature.

    -Karl-