[quote user="Mussab Zubair1"]1. It is said that for next SDK based on kernel 3.14 LTS, the beaglebone community code and TI code will be pretty much aligned for PRU. I want to know in which direction either in UIO driver side or RemoteProc driver side, PRU software will be aligned ?[/quote]We are going the remoteproc/rpmsg route. I believe the plan is to eventually phase out the uio driver completely, but to my knowledge that process has not yet begun in earnest.
[quote user="Mussab Zubair1"]2. After installing PRU package released on 30 june 2014 for TI SDK7, I find out that in Documentation "PRU-Package-v1.0-Manifest" pruss_rpmsg software name is also listed but in /drivers/rpmsg no such file or driver available and also no such patch available is in PRU-Swpkg that create pruss_rpmsg driver . Is it error in documentation or some files are missing in a PRU package?[/quote]This was supposed to be in there, but it missed the original deadline as it needs some additional work. This is on the roadmap, but I don't have an immediate ETA for the driver as of today.
[quote user="Mussab Zubair1"]3. In one of my project, I tried to get SPI0 interrupt in PRU. I followed the example PRU_PRUtoARM_Interrupt. SPI peripheral Interrupt Status Register indicate event is generated, but I could not get in PRU. I use Interrupt Number 44 for McSPI0 as referenced in AM335x-PRU-Reference guide and map channel 1 to host channel 1. Is Interrupt number 44 is correct? Any solution? I tested GPIO0 Interrupt number 57, PRU get interrupt successfully in this case. (baremetal project on BBB)[/quote]Event 44 looks correct to me. Which steps did you take to program this? By my count you should have something like...
HIEISR |= 1 << 1; //Enable host 1
HMR0 |= 1 << 8; // Ch1 -> host 1
CMR11 |= 1 << 0; // Evt44 -> Ch1
SICR = 44; // Clear evt44
EISR = 44; // Enable evt44
GER = 1; // Enable global interrupts
At this point you'd monitor R31[31] for the bit to go high signalling the interrupt. It sounds like you've figured this stuff out for the GPIO interrupt, but I'd like to make sure you've got something comparable to the above.
[quote user="Mussab Zubair1"]4. It is written on TI wiki that I should change PRU.out file to rproc_pru0_fw so that pruss_remoteproc driver load the PRU program, but this syntax does not load the program and give error message. If I try rproc-pru0-fw, it seems to work. [/quote]Thanks for pointing this out. We actually found this mistake yesterday and corrected the Wiki. It's suppose to use hyphens rather than underscores.
[quote user="Mussab Zubair1"]5. With Remoteproc, the examples provided does not work out of the box e.g PRU_gpioToggle example when try to load out the box gives following messages [ ... ][/quote]Error -12 looks like the system ran out of memory (ENOMEM), and -17 is showing that the resources are already used. I'd remove the interrupt assignment from the second resource table header (for PRU1) and assign all ten as HOST_UNUSED. This will be corrected in the next release of the SWPKG.
[quote user="Mussab Zubair1"]6. For my application, I need to have user interaction between ARM and PRU to handle events and read/write data on memory e.g DDR. Any user space program will be helpful to understand to how events are handled and messages are communicated using remoteproc/rpmesg driver from userspace. [/quote]This is something we are hoping to have completed soon, but it's not 100% done today. I don't have any great suggestions for the short-term, but you could cobble something together using some of the uio features if necessary. That's probably the easiest/quickest stop-gap solution for now.
↧
Forum Post: RE: Questions about PRU (Swpkg) and TI SDK7 AM335x
↧