**** BEGIN LOGGING AT Tue Apr 13 02:59:56 2021 Apr 13 03:34:07 https://www.hackster.io/functt/recording-and-usb-web-cameras-with-the-bbai-and-opencv-d8d68d down towards the bottom has two filters used for tracking balls or other things that hold matter. Yes. Matter! Apr 13 03:35:01 There are two odd photos of a man in a room being filmed in black and white fuzzies and also in white and black super fuzzies. Apr 13 05:00:36 I think I accidentally put systemd on my Win 10 computer. Apr 13 05:00:37 ha. Apr 13 05:01:15 I tell ya', one buildroot too many and Windows now is ran by systemd. Apr 13 06:15:38 ^ lol Apr 13 06:29:04 lol Apr 13 06:29:24 Hi zmatt Apr 13 06:37:42 I tried the circuit https://photos.google.com/share/AF1QipM7qksZsEbPuo5FFd1NVyKcnuUfw36RWLVGLmamb6mcmEeDn9Ow9tKbkL2FLwBp2w?key=OWxOSGJOQjA5ejk4X1VtZXk1bmY5ZUhqMi03NmNB for Ethernet port (PHY) power ON issue. Apr 13 06:40:57 When I connect the voltage supervisor(TPS3839K), it keeps the BBB down. (i.e.) not allowing BBB to start. Apr 13 06:42:18 then you must not have connected it correctly? Apr 13 06:44:05 ohh, or you got the wrong part? I see there's more than one TPS3839K Apr 13 06:44:39 Yes I connected as per schematic given. Apr 13 06:44:53 since it's connected to the 3.3V, obviously it should be the TPS3839K33, not the TPS3839K50 (which is for monitoring 5V) Apr 13 06:46:59 if you have the TPS3839K50, you could have it monitor the SYS_5V instead of the 3.3V Apr 13 06:50:15 Ok Got it. Apr 13 06:54:50 obviously even the most cursory glance at the datasheet should have clarified this Apr 13 06:59:05 Ok Thank you. Apr 13 07:27:06 d'oh Apr 13 21:13:43 I know... Apr 13 21:14:14 +vedant16[m]: I cannot figure out what it did to my system yet. I was installing a system on the BBB. Apr 13 21:14:46 It seems it placed a duplicate of Win 10 on both hard drives and added an extention of a partition... Apr 13 21:15:36 you were joking right 🤣 Apr 13 21:15:42 No. Apr 13 21:15:56 I am trying to figure out what has happened. Apr 13 21:16:34 I have two hard drives on this ole 'puter. I was in a hard drive w/ a Debian OS to install the buildroot build on my BBB. Apr 13 21:16:59 Now, I have one Win 10 on one hard drive and another one on another hard drive but they are the same system. Apr 13 21:18:00 But...my board would not boot. I am still trying to track down what is going on. Apr 13 21:19:26 and I have like 560 videos now of *.d on my hard drive. I am not sure what .d videos are as of now. Off to look that up. Apr 13 21:21:33 It seems it is a langauge dlang file format. Apr 13 21:32:18 It looks like it works w/ armhf too! Apr 13 23:16:41 Hi Apr 13 23:53:22 hi everyone, I'm trying to download a beaglebone image so I can boot my beaglebone black from my microSD card Apr 13 23:53:26 I'm looking here: Apr 13 23:53:27 https://beagleboard.org/latest-images Apr 13 23:53:54 that is indeed where you'll find the latest official images Apr 13 23:53:55 but I'm getting 404 not found errors for every link Apr 13 23:54:00 huh Apr 13 23:54:05 are you getting that? Apr 13 23:54:13 trying to figure out if it's my computer or the website Apr 13 23:54:35 getting it on multiple browsers Apr 13 23:54:39 nope, it's not you, I'm getting it too Apr 13 23:54:45 something is broken Apr 13 23:55:03 jkridner: debian.beagleboard.org is broken Apr 13 23:55:41 john_doe: I'm sure it'll be fixed soon enough Apr 13 23:55:56 ok, is there any particular place I should report it to? Apr 13 23:56:01 thanks for the help! Apr 13 23:56:21 also do you know of any other place to download the images from? Apr 13 23:57:48 I _think_ these should be the same or equivalent images: https://rcn-ee.com/rootfs/bb.org/testing/2020-04-06/ Apr 13 23:58:06 buster-iot/ would be the default recommended image Apr 13 23:58:31 i.e. https://rcn-ee.com/rootfs/bb.org/testing/2020-04-06/buster-iot/bone-debian-10.3-iot-armhf-2020-04-06.1-4gb.img.xz to boot from sd card, or https://rcn-ee.com/rootfs/bb.org/testing/2020-04-06/buster-iot/bone-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06.1-4gb.img.xz to reflash eMMC Apr 13 23:59:12 note: flashing to eMMC is recommended Apr 14 00:00:02 if for whatever reason you want to run from sd card, you should probably wipe eMMC or at least wipe the bootloader from eMMC Apr 14 00:00:38 since if the bootloader on eMMC is much older than (or otherwise not quite compatible with) the system on sd card, it may boot but you can have all sorts of weird problems Apr 14 00:02:13 there are also more recent testing images here: https://elinux.org/Beagleboard:Latest-images-testing ... I'm actually not quite sure what's blocking these from becoming the new official images (since they're quite a bit overdue) Apr 14 00:11:24 awesome, thanks for the info Apr 14 00:11:45 I do want to run from the SD card so that the system is more easily transferrable between beaglebones Apr 14 00:12:27 ok, wiping the eMMC is as simple as "sudo blkdiscard /dev/mmcblk1" Apr 14 00:13:03 cool Apr 14 00:13:10 which I'll do after booting from the SD card, right? Apr 14 00:13:19 if the bootloader on eMMC is really ancient, it may not be able to boot a current image on sd card unless you hold down the S2 button (the button closest to the sd card slot) during power-up (you can let go once the power led turns on) Apr 14 00:13:32 yeah Apr 14 00:14:36 (if the beaglebone is powered up with S2 held down, it will completely ignore the bootloader on eMMC until the system is power-cycled again) Apr 14 00:15:13 ok cool. I have a bootloader on there, but somehow messed it up and can no longer ssh into it Apr 14 00:15:22 and I don't have a microHDMI cable Apr 14 00:15:33 plus I'm trying to switch to SD booting anyways so I will try this Apr 14 00:17:14 usually booting from SD card doesn't require the S2 button, it's only needed if a bootloader is present on eMMC that's too ancient (or otherwise incompatible) to be able to boot the SD card Apr 14 00:17:43 (if eMMC is wiped then the system will automatically use the bootloader present on the SD card instead) Apr 14 00:17:58 (or ditto if the eMMC bootloader is bypassed using S2) Apr 14 00:18:10 gotcha Apr 14 00:18:23 the eMMC isn't wiped, or it won't be until I am able to boot and wipe it Apr 14 00:18:29 so I'll use that button if necessary Apr 14 00:18:40 yep Apr 14 00:19:31 although honestly I'm not seeing any buttons near the SD card Apr 14 00:20:04 oh I see one on the opposite side Apr 14 00:20:06 maybe that's it Apr 14 00:20:26 top side yes Apr 14 00:20:29 says R157 by it Apr 14 00:20:32 cool Apr 14 00:21:39 nah that'll be some nearby resistor, there's definitely "S2" on the silkscreen next to the button somewhere, but it can be hard to see since the pcb and silkscreen are pretty crowded Apr 14 00:37:00 ok sorry if this is a dumb question Apr 14 00:37:14 but how do I tell if the image flashing/booting worked? Apr 14 00:37:31 is there some LED flashing pattern that might indicate success or failure? Apr 14 00:37:46 I flashed the SD card with the image you linked and restarted the beaglebone with it in Apr 14 00:37:46 I mean, it's not going to flash unless you downloaded a flasher image Apr 14 00:37:53 (flash eMMC that is) Apr 14 00:38:03 zmatt: yeah, working with AWS to recover. Apr 14 00:38:04 sorry Apr 14 00:38:19 john_doe: no that's fine, you didn't want to flash eMMC Apr 14 00:38:23 I guess I should say, is there a way to tell if the booting worked Apr 14 00:38:26 from the SD card Apr 14 00:38:32 I'm still not able to ssh to it Apr 14 00:38:54 but I'm just kinda shooting in the dark there cause I think it should be ubuntu@192.168.7.2, but am unsure Apr 14 00:39:03 username debian Apr 14 00:39:06 password temppwd Apr 14 00:40:04 ah, that worked! Apr 14 00:40:05 thanks Apr 14 00:40:13 debian@192.168.7.2 .. or if you're on a Mac or Linux system you can typically ssh to debian@beaglebone.local which is nicer than using an IP :) Apr 14 00:40:29 (it might also work on windows 10, maybe, dunno) Apr 14 00:40:46 I am on ubuntu Apr 14 00:40:48 but Apr 14 00:40:48 ssh: Could not resolve hostname beaglebone.local: Name or service not known Apr 14 00:40:53 odd Apr 14 00:40:56 I get that when I try the beaglebone.local Apr 14 00:41:07 had the same problem with similar raspberry pi stuff previously Apr 14 00:41:14 so I think there's probably something off on my system Apr 14 00:41:20 the default IP works fine though :) Apr 14 00:41:30 your ubuntu system doesn't have libnss-mdns installed? Apr 14 00:42:23 looks like it has that Apr 14 00:43:04 can you share (via pastebin.com or some other paste service) your /etc/nsswitch.conf ? Apr 14 00:43:42 sure Apr 14 00:43:50 btw I didn't have to press the button to get it to boot from the SD card Apr 14 00:43:52 so that's nice Apr 14 00:44:02 yeah like I said, usually that's not needed Apr 14 00:44:16 https://pastebin.com/arp3T1Bf Apr 14 00:44:30 oh also I realized that I just put debian on the beaglebone Apr 14 00:44:41 but I'm actually trying to put ubuntu 18.04, which I need for my project Apr 14 00:44:49 but also, even if seems to boot fine, things may not always work as they should if there's an old bootloader on eMMC Apr 14 00:44:52 so would I just find a regular image for that, and flash it similarly to the card? Apr 14 00:45:07 or do I need a beaglebone specific image? Apr 14 00:45:10 gotcha Apr 14 00:46:24 ubuntu is not officially supported on the bbb... I know there are unofficial ubuntu images for bbb floating around, but they are rarely used, and I have no idea what does or doesn't work on them Apr 14 00:46:49 most things that "require" ubuntu will work just fine on debian Apr 14 00:47:35 it's for consistency with our development environment Apr 14 00:47:40 and strange that beaglebone.local doesn't work for you, it looks like your nsswitch.conf does have mdns resolution enabled Apr 14 00:47:43 probably could be made to work on debian Apr 14 00:47:48 huh Apr 14 00:48:03 but yeah I think it's better to use ubuntu cause that's what we're developing on Apr 14 00:48:08 ubuntu is based on debian and is overall very similar Apr 14 00:48:13 for sure Apr 14 00:49:10 so using a system that's tested and supported on the bbb instead of one that's untested and unsupported should probably take priority over "consistency" Apr 14 00:49:44 but that's up to you Apr 14 00:50:06 yeah I get where you're coming from Apr 14 00:50:17 but I'm going to at least try to make it work with ubuntu to start Apr 14 00:50:28 https://elinux.org/BeagleBoardUbuntu#Ubuntu_.2818.04.4.29 Apr 14 00:50:35 looks like these might be what i'm looking for? Apr 14 00:52:27 https://elinux.org/BeagleBoardUbuntu#All_BeagleBone_Variants_and_PocketBeagle looks like a prebuilt image Apr 14 01:00:50 awesome Apr 14 01:00:51 trying that Apr 14 01:22:36 ok I did that Apr 14 01:22:52 (followed the instructions on https://elinux.org/BeagleBoardUbuntu#Ubuntu_.2818.04.4.29) Apr 14 01:24:20 unfortunately I can't ssh into it anymore Apr 14 01:24:41 with ubuntu@192.168.7.2, or debian@192.168.7.2 Apr 14 01:25:06 any ideas? always frustrating when you can't ssh cause it's like you can't troubleshoot cause you can't see what's wrong cause you can't get in Apr 14 01:25:23 does it appear as usb network interface at all? I have no idea whether it has the same usb gadget setup Apr 14 01:25:53 I'd try getting in via ethernet (although that's easier when mdns works since that avoids the need to figure out its IP) Apr 14 01:27:10 or, if it appears as usb serial gadget you can get in via that, or the last resort of getting into a system is using a serial console cable (it's rare to need one, but in the rare case you do need one it really sucks when you don't have one) Apr 14 01:37:28 let's see Apr 14 01:45:27 I'm trying to figure out how to list USB network devices Apr 14 01:45:37 ip addr Apr 14 01:45:47 lists all network interfaces and their configured addresses Apr 14 01:46:20 oh hey actually I got in Apr 14 01:46:28 somehow it switched to 192.168.7.1 Apr 14 01:46:30 instead of .2 Apr 14 01:46:41 got that with ifconfig Apr 14 01:46:50 normally .1 is your own computer's ip on the interface Apr 14 01:47:20 at least, that's how the debian images are configured Apr 14 01:47:29 (ifconfig is an obsolete tool btw) Apr 14 01:49:27 oh ok Apr 14 01:49:33 so I'm maybe sshing into my own computer? Apr 14 01:50:12 actually this must be the right one Apr 14 01:50:15 I mean, normally I'd assume you'd be able to tell based on the username/password it accepts Apr 14 01:50:20 because it says ubuntu 18.04 Apr 14 01:50:22 yeah true Apr 14 01:50:26 it accepted ubuntu Apr 14 01:50:28 and temppwd Apr 14 01:50:35 so I think I'm in! Apr 14 02:30:26 hey guys Apr 14 02:30:35 sorry, I asked this earlier but neglected to write down the answer Apr 14 02:30:47 and now I'm not sure if it's possible to see past conversation Apr 14 02:30:57 but I'm booting a beaglebone from the SD card Apr 14 02:31:00 I figured out what happened. I booted the Buildroot image on the hard drive instead of the SD Card. Apr 14 02:31:06 Aw! Apr 14 02:31:19 and I'm trying to figure out how to wipe out everything on eMMC so it doesn't interfere Apr 14 02:31:28 anyone know how to do that? Apr 14 02:31:36 (sorry to dislodge your thread set_) Apr 14 02:31:49 Hello! Apr 14 02:31:59 I know and @zmatt knows too! Apr 14 02:32:04 @zmatt told me how. Apr 14 02:34:13 So... Apr 14 02:34:19 You want to erase the eMMC right? Apr 14 02:35:08 I am sure this is it: sudo blkdiscard /dev/mmcblk1 or whatever your partition is for your eMMC. Apr 14 02:37:58 yeah Apr 14 02:38:01 ok let me try that Apr 14 02:38:11 john_doe... Apr 14 02:38:26 I think you are the fellow on Overflow? Apr 14 02:38:34 yes haha Apr 14 02:38:39 You asked about the .dtb and .dts files. Apr 14 02:38:43 that's me! Apr 14 02:38:46 I started a chat w/ you! Apr 14 02:38:59 haha, are you De Funct? Apr 14 02:39:04 Ha. It is me. Sorry if my recommendations did not get too supportive. Apr 14 02:39:05 yes. Apr 14 02:39:41 no worries Apr 14 02:39:49 Did you see the last part of the chat? Apr 14 02:39:54 I think I figured out how to change the configuration for at least some of the pins Apr 14 02:40:06 I explained where to place the .dtb file in /boot/uEnv.txt. Apr 14 02:40:07 Okay. Apr 14 02:40:16 but then I accidentally bricked the beaglebone messing with the configuration Apr 14 02:40:23 now I reinstalled ubuntu on the SD card Apr 14 02:40:28 cause we want to do that anyways Apr 14 02:40:37 Right. That is all part of learning. Apr 14 02:40:39 and am trying to replicate the same steps, but for some reason this time it's not working Apr 14 02:40:41 I have bricked them! Apr 14 02:40:46 Hmm. Apr 14 02:40:48 haha, agreed Apr 14 02:40:52 it's a mark of passage Apr 14 02:40:59 I bricked the AI too. Apr 14 02:41:00 Right. Apr 14 02:41:11 currently I thought maybe it's cause I'm changing the dts file on local memory or something but booting from the SD card Apr 14 02:41:34 I think the .dts files should be okay. Apr 14 02:41:57 But...the .dtb on the /boot/uEnv.txt file will definitely disrupt current workings. Apr 14 02:42:05 It has to be exact and working. Apr 14 02:43:26 yeah i think that might have been what happened before Apr 14 02:43:38 but now I'm having trouble even repeating what was working before Apr 14 02:43:52 I'm using this config file exactly: Apr 14 02:43:53 https://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/device-tree-overlays Apr 14 02:44:05 I'm compiling it with Apr 14 02:44:06 dtc -O dtb -o test_config.dtbo -b 0 -@ test_config.dts Apr 14 02:44:15 but this tells me: Apr 14 02:44:15 test_config.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property Apr 14 02:44:16 test_config.dtbo: Warning (unit_address_vs_reg): Node /fragment@1 has a unit name, but no reg property Apr 14 02:44:54 I've got it in the /boot/uEnv.txt with: Apr 14 02:44:55 uboot_overlay_addr0=~/test_gpio_configurations/test_config.dtbo Apr 14 02:45:01 Yea...this is where the particular .dtb file comes into play. Let me see if I can find a link w/ the ideas in ppt format. Apr 14 02:45:04 but it's not affecting the pin configurations this time for some reason Apr 14 02:47:53 https://buildroot.org/docs.html is a site that has the ideas on Buildroot but they are part of the BBB ideas. There is a short presentation on ideas relating to the BBB. Apr 14 02:48:11 And... Apr 14 02:48:35 The people from Bootlin have extensive ideas on porting workable images to the BBB. Apr 14 02:48:59 Now, all this may get in your way but... Apr 14 02:49:35 ok, I will read through this Apr 14 02:49:46 do you have any ideas what specifically might be going wrong though? Apr 14 02:50:04 cause as far as I'm aware, this is the same process I underwent last time Apr 14 02:50:08 but this time it's not working Apr 14 02:50:56 It is a good lesson to learn, i.e. speaking from experience here. Also, did you look over the site here: https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black? Apr 14 02:52:02 That fellow that posted that page has a straight forward way to set up an image, Ubuntu or Debian, w/ the BBB. Apr 14 02:52:25 ok, I actually got the image working though Apr 14 02:52:32 Also...you can then mess w/ the .dtb and .dts files afterwards. Apr 14 02:52:33 Oh. Apr 14 02:52:36 Okay. Apr 14 02:52:54 it's the dts overlay that I'm still having trouble with Apr 14 02:53:23 Oh. Okay. It seems w/out the source of the .dts file, one is just guessing where you are located w/ trouble? Apr 14 02:53:38 For instance, me! I am guessing about this .dts file. Apr 14 02:53:57 pastebin.com a paste of the .dts. Apr 14 02:54:19 I may be able to help but I may not depending on the severity of what is going on in that file. Apr 14 02:54:29 https://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/device-tree-overlays Apr 14 02:54:30 for sure Apr 14 02:54:35 I'm using the exact example here Apr 14 02:54:54 Okay. I will go and look it up when you post it. Apr 14 02:55:04 Oh. Apr 14 02:55:07 That one. Apr 14 02:55:08 Okay. Apr 14 02:55:12 Let me go and look. Apr 14 02:56:29 Just install the BeagleBoard-DeviceTrees or the bb.org-overlays and install both of them, then put BB-UART1-00A0.dtbo in the /boot/uEnv.txt file under uboot_overlays. Apr 14 02:57:14 I know. Apr 14 02:57:53 You want the power to write .dts files whenever, however for your needs on the BBB. Apr 14 02:57:55 I get it. Apr 14 02:58:10 It is not so easy for whatever reason. **** ENDING LOGGING AT Wed Apr 14 02:59:56 2021