**** BEGIN LOGGING AT Fri Dec 09 02:59:57 2022 Dec 09 03:21:06 @zmatt: My bone is not working on the Debian Distro when connected via USB? Dec 09 03:21:17 Send rations Dec 09 03:39:13 Here and standing! Dec 09 03:39:27 * set_ actually is sitting! Dec 09 03:39:37 touche! Dec 09 18:38:18 Good day Dec 09 18:39:06 Been working on a net library quite a lot recently. Probably some to poke around a BB. Though it's been used to compile ARM code natively. Dec 09 23:31:14 There's no "/opt/scripts" directory on the latest Debian flasher image for the AI-64 board. Did they move somewhere else? Dec 09 23:53:39 Guest789: What command are you looking for now? Dec 09 23:55:59 For instance, ./grow_partition.sh or something else? Dec 10 00:00:51 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 Dec 10 00:02:36 Right. Dec 10 00:02:37 Okay. Dec 10 00:02:43 What image are you using? Dec 10 00:02:49 cat /etc/dogtag Dec 10 00:03:20 If you are using an updated image, I think those items have been moved and are not referenced for the BBAI-64. Dec 10 00:04:04 Fro instance, BBAI is not the BBAI-64. Dec 10 00:04:30 WHen you reboot, the total amount of space will be allocated from your SD Card. Dec 10 00:05:10 BeagleBoard.org Debian Bullseye Xfce Image 2022-06-14 Dec 10 00:05:24 For instance, I rebooted the board after updating/upgrading it. The full capacity of the SD Card was intact. Dec 10 00:05:26 Okay. Dec 10 00:05:51 I had a 128GB SD Card. It inflated after the reboot. Dec 10 00:06:12 Do I need space. NO. Was it worth it, yes. Dec 10 00:07:07 Guest789: What command from what link are you trying to use? Dec 10 00:08:30 I am sure people will catch up w/ updating to some good wiki info. Dec 10 00:10:12 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. Dec 10 00:10:25 Oh! Dec 10 00:10:39 Right. Dec 10 00:10:47 I think people are working now on that idea. Dec 10 00:11:07 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. Dec 10 00:16:31 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/ Dec 10 00:17:25 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 Dec 10 00:18:27 Hmm. Dec 10 00:18:50 Are you using the updated version two of the PRU Cookbook? Dec 10 00:19:19 Guest789: Sorry. My board does not boot right now. I make errors... Dec 10 00:19:38 Anyway, some stuff I have learned may, slightly may, be useful. Dec 10 00:19:55 Hmm, not sure - I'm using this one: https://markayoder.github.io/PRUCookbook/02start/start.html Dec 10 00:19:56 Is there an updated version? Dec 10 00:20:06 Let me go and see. Dec 10 00:20:07 Yes. Dec 10 00:20:21 I will link it. Dec 10 00:20:59 Here: https://docs.beagleboard.org/latest/boards/beaglebone/ai-64/index.html Dec 10 00:21:04 And... Dec 10 00:21:36 Here: https://docs.beagleboard.org/latest/books/pru-cookbook/index.html but in beta testing... Dec 10 00:22:58 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. Dec 10 00:23:39 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? Dec 10 00:23:46 Fruition...whatever. Dec 10 00:24:28 Odd words. I know but I cannot be of anymore assistance for now. Dec 10 00:24:30 I am sorry. Dec 10 00:24:54 Thank you! Dec 10 00:25:22 ! Dec 10 00:28:46 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. Dec 10 00:30:04 Hmm. Dec 10 00:30:10 Dang it. Dec 10 00:30:44 Right...that is what I was discussing earlier. Dec 10 00:31:20 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? Dec 10 00:31:24 Let me try...brb. Dec 10 00:34:55 There are also some items in /dev/bone/ Dec 10 00:35:52 All I have there is /dev/bone/uart Dec 10 00:37:56 Did you get a fan and update/upgrade? Dec 10 00:39:43 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. Dec 10 00:40:01 PWM/UART/ADC and etc... Dec 10 00:40:09 Let me see what is on mine. Dec 10 00:42:06 Hmm. Dec 10 00:42:10 I have only uart and PWM now. Dec 10 00:42:22 I think there was others that were available at some point... Dec 10 00:42:40 Yeah I've done update/upgrade and kernel update Dec 10 00:43:26 Okay. Try, if on Windows, 192.168.7.2:3000 Dec 10 00:43:55 If not and if you are using Ubuntu or Debian...try 192.168.6.1:3000 I think. Dec 10 00:44:18 Like I say, my host or target got busted the other day. Dec 10 00:44:36 So, I cannot use Linux w/ my BBB series SBCs for whatever reason... Dec 10 00:45:41 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). Dec 10 00:45:55 See. I am no help now. Dec 10 00:50:31 I will clone it and test it. Who knows? Dec 10 00:51:34 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. Dec 10 00:51:54 Oh! Dec 10 00:51:56 Yep. Dec 10 00:52:13 I manually cloned the cloud9 examples repo, which is what it seems to reference, but that code fails to compile haha Dec 10 00:52:21 I see it now. I think more people are working than expected on this rendition for the PRUs on the AI-64. Dec 10 00:52:51 I am not currently that person or a part to the group for PRU development. Dec 10 00:53:07 I am just some random diddly. Dec 10 00:53:22 Guess I should have bought the Black instead :) Dec 10 00:53:28 Sort of. I can be more than that at times but ask @zmatt, he know more. Ha! Dec 10 00:54:07 It is more of a starter board for me, the am335x has many capabilities and speed, performance, and PRUs. Dec 10 00:54:26 But, not like this monsoon of a SBC, this ai-64. Dec 10 00:54:44 It boots like in 4 seconds flat. Dec 10 00:54:58 Oh! Dec 10 00:55:25 Please hold. Dec 10 00:55:30 I will be back shortly. Dec 10 00:56:25 SimpPRU is another logic based PRU set of source. Dec 10 00:56:45 I mean...if you want to use PRUs, that may prove valuable. I have not tested it yet. Dec 10 00:56:49 I don't think that support AI64 Dec 10 00:56:54 Oh. Dec 10 00:56:55 Okay. Dec 10 00:57:27 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 :/ Dec 10 00:57:36 Right! So far... Dec 10 00:58:02 The PRUs are located at different sections due to the updated chip on the ai-64. Dec 10 00:58:19 I think...and this is what I wanted to check on. Dec 10 00:58:56 There is some Cape Layer Spec. that can be used w/ the AI-64. Dec 10 00:59:01 I think. Dec 10 00:59:09 I am not quite sure as of now. Dec 10 00:59:42 Anyway, this layer business handles the muxing of specific pins for Cape Usage. Dec 10 01:00:11 I tried to find the page online. Empty for now. Please hold. brb. Dec 10 01:02:16 Aw and here: https://docs.beagleboard.org/latest/boards/capes/cape-interface-spec.html#bone-i2c Dec 10 01:02:59 That may get you further down the road than just waiting for PRU instances. Dec 10 01:03:09 Also... Dec 10 01:03:36 There is another use case so far. Dec 10 01:04:48 Here: https://docs.beagleboard.org/latest/boards/beaglebone/ai-64/edge_ai_apps/getting_started.html Dec 10 01:04:54 I am terrible at AI so far. Dec 10 01:05:05 But, this is an interesting subject. Dec 10 01:05:31 And that processor can handle high heat. So, pushing tons of data per second may just work! Dec 10 01:05:46 W/ a fan of course. Dec 10 01:06:22 I have to stop. I keep telling all and receiving glory! Dec 10 01:06:23 That cape page also seems like it's out of spec for the AI64 - it references /dev/remoteproc/prussX-coreY, which is not the correct path. Dec 10 01:06:24 I just found this post that might get me going: https://forum.beagleboard.org/t/ai64-pru-basics-very/32288 Dec 10 01:06:38 Nice. Dec 10 01:07:13 Thanks for your help, I'll post back if I get it working! Dec 10 01:07:23 Have you been to /dev/remoteproc/* ? Dec 10 01:07:37 * is busy on the ai-64! Dec 10 01:07:57 Anyway, thank you for allowing me to settle down now. Dec 10 01:08:10 I keep telling all like I am under the light. Ha. Dec 10 01:08:11 Yeah, the new PRU paths seem to be /dev/remoteporc/j7-pru*_* Dec 10 01:08:17 Right. Dec 10 01:08:31 Lots! Dec 10 01:09:08 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. Dec 10 01:10:19 Anyway, thank you for allowing me to mouth off. I appreciate it. Dec 10 01:31:21 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 Dec 10 01:34:35 Nice! **** ENDING LOGGING AT Sat Dec 10 02:59:56 2022