**** BEGIN LOGGING AT Wed Nov 25 02:59:57 2020 Nov 25 03:02:08 seems like my overlay was compiled wrong Nov 25 03:08:38 i am confused by make sure you've compiled with -@ Nov 25 03:12:16 GenTooMan: dang Nov 25 03:12:29 how many computers do you have in the house Nov 25 03:12:44 do you have the wires in the walls or run the lines outside Nov 25 03:17:49 mattb000ne: yeah that error sounds like the overlay references a symbol that doesn't exist in the base dtb Nov 25 03:18:31 unfortunately the error handling for overlays in u-boot is... not great Nov 25 03:19:22 basically if an error occurs while applying the overlay, the dtb is completely gone, hence the subsequent errors Nov 25 03:19:37 (instead of something sane like ignoring the overlay) Nov 25 03:30:31 u boot is a universal thing right Nov 25 03:30:49 so learning how it works is worthwhile? Nov 25 03:30:59 it's a bootloader used on a fair number of devices Nov 25 03:31:17 dunno Nov 25 03:31:26 "how it works" seems really broad in scope Nov 25 03:31:33 do bootloaders work in vastly different ways Nov 25 03:31:44 i dont really need to know the nuts and bolts Nov 25 03:32:05 but I think maybe getting a better grasp of how my system boots would be benefical Nov 25 03:32:10 while I eat my turkey Nov 25 03:32:30 an aside what do you do for the speaker product you work on Nov 25 03:32:49 the details of a bootloader tends to be rather specific to a device architecture Nov 25 03:33:18 mostly software programming, mostly low-level stuff Nov 25 03:34:22 though I also help with hardware stuff (mostly double-checking schematics) Nov 25 03:35:15 since you are an audio guy what do you think of that bela project Nov 25 03:35:19 for the beagle bone Nov 25 03:35:42 I don't have experience with it nor do I know much about it Nov 25 03:38:41 like, if you want to do real-time audio generation/processing, generally a dsp is the more logical choice Nov 25 03:39:23 but obviously having a linux environment has its benefits too Nov 25 03:41:09 am i understanding this right, the capes eprom tells it what overlay file it would want ? Nov 25 03:41:28 that's how cape autodetection works yes Nov 25 03:41:54 interesting...... Nov 25 03:42:14 so what happens if it wants an overlay file but you do not have it Nov 25 03:42:19 failed boot Nov 25 03:42:31 missing overlay file is just ignored Nov 25 03:42:56 also if it can auto detect why do you need to add it manually to the uEnv.txt Nov 25 03:43:14 seems like it makes more sense to just have it go fetch from /lib/firmware Nov 25 03:43:39 you normally don't, but presumably the autodetection logic isn't actually in the bbai u-boot yet Nov 25 04:03:38 can I disable that auto loading part Nov 25 04:03:44 of u boot Nov 25 04:04:07 seems like the AI has it Nov 25 04:04:48 you can add a line to /boot/uEnv.txt to disable auto loading of an overlay Nov 25 04:04:55 e.g. for slot 0: disable_uboot_overlay_addr0=1 Nov 25 09:13:16 GenTooMan: I came across a nifty book on trace "exploration." R25C = 2 M ohms, R125C = 3 M ohms. This is for PCB trace resistance vs. length and width for 1 oz-Cu. Nov 25 09:13:52 I got that info. from the Analog Pocket Ref. from TI. Nov 25 09:14:41 The trace was 5 mil. Nov 25 09:15:37 I remember you were having an issue w/ a 4 mil. trace on an older Cape version. Nov 25 09:15:42 Did you ever figure it out? Nov 25 13:08:06 Hi! Can I connect P2_23 (3v3) directly to GPIO (GPIO_59 for example)? Nov 25 14:40:39 of course, as long as the gpio is configured as input (the default), not as output Nov 25 14:41:39 oh he left Nov 25 15:00:03 Hello Nov 25 15:00:21 The black does not have any wifi does it? Nov 25 15:00:31 no Nov 25 15:00:44 there are a few variants that do Nov 25 15:00:49 I thought I broke something lol Nov 25 15:00:57 the black wireless is essentially the black but with ethernet replaced by wifi + bluetooth Nov 25 15:01:09 oh Nov 25 15:02:28 so you can just pick: if you want ethernet get the beaglebone black, if you want wifi get the beaglebone black wireless Nov 25 15:02:31 the sancloud "beaglebone enhanced" has both wired and wireless Nov 25 15:03:21 yeah like mru says there are other beaglebone variants with various feature sets Nov 25 15:04:07 Yeah I see it now. I did not get to choose what to get so I gotta work with what I got Nov 25 15:04:18 I had some driver trouble with the beaglebone enhanced's wifi, but dunno if that's still an issue Nov 25 15:04:37 The Iss ssh enabled by default? Nov 25 15:04:54 the enhanced will be getting a different wifi module from next year Nov 25 15:05:07 ssh is enabled by default, it's the primary way people log into beaglebones Nov 25 15:05:09 rtl8723du instead rtl8723bu Nov 25 15:10:21 doesn't seem like that improves the driver situation Nov 25 15:11:04 that may well be Nov 25 15:17:06 or possibly makes it worse Nov 25 15:25:27 Hey guys Is there any way to migrate the OS to onboard SD? I have filled my 3 gigs Nov 25 15:26:06 with what? o.O Nov 25 15:26:12 I dont know Nov 25 15:26:20 It says 90% full Nov 25 15:26:43 what image did you start with? Nov 25 15:26:54 The one it came with Nov 25 15:27:15 i.e. probably a random old lqxt image :D Nov 25 15:27:21 hmm Nov 25 15:27:57 which includes a complete X11 desktop environment which most people have no need for Nov 25 15:28:41 generally speaking it's a good policy to reflash a beaglebone to the latest image the moment you get it Nov 25 15:28:49 hmm okay Nov 25 15:29:02 But can I boot from the external SD? Nov 25 15:29:12 Or do I have to re-flash? Nov 25 15:29:34 and the current default "IoT" image is a lot leaner than the lxqt image Nov 25 15:30:48 it can boot from SD, although it's a lot slower Nov 25 15:31:04 hmm okay Nov 25 15:31:11 and if you do intend to boot from SD, it's highly recommended to wipe eMMC to avoid problems caused by an old bootloader Nov 25 15:31:36 And how much space should the default image take ? Nov 25 15:32:02 software is a gas, it fills all the space available Nov 25 15:33:12 it seems the default 2020-04-06 IoT image uses 1.9G Nov 25 15:34:03 there's also the even leaner console image which uses less than 400M Nov 25 15:34:28 (intended for people comfortable with debian who are able to just install what they need) Nov 25 15:35:00 hmm okay Nov 25 15:35:26 I see it on the site Nov 25 15:35:35 I think i will just re-flash Nov 25 15:35:49 if you want to reflash the beaglebone, easiest is to use a flasher image (e.g. AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher) Nov 25 15:35:54 Thanks for the help :) Nov 25 15:36:49 you write that to sd card (using Etcher is recommended), stick it into the beaglebone, and power it on. it will proceed to reflash eMMC Nov 25 15:38:26 Yeah I see that on the site Nov 25 15:39:05 Wil it have ssh enabled? Nov 25 15:39:20 Or will I have to edit some files? Nov 25 15:39:22 all of the images have ssh enabled, like I said it's the primary way of logging into a beaglebone Nov 25 15:39:31 Oh okay Nov 25 15:40:11 I've never used any other mechanism. Nov 25 15:41:25 I tried using a display but the hdmi and usb were so close that I could not connect by keyboard/mouse Nov 25 15:41:47 heh, yeah the connectors are a bit cozy Nov 25 15:42:38 I don't think I've ever logged into a beaglebone by attaching a display and keyboard Nov 25 15:43:30 How can I see who is the owner of the channel? My first time using irc Nov 25 15:45:21 IRC in general doesn't have a concept of channel owner, though if an IRC network has services (which freenode does) you can typically get information on a registered channel from chanserv: /msg chanserv info #beagle Nov 25 15:47:54 And one last thing Nov 25 15:48:19 How do I close the convo I opened just now with the chanserv guy Nov 25 15:49:46 chanserv is a bot, not a guy :P and that's a question about whatever irc client you're using Nov 25 16:37:43 How to create iso image of SD card using PocketBeagle. I want to backup system to FTP. Nov 25 16:54:23 There is lot of instructions how to copy files or clone SD cards, but nothing about how to create ISO on FTP server. Nov 25 16:54:32 *are Nov 25 16:55:12 because you normally don't make an image of a filesystem that is mounted Nov 25 16:55:37 making an image of the filesystem you've booted from is kind of problematic Nov 25 16:55:54 hmm Nov 25 16:56:47 what about some raw readings from SD card? Could it help? Nov 25 16:57:13 ? Nov 25 16:57:25 remount the filesystem read-only Nov 25 16:57:37 remount read-only, or use filesystem freeze Nov 25 16:57:57 either way, processes on the system will be unable to write anything to SD card while the backup is in progress Nov 25 16:58:27 (they get an error if it's remounted read-only, or will hang if a filesystem freeze is used) Nov 25 17:00:33 https://github.com/billw2/rpi-clone Nov 25 17:00:51 But no FTP present Nov 25 17:01:39 this clones the filesystem, which requires being able to mount both source and destination filesystem Nov 25 17:02:39 i.e. it works to clone from one storage device to another, but if you want to go straight to ftp you don't have any place to put the backup image to mount it as part of the backup process Nov 25 17:03:01 what if mount network folder? Nov 25 17:04:50 why not use an actual backup program that supports backup to ftp? Nov 25 17:05:00 you knowm something designed for the intended purpose Nov 25 17:10:52 in all cases, backing up a running system is subtle and tricky Nov 25 17:11:47 you really need cooperation from any running apps Nov 25 17:12:52 if it's just a personal workstation, running backups at night is generally safe though Nov 25 17:13:05 or whenever you're not working Nov 25 17:13:36 a pocketbeagle is generally not a personal workstation Nov 25 17:13:43 one hopes Nov 25 17:19:21 Hello Nov 25 17:21:40 Siegurd: btw I did add two pocketbeagle led examples (one gpio, one pwm) to https://github.com/mvduin/overlay-utils ... completely untested obviously (other than that they compile) Nov 25 17:58:44 zmatt: for the network data activity led? Nov 25 17:59:39 for creating a led device that allows an external led to be controlled by kernel-defined triggers in general Nov 25 18:00:11 that's cool Nov 25 18:00:12 like the comments in the example explains, setting up the netdev trigger still requires configuration from userspace (unfortunately) Nov 25 18:00:37 ah Nov 25 18:01:42 (you could configure the trigger to "netdev", but it won't do anything until additional settings have been configured via sysfs, specifically the network interface to monitor and which activity to indicate (rx, tx, link)) Nov 25 18:04:04 Unfortunately at the moment my knowledge of Linux is still too low for these operations Nov 25 18:05:03 the led configuration shows up as a subdirectory of /sys/class/leds/ Nov 25 18:05:08 with a "file" per setting Nov 25 18:05:31 to change a setting you just write the value into that file Nov 25 18:06:27 (it's not really a file, sysfs is a pseudo-filesystem representing kernel objects and their properties, but it looks like a file and behaves more or less like one) Nov 25 18:06:50 =D Nov 25 18:08:18 abstraction above abstraction above abstraction..... Nov 25 18:09:01 ehm, no, it's exactly one layer of abstraction Nov 25 18:10:40 using the paradigm of a filesystem to represent a tree of kernel objects is a fairly obvious thing to do, since the kernel already has the infrastructure for defining filesystems and the APIs to access them, and userspace benefits from reusing a familiar concept and the tools that already exist for it Nov 25 18:12:00 still, it's sort of magic for me. I came from assembler and AVR where register's were only things mater :) Nov 25 18:14:04 I mean, yes Nov 25 18:14:15 that is indeed a very different environment to program in :) Nov 25 18:15:19 I don't want to lose my GF digging into linux deep :) Nov 25 18:21:32 zmatt: any way, I am grateful for your help! Seeya! Nov 25 21:06:12 made some progress!!! Nov 25 21:06:34 I know can boot with the cape attached and overlay loaded still no data on the screen Nov 25 21:07:53 question do I need to disable stuff to have an LCD cape, like the hdmi? my boot process does not kick out any glaring errors https://pastebin.com/0ktA7K9Z Nov 25 21:12:25 now* Nov 25 21:21:09 can you share the kernel log please? Nov 25 21:21:50 also it's showing an asynchronous bus fault at 21 seconds... generally speaking that's really bad Nov 25 21:22:35 that's basically something that should have crashed something, except the culprit can no longer be identified Nov 25 21:22:59 dang Nov 25 21:23:06 ok let me post the kernal log Nov 25 21:30:31 here is the kernal log Nov 25 21:30:32 https://pastebin.com/HW1rsfke Nov 25 21:32:56 a more complete version from 0 sec https://pastebin.com/KkwjjLP4 Nov 25 21:40:01 would be nice if they had something like ***ERROR*** in the mix so you can focus on that Nov 25 21:41:00 I see 3 instances of the word error Nov 25 21:41:06 will have to google them Nov 25 22:13:59 at first sight it looks like it recognized your display Nov 25 22:14:09 or, well, the DT declaration for it Nov 25 22:15:03 I think anyway Nov 25 22:16:52 I can probably dig up a tool I have somewhere to dump information from the drm device, but right now I'm too lazy Nov 25 22:36:12 yeah the show pins looks good Nov 25 22:36:28 that one error has connection to the ic2 Nov 25 22:36:31 or something Nov 25 22:36:35 and power management Nov 25 22:36:41 i will stare at it late r Nov 25 22:36:46 later * Nov 25 22:36:53 break time Nov 25 22:47:55 and bug you of course! Nov 26 00:58:09 Once a beaglebone black is connected online via ethernet can you ssh to it through that? I'm pretty sure there is, I just wanted to know if I could work on it while the BB is connected to a 5V power source and ethernet without being connected to my pc via USB Nov 26 00:59:34 yes Nov 26 01:26:45 To SSH to it through ethernet I need to setup a static IP? Nov 26 01:27:04 no Nov 26 01:28:43 Okay, guess I'll just look through more guides online Nov 26 01:29:06 often a local dhcp server will also be a local dns hence typically you can just connect to "beaglebone", or regardless of router the hostname "beaglebone.local" works at least on mac and linux, and maybe windows 10 (not 100% clear) Nov 26 01:30:20 Hmm okay I'll try that Nov 26 01:32:57 It worked, thank you very much Nov 26 02:07:42 beaglebone.local works? Nice. Nov 26 02:07:55 I could not sign in via ssh the other day. Nov 26 02:10:35 I used "beaglebone" Nov 26 02:14:06 Okay. Nov 26 02:15:11 For some reason I can only sign in via the COM port on Win. Nov 26 02:15:20 Is this natural? Nov 26 02:15:55 Or better yet, is there a .log I should access to see exactly what my issue has become? Nov 26 02:21:05 That was happening to me when I was working on the 2016 OS, but was fine when I updated Nov 26 02:21:16 Can you download SDKs and use them on beaglebone? Nov 26 02:21:49 that question is so vague as to be nonsense Nov 26 02:22:32 SDK for what? Nov 26 02:22:36 Ha. Nov 26 02:23:00 For Nordic BluetoothLE Nov 26 02:24:24 the nRF sdk is for nRF devices Nov 26 02:25:39 Right, I have an nRF bluetooth chip on an expansion board Nov 26 02:27:01 so, their sdk is for developing software to run on the nRF device... I can't imagine any reason why you'd want to use a beaglebone to develop software that's not going to run on the beaglebone itself Nov 26 02:28:04 (but you probably could if you really wanted to) Nov 26 02:28:26 I read the disclaimer! Nov 26 02:28:31 In the SRM. Nov 26 02:28:41 set_? Nov 26 02:28:55 I just thought people should read it, i.e. like it did. Nov 26 02:29:10 ?? Nov 26 02:29:13 ^ Nov 26 02:29:19 Please hold. Nov 26 02:29:41 https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual#this-document Nov 26 02:30:02 Below that heading are some nice ideas on disclaimers. Nov 26 02:30:27 ??? Nov 26 02:30:34 Consumer responsibilities and notices. Things like these ideas need to be known. Nov 26 02:30:38 I'm completely lost, why are you talking about / linking to this? Nov 26 02:30:53 randomly Nov 26 02:30:59 Oh. Nov 26 02:31:01 Sorry. Nov 26 02:31:19 I just thought it was an interesting subject about use for consumers and issuance.d Nov 26 02:31:53 set_: please stop, my brain is trying to flee out of my left ear Nov 26 02:32:14 Fine. Nov 26 02:32:35 Aceplosion: anyway, it would probably make more sense to use that SDK on a comfortable desktop system Nov 26 02:33:16 That makes sense, I'm just trying to figure out how to get the board to communicate with the bluetooth chip Nov 26 02:33:26 I'm still very green at this stuff Nov 26 02:34:57 that depends on the application running on the bluetooth chip Nov 26 02:36:15 That's fair, I'm downloading the sdk on my pc now. I have sensors with bluetooth chips on them in another box, and I want to read their output using the board and its bluetooth chip. That's pretty much my goal for now Nov 26 02:38:09 like, these nRF devices aren't "bluetooth chips" in the sense of something you connect to a host computer to provide it with generic bluetooth communication, they're microcontrollers with integrated wireless communication ability on which you can deploy your own application that uses bluetooth communication Nov 26 02:40:37 Well the sensors are already running with the nRF chip. I can connect to them via the nrf connect app on my phone. I'll just have to research a lot about this then Nov 26 02:41:02 That's interesting though, I didn't think of them as microcontrollers, thank you for the insight Nov 26 02:41:09 I'm reading through their documentation now Nov 26 02:42:57 regardless, it's mostly an nRF question, not a beaglebone question Nov 26 02:43:51 Hmmmm okay Nov 26 02:44:04 How long have you been working with this stuff zmatt? You're very knowledgable Nov 26 02:44:06 the only beaglebone-specific part is how to hook it up physically and configure those pins Nov 26 02:44:13 if e.g. a direct UART connection is used Nov 26 02:44:33 (if it's connected via usb then even that part is a non-issue) Nov 26 02:44:51 apart from that the beaglebone is just a linux system Nov 26 02:45:18 hence how to communicate with the device and use it to do what you want is no different than on any other linux system Nov 26 02:45:29 When anyone has some extra time, will you please paste in a service the contents of the original way /etc/nginx/sites-available/default? Nov 26 02:45:51 Aceplosion: and ehh.. dunno, quite a while Nov 26 02:46:00 depends also on the scope of "this stuff" Nov 26 02:47:11 set_: on the 2020-04-06 IoT image? Nov 26 02:47:46 Yes sir. Nov 26 02:48:06 https://pastebin.com/9ApEBW8L Nov 26 02:48:39 That be it. Thank you. Nov 26 02:50:01 Sorry for interrupting. Nov 26 02:50:31 IRC supports multiple conversations at once :P Nov 26 02:51:04 I know but you guys were getting down to 'da biz of things but I had to ask b/c my nginx config. seems a big awkward. Nov 26 02:52:07 I was thinking that my nginx config. directly had something to do w/ my IP Address as 192.168.7.2 and that IP being accessible. Nov 26 02:52:11 it was a clear and sane question with a quick and easy answer, I'll take those any day :P Nov 26 02:52:37 That's fair compared to my questions haha Nov 26 02:52:42 Got it. Okay. Still, oddities come and go. So, please bear w/ me. Nov 26 02:52:48 I'll try and be more direct next time Nov 26 02:52:52 Done for now. Nov 26 02:53:02 You weren't interrupting set Nov 26 02:53:51 "My ears are silenced." I cannot hear you any more. Ha. Nov 26 02:54:11 Sorry. Nov 26 02:55:06 I am super excited b/c I feel like I finally "broke" into my own board since i could not use it for so long. Nov 26 02:55:19 I am beside myself. Nov 26 02:55:38 Glad you could access your board Nov 26 02:56:26 ME TOO! Nov 26 02:57:43 It was those COM ports that kept giving me trouble and I could not figure out what happened. Luckily, the old, trusty router gave me the "new" IP Address. Nov 26 02:58:31 Nice, I'm lucky to not have run into that issue after working with the latest OS. Idk why it happened to me with the older versions **** ENDING LOGGING AT Thu Nov 26 02:59:57 2020