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.

C64x+ and aetlib - external memory protection



I have tried to figure out aetlib, but haven't found out if external memory protection is possible, and if it is, the how.

Is there any good examples or explanations about that?

The aetlib documentation seems to be aetlib sources commented mostly from the aetlib implementation perspective, that can really be

understandable if one knows about the underlying HW, and Doxygen-documents generated from the sources.

Also, the examples only cover the most common simple cases, like a watchpoint range for writing OR reading (but not both).

I understand that it could be possible to somehow use two aetjobs that share the data address comparators: one for read accesses one for write accesses.

The main aetlib interface doesn't seem to give that possibility, but it looks like it uses some kind of lower level interface that could allow that.

  • There's no external memory protection provided on C64x+ devices.  You'll probably want to post questions related to AETLIB to the Code Composer Studio forum as it's meant for debugging purposes and the team over there supports the AETLIB.

    Best Regards,
    Chad

  • "There's no external memory protection provided on C64x+ devices."


    I know, that's why the AETLIB  was mentioned in the title.

    Thanks for the hint of the right forum. I didn't know where I should have asked - here at least the underlying HW is right... ;-)

    By the way, it has become clear to me that the HW doesn't support both read and write protection of a memory region.

    The JTAG can't handle HW watchpoint regions with both read and write triggers.