**** BEGIN LOGGING AT Mon Jan 03 02:59:57 2022 Jan 03 06:58:27 Greetings Jan 03 06:59:25 What is the operating temperature range of the entire beagleboard AI? Jan 03 16:05:02 Hey folks. Just a question. Is there any GUI based image available for AI Beagle? Checking here and all of them are without GUI. The original one which came with the board is with explored certs and kina brick. https://beagleboard.org/latest-images Jan 03 16:06:52 overall im finding image support being bit obsolete. What people do in general? Jan 03 16:09:14 JustBoB, https://forum.beagleboard.org/tag/bbbio_debian updating for 2022-01-01 shapshots right now.. Jan 03 16:16:09 Thanks. Would be good to update webpage too with some of these :) Jan 03 16:26:44 by any change cloud-inti is supported for these imageS? Jan 03 16:30:02 JustBoB, sorry never heard of that... so not pre-installed... looks interesting.. Jan 03 16:32:33 ugh, it pulls in eatmydata... oh does that globally disable ext4/fsync, or do you have to force it.. Jan 03 16:33:30 okay, you need to call it from the wrapper.. so should be safe.. Jan 03 16:35:39 We use it everywhere to bootstrap the devices and virtual machines. quite neat to bootstrap multiple devices. I don't think It can be called from wrapper as it very early in the process of OS boot Jan 03 16:43:48 JustBoB, can you create an issue here, tag me (RobertCNelson) and please include an example (data can be fake..) https://github.com/beagleboard/Latest-Images/issues Jan 03 16:44:35 JustBoB, biggest issue, we have a few startup scripts that assume, uid 1000 or user debian, so need to massage it... Jan 03 16:45:46 all this is before that. All cloud providers uses them to bootstrap vms. I suspect all your script could go into cloud-init (no-cloud provider) and just do all the job there. Ok, gonna try to create issue with as much details as I can Jan 03 16:48:04 On a different topic. Im checking https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots/31280 and quite hard to understand how do I move SD content to the eMMC bootable? Jan 03 16:48:04 is there enough just to do this Jan 03 16:48:05 sudo cp -v /etc/beagle-flasher/beaglebone-black-microsd-to-emmc /etc/default/beagle-flasher Jan 03 16:48:05 sudo reboot Jan 03 16:48:06 and enable service? Jan 03 16:51:23 JustBoB, from command line, you can either run: sudo beagle-flasher Jan 03 16:51:31 and it'll start coping the microSD to eMMC Jan 03 16:51:51 or: sudo enable-beagle-flasher and it'll do it on the next "reboot".. Jan 03 16:52:17 if you have a ton of services setup, the "reboot" flasher works better.. (it's just where rsync runs..) Jan 03 16:52:31 as base image can be done either way.. Jan 03 16:53:22 beagle-flasher doesn't first stop all services not needed for flashing or ssh ? Jan 03 16:53:28 JustBoB, didn't you say the BBAI? use "sudo cp -v /etc/beagle-flasher/bbai-microsd-to-emmc /etc/default/beagle-flasher"... Jan 03 16:53:34 I dont have much. I basically need Synpse agent (https://synpse.net/ ) and docker. All other management comes from Synpse and is deployed as containers. Im trying to write a blog post how to use BB and Synpse Jan 03 16:53:55 zmatt, correct it doesn't stop anything.. so not 100% safe.. Jan 03 16:54:02 yap, sorry, copied from command from forum Jan 03 16:54:30 JustBoB, just double checking.. it wouldn't boot. ;) Jan 03 16:55:00 JustBoB, it just cordantes where the bootloader is installed and partition layout: https://github.com/rcn-ee/repos/tree/master/bb-beagle-flasher/suite/bullseye/debian Jan 03 16:55:48 zmatt, main change... user doesn't have to figure out how to use nano or sed.. i'm working on moving it back to buster.. Jan 03 16:56:08 rcn-ee: should be easy enough to fix... just create a .target that declares dependencies on the things you want to keep running, give it AllowIsolate=true, and then use systemctl isolate to stop everything that's not a dependency of that target Jan 03 17:15:11 `Debian 11.x (Bullseye) Xfce Desktop Snapshot` should this after flashing boots to X env? after flashing I'm getting no Xfce Jan 03 17:16:19 JustBoB, over hdmi you should see xfce load, there is a massive wait right now on first boot... not sure what's casuing the delay yet.. Jan 03 17:17:00 it's using the etnaviv open source 2d driver.. but yeah it's a massive regression from Buster.. Jan 03 17:20:07 JustBoB, i just got xorg working with the 2d driver late last week.. so it's a prety fresh image right now.. https://github.com/rcn-ee/repos/commit/a86560a1879e696024c0e158ea882f3358600f0b Jan 03 17:21:00 rcn-ee what is the massive delay? gonna try one more time but I suspect something might be off Jan 03 17:25:01 rcn-ee: have you tried using systemd-analyze plot >boot.svg to see what's causing the boot delay? Jan 03 17:32:59 i don't remember, flashing a mciroSD.. Jan 03 17:39:48 JustBoB, zmatt okay it's not as slow as last week...from bootup 13sec to screen init... 34sec to xorg cursor, 50sec to desktop showing.. Jan 03 17:42:02 ok, I think there is something. Di you tried new build with AI boards? Jan 03 17:42:30 this is a bbai.. Jan 03 17:44:03 i don't remember if this is outside my network... http://gfnd.rcn-ee.org:81/farm/bugs/bbai-xfce-2022-01-01.svg Jan 03 17:44:56 systemd-networkd-wait-online.service has been flackly, using this tweak since last week.. https://github.com/rcn-ee/repos/commit/dd8fb8a2b33f4505ad957b28c7570ff8bb7eaad5#diff-29f9eb212209f01de13ad1a09fd0dbd495712623ebbd6b2de0d52b250cdeabda Jan 03 17:45:16 what's pulling in systemd-networkd-wait-online.service ? Jan 03 17:45:18 usb-gadget isn't plugged in a pc.. Jan 03 17:45:28 just a power supply so it just fails.. Jan 03 17:45:46 mark the gadget as [Link] RequiredForOnline=no Jan 03 17:45:56 zmatt, that's with my override of: systemd-networkd-wait-online --interface=eth0 --interface=wlan0 --ignore=usb0 --ignore=usb1 --any --timeout=20 Jan 03 17:46:02 ew don't do that Jan 03 17:46:19 you can configure this per interface in their .network file Jan 03 17:46:37 what's the reason for using systemd-networkd-wait-online anyway? Jan 03 17:46:52 they are all RequiredForOnline=no Jan 03 17:47:12 before that overide, systemd-networkd-wait-online would time out at 2mins... Jan 03 17:48:05 zmatt, should i just: https://wiki.debian.org/systemd/howtos/WaitOnline Jan 03 17:48:14 note that --interface=eth0 --interface=wlan0 is saying you're rewriting eth0 _and_ wlan0 and everything else is ignored Jan 03 17:48:22 *requiring Jan 03 17:48:38 rcn-ee: what cares about waiting for online? Jan 03 17:48:45 like, why are you using this service at all? Jan 03 17:48:53 i added those after --any failed... that was the only combination that actually worked without a 2minute delay.. Jan 03 17:49:05 debian enables it by default with you configure systemd-networkd.. Jan 03 17:49:20 wtf Jan 03 17:49:30 it should not be enabled at all, ever really Jan 03 17:49:32 disabling... and reboot.. Jan 03 17:49:42 let's see what changes.. Jan 03 17:49:48 no wait, I'm sayign that wrong Jan 03 17:50:29 it can be enabled, but it's pulled in by network-online.target Jan 03 17:50:40 so sorry, it's normal to be enabled Jan 03 17:50:49 but it's not normal for it to actually get started Jan 03 17:50:57 that means a service is pulling in network-online.target Jan 03 17:52:37 well that got us 5seconds back: http://gfnd.rcn-ee.org:81/farm/bugs/bbai-xfce-2022-01-01-wait-online-disabled.svg Jan 03 17:52:45 i'll kill it globally.. Jan 03 17:53:15 the proper fix is finding which services are pulling in network-online.target and make them... not Jan 03 17:55:03 systemctl show -p WantedBy -p RequiredBy network-online.target Jan 03 17:55:41 killed https://github.com/RobertCNelson/omap-image-builder/commit/a60ed152349b6d1f5760b2b2c28d2dd8dd0d0616 Jan 03 17:56:44 right now that's just cockpit-motd.service, working on killing that too.. Jan 03 18:00:58 I'm checking how wait-online works exactly Jan 03 18:01:55 my biggest worry, PocketBeagle when no ethernet is connected.. Jan 03 18:02:03 because the intention *is* that network-online.target succeeds when you actually have network up, i.e. it's means to be pulled in by services which _require_ working network Jan 03 18:02:13 the beaglebone should not have any such service by default Jan 03 18:02:27 but it's good form to ensure it does work for people who do need it Jan 03 18:03:23 ah, setting all of them RequiredForOnline=false is what breaks --any Jan 03 18:03:49 since RequiredForOnline=false means the interfaces are ignored, so then it never finds an interface up Jan 03 18:04:03 so 'one' needs to be enabled... ugh... PocketBeagle, BeagleBone, Wireless.. Jan 03 18:04:12 we never have 'one' always... Jan 03 18:04:17 no, just enable them all, but use --any Jan 03 18:05:03 and by "all" I mean eth0 and wlan0 ... I don't think what the usb interfaces provide is what would generally by meant by "being online" Jan 03 18:05:13 *be meant by Jan 03 18:06:34 again, nothing on the image should pull in network-online.target by default, but e.g. if someone writes a service that requires internet access and doesn't want to have to deal with dynamic network changes, that's where you'd add a dependency on network-online.target Jan 03 18:07:22 so with eth0 and wlan0... 7.411s systemd-networkd-wait-online.service Jan 03 18:07:49 is that the time it takes for one of them to get link up? is it still being invoked with --any ? Jan 03 18:08:16 obviously anything that depends on network-online.target will not be able to start very early in the boot process Jan 03 18:09:02 that's one of the big downsides of using network-online.target ... but for some people that may be a price they're willing to pay to be able to assume the network is already up in their own code Jan 03 18:10:10 10.192s with -ignore=usb0 --ignore=usb1 --any --timeout=10 Jan 03 18:10:26 it should not have a timeout, that breaks things Jan 03 18:10:38 lost 2.5 sections by removing --interface=eth0 --interface=wlan0 Jan 03 18:10:40 also, why are you timing your boot? again, nothing should be pulling in network-online.target on the bbb Jan 03 18:10:52 so the time it takes is unimportant Jan 03 18:10:57 since it should get run Jan 03 18:10:59 *shouldn't Jan 03 18:11:27 certainly nothing that actually stalls the boot process in a user-relevant way Jan 03 18:11:47 trying to figure out what's causing xfce to take forever to load... it's the only outlier https://paste.debian.net/1225714/ Jan 03 18:12:26 rcn-ee: can you share the svg from systemd-analyze plot ? Jan 03 18:13:43 you said network-online.target was being pulled in by cockpit-motd.service ... whatever that is Jan 03 18:14:30 latest http://gfnd.rcn-ee.org:81/farm/bugs/bbai-xfce-2022-01-01-RequiredForOnline-true.svg Jan 03 18:15:50 cockpit-motd.service is jsut figureing out the Ip address and updating motd... i'm working on disabling it globally.. Jan 03 18:16:45 doesn't look like anything in the boot is waiting for it anyhow? Jan 03 18:17:24 hmm, or is it Jan 03 18:17:32 no, doesn't look like it Jan 03 18:18:17 lightdm starts way before systemd-wait-online finishes Jan 03 18:19:13 so, if this cockpit-motd.service wants to know your "real" ip address, then yeah it makes sense for it to pull in network-online.target Jan 03 18:19:47 though such a thing probably shouldn't be on it in the first place Jan 03 18:19:54 but it also doesn't look like it's slowing down boot Jan 03 18:20:22 it's done all the way at the end after everything else Jan 03 18:20:32 with nothing waiting on it Jan 03 18:20:58 yeah i nuked it, and rebooted.. boot time is hte same, but systemd-wait-online doesn'tshow up.. http://gfnd.rcn-ee.org:81/farm/bugs/bbai-xfce-2022-01-01-RequiredForOnline-true-purged-cockpit.svg Jan 03 18:21:08 exactly Jan 03 18:21:18 so yeah.. wonder if it's just entropy and xfce... Jan 03 18:22:20 so, don't put a low timeout on network-online.target ... by definition it should wait for network online, that's the purpose it provides to whichever unit is depending on it Jan 03 18:22:26 or any timeout really Jan 03 18:22:51 on systemd-networkd-wait-online.service I mean Jan 03 18:22:58 i'll stick it back to it's default. i'm not using it.. Jan 03 18:23:23 the --any option sounds like a good idea, can't imagine why it's not default (assuming it isn't) Jan 03 18:23:31 it's not... Jan 03 18:23:41 and RequiredForOnline=false on the usb interfaces Jan 03 18:24:13 yeap, usb0/usb1 are too be locked out at all cost.. Jan 03 18:24:38 yes, no need to use commandline args for that, RequiredForOnline=false in the [Link] section of the .network takes care of that Jan 03 18:25:23 yeap, those are set.. https://github.com/rcn-ee/repos/blob/master/bb-usb-gadgets/suite/bullseye/debian/usb0-DHCPServer.network Jan 03 18:25:58 makes you wonder thou.. is anyone shipping systemd-networkd 'enabled' by default... seems like some of the final tweaks are just missing (--any)... Jan 03 18:27:36 I'm still checking what exactly --any vs default does, since even by default it apparently only needs "at least one link to be online" though it needs all of them "fully configured or failed" Jan 03 18:30:01 my ethernet interface shows as "configured" even when not plugged in Jan 03 18:30:26 then again usb0 on a bbb here shows as "configuring" Jan 03 18:31:13 usb0 should change from configuring -> configured when it gets plugged in.. Jan 03 18:32:57 hmm, so my ethernet when unplugged when networkd starts indeed gets stuck in "configuring", and in fact only goes to "configured" well after the operational state is "routable" Jan 03 18:33:07 but Jan 03 18:33:21 it subsequently remains "configured" even after unplugging Jan 03 18:33:32 I'm not sure what systemd-networkd means by this Jan 03 19:45:25 rcn-ee: summary of how wait-online works: https://pastebin.com/YJaYxne4 Jan 03 19:46:43 I still don't quite get the logic behind the link state being "configuring" while carrier is down (but not going back to "configuring" if the carrier goes down again once configured) and wait-online failing on that if --any isn't specified Jan 03 19:48:23 it is possible to get the interface to go to "configured" even if the carrier is down by ConfigureWithoutCarrier=yes (in which case you'll also want IgnoreCarrierLoss=no) in the [Network] section but I'm not sure if that has bad side-effects Jan 03 19:51:51 thanks zmatt i think i have eerything cleaned up in git, and pushsing deb builds out.. Jan 03 20:06:08 I just bought one of the latest bbg available in my country ... and I haven't seen a bbb for sale in a long time. I have a bbb though.. Jan 03 20:16:20 CoffeeBreakfast: farnell says they'll get 10,000 BBBs in stock in 2-3 weeks Jan 03 20:18:07 CoffeeBreakfast: digikey has 5337 BBBs in stock Jan 03 20:18:36 https://www.digikey.com/en/products/detail/beagleboard-by-seeed-studio/102110420/12719590 Jan 03 20:19:15 oh man! thanks @zmatt those have the new phy fix.. i need to pick a up couple asap.. Jan 03 20:21:07 woo Jan 03 20:25:24 Import taxes are insane these days. Well.. at least I have a couple now.. Jan 03 20:50:50 hi can anyone Jan 03 20:50:52 help me Jan 03 20:51:15  end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Jan 03 20:51:21 help please Jan 03 20:51:29 uhh Jan 03 20:51:34 how'd you manage that Jan 03 20:52:46 i don't get it Jan 03 20:52:51 what do u mean Jan 03 20:52:52 > Jan 03 20:52:55 ? Jan 03 20:53:20 this needs a lot more context... what device are you using? what image are you using? what are you trying to do? what is the context of this error? can you share the whole kernel log? (please share using pastebin.com, don't paste it directly into chat) Jan 03 20:53:30 Guest95: do not send unsolicited private messages Jan 03 20:54:33 ok Jan 03 20:54:45 i'm using beagle bone black Jan 03 20:55:59 AM3358 Debian 10.3 2020-04-06 1GB SD console Jan 03 20:56:09 that's image i use Jan 03 20:56:16 and what did you do that resulted in this error? Jan 03 20:56:29 okay Jan 03 20:56:46 setenv bootargs console=console=ttyO0,115200 root=/dev/mmcblk1p1 rw Jan 03 20:57:01 Guest95, why? Jan 03 20:57:11 where are you doing that and why? Jan 03 20:57:13 Guest95, what book are you reading? Jan 03 20:57:59 n't book i just watch tutorial on udemy Jan 03 20:58:08 how old that tutorial? Jan 03 20:58:14 i'm doing that Jan 03 20:58:24 when was it published? Jan 03 20:58:30 cause i'm still learn hoe to write Jan 03 20:58:36 uEnv.txt Jan 03 20:58:42 Guest95, what's the name of the "course? Jan 03 20:58:53 generally speaking you have you reason to mess with uEnv.txt Jan 03 20:58:56 *no reason to Jan 03 20:59:15 and what you showed isn't even valid syntax for that file Jan 03 20:59:19 Embedded Linux Step by step with beaglebone Jan 03 20:59:39 why Jan 03 20:59:41 ? Jan 03 20:59:45 Guest95, this one? https://www.udemy.com/course/embedded-linux-step-by-step-using-beaglebone/ Jan 03 21:00:22 [ 2.702606] VFS: Cannot open root device "mmcblk1p1" or unknown-block(0,0): error -6 Jan 03 21:00:22 [ 2.710539] Please append a correct "root=" boot option; here are the available partitions: Jan 03 21:00:23 [ 2.719008] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Jan 03 21:00:23 [ 2.727319] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.108-ti-r113 #1 Jan 03 21:00:24 [ 2.734135] Hardware name: Generic AM33XX (Flattened Device Tree) Jan 03 21:00:24 it does say it's recently updated Jan 03 21:00:24 [ 2.740302] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) Jan 03 21:00:25 [ 2.748094] [] (show_stack) from [] (dump_stack+0x80/0x94) Jan 03 21:00:25 [ 2.755358] [] (dump_stack) from [] (panic+0x100/0x284) Jan 03 21:00:26 [ 2.762360] [] (panic) from [] (mount_block_root+0x1b8/0x2a4) Jan 03 21:00:26 [ 2.769883] [] (mount_block_root) from [] (mount_root+0x140/0x15c) Jan 03 21:00:27 [ 2.777838] [] (mount_root) from [] (prepare_namespace+0x160/0x1a8) Jan 03 21:00:59 when he comes back, it looks like 2017.03.19 image was used as a base.. Jan 03 21:02:18 i think this is the repo... https://github.com/niekiran/EmbeddedLinuxBBB Jan 03 21:03:12 thnx Jan 03 21:03:34 Guest95, is this the course or not? https://www.udemy.com/course/embedded-linux-step-by-step-using-beaglebone/ Jan 03 21:04:25 Guest95: also, the fragment you pasted is showing kernel 4.14.108-ti-r113 .. but you claimed you were using AM3358 Debian 10.3 2020-04-06 1GB which does _not_ use that kernel Jan 03 21:05:15 https://pastebin.com/U12PHJYE Jan 03 21:06:43 I can't really tell anything from this other than that the kernel didn't see any mmc devices Jan 03 21:06:59 how?? Jan 03 21:07:17 when i restart it Jan 03 21:07:27 it can boot from mmc Jan 03 21:07:31 I have no way to guess based on the negligible information provided Jan 03 21:07:40 okay, so what are you doing to cause t to fail? Jan 03 21:07:48 what other info do u need Jan 03 21:07:49 ? Jan 03 21:07:49 *cause it Jan 03 21:08:11 i rellay appreciate your help Jan 03 21:09:28 I have no idea what you're doing or trying to do, what steps are leading you to this error... all I know is that you're apparently trying to do something weird with u-boot, and that you're having trouble booting your kernel Jan 03 21:09:55 and that what little information you provided isn't actually correct (since this kernel isn't the one on the 10.3 2020-04-06 image you said you're using) Jan 03 21:10:22 I cannot magically guess what you might have done wrong if you don't even know what you did in the first place Jan 03 21:10:30 *if I don't even know Jan 03 21:11:10 rcn-ee: you any idea why the kernel might not see any mmc devices? (since it's not listing anything after "here are the available partitions:") Jan 03 21:11:14 can i send Jan 03 21:11:16 commands Jan 03 21:11:17 here Jan 03 21:11:26 Guest95, use pastebin for anything over a line.. Jan 03 21:11:38 zmatt, without a full boot log (and quiet) disabled, it's a guess. .;) Jan 03 21:11:48 i'm afraid to ask them that.. Jan 03 21:12:17 probally /dev/mmcblk1 -> /dev/mmcblk0 name issues.. Jan 03 21:12:59 Guest95, you seem to be mixing a bunch of different guides... Which guide are you trying to do right now? igrning all other guides you'd touched? Jan 03 21:12:59 Guest95: honestly, the list of topics in this course doesn't sound like it's particularly suited for for novices Jan 03 21:13:31 like, details of the boo process, TFTP booting, buildroot, building kernel and bootloader, NFS booting... that's all really advanced stuff Jan 03 21:15:30 some of it is really obscure... like, serial booting? wtf? Jan 03 21:15:34 who on earth uses that Jan 03 21:16:13 the comments on that course are hilarous... it's a 10 year old version of Angstrom... no way those are 5 stars... Jan 03 21:22:43 Guest95: regardless, if you can clearly communicate exactly what steps you performed then we may be able to provide feedback, but otherwise there's no way to guess Jan 03 21:26:25 ? Jan 03 21:26:36 i'm guest 95 Jan 03 21:26:41 sorry Jan 03 21:27:05 you know you could also try setting a better name than the "Guest" and some digits Jan 03 23:13:31 Good evening, Jan 03 23:13:38 the test lab is online Jan 03 23:14:03 zmatt, the modbus probe indeed responds immediately, it does not wait 3.5 char ... Jan 03 23:14:56 I asked the manufacturer. Someone suggested 3.5 char is a maximum recommended wait time, not mandatory minimum. I'm a bit lost but i can perform tests, great. Jan 03 23:22:27 Nice! Jan 03 23:22:39 Way to go, fine person. Jan 03 23:23:02 I am working on something completely different. Motors (still)! Jan 03 23:29:22 (to all) What is your favorite new command that you discovered the past year? (from someone on twitter). I go first: `remake` Jan 03 23:40:03 Twitter? Does twitter.com have commands now? Jan 03 23:40:29 I twitted a couple times already in the last month. But...I was unaware of their commands. Jan 03 23:41:03 I found macrofab outside of twitter for building my TIDA-00320! Jan 03 23:41:44 Servos! Jan 03 23:43:11 Oh and @zmatt: I saw your posts on the forum. Thank you for still pitching in to support people who are lost in a world of electronics... Jan 03 23:43:25 * set_ <<< Jan 03 23:44:02 I mean Linux commands Jan 03 23:46:56 Oh. I learned from jfsimon1981 about the / -name command when searching for specific things in the file system. Jan 03 23:47:28 I am sad to admit, I know very little of Linux commands on Twitter b/c they will not allow me to have their SDK any longer. Jan 03 23:47:33 I am boycotting them. Jan 03 23:48:12 A lot of my source was dedicated to their SDK for use in the system of twittering. Now, they say no to me. Boo! Jan 03 23:49:10 "How are you going to use our software," they asked. I told them exactly how I would use it. Blam. "No set_, you cannot have our SDK any longer." Jan 03 23:50:04 CoffeeBreakfast: I understand your question. I was poking fun w/ you. Please forgive me. Jan 03 23:53:16 jfsimon1981: wtf, no it's most definitely the minimum _required_ Jan 03 23:55:49 jfsimon1981: "In RTU mode, message frames are separated by a silent interval of _at least_ 3.5 character times." (the _at least_ is underlined in the spec itself) Jan 03 23:57:28 jfsimon1981: and the maximum idle time between two consecutive bytes of a single frame is max 1.5 character times Jan 03 23:59:07 jfsimon1981: it also explains that the 3.5 char idle is used to delineate frames: "When the link is in idle state, each transmitted character detected on the link is identified as the *start of a frame*. The link goes to the "active" state. Then, the *end of frame* is identified when no more character is transmitted on the link after the time interval t3,5." Jan 04 00:03:47 jfsimon1981: presumably they infer the frame has ended based on the higher protocol layer, but that is not how the protocol is specified. the serial protocol layer considers a packet to consist of one address byte, a variable-size payload, and two crc bytes. it considers the payload to be opaque hence has no way to determine the end of a frame other than by recognizing the 3.5-char idle time Jan 04 00:04:58 jfsimon1981: so, the device you have is broken, what they implemented is not modbus Jan 04 00:47:47 Went ahead and grabbed a second BBB to replace dead NIC, will try and troubleshoot more at a later date I guess Jan 04 00:48:02 I still want to try the near/far loopback modes on the NIC though, maybe later tonight even Jan 04 01:13:44 jfsimon1981: anyway, if this thing was sold to you as a modbus device you can perhaps complain loudly to the manufacturer to try to get them to fix it. alternatively, if you want to make it work with extremely tight bus turnaround, your options are either using pru or perhaps use an rs485 transceiver with automatic driver-enable **** ENDING LOGGING AT Tue Jan 04 02:59:56 2022