**** BEGIN LOGGING AT Sun Sep 08 02:59:57 2019 Sep 08 12:39:55 hello, I recently bought a bbb, this has debian 9.5. I'd like to control the PRU, but unfortunately the doc I could find on concerning enabling the PRU seem out of date Sep 08 12:43:06 mm302: yeah... docs aren't great Sep 08 12:43:28 though older docs related to uio-pruss still apply if you enable it Sep 08 12:43:38 there's a setting in /boot/uEnv.txt that lets you switch between uio-pruss and remoteproc-pru Sep 08 12:44:37 if you select uio-pruss then you can still use libprussdrv. my py-uio library also depends on uio => https://github.com/mvduin/py-uio Sep 08 12:48:37 oh, I see I have /sys/class/remoteproc/remoteproc1/state set to running, I checked a pru-software-support-package example, I can build but that seems to rely on /dev/rpmsg_pru30 that doesn't exist (not exactly sure how these things work though) Sep 08 12:49:39 note that which of those you use constrains which development tools you can use: remoteproc-pru can only load ELF executables as produced by clpru (TI PRU CGT) libprussdrv can only load raw binaries as produced by pasm, py-uio supports both although I do not yet support the resource table in ELF executables Sep 08 12:50:25 thank you very much, I will look into uio-pruss then Sep 08 12:50:43 sorry I don't really know much about remoteproc or rpmsg... using the C compiler and especially rpmsg pretty much destroys PRU's deterministic timing, hence I view them as useless Sep 08 12:52:35 interesting point of view, I see your point Sep 08 12:52:45 in case of remoteproc-pru, also beware that it changed a lot between major kernel versions, so if you want to follow any instructions on the internet as-is, you'll also need to make sure you have the same major kernel series as the author of those instructions Sep 08 12:54:30 (uio-pruss has remained stable from 3.8 or earlier to the latest 5.x kernels) Sep 08 12:56:16 at least I'm assuming it's in 5.x, haven't really checked Sep 08 12:57:07 cool I'm going to uncomment in uEnv.txt: uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo instead of the current AM335X-PRU-RPROC-4-14-TI-00A0 Sep 08 12:57:10 (I helped out porting it to 4.19, haven't heard anything about it not working in 5.x yet) Sep 08 12:57:21 mm302: yep, that's how you switch Sep 08 12:58:10 I'm looking forward to reboot it :-) Sep 08 12:58:11 (with the RPOC overlay also having the kernel series 4-14-TI in its name because of aforementioned changes between kernel versions) Sep 08 12:59:13 py-uio is probably easier to play with pru than libprussdrv btw, but unfortunately I haven't written much documentation yet beyond the README /o\ Sep 08 13:00:05 it does have a bunch of examples Sep 08 13:01:14 Hi, I need some advice flashing a beaglebone black Sep 08 13:02:05 I have the SD card ready in the micro SD slot. I press the boot button (the one close to the SD card slot) Sep 08 13:02:15 and power the board via USB. Sep 08 13:02:26 Power LED shows up. Sep 08 13:02:33 nothing else is happening. Sep 08 13:02:38 then the card is not bootable Sep 08 13:02:39 any idea? Sep 08 13:02:52 hm, created it with etcher. Sep 08 13:03:10 which image did you write to card? Sep 08 13:03:32 (the exact filename) Sep 08 13:03:35 bbxm-debian-9.5-lxqt-xm-armhf-2018-10-07-4gb.img.xz Sep 08 13:03:50 wrong device, bbxm = BeagleBoard xM Sep 08 13:04:52 also, if you want to reflash eMMC, easiest is to use a flasher Sep 08 13:05:13 e.g. "Debian 9.5 2018-10-07 4GB eMMC IoT Flasher" (third big blue download link on https://beagleboard.org/latest-images ) Sep 08 13:05:35 oops, indeed got the wrong image! Sep 08 13:05:42 thx will try Sep 08 13:05:58 that's also the IoT image rather than the lxqt image, which is recommended unless you absolutely need a desktop environment running (poorly) on the beaglebone itself Sep 08 13:06:44 hm, need qt5 without GUI. Sep 08 13:06:58 IoT image is fine for that Sep 08 13:07:25 you can use either the linuxfb or eglfs QPA backend Sep 08 13:08:13 ok, thx. I guess installing QT is just using apt right? Sep 08 13:09:32 yes Sep 08 13:11:40 actually the eglfs backend might prove a headache still, even if the sgx drivers are installed by default as rcn-ee[m] mentioned... back when I needed to get qt5 eglfs working on a BBB I even ended up patching qt5-base Sep 08 13:11:51 but that was a while ago, maybe things are better now Sep 08 13:14:01 let's see. first need a more recent linux on the board :) Sep 08 13:14:47 and a way to ssh into it, as the root password is set but no one remembers it XD Sep 08 13:15:30 ssh (in its default configuration) prohibits logging in as root using password authentication Sep 08 13:15:42 nor is there usually any reason to log in as root Sep 08 13:16:09 so what is the default login? Sep 08 13:16:12 the default ("debian") user has sufficient privileges for most day to day use, and can use sudo for the rare occasion that root privileges as needed Sep 08 13:16:37 debian/temppwd ... you could have found that easily by googling or by checking the getting-started guide Sep 08 13:18:16 well the getting started page on the device said "root" w/o password. But using the one from the Web says different. good to know. Sep 08 13:18:42 well if your device is running an ancient system, the getting-started guide on the device will be equally ancient Sep 08 13:19:01 root login has been disabled by default for many years Sep 08 13:20:19 yes that what I had in my mind, too. But trusted the old guide. Anyway it's currently updating! big thank you! Sep 08 13:23:46 good luck :) Sep 08 13:24:41 yeah, it's raining outside anyways :D perfekt day to re-animate that board. Sep 08 13:25:35 heh, re-aminate? Sep 08 13:26:29 I hope it's not a BBB revision older than rev C, since then the latest IoT (let alone lxqt) images won't fit Sep 08 13:27:48 I was told it should be a 4GB version. Sep 08 13:27:58 ok! Sep 08 13:28:11 software is so bloated -.- Sep 08 13:28:24 hm, no all LEDs stopped. even power LED is not on. Sep 08 13:28:52 that's unexpected, should all LEDs be on at the end? Sep 08 13:28:53 yes it powers off when it's done Sep 08 13:29:18 I think they briefly stay all-on and then the device powers off Sep 08 13:29:30 failure is indicated by all leds flashing simulaneously Sep 08 13:34:32 I am on the board. And it has the expected image with expected date Sep 08 13:35:23 and updated README.html :D Sep 08 19:38:02 ;2A Sep 08 19:47:16 Hi, just downloaded the latest image for my pocket boagle, i'm trying to connect to it via SSH but i can't find the default credentials, i have tried with user: root pwd: - but those are incorrect Sep 08 19:47:37 Am i missing something? Sep 08 19:52:05 carl0s: the correct credentials are in the getting started guide, as well as easy to find on the internet... Sep 08 19:52:10 but it's username "debian" password "temppwd" Sep 08 19:55:28 the first three google hits when searching for "beaglebone password" all list this information Sep 08 19:57:59 oh right, pocketbeagle, not beaglebone... Sep 08 19:58:07 same thing Sep 08 20:03:21 Yep, i was using the wrong user name Sep 08 20:03:43 thanks for the quick help Sep 08 20:03:53 carl0s: how exactly did you even search if you were unable to find this? https://liktaanjeneus.nl/pocketbeagle-password.png Sep 08 20:04:46 (the first two search results did have this username/password in the article, just not in the preview) Sep 08 20:09:30 ok bye :P **** ENDING LOGGING AT Mon Sep 09 02:59:58 2019