**** BEGIN LOGGING AT Fri Dec 31 02:59:56 2021 Dec 31 06:05:33 hm ok, so I've got a serial console and am looking at this suspect beaglebone Dec 31 06:05:47 I'm running the latest default image, off an SD card Dec 31 06:06:09 eth0 comes up, but if I send DHCPDISCOVER with dhclient, I cannot see the DHCPOFFER from my router Dec 31 06:06:19 I know it's being made, because I see it in LuCi's logs... Dec 31 06:06:54 Does this point to hardware failure, misconfigured uboot, ... ? Dec 31 06:25:19 In uboot the phy does come up on mdio address too, but I mean I can see the interface from debian, etc. etc. and one direction clearly works Dec 31 06:25:29 It just...cannot see the dhcpoffer for some reason (tm) Dec 31 06:28:55 ah nvm Dec 31 06:30:07 ah no no, that is right -- i thought i was looking at another client but I see the mac addr there Dec 31 06:32:50 It does come up on mdio addr 2 but the image seems to be able to deal with that just fine Dec 31 06:45:22 Ok, the LAN8710 register contents tells me: BCR = 0x1000 (auto-negotiate mode, not in reset), BSR = 0x7809 (100basetx and some-other-stuff-capable, can autonegotiate, supports extended capabilities) Dec 31 06:49:02 No fault is shown in the auto negotiation advertisement register, expansion register says no faults & auto-negotiation is possible. Not sure what else to check in there Dec 31 06:49:27 guess it's getting about time to check physical continuity and then blame software again... Dec 31 06:51:06 "cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !" but the symbol error register...reads as 0 Dec 31 08:05:00 mewt: maybe phy got damaged? Dec 31 08:06:02 yep, seems like that's about all I can think now, or something else in the path... Dec 31 08:06:19 we had a case where a customer connected the ethernet port to a phone line... it kinda survived, except after that phy could no longer detect link changes without manually resetting the phy Dec 31 08:06:24 I didn't read closely enough in the LAN8710 datasheet to see how that register stuff works Dec 31 08:06:34 hmmm Dec 31 08:07:05 It just seems odd it'd read fine over MDIO and have only one way broken, but I guess it could also be stuff later in the chain Dec 31 08:07:39 I guess I could try to probe pins Dec 31 08:09:20 It does have near and far-end loopback to play with too right? Dec 31 08:09:32 near-end would rule out any digital issue Dec 31 08:12:37 There's also some kind of link integrity test. But there's no way I could look at that til tomorrow, much too tired Dec 31 08:19:55 Seems quite hard to get another one right now, as well -- backordered everywhere I looked... so it's probably worth trying a bit more Dec 31 08:29:33 if I have /dev/ttyO4 that means it's already enabled right? we have a peripheral connected to it but I'm unable to talk with it at the moment Dec 31 08:55:24 >I cannot see the DHCPOFFER from my router Dec 31 08:55:44 sorry, that should read "I cannot see the DHCPOFFER from the beaglebone". It is logged by LuCi Dec 31 09:12:06 markand: you mean ttyS4 ? Dec 31 09:12:48 markand: unfortunately the 8250 driver that creates the ttyS devices is a bit weird... they're created unconditionally, regardless of whether they're enabled in DT Dec 31 09:21:31 hmmm, I've seen that it's ttyO4 somewhere over the internet, let me try with ttyS4 Dec 31 09:22:21 oh well, it's a symbolic link to ttyO4 Dec 31 09:23:25 I mean the opposite, ttyS4 -> ttyO4 Dec 31 09:24:10 (the number of ttyS devices created can be set in the kernel config or overridden at boot time using the 8250.nr_uarts kernel parameter) Dec 31 09:24:34 yeah ttyO* are symlinks to ttyS* for backwards compatibility Dec 31 09:24:49 I've read that I should use uboot_overlay_addr2=/lib/firmware/BB-UART4-00A0.dtbo Dec 31 09:25:18 markand: sounds like you're reading a lot of old info Dec 31 09:25:22 heh Dec 31 09:26:35 if you're on a modern image in its default configuration, "cape-universal" is enabled which enables most peripherals and creates "pinmux helper" devices that allow the pins to be muxed to peripherals at runtime (using the "config-pin" utility or by directly writing a sysfs attribute, e.g. https://pastebin.com/MKtWJ8G8 ) Dec 31 09:26:51 so to use an uart all you then need to do is configure the pins using config-pin Dec 31 09:29:09 so it's P9.11 and P9.13 for uart 4 ? Dec 31 09:58:16 Yes! Dec 31 09:58:21 11 and 13! Dec 31 09:59:20 config-pin p9.11 uart && config-pin p9.13 uart <<< This does it! Dec 31 09:59:31 okay it goes better, thanks Dec 31 09:59:39 Nice! Dec 31 09:59:45 so I'll need to wrap my application into a sheel script to enable this before Dec 31 09:59:50 shell * Dec 31 10:00:09 oh and by the way, never buy any feig product Dec 31 10:00:15 Yes... Dec 31 10:00:17 Feig? Dec 31 10:00:21 Okay. Dec 31 10:00:37 Sounds like a Italian car. Dec 31 10:01:21 In your shell script, you do not need sudo for config-pin. Dec 31 10:02:41 markand: What file do you use to start your shell scripts on boot? Dec 31 10:02:53 it's the worse company for RFID identification products Dec 31 10:02:58 Oh. Dec 31 10:03:27 .bashrc? Dec 31 10:03:43 needs a large proprietary C++/Java SDK, are pretty unhelpful, anaemic documentation, needs proprietary software to read documentation (yes, a .exe file that shows up docs, really!) Dec 31 10:03:56 Ha. Dec 31 10:03:59 SDK throws undocumented errors Dec 31 10:04:11 Hahhaha. That does sound terrible. Dec 31 10:04:14 :( Dec 31 10:04:18 Sorry. Dec 31 10:04:37 Frowns all around! Dec 31 10:06:39 I see .service files pop up on the google searches but I thought there was another way to boot files when the board starts, i.e. shell scripts in particular. Dec 31 10:07:46 In this dir. /etc/init.d/? Dec 31 10:09:02 or symlink the file in /etc/init.d/ to /etc/rc.d/? Dec 31 10:09:13 Anyway. Off to test! Jan 01 01:04:21 First Cool Yule and now a beginning to a "wonderful" year! Good luck Moses and be steadfast! Happy New Years blah. Jan 01 01:04:56 I hope people will set fireworks safely w/ their BBBs and BBAIs! Jan 01 01:05:18 An onslaught of BBB actions to create the ultimate firework showing! Jan 01 01:11:41 I am done, though. No fun for me. Jan 01 01:24:01 I never really thought about it until now. They have coils and other mechanical parts that can be heated to produce a lighting apparatus! Jan 01 01:24:22 The BBB can produce that specific request w/ ease. Jan 01 01:24:33 Anyway, Happy New Year. Jan 01 02:00:17 Happy New Year indeed! Jan 01 02:34:06 yes. Jan 01 02:34:13 Indeed, matey. Jan 01 02:35:15 I should be a party where only the super rich would dare go. But! I am alone and scared in a time warp! Jan 01 02:39:18 I just need a kettle to settle my need. I need a BBB flame thrower for heating my kettle. Jan 01 02:39:45 Kerosene and a shutoff. Done. Jan 01 02:40:26 Well, I would need a spark plug and in CA, I would most likely need a spark arrestor. Jan 01 02:42:32 I wonder, do spark arrestors cause cancer? That would be a double entendre. Jan 01 02:43:04 Anyway, I should do it this winter for the sake of the BBB and lack of cancer! Jan 01 02:44:09 I mean it. Should random mechanical and electrical devices be powered by the BBB and other circuitry? Jan 01 02:44:58 For instance, Jed goes big and flame throws his kettle w/ the BBB at the helm? That has a ring to it. Jan 01 02:47:23 It would be like a backyard beaker. Jan 01 02:48:26 Anyway. I need to calm down and now. Alone and random! Yours truly, Jed and his kettle. Jan 01 02:48:29 ha. **** ENDING LOGGING AT Sat Jan 01 02:59:56 2022