• State
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 195 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

CODECOMPOSER: Find Register Doesn't Do Anything

Kier
Mastermind 7170 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: AM263P4

Tool/software:

Hello,

I'm using CCS12.8.1 with AM263P4 with register patch described here:(+) AM263P4: Peripheral Registers For Debugger - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

Right clicking the Register tab and typing a registers name then double clicking the register does nothing. I think it should expand the tree and move the focus to the click register cluster at the very least. Video attached.

It's very difficult to use in this state.

  • 0
    TI__Guru**** 160620 points

    Kier,

    If you search for registers that were not added by that updated chip support package does it work ok for you?  If I try to search for CAN registers I see exactly what you see but if I search for IRQ or something that was already there prior to the update it works.  I am also seeing some issues with the IDs in the xml files as the AM263Px_LS.xml and the AM263Px.xml use the same device ID of AM263Px.

    I am thinking it is an issue with the xmls but someone will need to dig into them.

    Regards,

    John

  • 0 in reply to JohnS
    Mastermind 7170 points

    Thanks John,

    Yes I see the same results: The problem only affects the added (peripheral) registers.

    I guess the sooner we get the AM263P4 peripheral registers into the the support package, the better. The device is ACTIVE now so it should be in CCS by default.

  • 0 in reply to Kier
    TI__Guru**** 435271 points
    Kier said:
    The problem only affects the added (peripheral) registers.

    Not all of them. For example, Try "MEM_PID". It will properly expand the tree to the location of the register. So far the issue seems specific to the CAN registers.

  • 0 in reply to JohnS
    TI__Guru**** 435271 points
    JohnS said:
    I am also seeing some issues with the IDs in the xml files as the AM263Px_LS.xml and the AM263Px.xml use the same device ID of AM263Px.

    Yes both those files have the same ID causing issues when trying to select the correct device in the target configuration editor.