**** BEGIN LOGGING AT Thu Oct 27 02:59:57 2022 Oct 27 07:09:08 We have Beaglebone black wifi boards that are not connecting to the local wifi network. We are able to capture the Journalctl logs. Please do the needful in this issue. Logs are available in the pastebin link: https://pastebin.com/k3sUzG3m Oct 27 13:18:23 Hi zmatt , Oct 27 13:18:41 someone said that after the patching I needed to go to kernel device tree adjust the console uart used for output Oct 27 13:18:52 that just means selecting the baud right? Oct 27 13:19:07 uart0_person72: I'm pretty sure no DT changes are needed Oct 27 13:19:37 unless you want the console to actually *work* and not be merely out of the way Oct 27 13:19:52 but my impression was you don't actually care about the console, you just want it off of uart0 Oct 27 13:20:03 yes that's it Oct 27 13:20:09 then the person misunderstood me Oct 27 13:20:12 ok Oct 27 13:20:37 about the uart, do I need to set the baud anywhere, or can I just set inside a script using a serial library? Oct 27 13:21:08 you configure the baudrate (and other settings) of the serial port when you open the port in your software Oct 27 13:22:16 ok, thanks, thank you very much Oct 27 13:23:21 you are always so helpful. A few months ago when I was doing a project with pocketbeagle capes you also helped me a lot **** BEGIN LOGGING AT Thu Oct 27 13:52:39 2022 Oct 27 20:37:41 zmatt so I did the steps, but the pocketbeagle is not booting Oct 27 20:39:09 that's unfortunate.... maybe check the serial console to see what's going on? oh wait never mind :D Oct 27 20:39:32 I was expecting for that joke Oct 27 20:39:37 hehehe Oct 27 20:43:21 So I did everything we talked about it. I downloaded the u-boot, made the modifications to the file you said, every ttys0 became ttys1 and then saved. Then I installed the gcc cross compiler and the dependencies, used the three commands to compile. Found which was the sd name in the machine, that /dev/name_device, used the command you told me to do Oct 27 20:43:21 the backup, then used that two commands to install the two files Oct 27 20:44:21 might be a good idea to actually first try this without making any changes to u-boot, just to confirm the build is okay and this much newer u-boot is compatible with your current image Oct 27 20:45:20 you mean do the same steps but without replacing tty? Oct 27 20:45:24 yeah Oct 27 20:45:35 and obviously skip making the backup this time since you already have one Oct 27 20:46:17 git clone -b v2022.04 https://github.com/u-boot/u-boot --depth=1 Oct 27 20:46:24 maybe it's because its from april? Oct 27 20:46:31 ? Oct 27 20:46:42 v2022.04 Oct 27 20:46:46 what about it? Oct 27 20:47:02 maybe it didn't work because the version it's from april and we have newer? Oct 27 20:47:32 if this version doesn't work, that'll be because it's way too new for your image and you need an older one :P Oct 27 20:47:48 oh ok Oct 27 20:47:52 now I understand Oct 27 20:49:35 probably it's that because of the date in the image I got it Oct 27 20:49:36 AM3358 Debian 10.3 2020-04-06 4GB SD IoT Oct 27 20:50:34 it's just a guess, let's first see if it works without the tty customization Oct 27 20:50:42 ok Oct 27 20:50:44 I will do it Oct 27 21:02:40 ok without modifications it works Oct 27 21:03:34 so only Oct 27 21:03:59 replacing the instances of ttys0 doesn't work Oct 27 21:42:21 so rcn answered my last question and said I need to replace in more files Oct 27 21:43:16 in this link(https://forum.beagleboard.org/t/using-uart0-as-uart/33062/5)  where the lines are highlighted Oct 27 21:44:24 I don't understand in board/ti/am335x/board.c if I need to replace return &eserial1_device for return &eserial0_device or remove it altogether Oct 27 22:04:02 ok they said eserial1_device = ttyS0 Oct 27 22:04:35 to I just need to find out if eserial2_device is ttyS1 then I can replace them Oct 27 22:52:21 Hi, I just bought a beaglebone black and I'm trying to get started but I can't download the drivers. I have a Mac with BigSur 11.3 and I'm using the USBA-USBC connector that comes with the beaglebone. Oct 27 22:52:47 Guest7738: no drivers should be needed Oct 27 22:53:04 usbc ? the bbb has no usbc Oct 27 22:53:24 it has mini-usb Oct 27 22:53:39 sorry mini-usb Oct 27 22:55:02 How do I access the Linux terminal on the beaglebone then? Oct 27 22:56:50 it *should* show up as network interface when connected via usb.... though I do vaguely recall there was some kind of issue with apple having managed to break something in newer versions of macos, but I think that has already been worked around in the current beaglebone image? Oct 27 22:59:07 of course if you have trouble with usb networking, connecting it via ethernet should work as an alternative (in which case you'd access it using the hostname beaglebone.local, e.g. "ssh debian@beaglebone.local") Oct 27 23:00:19 rcn-ee: do the 2020-04-06 images already use CDC-NCM instead of CDC-ECM as workaround for the macOS issue? Oct 27 23:01:22 I'm not sure what you mean by the network interface and current beaglebone image. There's a drive that appears on my desktop that is called Beaglebone and it has files like App, Drivers, scripts,  and static Oct 27 23:01:36 yeah you can ignore that drive Oct 27 23:01:47 I don't think there's anything of use on there Oct 27 23:01:59 by network interface I mean... network interface Oct 27 23:02:41 to access the beaglebone via ssh or http you need a network connection to it... this can be done either via ethernet or via usb Oct 27 23:03:10 people generally connect via usb because that allows for a single cable to be used for poewr and data Oct 27 23:03:16 *power Oct 27 23:03:58 How do I check that the network is connected? I'm using the usb cable Oct 27 23:05:54 Guest7738: it would show up in networking in system preferences Oct 27 23:06:31 jkridner: the connection status thing of https://beagleboard.org/getting-started#step2 no longer works because beagleboard.org has HSTS enabled Oct 27 23:06:49 so you can't go to the http:// version Oct 27 23:07:19 Guest7738: or just try ssh debian@beaglebone.local in the terminal Oct 27 23:07:43 which should work if you have any network connection to the beaglebone Oct 27 23:08:09 I don't have network connection to the beaglebone Oct 27 23:08:30 I'm trying to manually enter the IP address. Would it be 192.168.6.2? Oct 27 23:10:25 manually enter? Oct 27 23:11:58 if you don't have a network connection to it when connected via usb then my guess would be the system on the beaglebone doesn't have the workaround for the mac issue yet... Oct 27 23:12:55 I don't know if that means it happens to have a really old system (e.g. this beaglebone happened to have been lying on some shelf in a warehouse for a long time before you got it) or maybe the latest official image (2020-04) doesn't actually include this fix yet Oct 27 23:13:00 I'm in Network in Systems preferences on the mac. Under The beagleboneblack, there's configure IPv4 and on the dropdown menu it says manual Oct 27 23:13:19 don't do that, use automatic (DHCP) Oct 27 23:13:29 but wait, you're saying the beaglebone *does* show up as network interface? Oct 27 23:13:49 It shows up but it says it's not connected Oct 27 23:13:55 uhhh Oct 27 23:14:48 I'm not using ethernet, is that part of the issue? Oct 27 23:14:50 that doesn't really make sense... if it can detect the interface it should implicitly have a connection Oct 27 23:15:33 using ethernet would be a workaround, but that doesn't explain why the usb network interface shows up yet isn't working Oct 27 23:16:55 Is there a key for the wifi I'd have to enter for the beagleboard to connect? Oct 27 23:17:11 the beaglebone black doesn't support wifi Oct 27 23:17:27 unless you have a beaglebone black wireless (which has wifi+bt *instead of* ethernet) Oct 27 23:21:03 Should I reset the beaglebone? Oct 27 23:22:39 I don't see how that would help Oct 27 23:25:29 you could try using ethernet connection as a workaround, or reflash the beaglebone to a newer image which includes the fix for this issue, e.g. https://rcn-ee.com/rootfs/bb.org/testing/2022-10-10/buster-iot-armhf/bone-eMMC-flasher-debian-10.13-iot-armhf-2022-10-10-4gb.img.xz Oct 27 23:26:22 (as the name suggests this is an eMMC-flasher image... write it to a microSD card using Etcher (https://etcher.io/) and then boot the beaglebone from that sd card and it should proceed to automatically reflash the eMMC) Oct 27 23:28:07 (you could also use a bullseye testing image instead of a buster image, but the bullseye images are still somewhat experimental) Oct 27 23:29:10 Guest7738: this is assuming the issue is the one I'm thinking of... I'm not a mac user myself and don't see many mac users here so I don't know whether there's any other mac-specific issues that people might run into Oct 27 23:30:29 ok, I'll have to buy an SD and adapter before I can do that Oct 27 23:32:09 that's a useful thing to have anyway Oct 27 23:36:04 Ya, I figured I'll need the extra storage Oct 27 23:36:12 for what? Oct 27 23:39:26 I'm using the beagle mostly for data processing/analysis, so I think it'll need more storage than what's already on there Oct 28 01:05:48 Hey guys/gals. It is almost Friday Funday! Oct 28 01:09:17 and finally, i.e. yesterday! I finally got the build process down pat again! I know, I know. Everyone already knows. Oct 28 01:09:36 I had to remember what happened and when. Then, a wild guess. Now, building! **** ENDING LOGGING AT Fri Oct 28 02:59:56 2022