Linux/PROCESSOR-SDK-AM335X: PRU hands-on labs

Hi Biser,

Thanks for the reply.

I already told that i am following PRU_Training Hands_on_lab that you provided in above link.

I also built first project with CCS. But i am not using XDS emulator for debugging. I copied the generated .out file to rootf/boot/lib/firmware of file system.

Then i booted my Beaglebone, but my LED is not toggling. 

Should i have to change pinmux configuration?

Hi Biser,

I apologise i did not provided the full information, I thought that register R30 that has been configured as output in the first project of PRU Hands on lab is 31st pin on P9 Header on Beaglebone, so i connected my external LED on that pin. But that didn't glow. 

If i am not doing any mistake then definitely i am unable to correlate the pinmuxing. Can you suggest me the correct way to select the external pins in program?

Ok,

I got that.

Just one last thing. I am using the project 1 of PRU hands on lab "Toggle LED with PRU GPO". There register R30 is getting used as direct output and i am suspecting that as 31st pin of P9 Header of beaglebone. Is anything else i should take care of? What i am missing?

Please just provide me the command line steps for toggling that particular pin "P9_31" in beaglebone as PRU.

I just want some confident in working with PRUs without using CCS.

It would be great help for me.

Thanks.

Hi Jason,
Thanks.
I appreciate your clarification. My steps are-
1) Done with steps followed in modification of device tree that you suggested.
2) Copied the .out file that i built in project 1 "Led Toggling" in lib/firmware folder of file system.
3) Created symbolic link as per the steps followed up to "sync" step.
4) Putted the SD card back to Beaglebone. I think Led should start toggling.

Please suggest if i am doing something wrong.

Rahul,

Did you follow all of the steps for lab 4? You need to rebuild the firmware to include the resource_table header file that is required by the Linux driver: processors.wiki.ti.com/.../PRU_Training:_Hands-on_Labs

If you take the .out file from lab 1 then you will get a load failure when the RemoteProc Linux driver cannot find the resource table.

Jason

yes, i followed full lab 4. i built the firmware including with resource_table also. And when i booted the beaglebone i found RemoteProc driver is online. No error. I just want to know whether my steps are wrong or not once it is confirmed then i will try once again.

It sounds like you did everything right. You connected your LEDs to the same pins that the cape uses correct?

Can you post your full boot log here as an attachment?

Jason Reeder

Hi, pfa.

I connected my led with 31st pin of P9 Header of Beaglebone.

I don't see anything wrong in your boot log. Also, pin P9-31 is connected to PRU R30[0] which on the PRU cape is connected to a Blue LED. So, that part looks right as well.

Are you certain you've replaced the dtb that the board is using with the one that you rebuilt that includes the pru cape dtsi file? And are you certain that you've rebuilt the PRU firmware from lab 1 to include the resource_table header file and then replaced that in the device's filesystem as well. If so, you may want to check your circuit because those two changes will will load a PRU firmware that toggles pins P9-28, P9-29, P9-30, and P9-31.

Can you post the output of the following commands:
ls -la /lib/firmware/
ls -la /lib/firmware/pru/
ls -la /boot/

Jason Reeder

ls -la /lib/firmware/
total 400
drwxr-xr-x 6 root root 4096 Apr 19 00:39 .
drwxr-xr-x 9 root root 4096 Mar 30 02:54 ..
-rw-r--r-- 1 root root 73 Mar 30 02:32 am335x-bone-scale-data.bin
-rw-r--r-- 1 root root 17 Mar 30 02:32 am335x-evm-scale-data.bin
-rw-r--r-- 1 root root 217280 Mar 30 02:32 am335x-pm-firmware.elf
lrwxrwxrwx 1 root root 13 Apr 19 00:39 am335x-pru0-fw -> led_toggl.out
-rw-r--r-- 1 root root 41 Mar 30 02:32 am43x-evm-scale-data.bin
-rw-r--r-- 1 root root 34828 Apr 18 15:11 led_toggl.out
drwxr-xr-x 2 root root 4096 Mar 30 05:19 pru
-rw-r--r-- 1 root root 27904 Apr 18 17:58 PRU_Halt.out
-rw-r--r-- 1 root root 74876 Apr 18 17:51 PRU_RPMsg_Echo_Interrupt1.out
drwxr-xr-x 2 root root 4096 Mar 30 05:20 ti-connectivity
drwxr-xr-x 2 root root 4096 Apr 18 15:53 tigon
drwxr-xr-x 2 root root 4096 Mar 30 02:48 ti-pruss


ls -la /lib/firmware/pru/
total 196
drwxr-xr-x 2 root root 4096 Mar 30 05:19 .
drwxr-xr-x 6 root root 4096 Apr 19 00:39 ..
-rw-r--r-- 1 root root 28320 Mar 30 02:57 PRU_Halt.out
-rw-r--r-- 1 root root 75724 Mar 30 02:57 PRU_RPMsg_Echo_Interrupt0.out
-rw-r--r-- 1 root root 75724 Mar 30 02:57 PRU_RPMsg_Echo_Interrupt1.out


ls -la /boot/
total 3436
drwxr-xr-x 2 root root 4096 Apr 19 00:41 .
drwxr-xr-x 22 root root 4096 Apr 18 18:03 ..
lrwxrwxrwx 1 root root 28 Apr 19 00:41 am335x-boneblack.dtb -> am335x-boneblack-prucape.dtb
-rw-r--r-- 1 root root 37660 Apr 19 00:40 am335x-boneblack-prucape.dtb
-rwxr-xr-x 1 root root 3463400 Apr 18 15:51 zImage

And I will check the connection again. Also will rebuild the project again with all considerations.

Hi Jason,
I completed lab 5 and lab 6. I can now access PRU with Remotproc driver communication. I must did some mistake in lab 4. I will do that again. Thanks for your support.

Hi,
Are there lab examples for PWM generation and UART communication also?