• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 172 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.

DRA821U: Reading registers with u-boot code

Luke
Expert 3740 points
Part Number: DRA821U
Other Parts Discussed in Thread: DRA821

Tool/software:

Hi team,

My customer is trying to read the DRA821 registers and has written some code in u-boot to do so. Currently, when the code is ran, it causes u-boot to panic.

Right now, CTRLMMR_WKUP_RESET_SRC_STAT 0x43000050 is giving them issues. They also have all the ADC and temp sensor registers as well as a few others but I'd assume once they figure one out, all the others will follow.

Is there any sample code (or app notes, etc.) that they could reference to assist them in reading the registers?

Thanks for the support,

Luke

  • 0
    TI__Genius 17185 points

    Hi Luke,

    Is this the only register giving them issues?

    Do you know if they are unlocking the registers?

    I am specifically referring to the CTRLMMR_WKUP_LOCKx_KICKx registers that can be found within the TRM

    Best,
    Jared

  • 0 in reply to Jared McArthur
    TI__Expert 3740 points

    Hi Jared, 

    They are just getting started again with the register access so this is the only one they have specifically called out. They had done some reading of registers a few weeks ago and didn't seem to have the same issue but I am still waiting to hear back. 

    They are looking into unlocking the registers now and will let me know if they are still having issues. 

    Thanks,

    Luke

  • 0 in reply to Luke
    TI__Expert 3740 points

    Jared,

    After looking at the TRM at the CTRLMMR_WKUP_LOCKx_KICKx resgisters, it sounds like they only control writing to the registers and not reading. Are you saying they also control reading? This is the issue they are currently running into.

    Best,

    Luke

  • +1 in reply to Luke
    TI__Genius 17185 points

    Hi Luke,

    They shouldn't have an issue reading the register. They're probably touching the following register as well which is causing the kernel panic.

    If they use the following command, they shouldn't have any issues:

    => md.l 0x43000050 1

    Here is the output when I tried it:

    => md.l 0x43000050 1   
43000050: 00000000                             ....

    Best,
    Jared