• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1283 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.

MMU Page Table view in CCS 6.1 just displays a red cross when used on a AM3352

Chester Gillon
Guru 92251 points

Other Parts Discussed in Thread: AM3352

Using 6.1.0.00104 with a AM3352 connected via a XDS100v2, with the MMU Page Table view used on the Cortex-A8 core, when enter a valid address get a view which just contains a red cross. E.g.:

The MMU Page Table appears to have accepted the address of 0x80000000 as valid in this example, since if enter an invalid numeric address, or a non existent symbol name, get an error message displayed after the red cross.

Is the MMU Page Table view supposed to be supported in CCS 6.1 for AM335x Cortex-A8 based devices?

I found some old threads which mentioned problems with MMU Page Table views in CCS 5 for which the suggested work-around was to call ptvLookupAddress from the Scripting Console. With CCS 6.1 confirm that calling ptvLookupAddress from the Scripting Console works, but wasn't sure if the MMU Page Table view not displaying any information is a known limitation or a "bug".

The same problem occurs with CCS 6.1 under Windows 7 64-bit or CentOS 6.6 64-bit.

  • 0
    TI__Guru**** 171519 points

    Chester,

    I also see the same issue with this view, despite it nicely shows the addresses using ptvAddressLookup and ptvReverseLookup in the scripting console.

    I will try to get some input if this feature will be supported in the future or not. 

    I apologize for the inconvenience,

    Rafael

  • 0 in reply to desouza
    TI__Guru**** 171519 points

    Chester,

    The official stance is that MMU Page Table view is not supported due to severe technical difficulties. I filed SDSCM00051932 to track its removal from the IDE.

    On the other hand, you can use some DSS APIs to get an insight over the MMU configurations. Check the quick tip below:

    I apologize for the inconvenience,

    Rafael