<Guest789>
I'm going through the getting started docs and have seen several references to things in /opt/scripts - grow_partition, update_kernel, show_pins, etc
<set_>
Right.
<set_>
Okay.
<set_>
What image are you using?
<set_>
cat /etc/dogtag
buckket has quit [Quit: buckket]
<set_>
If you are using an updated image, I think those items have been moved and are not referenced for the BBAI-64.
<set_>
Fro instance, BBAI is not the BBAI-64.
<set_>
WHen you reboot, the total amount of space will be allocated from your SD Card.
<set_>
For instance, I rebooted the board after updating/upgrading it. The full capacity of the SD Card was intact.
<set_>
Okay.
<set_>
I had a 128GB SD Card. It inflated after the reboot.
<set_>
Do I need space. NO. Was it worth it, yes.
buckket has joined #beagle
<set_>
Guest789: What command from what link are you trying to use?
<set_>
I am sure people will catch up w/ updating to some good wiki info.
<Guest789>
In general, I'm just trying to learn how to use the PRUs on the BBAI-64. Going through the PRU Cookbook and it mentioned the show_pins script for debugging. I've found the source, so I can install it manually, just wasn't sure if there was something wrong with my kernel since the scripts dir isn't there.
<set_>
Oh!
<set_>
Right.
<set_>
I think people are working now on that idea.
<set_>
I saw a guy online at the forums. he stated that he will fix the compiler issues but does not know where to link them.
<Guest789>
Yeah there seem to be quite a few filename changes that aren't really documented. Have to keep symlinking missing files and guessing at their new locations, e.g. it seems /dev/remoteproc/pruss1-core1/ is now at /dev/remoteproc/j7-pru1_1/
<Guest789>
But then the common Makefile then thinks the PRU firmware should be at /lib/firmware/j7-pru1_1-fw, but it seems to actually be at /lib/firmware/am57xx-pru1_1-fw
<set_>
Hmm.
<set_>
Are you using the updated version two of the PRU Cookbook?
<set_>
Guest789: Sorry. My board does not boot right now. I make errors...
<set_>
Anyway, some stuff I have learned may, slightly may, be useful.
<set_>
It may be worth a shot. I know sometimes older things are just that...older things. People just pass it and forget it at times.
<set_>
But...if you use an older model image, maybe using the PRU Cookbook versioning one or whatever it is called that you linked may find warmth?
<set_>
Fruition...whatever.
<set_>
Odd words. I know but I cannot be of anymore assistance for now.
<set_>
I am sorry.
<Guest789>
Thank you!
<set_>
!
otisolsen70 has quit [Quit: Leaving]
<Guest789>
Unfortunately it seems that version of the cookbook also needs updating. Trying to run the LED blinking code still throws errors in dmesg: "PRU memory copy failed for da 0x100 memsz 0x36". Looks like trying an older image is best for now.
<set_>
Hmm.
<set_>
Dang it.
<set_>
Right...that is what I was discussing earlier.
<set_>
Something about linking. Try to go to 192.168.7.2:3000 w/ VS Code or install it w/ sudo apt install beagle-code-server?
<set_>
There is a layer that is being pushed from the beagleboard.org people. It has to do w/, I do news now, adding support for various Capes and things w/ those technologies.
<set_>
PWM/UART/ADC and etc...
<set_>
Let me see what is on mine.
zjason`` has quit [Ping timeout: 252 seconds]
<set_>
Hmm.
<set_>
I have only uart and PWM now.
<set_>
I think there was others that were available at some point...
<Guest789>
Yeah I've done update/upgrade and kernel update
<set_>
Okay. Try, if on Windows, 192.168.7.2:3000
<set_>
If not and if you are using Ubuntu or Debian...try 192.168.6.1:3000 I think.
<set_>
Like I say, my host or target got busted the other day.
<set_>
So, I cannot use Linux w/ my BBB series SBCs for whatever reason...
<set_>
And now, clone w/ git the new ideas for the beta version. I think...but dang it. Others are working on the beta stuff (I think).
<set_>
See. I am no help now.
<set_>
I will clone it and test it. Who knows?
<Guest789>
Darn - yeah I've pulled the latest of that examples dir that shows up in VSCode, but it only has example code for the Black board.
<set_>
Oh!
<set_>
Yep.
<Guest789>
I manually cloned the cloud9 examples repo, which is what it seems to reference, but that code fails to compile haha
<set_>
I see it now. I think more people are working than expected on this rendition for the PRUs on the AI-64.
<set_>
I am not currently that person or a part to the group for PRU development.
<set_>
I am just some random diddly.
<Guest789>
Guess I should have bought the Black instead :)
<set_>
Sort of. I can be more than that at times but ask @zmatt, he know more. Ha!
<set_>
It is more of a starter board for me, the am335x has many capabilities and speed, performance, and PRUs.
<set_>
But, not like this monsoon of a SBC, this ai-64.
<set_>
It boots like in 4 seconds flat.
<set_>
Oh!
<set_>
Please hold.
<set_>
I will be back shortly.
<set_>
SimpPRU is another logic based PRU set of source.
<set_>
I mean...if you want to use PRUs, that may prove valuable. I have not tested it yet.
<Guest789>
I don't think that support AI64
<set_>
Oh.
<set_>
Okay.
<Guest789>
And I think I just realized the Cookbook only supports the normal AI, not AI-64 - I think that might be why I'm getting the firmware errors :/
<set_>
Right! So far...
<set_>
The PRUs are located at different sections due to the updated chip on the ai-64.
<set_>
I think...and this is what I wanted to check on.
<set_>
There is some Cape Layer Spec. that can be used w/ the AI-64.
<set_>
I think.
<set_>
I am not quite sure as of now.
<set_>
Anyway, this layer business handles the muxing of specific pins for Cape Usage.
<set_>
I tried to find the page online. Empty for now. Please hold. brb.
<Guest789>
Thanks for your help, I'll post back if I get it working!
<set_>
Have you been to /dev/remoteproc/* ?
<set_>
* is busy on the ai-64!
<set_>
Anyway, thank you for allowing me to settle down now.
<set_>
I keep telling all like I am under the light. Ha.
<Guest789>
Yeah, the new PRU paths seem to be /dev/remoteporc/j7-pru*_*
<set_>
Right.
<set_>
Lots!
<set_>
Even those R5f rat funtions may show themselves soon. On the forums, there was a person that got them to do all sorts of stuff.
<set_>
Anyway, thank you for allowing me to mouth off. I appreciate it.
<Guest789>
Got the example from the forum link above working! There's a couple of example projects for the PRUs and R5 in /usr/lib/ti/pru-software-support-package/examples/j721e
<set_>
Nice!
Guest789 has quit [Quit: Client closed]
Guest789 has joined #beagle
Guest789 has quit [Client Quit]
brook has joined #beagle
vagrantc has joined #beagle
ikarso has joined #beagle
vagrantc has quit [Quit: leaving]
buzzmarshall has quit [Quit: Konversation terminated!]
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 246 seconds]
indigaz has quit [Quit: Good bye!]
indigaz has joined #beagle
indigaz has quit [Client Quit]
xet7 has quit [Ping timeout: 248 seconds]
indigaz has joined #beagle
xet7 has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
Shadyman has quit [Quit: Leaving.]
ft has quit [Ping timeout: 264 seconds]
ft has joined #beagle
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
starblue1 has quit [Ping timeout: 252 seconds]
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
wonko-the-sane has quit [Ping timeout: 255 seconds]
wonko-th1-sane has joined #beagle
brook has quit [Remote host closed the connection]
starblue1 has joined #beagle
brook has joined #beagle
starblue1 has quit [Ping timeout: 256 seconds]
wonko-th1-sane has quit [Remote host closed the connection]
wonko-the-sane has joined #beagle
starblue1 has joined #beagle
wonko-the-sane has quit [Ping timeout: 255 seconds]