**** BEGIN LOGGING AT Fri Sep 28 03:00:02 2018 Sep 28 04:09:37 hello Sep 28 04:10:09 need advise for error using beaglebone with matlab simulink Sep 28 04:14:46 then you should probably describe the error you're getting, otherwise nobody can help you obviously :) Sep 28 04:20:12 Hello! I am getting this error on my beaglebone black: http://dpaste.com/2KKVCF2 Sep 28 04:20:28 can someone help me debug this issue? Sep 28 04:20:43 is the emmc corrupted? any help is greatly appreciated! Sep 28 04:22:13 fafa: that's impossible to say from this, all it's saying is that the filesystem is readonly Sep 28 04:22:35 zmatt: is there any information I can give you that would help? Sep 28 04:22:59 from uname -a Sep 28 04:23:00 Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT RT Thu Jan 21 20:13:58 UTC 2016 armv7l GNU/Linux Sep 28 04:23:26 hmm, pretty old system with an rt kernel Sep 28 04:23:35 kernel log would be a useful start Sep 28 04:23:43 (output of the dmesg command) Sep 28 04:25:15 hmmm now I am getting this: http://dpaste.com/252A1VX Sep 28 04:25:25 when I try to output dmesg Sep 28 04:26:13 okay something is really fucked. this just started happening randomly? Sep 28 04:26:21 when I reboot or shutdown that input/output error goes away Sep 28 04:26:32 regardless you'll have to reboot first, there's no way to diagnose what's going on here Sep 28 04:26:32 no this has happened before Sep 28 04:26:42 ok rebooting now Sep 28 04:27:16 and consider using a less ancient system and/or a non-rt kernel Sep 28 04:27:42 in case you're just running into some old kernel bug Sep 28 04:30:28 here it is: http://dpaste.com/1Z99PA8 Sep 28 04:30:36 output of dmesg Sep 28 04:31:07 also check df -h Sep 28 04:32:08 http://dpaste.com/3892PND Sep 28 04:32:20 there you go ( output of df -h) Sep 28 04:32:33 hmm, plenty of free space Sep 28 04:33:26 my best guess would be you're getting the rarely occurring dma bug of the omap-hsmmc driver Sep 28 04:33:42 zmatt: I was trying to back of the bios on a lenovo thinkpad R400 in order to flash libreboot Sep 28 04:34:01 but it's impossible to say for sure without a kernel log after the problem has happened Sep 28 04:34:23 I think I can reproduce it Sep 28 04:34:29 the error that is Sep 28 04:34:39 invoking dmesg at least once before the problem occurs should cause dmesg to remain in cache, hence allow you to run it after the bug occurs Sep 28 04:35:08 or to be extra sure you could copy dmesg to a tmpfs like /dev/shm/ or /run/ Sep 28 04:36:41 still, as long as you're using an ancient kernel, reporting a bug is mostly useless since you'll just get the reply "have you tried a more recent kernel?" Sep 28 04:37:31 also beware that an -rt kernel is more likely to exhibit buggy behaviour, and you should probably just use a normal one Sep 28 04:39:50 zmatt: should I just flash a newer version of debian and retry then? Sep 28 04:40:55 yes. on the latest image it's also easier to configure pins for spi: there's no need to mess with overlays, you can just do something like for pin in P9.17 P9.18 P9.21 P9.22; do config-pin $pin spi; done Sep 28 04:40:59 Here are some newer errors from flashrom: http://dpaste.com/0SGR9F4 Sep 28 04:41:25 oh this is weird Sep 28 04:42:13 uh oh, this is actually starting to look more like a problem with the eMMC, possibly wear-out Sep 28 04:42:14 zmatt: I download this Stretch IoT from here? http://beagleboard.org/latest-images/ Sep 28 04:42:44 yes Sep 28 04:42:53 what could have caused that wear out? Sep 28 04:43:21 this is a newly purchased beaglebone bone black. I haven't tried flashing the emmc yet Sep 28 04:43:36 hum, that makes wear-out unlikely Sep 28 04:43:55 should I run debian solely off the sd card then? Sep 28 04:43:57 unless you have a process that's behaving really badly in some way Sep 28 04:44:31 zmatt: maybe this line: 525.512058] EXT4-fs (mmcblk0p1): Remounting filesystem read-only Sep 28 04:44:43 was the one that caused the first read only message? Sep 28 04:45:07 it remounted my filesystem to read-only Sep 28 04:45:10 like, we've managed to wear out eMMC pretty quickly on a beaglebone, but that was due to a bug in a logging system we made that was causing something like 16 GB of data to be written per hour Sep 28 04:45:19 I was able to write before that error Sep 28 04:46:02 yes, the eMMC seems to become unresponsive, and as a result of the I/O errors the filesystem journal aborts, causing the filesystem to be marked readonly Sep 28 04:46:06 what else can cause this error besides the emmc being worn out? Sep 28 04:46:49 no idea. I'm assuming you're not accidently messing with the pins reserved for eMMC? (P8.03-06, P8.20-25) Sep 28 04:49:36 https://libreboot.org/docs/install/r400_external.html Sep 28 04:50:13 1, 18, 22, 21, 17, 3 Sep 28 04:50:29 those are the ones I am using with leads Sep 28 04:50:42 to a soic-16 flash chip Sep 28 04:51:21 yeah but did you make sure you're connecting to P9 and not P8 ? Sep 28 04:51:45 via a pomona 5252 Sep 28 04:52:06 yes P9 next to the 5v power plug Sep 28 04:52:52 the rail next to where you connect the 5v external power Sep 28 04:53:19 ok. another possibility I can think of is that what you're doing is messing with the 3.3V supply in a way that causes the eMMC to reset or otherwise become unresponsive Sep 28 04:53:30 e.g. if it's drawing too much power from the 3.3v supply Sep 28 04:53:48 even if momentary Sep 28 04:56:00 the 3.3v supply that's available on P9.03 is a separate LDO, not monitored by the PMIC, hence an overcurrent situation would not cause the beaglebone to shut down. but the eMMC is powered from the same supply, hence it *would* fail Sep 28 04:56:26 I am using the an external 5v power adapter and pin 3 for 3.3v Sep 28 04:56:58 yes I understand Sep 28 04:57:24 the beaglebone is also connect via usb my laptop Sep 28 04:58:50 zmatt: thank you for your help Sep 28 04:59:09 I am going to try reinstalling debian and setting up spi again Sep 28 04:59:13 it may be wise to ensure your laptop is grounded to the target system whose flash you're trying to reprogram Sep 28 04:59:18 I don't think it's a kernel issue Sep 28 04:59:38 it was just my first guess based on your initial symptoms, but having seen the kernel log I see no evidence for it Sep 28 04:59:53 how can I ensure my laptop is grounded to the target system? Sep 28 04:59:54 you could still try it I guess Sep 28 05:01:03 but I'm leaning more towards electrical issues resulting from interfacing with the target you're attempting to reprogram Sep 28 05:01:21 could it be that I setup spi incorrectly in these instructions: https://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0? Sep 28 05:01:49 from these instructions* Sep 28 05:03:22 those instructions are kinda weird and obsolete, but they're not going to create the issues you're having Sep 28 05:04:02 but like I said above, if you switch to the latest image you can simply configure the pins using the config-pin utility without having to mess with overlays Sep 28 05:04:47 reflashing to the latest image is probably a good idea, but unlikely to solve your problem Sep 28 05:08:51 is this at all helpful? http://dpaste.com/0Y6FJ47 Sep 28 05:09:18 this my last query. I will try to look into the interfacing issues next Sep 28 05:10:52 making sure systems are grounded together simply means making sure there's a good electrical connection between the ground of both systems. how to do so is a bit dependent on the devices: if they have a metal chassis then that's usually ground, hence that makes things easy. if your laptop's power supply has a plug with protective earth then that should probably ground your laptop. if it doesn't have ... Sep 28 05:10:57 ...PE then you may actually be better off by not having your laptop's AC adapter plugged in at all Sep 28 05:11:10 no it isn't Sep 28 05:12:26 the standard spi0 overlay (included with beagleboard.org images, including the one have you preinstalled) is /lib/firmware/BB-SPIDEV0-00A0.dtbo Sep 28 05:12:46 I am using a desktop computer actually to connect Sep 28 05:12:46 though like I said, on recent images it's unnecessary to deal with overlays to use spi Sep 28 05:13:09 06:57 < fafa> the beaglebone is also connect via usb my laptop Sep 28 05:13:24 any docs on using QNX booting from SD card Sep 28 05:13:24 is there some where I can read about the difference in the new images with dealing with overlays to use spi? Sep 28 05:13:30 ? Sep 28 05:14:09 Prasanna_: I've never seen or heard of anyone here using QNX. since it's a commercial offering, I'm assuming they offer support themselves Sep 28 05:15:53 fafa: I already said you don't need to mess with overlays at all on recent images. just do: for pin in P9.17 P9.18 P9.21 P9.22; do config-pin $pin spi; done Sep 28 05:16:17 (i.e. config-pin P9.17 spi and similar for the other three pins) Sep 28 05:17:06 zmatt: ok thank you. I will keep that in mind Sep 28 05:25:13 The bot is up and running! Sep 28 05:25:56 I need to make reverse now. F, L, R is all good but I need reverse too. Sep 28 05:37:46 @Zmatt Thank you Sep 28 05:50:41 Reverse! Sep 28 06:02:16 I thought nothing was working for a second. I had to disable the .service file reload the daemon and enable it again. Sep 28 13:06:44 m Sep 28 13:21:16 Hey there! Sep 28 13:21:57 I have some issues with my TT3201 board. Anyone got some experience with it? Sep 28 13:53:53 smartflyer: what is it? Sep 28 13:54:17 oh that thing Sep 28 14:15:21 smartflyer: I once attempted to make an overlay for that thing compatible with not-ancient kernels. I don't remember whether it worked or not Sep 28 14:20:01 smartflyer: you can find it in https://github.com/mvduin/overlay-utils Sep 28 15:22:32 Hi Sep 28 15:23:35 I have problem when run beaglebone Black using Simulink program. An error occurs when to run it. "The following error occurred during deployment to your hardware board: Error connecting to SSH server at 192.168.7.2" Sep 28 15:23:50 Anyone know to solve it? Sep 28 18:05:18 Hi I am new to beaglebone. Does anyone know of a way to mount the filesystem of the beaglebone over usb onto the Ubuntu PC connected to it to allow easier exchange of files? I am using the Debian 9.5 2018-08-30 4GB SD IoT image Sep 28 18:08:49 I do not. Sep 28 18:09:01 That is odd you ask b/c i used to know that answer. Sep 28 18:09:24 There may be a way. Let me check my book. Sep 28 18:10:08 Okay. Sep 28 18:10:11 I found something. Sep 28 18:10:29 Do you want to look at files on your host computer that is mounted on the BBB? Sep 28 18:11:06 sshfs! Sep 28 18:11:10 bbbnewbie: you could consider sshfs or NFS or SMBfs Sep 28 18:11:14 That should work. Sep 28 18:11:40 So, you need instruction on this process? Sep 28 18:14:19 Hello tbr: set_ here. Sep 28 18:14:37 Good idea! Sep 28 18:15:26 I actually want to avoid using the network connection for this. The reason is the Ubuntu box is connected to our internal network, so we are not keen on the fact that the bbb shows up as an ethernet connection. Is there a way to just mount it as a usb storage device? Sep 28 18:16:02 Also is there a way to prevent the board from showing up as an ethernet connection? Sep 28 18:18:05 To further clarify, the bbb is directly connected to the Internet, so we feel less secure when it is connected to both our internal network and the internet at the same time Sep 28 18:18:06 bbbnewbie: there shouldn't be any problem with the beaglebone showing up as ethernet interface: unless your ubuntu box is specifically configured to route or bridge between your internal network and the beaglebone, the beaglebone will not be able to reach your internal network in any way Sep 28 18:19:09 if need be you could also use a firewall to prevent the beaglebone from even being able to initiate any connection to your ubuntu machine Sep 28 18:20:55 it is possible to present a disk image to the ubuntu machine as a mountable filesystem, in fact the default image does so, but then the beaglebone would not be able to safely access the contents of this image (since an image cannot be mounted on two systems at the same time) Sep 28 18:22:54 you could perhaps use a serial console to manually mount and unmount it, but then you'd end up with something no more convenient than simply using an sd card Sep 28 18:23:47 in practice a serial console also works crappy compared to ssh, so having a network connection to the beaglebone is rather desirable Sep 28 18:25:32 Thanks. Are there instructions on how to set up a firewall on the bbb? And would it still allow the ubuntu machine to mount the filesystem via sshfs? Sep 28 18:26:42 I meant a firewall on the ubuntu machine. a firewall on the beaglebone wouldn't add any security, since the case you're presumably worried about is someone somehow gaining access to the beaglebone because of its internet connection, and that someone would simply be able to turn a firewall on the beaglebone off again Sep 28 18:27:50 I mean, a firewall on the internet connection of the beaglebone might still have added value, but typically that's already taken care of by your internet router (e.g. the presence of NAT already suffices to block inbound connections from the internet to the beaglebone) Sep 28 18:29:47 I see. That makes sense. I'll see if I can set something up on the ubuntu machine. Thanks for the suggestions! Sep 28 18:30:18 Just in case we decide to shut off the network connection, is there an easy way to do it on the bbb? Sep 28 18:31:18 firewalling the virtual ethernet interface of the BBB on the ubuntu machine would for example prevent the beaglebone from attempting to ssh to the ubuntu machine. of course that only matters if the ubuntu machine has an ssh server enabled and you use crappy passwords, but you get the idea Sep 28 18:31:32 if you want to shut it off, again just disable the interface on the ubuntu side Sep 28 18:31:57 doing anything on the bbb side once again provides no real protection since an attacker who gains access to the bbb would be able to undo it Sep 28 18:33:33 Got it. Thanks so much! This helps a lot. Sep 28 18:35:00 the best security would probably be gained by actually setting up port forwarding from some high-numbered port on the bbb's internet connection to the ssh port of the bbb, make sure public-key authentication is required (i.e. ssh login using passwords is rejected), and then use that to ssh from your machine to the bbb instead of using any usb connection whatsoever Sep 28 18:35:32 a usb device has a dangerous amount of power over the machine it's connected to in all cases, for example it can pretend to be a keyword and type anything it wants Sep 28 18:36:26 probably not very practical to exploit, but still Sep 28 18:37:06 you'll just need to figure out the best balance between convenience and paranoia in your particular situation :) Sep 28 21:03:25 I see a directory named /media/BEAGLEBONE that is automounted when I connect my bbb to my Ubuntu box. Does anyone know how to access the contents in this directory from the beaglebone itself? Sep 28 21:10:44 like I said earlier "the beaglebone would not be able to safely access the contents of this image (since an image cannot be mounted on two systems at the same time)" Sep 28 21:15:00 the image itself is apparently /var/local/bb_usb_mass_storage.iso or .img Sep 28 21:15:06 I see, so this is what you were specifically referring to. I only noticed this directory just now and thought maybe it can be used as a way to share files Sep 28 21:15:50 Is there support for PTP/MTP on the beaglebone? Just trying to explore all options here. Sep 28 21:16:27 just use ssh Sep 28 21:16:46 as I said earlier, changing settings on the bbb to make the network interface go away does not increase security Sep 28 21:17:00 for that you'd need to get rid of the usb connection entirely Sep 28 21:20:07 ok thanks Sep 28 21:20:57 I don't use my USB tcp/ip interfaces and I'd like them to go away. Sep 28 21:21:23 so would I edit the /network/interfaces file to do this? Sep 28 21:21:52 me hates tcp/ip over usb. Sep 28 21:22:30 Snert__: those interfaces are setup by some ugly shell script in /opt that's invoked by a startup service. I don't think that service really does anything else that's useful, so I suggest disabling it entirely Sep 28 21:22:34 lemme check its name Sep 28 21:22:44 thx. Sep 28 21:22:56 sudo systemctl disable generic-board-startup Sep 28 21:22:57 try that Sep 28 21:23:25 see /opt/scripts/boot/generic-startup.sh to check what it normally does Sep 28 21:23:42 ok...cool...now I know where to look. Sep 28 21:24:37 Imma a little disoriented when it comes to this beagleboard x15. It's a little different. Sep 28 21:26:31 a lot of it inherited from the image for the beaglebone Sep 28 21:28:33 -bash: warning: setlocale: LC_ALL: cannot change locale (en_US) Sep 28 21:28:44 I see that when I login as root. Sep 28 21:28:51 huh, that's odd Sep 28 21:29:18 although "en_US" is weird, normally it would be "en_US.UTF-8" Sep 28 21:29:36 maybe your ssh client is sending locale environment vars over? Sep 28 21:30:15 I'll run through the locale setup and see. The keyboard also puts out funky chars like it's set for another language. Sep 28 21:30:26 when I VNC. Sep 28 21:30:43 but if I just plain ssh in.....the typed chars are correct. Sep 28 21:30:49 dunno where to look for that. Sep 28 21:30:57 sounds like VNC is confused Sep 28 21:31:11 maybe so. Sep 28 21:31:32 for the locale thing you can probably fix it by commenting out "AcceptEnv LANG LC_*" in /etc/ssh/sshd_config and restarting sshd Sep 28 21:31:45 oh cool...thx. Sep 28 21:31:59 that prevents ssh clients from asking for a different (probably unsupported) locale Sep 28 21:33:09 on the better side....just got the heatsink and fan for the X15 from digikey. Sep 28 21:33:35 dang that little board is a beast Sep 28 21:34:25 (you should probably also look into the locale config on your local system, since having LC_ALL set is pretty odd, and LC_ALL=en_US even weirder) Sep 28 21:34:53 haven't felt the need for a heatsink yet, but I haven't done anything particularly heavy computationally Sep 28 21:35:24 it was running really hot - fried finger to touch the processor top. Sep 28 21:35:32 doing what? Sep 28 21:35:43 and it's just sitting there running etherape. Sep 28 21:35:51 and vnc Sep 28 21:36:07 what's the load average reported by 'uptime' ? Sep 28 21:37:17 root@Beagle-X15:~# uptime Sep 28 21:37:17 21:36:56 up 10:45, 5 users, load average: 0.94, 1.03, 0.98 Sep 28 21:37:39 seems like pretty high load Sep 28 21:38:05 it's doing quite abit with vnc and etherape I guess. Sep 28 21:38:16 but it's still bitchin' fast. Sep 28 21:38:33 well might want to check if there isn't any other crap running in the background Sep 28 21:38:37 I type shutdown -h now and it's down in 2 seconds. Sep 28 21:39:31 there is, of course....any/all stock stuff in the image running. Only thing I added was etherape. Sep 28 21:41:01 I'd like to get rid of node red and all the bonescript stuff. Sep 28 21:41:11 but yeah it's decently fast, especially compared to the beaglebone ;) even with the bloated default kernel I still get a pretty decent boot time... https://liktaanjeneus.nl/boot-x15.svg Sep 28 21:42:20 I flashed the console image and then just added stuff to taste Sep 28 21:42:43 have you seen any expansion boards for the X15....anything at all? Sep 28 21:43:10 I'll try that...I used the full image so I'll reflash. Sep 28 21:43:12 I've never looked Sep 28 21:43:47 dealing with expansion boards isn't quite as convenient on the x15 as it is on the beaglebone anyway Sep 28 21:43:58 I'm wanting an SSD m.2 on a little card attached to one of those hirose connectors on the bottom. Sep 28 21:44:57 last time I checked u-boot contained fixed pinmux for the lcd board that the am572x attached to those expansion connectors Sep 28 21:45:47 m.2 is that weird connector that has a random bunch of interfaces on it right? Sep 28 21:46:03 you mean the lcd board utilizes all 4 of those hirose connectors on the bottom? Sep 28 21:46:48 I'm not sure about the m.2 thing....not familiar enough with SSDs yet. Sep 28 21:47:11 I just know that I would sidestep Esata if possible. Sep 28 21:47:47 yes. the "lcd board" contains a lot more than just an lcd though, e.g. it also has a miniPCIe slot, an mSATA slot, a camera board connector, etc Sep 28 21:48:15 sidestep esata, why? Sep 28 21:48:51 I do not want a big bulky external esata cable hanging off the board. Sep 28 21:48:52 I mean, presumably an m.2 ssd also just uses the SATA interface on that connector, or does it use pcie? Sep 28 21:49:02 fair enough Sep 28 21:49:24 but good to know that msata is on the lcd board perhaps I'll go that way. Sep 28 21:49:49 I'm not sure whether the lcd board is available for sale separately though Sep 28 22:22:24 Hi all! I'm currently using a beagle board blue, with a 2 cell connected. I'm trying to run rc_test_servos but keep getting `Bus error` Sep 28 22:23:20 that's its user-friendly way of saying "pru firmware has not been loaded" Sep 28 22:23:47 That's what I thought Sep 28 22:23:53 Just ran rc_test_drivers Sep 28 22:24:28 *sigh* Sep 28 22:24:55 are you booting from sd card or eMMC ? Sep 28 22:25:07 sd card Sep 28 22:25:16 I messed up the eMMC version Sep 28 22:25:21 if you don't care about eMMC contents, wipe it using sudo blkdiscard /dev/mmcblk1 Sep 28 22:25:24 So wiped and booted from sd Sep 28 22:25:44 an old bootloader on eMMC can cause weird problems with the sd card Sep 28 22:25:55 or, usually a better option, reflash eMMC Sep 28 22:26:20 Hmmm, used the latest stable version on the beagleboard site Sep 28 22:26:28 Yea, I want to refresh, but it takes a little while Sep 28 22:26:35 So wanted to see if I could get something working first Sep 28 22:26:38 *reflash Sep 28 22:26:47 fine too, but then at least erase eMMC with the command above Sep 28 22:26:53 will do Sep 28 22:27:26 Just wiped Sep 28 22:27:40 And also checked /opt/source/dtb-4.4-ti Sep 28 22:27:43 It is up-to-date Sep 28 22:27:53 And librototcontrol is on version 1.0.2 Sep 28 22:28:02 never heard of that directory Sep 28 22:28:19 you're running a 4.4 kernel? Sep 28 22:28:33 that's really old Sep 28 22:28:35 Is it not the one for the PRU driver? Sep 28 22:28:42 4.9 Sep 28 22:29:10 you can select between uio-pruss and remoteproc-pru by uncommenting the appropriate line in /boot/uEnv.txt Sep 28 22:29:16 nothing else needs to be done Sep 28 22:30:06 I think remoteproc-pru might be enabled by default but I'm not sure. you'd need to check which uboot_overlay_pru= line is uncommented there (if any) Sep 28 22:30:40 I'm assuming librobotcontrol uses remoteproc-pru since if they were using uio-pruss then I would expect things to simply work and not give a bus error :) Sep 28 22:32:41 Checking now, thanks for your help thus far! Sep 28 22:35:49 ok, so Sep 28 22:35:55 The uncommented line is Sep 28 22:36:04 uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo Sep 28 22:36:39 The other two options are Sep 28 22:36:40 uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-9-TI-00A0.dtbo Sep 28 22:36:45 uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo Sep 28 22:36:56 I assume I should uncomment the 4-9 and comment out the 4-14? Sep 28 22:37:18 did you downgrade to a 4.9 kernel? presumably 4.14 is the default nowadays Sep 28 22:38:15 Hmmm possibly Sep 28 22:38:18 It seems so Sep 28 22:38:20 if so, why? Sep 28 22:38:40 Not sure haha Sep 28 22:38:50 I downloaded the `Debian 9.4 2018-06-17 4GB SD LXQT ` Sep 28 22:38:57 From the beagle board site Sep 28 22:39:00 that's definitely not the one you should use on a blue Sep 28 22:39:09 Darn Sep 28 22:39:10 grab the first recommended image Sep 28 22:39:24 Debian 9.5 2018-08-30 4GB SD IoT Sep 28 22:40:53 Darn! 4 hours down the drain Sep 28 22:40:57 It's weird though Sep 28 22:41:07 My Debian version says it is 9.5 Sep 28 22:41:15 2018-06-17 Sep 28 22:41:18 why did you download the lxqt image? Sep 28 22:41:33 the blue doesn't even have a video output Sep 28 22:41:41 That was what was recommended to me Sep 28 22:41:50 what? by who? Sep 28 22:42:05 A person I work with Sep 28 22:42:12 That I probably won't ask for help from again haha Sep 28 22:42:41 lol Sep 28 22:43:55 Alright, I'll download the correct version and try it all again Sep 28 22:44:20 Thanks again for your help Sep 28 22:44:28 I'll make sure to come ask you first next time, rather than him lol Sep 28 22:44:34 since the right uboot_overlay_pru is uncommented by default, I feel like it ought to work without having to meddle with any system config or kernel stuff Sep 28 22:45:04 That's what I figured, but I thought maybe I somehow messed with the defaults Sep 28 22:47:57 Thanks again! Sep 28 22:47:59 Have a good day Sep 28 22:48:06 good luck! Sep 28 22:48:20 Thanks! **** ENDING LOGGING AT Sat Sep 29 03:00:00 2018