Bruce What do " The Others" say is wrong? I have seen that PRU support package. In my reply last week it appears to me you have adopted what I call the apple 🍎 and oranges approach. I'm trying to say serious but I think "the other's" were a mysterious cult on star trek. These instructions look like they were cut out of something. It's helpful to display a copy paste from your terminal window in Linux showing your prompt and maybe a directory list at end of / dev/. This procedure looks similar to what's in the sdk instructions but I'm guessing your not following that. It's possible your instructions are missing something. Let us know if " The other's" communicate back. Mark
Sent from Yahoo Mail on Android On Tue, May 25, 2021 at 11:47 AM, Bruce Chidester<[email protected]> wrote: I have a new image with 10.9 installed with an apt update; apt upgrade I wonder if my issue is around /dev/rpmsg_pru* Others suggest that after the following steps, the device shows up, but mine does not. cd /tmp git clone git://git.ti.com/pru-software-support-package/pru-software-support-package.gitcd /tmp/pru-software-support-package/examples/am335x/PRU_RPMsg_Echo_Interrupt0 export PRU_CGT=/usr/share/ti/cgt-prumake cp gen/PRU_RPMsg_Echo_Interrupt0.out /lib/firmware/am335x-pru0-fw echo start > /sys/class/remoteproc/remoteproc1/state I do not get the message: rpmsg_pru virtio0.rpmsg-pru.-1.30: new rpmsg_pru device: /dev/rpmsg_pru30 and the device does not show in /dev/ What is the secret to making those devices show up? On Tuesday, May 25, 2021 at 11:25:28 AM UTC-5 Bruce Chidester wrote: Dennis, I have made a flasher and have flashed 10.9 image that you referred to me earlier. Re-adding everything on the system now and re-testing. Also processing the requests from Lazarman about the lab and quick start guide. Really appreciate the help On Tuesday, May 25, 2021 at 11:20:45 AM UTC-5 Dennis Bieber wrote: On Tue, 25 May 2021 07:40:20 -0700 (PDT), in gmane.comp.hardware.beagleboard.user Bruce Chidester <[email protected]> wrote: >*It is asking you to confirm which Beagle you are using.:* >I am using Beaglebone Black Revision C > > >*It will be much quicker to do an apt update/aptupgrade.:* >I performed the update/upgrade and /etc/dogtag still reports the same info. >Should I get a newer image? Is the issue my distro? > I don't think the "dogtag" gets updated from repositories. It likely just identifies the original image burned to the memory. debian@beaglebone:~$ uname -a Linux beaglebone 4.19.94-ti-r48 #1buster SMP PREEMPT Wed Aug 19 17:38:55 UTC 2020 armv7l GNU/Linux debian@beaglebone:~$ cat /etc/dogtag BeagleBoard.org Debian Buster IoT Image 2020-08-19 debian@beaglebone:~$ I've been doing apt update/apt upgrade at least monthly since writing that image. -- Dennis L Bieber -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e55624c8-a8b1-4306-903c-5236174b53c1n%40googlegroups.com. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/67658706.2474576.1621964339723%40mail.yahoo.com.
