not blinking Internal LED in BeagleBone AI

Farzad · April 10, 2020, 4:49pm

hi. I use the Debian 9.12 2020-04-06 on BeagleBone AI.
for the first boot, I go to /var/lib/cloud9/BeagleBone/AI/pru directory and run

`
root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# source setup.sh
TARGET=blinkInternalLED.pru1_1

`
and run make command

`
root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# make
/var/lib/cloud9/common/Makefile:28: MODEL=TI_AM335x_BeagleBone_Black,TARGET=blin kInternalLED.pru1_1,COMMON=/var/lib/cloud9/common
/var/lib/cloud9/common/Makefile:147: GEN_DIR=/tmp/cloud9-examples,CHIP=am57xx,PR OC=pru,PRUN=1_1,PRU_DIR=/sys/class/remoteproc/remoteproc1,EXE=.out
/var/lib/cloud9/common/Makefile:150: warning: overriding recipe for target ‘all’
Makefile:4: warning: ignoring old recipe for target ‘all’
Makefile:9: warning: overriding recipe for target ‘clean’
/var/lib/cloud9/common/Makefile:225: warning: ignoring old recipe for target ‘cl ean’

Stopping PRU 1_1
CC blinkInternalLED.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
“blinkInternalLED.pru1_1.c”, line 36: warning #112-D: statement is unreachable
LD /tmp/cloud9-examples/blinkInternalLED.pru1_1.o
copying firmware file /tmp/cloud9-examples/blinkInternalLED.pru1_1.out t o /lib/firmware/am57xx-pru1_1-fw
write_init_pins.sh
writing “none” to “/sys/class/leds/beaglebone:green:usr1/trigger”
writing “none” to “/sys/class/leds/beaglebone:green:usr2/trigger”
Starting PRU 1_1
CC bitflip.arm.c
LD /tmp/cloud9-examples/bitflip.arm.o
CP /tmp/cloud9-examples/bitflip.arm.out
CC bitflip.pru1_1.c
LD /tmp/cloud9-examples/bitflip.pru1_1.o
CP /tmp/cloud9-examples/bitflip.pru1_1.out
CC bitflip.pru2_1.c
LD /tmp/cloud9-examples/bitflip.pru2_1.o
CP /tmp/cloud9-examples/bitflip.pru2_1.out
CC blinkExternalLED.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
“blinkExternalLED.pru1_1.c”, line 32: warning #112-D: statement is unreachable
LD /tmp/cloud9-examples/blinkExternalLED.pru1_1.o
CP /tmp/cloud9-examples/blinkExternalLED.pru1_1.out
CP /tmp/cloud9-examples/blinkInternalLED.pru1_1.out
CC blinkR30.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
“blinkR30.pru1_1.c”, line 29: warning #112-D: statement is unreachable
LD /tmp/cloud9-examples/blinkR30.pru1_1.o
CP /tmp/cloud9-examples/blinkR30.pru1_1.out
CC inputR31.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
“inputR31.pru1_1.c”, line 29: warning #112-D: statement is unreachable
LD /tmp/cloud9-examples/inputR31.pru1_1.o
CP /tmp/cloud9-examples/inputR31.pru1_1.out
CC neopixelDynamic.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
LD /tmp/cloud9-examples/neopixelDynamic.pru1_1.o
CP /tmp/cloud9-examples/neopixelDynamic.pru1_1.out
CC neopixelRpmsg.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
LD /tmp/cloud9-examples/neopixelRpmsg.pru1_1.o
CP /tmp/cloud9-examples/neopixelRpmsg.pru1_1.out
CC neopixelStatic.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
LD /tmp/cloud9-examples/neopixelStatic.pru1_1.o
CP /tmp/cloud9-examples/neopixelStatic.pru1_1.out
MODEL = TI_AM335x_BeagleBone_Black
PROC = pru
PRUN = 1_1
PRU_DIR = /sys/class/remoteproc/remoteproc1
rm /tmp/cloud9-examples/neopixelDynamic.pru1_1.o /tmp/cloud9-examples/neopixelDynamic.pru1_1.out /tmp/cloud9-examples/blinkInternalLED.pru1_1.o /tmp/cloud9-examples/inputR31.pru1_1.o /tmp/cloud9-examples/bitflip.pru1_1.o /tmp/cloud9-examples/bitflip.arm.o /tmp/cloud9-examples/neopixelStatic.pru1_1.o /tmp/cloud9-examples/neopixelRpmsg.pru1_1.o /tmp/cloud9-examples/blinkR30.pru1_1.o /tmp/cloud9-examples/blinkExternalLED.pru1_1.o /tmp/cloud9-examples/bitflip.pru2_1.o /tmp/cloud9-examples/inputR31.pru1_1.out /tmp/cloud9-examples/bitflip.pru1_1.out /tmp/cloud9-examples/bitflip.arm.out /tmp/cloud9-examples/neopixelStatic.pru1_1.out /tmp/cloud9-examples/neopixelRpmsg.pru1_1.out /tmp/cloud9-examples/blinkR30.pru1_1.out /tmp/cloud9-examples/blinkExternalLED.pru1_1.out /tmp/cloud9-examples/bitflip.pru2_1.out
…
`

