Yes ,the answer is there - 4.2 Em dom., 17 de jan. de 2021 às 01:55, Pedro Henrique Fonseca Bertoleti < phfbertol...@gmail.com> escreveu:
> Sorry, I couldn't find any information on this error 22 on PRU cook book. > Please, anyone can help me on handling this error? > > Em dom, 17 de jan de 2021 01:46, Vinicius Juvinski < > vinicius.juvin...@gmail.com> escreveu: > >> Hi Pedro, >> >> >> You are having error 22 - I don’t remember right now the cause , the >> prucookbook has the explanation and how to fix :) >> >> Em dom., 17 de jan. de 2021 às 00:59, phfbertoleti < >> phfbertol...@gmail.com> escreveu: >> >>> Hi vinicius. >>> >>> First of all, thanks for the reply and for indicating me PRU cook book. >>> Regarding dmesg messages, yes, I've checked them (as shown below). It >>> seems PRUs are available for use, am I right? >>> What do you recommend as a hello world test for PRU? >>> >>> --------------------- >>> [ 11.169923] remoteproc remoteproc0: 4a334000.pru is available >>> [ 11.171927] remoteproc remoteproc1: 4a338000.pru is available >>> [ 60.948771] remoteproc remoteproc2: wkup_m3 is available >>> [ 60.956133] remoteproc remoteproc2: powering up wkup_m3 >>> [ 60.956160] remoteproc remoteproc2: Booting fw image >>> am335x-pm-firmware.elf, size 217168 >>> [ 60.956412] remoteproc remoteproc2: remote processor wkup_m3 is now up >>> [ 454.023370] remoteproc remoteproc1: powering up 4a338000.pru >>> [ 454.027965] remoteproc remoteproc1: loading >>> /lib/firmware/am335x-pru1-fw failed with error -22 >>> [ 454.027986] remoteproc remoteproc1: Direct firmware load for >>> am335x-pru1-fw failed with error -22 >>> [ 454.028006] remoteproc remoteproc1: request_firmware failed: -22 >>> [ 454.043116] remoteproc remoteproc1: Boot failed: -22 >>> --------------------- >>> >>> >>> Best Regards, >>> Pedro Bertoleti >>> >>> Em sábado, 16 de janeiro de 2021 às 23:05:07 UTC-4, >>> vinicius...@gmail.com escreveu: >>> >>>> Hi Pedro, >>>> >>>> I recommend you take a look at >>>> https://markayoder.github.io/PRUCookbook/ >>>> >>>> Have you checked the dmesg to see what is happening at kernel level ? >>>> >>>> Em sáb., 16 de jan. de 2021 às 23:25, phfbertoleti <phfber...@gmail.com> >>>> escreveu: >>>> >>>>> Hi everyone. >>>>> >>>>> My name is Pedro and I'm from Brazil. I'm trying to learn how to use >>>>> PRUs in BeagleBone (I'm using BeagleBone Green Wireless now) and I'm >>>>> facing >>>>> a problem I cannot solve. >>>>> >>>>> I'm reading Derek Molloy's book (Exploring BeagleBone) and one of the >>>>> first examples / "hello world"-like is checking which firmware is loaded >>>>> in >>>>> PRU0 and start it. However, when I try to do this, I get "write error: >>>>> Invalid argument" as error output: >>>>> >>>>> debian@beaglebone:/sys/class/remoteproc/remoteproc1$ cat firmware >>>>> am335x-pru1-fw >>>>> debian@beaglebone:/sys/class/remoteproc/remoteproc1$ echo 'start' > >>>>> state >>>>> -bash: echo: write error: Invalid argument >>>>> >>>>> What am I doing wrong? I would like to see "running" at state value, >>>>> in order to be sure PRU0 is working. >>>>> >>>>> Here follows some useful information: >>>>> >>>>> Kernel version: 4.19.94-ti-r42 >>>>> Dmesg output related to remoteproc: >>>>> >>>>> --------------------- >>>>> [ 11.169923] remoteproc remoteproc0: 4a334000.pru is available >>>>> [ 11.171927] remoteproc remoteproc1: 4a338000.pru is available >>>>> [ 60.948771] remoteproc remoteproc2: wkup_m3 is available >>>>> [ 60.956133] remoteproc remoteproc2: powering up wkup_m3 >>>>> [ 60.956160] remoteproc remoteproc2: Booting fw image >>>>> am335x-pm-firmware.elf, size 217168 >>>>> [ 60.956412] remoteproc remoteproc2: remote processor wkup_m3 is now >>>>> up >>>>> [ 454.023370] remoteproc remoteproc1: powering up 4a338000.pru >>>>> [ 454.027965] remoteproc remoteproc1: loading >>>>> /lib/firmware/am335x-pru1-fw failed with error -22 >>>>> [ 454.027986] remoteproc remoteproc1: Direct firmware load for >>>>> am335x-pru1-fw failed with error -22 >>>>> [ 454.028006] remoteproc remoteproc1: request_firmware failed: -22 >>>>> [ 454.043116] remoteproc remoteproc1: Boot failed: -22 >>>>> --------------------- >>>>> >>>>> Thanks in advance. >>>>> >>>>> Best Regards, >>>>> Pedro Bertoleti >>>>> >>>>> -- >>>>> For more options, visit http://beagleboard.org/discuss >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "BeagleBoard" group. >>>>> >>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to beagleboard...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/beagleboard/7c2be7bd-63f3-4798-85dd-e5be63d86831n%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/beagleboard/7c2be7bd-63f3-4798-85dd-e5be63d86831n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/8e94c2a0-287a-4c6c-8342-87a7f6a9fcabn%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/8e94c2a0-287a-4c6c-8342-87a7f6a9fcabn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/CAB6xwCr3DMGwQD0%2Be5dxHMZJHy6roXgRDHYAvYpJJuqTPw175w%40mail.gmail.com >> <https://groups.google.com/d/msgid/beagleboard/CAB6xwCr3DMGwQD0%2Be5dxHMZJHy6roXgRDHYAvYpJJuqTPw175w%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CAJK9pqdUcG%2Bi9zZBzqU5VFQDJM2R5Hu0WYwFc2jwT4q7M8nnkg%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CAJK9pqdUcG%2Bi9zZBzqU5VFQDJM2R5Hu0WYwFc2jwT4q7M8nnkg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAB6xwCqFvpRVanfBe4w-1y3vomgrb1Jax%2BzPBfJ%2BNrXsir4vgQ%40mail.gmail.com.
