**** BEGIN LOGGING AT Fri Dec 24 02:59:56 2021 Dec 24 03:25:16 Hello, how should I interpret the error message Could not initialize timer (err -19) when trying to boot a pocket beagle from a system created with buildroot? Dec 24 03:28:28 Hmm. Good question! I bet there is something online. Let me look. Dec 24 03:32:00 I found that by using the provided beaglebone defconfig, the system would start up correctly and by comparing the two config files it appeared that the error most likely to be caused by the kernel, but I was just wondering if I could've found this out from the error message? Dec 24 03:34:43 Oh! Dec 24 03:34:53 You want commands I am assuming... Dec 24 03:35:52 I looked up err -19. I am unfamiliar w/ this error message but if dmesg is installed, try that command. Scroll. And...if you have systemd, use journalctl -xe if you have sudo privileges. Dec 24 03:36:59 Just for reference, I do not use the Pocket Beagle for whatever reason but I am sure the Linux kernel may be similar. Dec 24 03:38:03 U-Boot SPL 2021.04 (Dec 15 2021 - 14:32:47 +1100) Dec 24 03:38:03 Trying to boot from MMC1 Dec 24 03:38:04 U-Boot 2021.04 (Dec 15 2021 - 14:32:47 +1100) Dec 24 03:38:04 CPU  : AM335X-GP rev 2.1 Dec 24 03:38:05 Model: TI AM335x PocketBeagle Dec 24 03:38:05 DRAM:  512 MiB Dec 24 03:38:06 WDT:   Started with servicing (60s timeout) Dec 24 03:38:06 Could not initialize timer (err -19) Dec 24 03:38:10 This is the full readings from the serial port Dec 24 03:38:29 the system doesn't seem to start and it just loops the error message over and over again Dec 24 03:38:52 Oh. Dec 24 03:38:56 I thought you said it booted? Dec 24 03:39:28 Okay... So, did the entire command to start your buildroot build run successfully? Dec 24 03:39:57 No errors or warnings? Dec 24 03:41:49 Also, I have, when using Buildroot, tried different u-boot versionings and different kernels. This is a lengthy process that has not cure to me. But! Every so often I get it booted. it just takes time to use the correct versioning and kernel from what I have seen. Dec 24 03:42:33 I had been following the buildroot training instructions to create a beaglebone image, and that didn't seem to work. However, using the provided defconfig file for the beaglebone works, and the only significant difference i could find between the two .config files was the kernel that was used Dec 24 03:42:54 Adding different arguments to your make command after menuconfig will prove valuable. Dec 24 03:42:55 Hmm. Dec 24 03:43:02 Okay. Dec 24 03:43:14 I was just wondering if I was able to come to this conclusion quicker by just looking at the error messages I had gotten from the initial boot Dec 24 03:43:22 Oh. Dec 24 03:43:44 Got it. Sorry. I am not familiar w/ that (err -19) in the logs. Dec 24 03:43:46 I can keep checking. Dec 24 03:45:15 time.c ? Dec 24 03:48:39 Maybe you need to set the date? Dec 24 03:52:04 U-Boot 2021.04 (Dec 15 2021 - 14:32:47 +1100 It seems that u-boot has the date as one day behind that might that be the problem Dec 24 03:54:03 Hmm. Oh and if you get bored one day, sent your commands in w/ the allocated kernel parameters picked as options. I can probably help one day. It is almost 10:00 now. I might need to retry tomorrow or after Christmas. Dec 24 03:54:59 Ok, thank you very much for the help today Dec 24 03:56:05 Also: Part III in the developers guide may help >>> https://buildroot.org/downloads/manual/manual.html#faq-boot-hang-after-starting . Dec 24 03:56:44 I think when I booted last, the files needed for booting w/ a network were located in a specified location. Dec 24 03:57:33 Hmm, I'll have a look Dec 24 03:57:48 Okay. Until next time. Snore! Dec 24 03:57:56 Zzzzz. Dec 24 03:58:28 Oh and by the way, I am learning as much as feasibly possible about buildroot in case the coffee hits the fan. Dec 24 03:58:31 I had a similar problem running U-Boot on a stm32. The problem was a missing property in the device tree from the u-boot source Dec 24 03:58:47 You guys chat. I am out. Dec 24 04:01:13 But, when I tried with a different kernel the device seemed to boot without any problems? Dec 24 04:01:32 So I had assumed that the problem was with the kernel itself and not the u-boot loader Dec 24 04:07:35 I compiled u-boot with the DEBUG flag, then I got "ofnode_read_prop: tick-timer: ", also, that error msg is in the u-boot source.. I don't know if it's also in the kernel Dec 24 04:10:51 Hmm, so since the error message is from the u-boot source it is more likely to be a problem due to u-boot than the kernel itself? Dec 24 04:17:01 Oh! Also, try multiple, different toolchains to test... Again. Three main components (Uboot, toolchain, Kernel). Mix and match until perfection! I cannot wait until you all figure out the less stressed way of compilation. I am waiting too! Dec 24 04:19:03 Oh and I found this idea a long time ago outside of buildroot: https://forum.digikey.com/c/eewiki/linux-guides/71 . Dec 24 04:21:38 Ok, I'll have a look around thank you Dec 24 04:24:48 I have been reading about buildroot. It seems things need to be associated a specific way in specific files. Dec 24 04:27:05 I think you can account for br2_package_libWhatever in the Config.in file in case something is missing. Dec 24 04:28:07 Instead of building the same kernel and other components again and again under the same name, also, make a new name for each build and mark it down. Dec 24 04:28:23 There was something about buildroot that makes incremental building a pain. Dec 24 04:29:50 I had been creating completely new buildroot directories and testing different settings, so I don't think that should be much of a problem Dec 24 04:30:59 Oh. Okay. I just remember using make constantly instead of make MyNewFile during builds. This created issues as it kept iterating the old build w/ the same properties. Dec 24 04:32:05 Ok, I will keep that in mind, Thank you so much for your help. Dec 24 04:33:21 I also used a specified toolchain outside of what is offered internally. ARM has them and so does linaro (for now). Dec 24 04:33:26 No issue. I try. Dec 24 04:33:35 what repo are you using? Dec 24 04:39:38 Me...none. Dec 24 04:42:06 the buildroot one Dec 24 04:43:05 I Dec 24 04:43:15 I'm using this https://git.buildroot.net/buildroot repo Dec 24 04:45:57 11-2021 Dec 24 11:41:05 Um, hello and how does one get WiFi up and runnin' on the BBBW w/ the Bullseye Distro? Dec 24 12:04:42 It boots and it keeps booting. But! No the WiFi! No the WiFi. Send rations! Dec 24 12:45:39 apt is loaded and firmware-ti-connectivity is loaded but... Dec 24 12:48:16 networkd and network-manager is not loaded. Dec 24 12:48:18 Aw! Dec 24 13:01:50 So, I checked the outdated udev rule dept. and notta. I think NetworkManager in Bullseye is leaning towards something different that is not udev rules for setting up interfaces in /etc/network/ . Dec 24 13:02:38 But...damn debian is not stating what exactly their method of use will be like currently or what the future may bring. Dec 24 13:15:48 Some stuff is working! I can get to Node-red online and a VSCode thing. Dec 24 13:15:50 It works! Dec 24 13:16:07 No updates or upgrades, no git, and no blah. I know, I am in the way. Enjoy today! Dec 24 17:43:17 rcn-ee: amazing, we just discovered that someone in the world has a pair of the speakers we make connected to a network where DHCP hands out public unfirewalled IPv4 addresses Dec 24 17:44:35 (fortunately we made sure sshd only accepts public-key authentication) Dec 24 19:41:14 I am like a spoiled rug. Leave me alone w/ my BBB! Dec 24 19:43:55 Oh and sorry but did anyone figure out how to add wifi to the BBBW w/ Bullseye? I am asking b/c I would like to know, i.e. outside of me being spoiled w/ my spoils. BBB! Dec 24 19:46:49 Santa can wait! Dec 24 19:50:09 "Silent Night" is my favorite song during Christmas... Dec 24 19:50:19 Can someone tell me now? Dec 24 19:54:42 Aw! Dec 24 19:56:30 probably a wpa-supplicant config file? unless there's a utility/script to help with setting up wifi yet Dec 24 19:56:48 Oh. Dec 24 19:56:57 @zmatt: Do you hate Christmas? Dec 24 19:57:15 I do not hate it. I like it. Family, yelling, fun! Dec 24 19:57:27 The reason I bring that up is this idea. Dec 24 19:57:51 A long time ago, my bot was supposed to listen to me w/ a specific library during Christmas. Dec 24 19:58:27 But...the lib. was deprecated and the people from the college moved on in the speech recognition "game." Dec 24 19:58:51 Anyway, thank you for answering. I will try wpa-supplicant and the config file. Dec 24 19:59:48 config file is probably /etc/wpa_supplicant/wpa_supplicant.conf or /etc/wpa_supplicant/wpa_supplicant-wlan0.conf depending on how it's been setup, assuming it has been Dec 24 20:02:06 Right. Off to look. Dec 24 20:02:53 I tried so many files so far. I will most likely have to restart something or another thing. Dec 24 20:03:30 if you modify the config file you can ask wpa-supplicant to re-read it using "wpa_cli -i wlan0 reconfigure" Dec 24 20:03:45 Nice. Dec 24 20:04:13 Thank you kind gent. Now, Santa will be gracious upon thee or whatever. Time to test! Dec 24 20:09:44 FAIL Dec 24 20:09:49 I tried that command. Dec 24 20:10:21 I tried sudo wpa_cli -i wlan0 reconfigure b/c w/out sudo, it does not do anything. Dec 24 20:10:37 that's weird on both counts Dec 24 20:11:02 Now, I set up a loopback and wlan0 inet thing in networking in that specified file in /etc/wpa-supplicant/ . Dec 24 20:11:16 uhh what? Dec 24 20:11:34 what are you talking about? Dec 24 20:11:57 That is what returned in the terminal, e.g. FAIL. Dec 24 20:12:13 not that, what you just said Dec 24 20:12:17 Also, is this a good routine to look over for this stuff: https://wiki.debian.org/WiFi/HowToUse ? Dec 24 20:12:21 Oh. Dec 24 20:12:34 Oh. yea. Um, let me better show you in a paste. Dec 24 20:12:35 no, it's not Dec 24 20:12:45 Oh. Okay. Dec 24 20:12:59 almost none of the info on that wiki page is applicable Dec 24 20:13:08 I figured this much. Dec 24 20:13:10 Argh. Dec 24 20:13:27 I guess I could download the buster image and see how it's setup Dec 24 20:13:35 Oh. Dec 24 20:13:40 Do not worry. Dec 24 20:13:43 I will check another board. Dec 24 20:13:53 I just was using connmanctl for so long. Dec 24 20:14:00 I never really thought of other ideas. Dec 24 20:15:40 https://pastebin.com/KrbayMt5 Dec 24 20:16:17 wtf Dec 24 20:16:25 that config file is utter nonsense Dec 24 20:16:26 I know. Dec 24 20:16:31 which is why reconfigure said FAIL Dec 24 20:16:41 I understand. I was listening to a wiki. Dec 24 20:16:43 Ha. Okay. Dec 24 20:17:10 well no wiki will have told you this, since you're mixing syntax of different config files Dec 24 20:17:23 You are right. Dec 24 20:17:26 I just added to it all. Dec 24 20:18:04 just to clarify, you want it to connect to a wifi? or did you mean you want it to act as wifi access point? Dec 24 20:18:16 I want to connect to wifi. Dec 24 20:18:34 https://pastebin.com/0CenbWey Dec 24 20:19:18 That seems dangerous. Dec 24 20:19:24 Is this okay? Dec 24 20:19:55 Just post my credentials in an open file that is writable by sudo? Are you sure? Dec 24 20:20:33 I mean, connman also stores your credentials in a file Dec 24 20:20:59 if a computer needs to be able to connect to wifi on its own, it needs to store the credentials *somewhere* Dec 24 20:21:04 and any file can be accessed with sudo Dec 24 20:21:23 I am not trying to get you to do other work...Oh. Well, there I go again. Getting ramshafted by technology w/out knowing it. Should I use some encryption or a Santa Sley? Dec 24 20:21:48 Hash the Santa Sley part. Dec 24 20:22:39 I mean, I can do one of those odd 128-bit ram-jams of encryption. Dec 24 20:22:51 Or more...whatever really. Dec 24 20:23:48 Thank you sir. Dec 24 20:24:24 Oh! Dec 24 20:25:00 it's possible to use the wpa_passphrase utility to hash the password... but it should be noted that that hashed password is equally useful to connect to the wifi network as the original password is, the main benefit is that someone looking over your shoulder when you edit the config file probably can't memorize a 64-character hexadecimal string Dec 24 20:25:02 Can I type network1 { blah, blah, blah } && network2 { more, more, more } ? Dec 24 20:25:19 you can put multiple network {...} blocks in the config file Dec 24 20:25:30 Nice. Dec 24 20:26:05 So, I can ssh and sftp from some other location to look at my files and get/put them on the BBBW! Dec 24 20:26:07 Nice. Dec 24 20:26:12 ? Dec 24 20:26:17 No? Dec 24 20:26:23 Well. Dec 24 20:26:42 it will connect to only one network, whichever has the strongest signal Dec 24 20:26:47 I mean, w/ separate networks, one would think I could access. Oh. Nevermind. I can get joggled. Dec 24 20:26:57 Okay. Nice and smart. Dec 24 20:27:10 I will try right now. Dec 24 20:27:17 it's mostly useful if you move the bbb between different locations Dec 24 20:28:07 Right. Or around an extremely large house w/out hotspots or tethers? Dec 24 20:28:48 My system is so jacked up right now. It says I am offline but I can communicate via chat. Odd! Dec 24 20:28:56 even if you have multiple wifi access points in a house, you'd normally give them all the same wifi network name Dec 24 20:29:40 Oh! I never do that...I always try to make the access point another name. I have a thing and access point. The thing handles Ethernet. Dec 24 20:29:52 The access point handles wifi. Dec 24 20:30:22 I am in a tiny home w/ many shitty, if I can say so (Cox), connections. Ha. Dec 24 20:30:36 That is their actual name. Dec 24 20:30:47 ISPs and their odd names. Dec 24 20:31:03 It is like that type of dog. Shi Tsu. Dec 24 20:31:16 For some reason, that never gets old. Dec 24 20:32:20 also, for improved security it is worth telling wpa-supplicant to require the use of WPA2 and CCMP like this: https://pastebin.com/zdBBKsSV Dec 24 20:32:29 Okay. Dec 24 20:32:45 so that it will not even attempt to connect to a wifi access point with the same name that doesn't support proper encryption Dec 24 20:33:15 Nice. That is extra smart. I never really thought about connections like w/ what you just presented. Dec 24 20:33:38 (this is assuming your access point does in fact support proper encryption... though if it doesn't it probably belongs in a museum) Dec 24 20:34:06 It is easy to stroll in, say high, and then access "delicate" info. on purpose when close enough to specific hot spots I guess. Dec 24 20:34:11 There is so much to learn. Sheesh. Dec 24 20:34:39 FAIL == still the print out. Dec 24 20:34:56 or the error on the terminal, FAIL . Dec 24 20:36:55 I will brb. here and there. Something is yelling outside. I need to make sure people are not w/ pitch forks and knives outside my door. Dec 24 20:38:04 hmm, is there a page linking the latest bullseye testing images? https://elinux.org/Beagleboard:Latest-images-testing and https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots still only list buster images Dec 24 20:39:12 zmatt, i'm going to launch the first monthy bullseye image on the first.. Dec 24 20:41:16 it'll look similar to this list, just with lots of xyz is now abc... https://forum.beagleboard.org/t/debian-10-x-buster-monthly-snapshots/31203 Dec 24 20:41:54 set_: so what are you running right now? (and why?) Dec 24 20:42:02 fixed the BBGG last night, so bluetooth works again on that board, here's the snapshot from this morning.. https://rcn-ee.net/rootfs/debian-armhf/2021-12-24/ Dec 24 20:42:20 Oh. Dec 24 20:42:26 I saw on the forums... Dec 24 20:42:51 A thing. This thing had rcn-ee.com and rootfs debian distros galore. Dec 24 20:43:03 I picked a couple up and tried them out. Dec 24 20:43:29 set_, well i've been spending a lot of time cleaning up bullseye.. Dec 24 20:43:29 5.10.80-ti-r32 Dec 24 20:43:33 "some thing I saw somewhere" .. you're always so great with being specific Dec 24 20:43:43 Oh. No issue. Dec 24 20:43:43 I know. Dec 24 20:43:47 and the kernel version is not useful information Dec 24 20:44:02 Let me get the dogtag. Sheesh. Dec 24 20:44:09 set_, only that it's old and broken. ;) Dec 24 20:44:12 sudo beagle-version ;) Dec 24 20:44:32 BeagleBoard.org Debian Bullseye IoT Image 2021-12-23 Dec 24 20:44:33 Oh. Dec 24 20:44:36 It is broken. Dec 24 20:44:41 Let me post that in a paste. Dec 24 20:45:00 set_, on the "BeagleBone Green Gateway" it should 'hardlock' on bootup.. Dec 24 20:45:09 I am on BBBW. Dec 24 20:45:15 yeah that's fine.. Dec 24 20:45:29 Hahhaha. Okay. Let me get that paste out. Dec 24 20:45:40 no reason too.. Dec 24 20:45:45 i know what your running.. Dec 24 20:45:56 its' the iot image.. Dec 24 20:46:35 Okay. No issue. Dec 24 20:46:43 I have a lot of GPIOs! Dec 24 20:47:03 And...UART works too but does not register as a device. Dec 24 20:47:12 Actually, scratch that. Dec 24 20:47:14 what's the issue? Dec 24 20:47:32 It was my computer not being able to access the FTDI cable. Dec 24 20:48:02 For reading the Uboot prompt(s), my FTDI cable and the BBBW do not comprehend one another. Dec 24 20:48:46 I used tio /dev/ttyUSB0 and it reads info. but it does so w/ or w/out the FTDI cable attached. This made me think. Dec 24 20:49:03 It is most likely my 'puter. Dec 24 20:49:07 zmatt, going thru my list of bullseye debian packages... what do you want to call https://github.com/mvduin/overlay-utils Dec 24 20:49:29 rcn-ee: does it make sense to package that? Dec 24 20:49:31 zmatt, i also want to package show-pins.pl... so 2 debian package names. ;) Dec 24 20:49:49 show-pins hasn't had a .pl suffix since... forever Dec 24 20:49:51 zmatt, the other option, pre-git clone it under /opt/source/ Dec 24 20:50:57 yeah that sounds more sensible to me Dec 24 20:50:59 set_, did you accently write to /dev/ttyUSB0 at some point whithout a cable present? you might have created a file there.. thus messing everything up.. Dec 24 20:51:19 Hmm. Maybe but I seriously doubt it. Dec 24 20:51:44 I really do not think I wrote anything to /dev/ttyUSB0 w/out the cable present. Well. Dec 24 20:51:58 I did type tio /dev/ttyUSB0 w/out the FTDI cable present. Dec 24 20:52:03 if you remove the cable, is that node still present? you are dialout? Dec 24 20:52:15 I am on dialout. Dec 24 20:52:44 rcn-ee: the bulk of overlay-utils is its examples, which people may want to modify, or use to create their own overlay, so it should be in a writable directory and not be unintentionally overwritten if they update their packages Dec 24 20:52:46 Right now, the "node" is present if it is hotplugged or hotpulled. Dec 24 20:53:23 zmatt, perfect, so git clone would make sense, that directory is already masked 1000:1000, so they just have to use it or git pull to update it.. Dec 24 20:53:44 set_: just check if a new /dev/ttyUSB* device shows up when you plug in the ftdi Dec 24 20:53:46 set_, as long as "nothing" is plugged in and using it, nuke it as root, then replug it in.. Dec 24 20:54:06 I wouldn't suggest that Dec 24 20:54:26 unless it really is a normal file (check with ls -l) Dec 24 20:54:34 it might just be a random internal device Dec 24 20:54:42 No /dev/ttyUSB* shows up on the BBBW at all when plugged in. Dec 24 20:54:50 Hmm. Dec 24 20:54:54 none is expected there Dec 24 20:55:12 Oh. Okay. Hmm. Dec 24 20:55:13 I meant on the computer where you're plugging it into usb Dec 24 20:55:21 set_, where is the "usb" plugged into.. your computer or the bbgw? Dec 24 20:55:21 Right. Dec 24 20:55:32 also wtf is tio Dec 24 20:55:33 Computer. Dec 24 20:55:45 it's a very simple serial terminal.. Dec 24 20:55:51 ah Dec 24 20:56:00 rcn-ee told me about it years ago. CTRL-t then q to exit. Dec 24 20:56:06 dirt simple: https://github.com/tio/tio Dec 24 20:56:06 Ha. Dec 24 20:56:20 Nothing wrong w/ dirt "don't" hurt. Dec 24 20:56:43 Oh. Dec 24 20:56:47 Okay. So, back to it. Dec 24 20:56:58 nice, that's useful. I generally use screen for that purpose, but that's something I'd hesitate to recommend to other people, especially since it's easy to accidently still have it running without realizing it Dec 24 20:57:04 um, the device showed up after plugging it in many times. Dec 24 20:57:43 I cannot remember what my computer called it... Dec 24 20:57:46 Let me check again. Dec 24 20:57:49 it supports autoconnect out of the box too.. i always fail when using screen.. Dec 24 20:58:57 TTL232R-3V3 yep and yep. Dec 24 20:59:10 It is working again. Dec 24 20:59:18 good, it's alive! Dec 24 20:59:23 Yep! Dec 24 20:59:26 Yes sir. Dec 24 20:59:47 I don't think I've ever felt a desire for autoreconnect... I guess for something like the usb-serial console of the beaglebone, because it temporarily disappears when you reboot? Dec 24 21:00:54 yeah it works nice when rebooting a beagle with usb-serial console.. it just comes right back up... Dec 24 21:01:36 Bare metal as they call it! It works wonders on speed. Dec 24 21:01:39 I've never used the usb-serial console... in part because I almost never connect a beaglebone via usb, and if I do I have a network connection to it and just ssh Dec 24 21:02:16 the only time I've needed a serial console is when things are so fucked that the usb-serial console probably wouldn't be available either Dec 24 21:02:33 I get that at times. Dec 24 21:02:48 The serial console is busted and quits and hangs. Dec 24 21:04:31 I remember trying to get into the system. I had to do this for 10 seconds then it would quit. Another two mintues and then it would quit. Dec 24 21:04:52 set_: whatever you're talking about is not what I was talking about Dec 24 21:05:04 do you remember which kernel? Dec 24 21:05:16 a month, or year ago? Dec 24 21:05:44 4.14.x Dec 24 21:05:58 Before the udpate to 4.19.x. Dec 24 21:06:14 Even my silly bot started to act oddly and was out of control. Dec 24 21:07:01 weird, as 4.14.x was especially rock solid a few of my installs.. it took awhile before 4.19.x(eventually 5.4.x) till they were as solid again in my testers.. Dec 24 21:08:04 I had all kinds of trouble before the update to the new kernel for reasons I did not look into or explain well at the time. Dec 24 21:10:59 I need to reboot. My old computer crashed and this one is on the fritz. Reboot! Dec 24 22:32:14 Some guides use arm-linux-gnueabihf.... for compiling the kernel... (chicken and egg situation?);  isn't that for making normal linux programs, using glibc? Dec 24 22:33:10 doesn't matter, kernel doesn't use any of the headers or libraries from the toolchain Dec 24 22:34:57 same for other baremetal projects like u-boot, or my tiny tiny baremetal asm example for the bbb: https://github.com/mvduin/bbb-asm-demo/blob/master/Makefile#L1-L3 **** ENDING LOGGING AT Sat Dec 25 02:59:56 2021