Linux/PRU-CGT: Beaglebone: RPMsg not working on PRU1

Hi,

This forum supports only the AM335x Processor SDK (www.ti.com/.../PROCESSOR-SDK-AM335X ) released by TI. Debian is a community release, supported on www.beagleboard.org Please direct your question to them.

Thank you for your answer, but debian package is just a wrapper, which installs TI's code generation tools for PRU. If this is not the right forum to ask questions about the CDT, could you please direct me to the more appropriate place to ask question about this product from TI?

ello Jacek,

This PRU issue might be something we can help with - just keep in mind that I won't try to replicate any of your results on my side since you're using a non-TI operating system, and we may get to a point where it looks like a Debian vs SDK issue and you'll need to go somewhere else for more debug assistance.

1) Have you checked that the unmodified examples PRU_RPMsg_Echo_Interrupt0 and PRU_RPMsg_Echo_Interrupt1 work as expected? Based on your version of Linux I'd use the most up-to-date version of the PRU Software Support Package (found at the git repo or under example-applications in Processor Linux SDK). Reference for getting those running is the RPMsg Quick Start Guide.

2) FYI another way to debug in Linux without depending on hardware external to the processor is writing values to a known portion of the PRU's DRAM, for example:

Note that the absolute memory address is different than the memory address from the PRU’s perspective, e.g. TESTA is at 0x4a300100 when you are trying to look at it from the Linux command line on an AM335x. So you would probe the memory location using devmem2 0x4a30100

Nick,

thank you for suggestions. I tried the PRU_RPMsg_Echo_Interrupt* examples with one tiny modification: Whenever an interrupt comes, I xor a bit in R30 to change status of an LED. The rest of the code is left unmodified. To make sure that the signalling works I also xor the bit just before entering the loop. PRU_RPMsg_Echo_Interrupt0 works as expected: it switches state when program starts, and every time a message comes. However on PRU1 (running PRU_RPMsg_Echo_Interrupt1) the debugging LED changes state only when the program starts.
I asked for help on beagleboard list before posting here, but the only suggestion I've got was to check if the interrupts numbers are correct, what I did before resorting to ask on support fora.

Hello Jacek,

I hope everything is working on your end. I am marking this thread resolved.

Regards,
Nick