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

PRU0 vs PRU1

Samuel Lin
Prodigy 30 points
Other Parts Discussed in Thread: OMAP-L138

Hi,

I have PRU code for OMAP-L138. I am trying to write the result back to the DSP L2 RAM (at 0x11820000) by using the Constant Table (c28). I loaded the code to PRU0. It worked fine. I checked the DSP memory location (0x11820000) on the CCS v4. The value is what I expected.

But when I loaded the same code to PRU1, the PRU code did not write to the memory location (0x11820000). Can PRU1 access the DSP L2 RAM?

 

Sam

 

 

 

 

 

  • 0
    TI__Genius 15910 points

    Hi Sam,

    The PRU1 core can access the DSP L2 RAM.  Have you confirmed that the PRU1's Constant Table Programmable Pointer Register 0 is correctly programmed to point to this address?

    Regards,

    Melissa

  • 0 in reply to melissaw
    Prodigy 30 points

    Thank you, Melissa. That’s right. It is working now. I need to change the address in the PRU code for the Control Registers for PRU1.

     

    Sam

  • 0 in reply to Samuel Lin
    Prodigy 30 points

    Hi,

     

    I have another question. I have programmed Timer 0 (T64P0_TINT12_SYS_EVT) to generate interrupt continuously.  Again, it worked on PRU0, but not PRU1. The host number is 0, and channel number is also 0. It seems R31[30] bit is set, but the interrupt vector is not T64P0_TINT12_SYS_EVT (3).

     

    Sam

     

     

  • 0 in reply to Samuel Lin
    TI__Genius 15910 points

    Hi Sam,

    Here are a few suggestions of things you could check:
        1.  Confirm that the Timer 0 is still being configured correctly.
        2.  Timer 0 is always being cleared after you process the interrupt.
        3.  Confirm that CFGCHIP3 is still being set to the correct EVTSEL setting.  If case your code was developed using the Linux-based PRU timer example code, please note that this example uses Timer 2 and sets the CFGCHIP3 for PRUSSEVTSEL = 1.
       
    You could also try to identify which system event is causing Host 0 to be set.    This would help you better understand the system.

    Regards,
    Melissa