every things is fine and start blinking Internal LED.also /sys/class/remotproc/remotproc1/state is “running” and
/sys/class/remotproc/remotproc1/firmware is “am57xx-pru1_1-fw”

but

after reboot and run previous commands to make blinkInternalLED.pru1_1.c ,make is complete but internalLED not blinking and
/sys/class/remotproc/remotproc1/state is “suspended” also /sys/class/remotproc/remotproc1/firmware is "dra7-ipu1-fw.xem4" :|

root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# make
/var/lib/cloud9/common/Makefile:28: MODEL=BeagleBoard.org_BeagleBone_AI,TARGET=blinkInternalLED.pru1_1,COMMON=/var/lib/cloud9/common
/var/lib/cloud9/common/Makefile:147: GEN_DIR=/tmp/cloud9-examples,CHIP=am57xx,PROC=pru,PRUN=1_1,PRU_DIR=/sys/class/remoteproc/remoteproc1,EXE=.out
/var/lib/cloud9/common/Makefile:150: warning: overriding recipe for target ‘all’
Makefile:4: warning: ignoring old recipe for target ‘all’
Makefile:9: warning: overriding recipe for target ‘clean’
/var/lib/cloud9/common/Makefile:225: warning: ignoring old recipe for target ‘clean’

Stopping PRU 1_1
CC blinkInternalLED.pru1_1.c
“/var/lib/cloud9/common/prugpio.h”, line 4: warning #1181-D: #warning directive: “Found AI”
“blinkInternalLED.pru1_1.c”, line 36: warning #112-D: statement is unreachable
LD /tmp/cloud9-examples/blinkInternalLED.pru1_1.o
copying firmware file /tmp/cloud9-examples/blinkInternalLED.pru1_1.out to /lib/firmware/am57xx-pru1_1-fw
write_init_pins.sh
writing “none” to “/sys/class/leds/beaglebone:green:usr1/trigger”
writing “none” to “/sys/class/leds/beaglebone:green:usr2/trigger”
Starting PRU 1_1
CP /tmp/cloud9-examples/blinkInternalLED.pru1_1.out
MODEL = BeagleBoard.org_BeagleBone_AI
PROC = pru
PRUN = 1_1
PRU_DIR = /sys/class/remoteproc/remoteproc1
rm /tmp/cloud9-examples/blinkInternalLED.pru1_1.o
root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# cat /sys/class/remoteproc/remoteproc0/state
suspended
root@beaglebone:/var/lib/cloud9/BeagleBone/AI/pru# cat /sys/class/remoteproc/remoteproc0/firmware
dra7-ipu1-fw.xem4

Why is this happening? However, this is not the case for BeagleBone Black with the same image??

Thanks for any suggestions,
Best regards,
Farzad

RobertCNelson · April 10, 2020, 4:58pm

On the am57xx family there are many more "remoteproc" devices, the
script used "remoteproc1" but you referenced "remoteproc0".. We are
working on symlinks to fix this confusion, but it hasn't shipped yet.

https://elinux.org/Beagleboard:BeagleBone_cape_interface_spec#PRU

Regards,

Farzad · April 11, 2020, 6:42am

It was my mistake.but remotproce1 also gives the same error. In fact, all remotproce 0-3 state is suspended with and 4-7 state is offline.

`
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc5/state
offline
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc0/state
suspended
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc0/firmware
dra7-ipu1-fw.xem4
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc1/state
suspended
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc1/firmware
dra7-ipu2-fw.xem4
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc2/state
suspended
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc2/firmware
dra7-dsp1-fw.xe66
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc3/state
suspended
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc3/firmware
dra7-dsp2-fw.xe66
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc4/state
offline
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc4/firmware
am57xx-pru1_0-fw
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc5/state
offline
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc5/firmware
am57xx-pru1_1-fw
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc6/state
offline
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc6/firmware
am57xx-pru2_0-fw
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc7/state
offline
debian@beaglebone:~$ cat /sys/class/remoteproc/remoteproc7/firmware
am57xx-pru2_1-fw

`

Why remotproce0-3/firmware have changed by remotproce4-7/firmware that are in the first boot??

Best regards,

Farzad