• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 542 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM3358: PRU Labs questions

Mike Colasono
Prodigy 20 points
Part Number: AM3358

Hi:

Until II get a JTAG adapter that works with a free CCS instead one of the (per TI ) "more professional ones" (so now JTAG becomes a proprietary thing and TI's emulator isn't very professional?)  I'm using Eclipse to drag files to the target and building projects there using a makefile I got from some joe's blog. Now I'm reading 5 of lots of articles on which one to buy before I get the wrong one.

I gotta say it's bad when the manufacturer's instructions fail and 1 out of 100 google returns (i.e., returns actually clicked on) to some basement blog does work.

This is a pretty good platform for some of the automation efforts I'm making here.

Here are my questions and problems. Note that some of them appear to be statements. That means there is an implied question (or ten) and there isn't enough info for me to know what to ask, or something close to that.

1. I'm using a relatively recent ti-rtos linux; but I've seen some blogs on PRU that suggest using Angstrom

      What should I use and does it matter - no debian if possible, please?

       Seems there's a bit of talk about which build of what supports or doesn't support PRUSS_UIO (or whatever) vs. rpmsg.

2. LAB 1 works using my makefile and a bash script to deploy the build(s) to /lib/firmware, run, stop, etc.

  -- no question implied 8)

3. I use config-pin commands to set the pruins and pruouts.

 -- no question implied 8)

4. There's no way to use config-pin for PRU interrupts (Lab 2) but it seems it 's something that has to be done in a .dts.

-- any practical info appreciated

5. i can't find a doc that really teaches writing overlay source files.

6. I need these guys to talk to each other, read I/O pins, use shared memory, and communicate with the host OS

7. I don't have a clue why (per PRU lab wiki) I need a PRU CAPE  -- that would be so wrong.

8. PRU Lab 2 compiles using the hacks I mention above. Nothing happens though. One PRU bind  command might result in "No such Device" while the other does nothing. Typically in a forum, by now, someone would ask me to post project files, code, etc., but  then the answer is that I didn't follow all of the instruction -- because they didn't work - sorry. Facts.

Thanks in advance for helping me sort this out and thanks for hanging here long enough to be thanked 8)

Mike

  • 0
    TI__Guru**** 393215 points
    The PRU experts have been notified. They will respond here.
  • 0
    TI__Intellectual 1610 points

    See some answer below in red:

    Until II get a JTAG adapter that works with a free CCS instead one of the (per TI ) "more professional ones" (so now JTAG becomes a proprietary thing and TI's emulator isn't very professional?)  

    I’m not sure what you mean by this.  There are numerous JTAG emulators that work with CCS, with varying options as to features and performance.  CCSv7 supports all features and is free.

    I'm using Eclipse to drag files to the target and building projects there using a makefile I got from some joe's blog.  

    The labs are based on the TI compiler and make file, which should also work for your projects.

    1. I'm using a relatively recent ti-rtos linux; but I've seen some blogs on PRU that suggest using Angstrom

          What should I use and does it matter - no debian if possible, please?

          Seems there's a bit of talk about which build of what supports or doesn't support PRUSS_UIO (or whatever) vs. rpmsg.

    I’ll have to check into this more, but there are several solutions that work.   

    4. There's no way to use config-pin for PRU interrupts (Lab 2) but it seems it's something that has to be done in a .dts. -- any practical info appreciated

    Lab 2 is just configuring the interrupts in the PRU via code, which is required for the PRU core.   But if you are running the host application under Linux to communicate with the PRU, it also has to know the pin config.   This is done through the .dts file—see lab 4.

    5. i can't find a doc that really teaches writing overlay source files.

    I’m not sure what you mean by overlay source files, but have you looked through the material on the Wiki site?  http://processors.wiki.ti.com/index.php/PRU-ICSS.  This is the best source of documentation on this processor core that I’m aware of.  There is some additional training material at  https://training.ti.com/PRU-training-series

    6. I need these guys to talk to each other, read I/O pins, use shared memory, and communicate with the host OS

    See links in answer above.

    7. I don't have a clue why (per PRU lab wiki) I need a PRU CAPE  -- that would be so wrong.

    This is just a convenient way to exercise the PRU--it includes LEDs and push buttons for GPIO, audio, and a temp sensor.  You are free to add your own external circuitry.

    8. PRU Lab 2 compiles using the hacks I mention above. Nothing happens though. One PRU bind  command might result in "No such Device" while the other does nothing. Typically in a forum, by now, someone would ask me to post project files, code, etc., but  then the answer is that I didn't follow all of the instruction -- because they didn't work - sorry. Facts.

    I’m not sure why this is not working for you.  I will look into this further.