• Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 1894 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.

"Cannot find a driver for PRU_0"

Walter Snafu
Genius 3450 points

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

CCS tells me it "Cannot find a driver for PRU_0" and "Cannot find a driver for PRU_1". 

 

(I just upgraded to CCS v5.4.0.00091, and this error is new to me.  So, perhaps these clues are related?) 

 

The CCS error report lists the resource as: LogicPD EVM OMAP-L138 -XDS100v2.ccxml   .  That configuration file uses two gel files:  OMAPL138_ARM.gel and OMAPL138_DSP.gel.  But it doesn't contain anything for the two PRUs. 

 

(I'm trying to work with the ARM on the OMAP-L138.  Yet it's flagging an error with the PRU_x.)

 

How do I solve this?

Thanks for your help.

 

  • Genius 3450 points

    I think I found an answer (?).  In the target configuration file, under "advanced setup", set the checkboxes for "bypass" the PRU_0 and PRU_1.  I suspect that tells the system to ignore the PRU subsystems.  When I did that, CCS stopped complaining, and compiled my project.  I assume that's the solution.

  • in reply to Walter Snafu
    TI__Guru**** 474841 points

    Hi Walter,

    Walter Snafu said:
    I assume that's the solution.

    Sort of... you simply told the debugger to ignore/bypass the PRUs so that the debugger would not need to access the drivers for them. Since you do not need access to the PRUs, it resolves your immediate need. But the overall issue is there.

    When do you get the error? On debugger startup or attempts to connect to the target?

    And are you reusing a ccxml file that you created with the CCS version prior to the update to v5.4? Could you attach your ccxml to this thread?

    Thanks

    ki

  • in reply to Ki
    Genius 3450 points

    Hi Ki-Soo,

    Ki-Soo said:
    When do you get the error? On debugger startup or attempts to connect to the target?

    I got the error prior to debugger startup, and prior to connecting to the target.  That is, I got the error when I attempted to build the project.  CCS reported the error at that time, and failed to successfully complete the build. 

    Yes, I was reusing a ccxml file that I created with the CCS version prior to my update to v5.4.  As you requested, I attached that file to this post. (NOTE: the TI uploader for this forum website would not accept the .ccxml file extension, so I changed it to .txt  .   You will need to change it back again to .ccxml)

    Thanks for your help.

    -- Walter

     

     

  • in reply to Walter Snafu
    TI__Guru**** 474841 points

    Thanks Walter.

    Could you try creating a new configuration from scratch in v5.4? The one you gave me has some issues with it. I suspect they changed some things with the L138 device xml files which broke your old ccxml file.

    Thanks

    ki

  • in reply to Ki
    Intellectual 320 points

    Hello Ki-Soo Lee:

    Creating a new configuration solves this problem. This is done by using View, Target Configurations. On the Target Configurations tab, select the project, right-click, New Target Configuration.

    Nice to see that the PRU's have come out of the closet!

    Timothy Frank