**** BEGIN LOGGING AT Mon Mar 07 02:59:57 2022 Mar 07 03:27:38 ok got me a usb cable.... and failed to connect to rdnis network =\ Mar 07 03:28:43 Whiskey`: on the programmed one you mean? well if it's a highly custom system then there's no reason to expect an rndis interface there Mar 07 03:34:14 uh thats an unprogrammed one i think Mar 07 03:34:49 waiting on a new uart adapter, cant find mine and my son's seems to have no tx Mar 07 03:35:09 then what do you mean exactly by "connect to" rndis? it will show up as rndis interface but there's nothing to "connect" to, the beaglebone will act as bootp/tftp client Mar 07 03:35:57 also, I think newer Windows systems don't recognize it because it is notoriously difficult to get windows to recognize usb devices and they keep changing things Mar 07 03:36:19 linux is just being derpy then. its giving a error 'activation of network failed' Mar 07 03:36:27 what is? Mar 07 03:36:51 network manager Mar 07 03:37:06 network manager is probably trying to get an IP address, which it won't get Mar 07 03:48:11 you'll need to setup static configuration Mar 07 03:48:43 (obviously, since the bbb will be getting its ip *from you* via bootp) Mar 07 06:43:45 Does anyone know what could cause the onboard EMMc to fail to load with a fresh image on the SD card? Mar 07 06:44:06 what do you mean? what exactly are you observing? Mar 07 06:44:18 (Beagleboard Black AM3358) Mar 07 06:44:30 beaglebone black, not beagleboard black Mar 07 06:44:37 Right you are Mar 07 06:44:49 I can't seem to flash the EMMc storage Mar 07 06:45:04 Flashed a brand new light image on the SD card Mar 07 06:45:18 dmesg readout gives error -110 Mar 07 06:45:42 As far as I understand it means that it got a timeout error Mar 07 06:46:27 I've seen that happen when the eMMC has been worn out by too many writes Mar 07 06:47:10 (which doesn't seem to be handled very well by this eMMC's internal firmware, causing it to go unresponsive upon attempted write) Mar 07 06:47:59 That /would/ make a lot of sense Mar 07 06:48:10 Is there a way to check that? Mar 07 06:48:59 well, if the eMMC is initially detected but subsequently goes unresponsive, it seems almost certain that that's what's going on Mar 07 06:49:24 I actually don't see it being detected at all in the dmesg Mar 07 06:50:03 can you share (using pastebin.com or similar paste service) whatever is getting logged related to mmc1/mmcblk1 ? Mar 07 06:51:59 Sure, give me a minute Mar 07 06:53:23 https://pastebin.com/pkc4eW8S Mar 07 06:53:45 well that ain't good Mar 07 06:54:31 but could still be due to wearout, I've seen it manifest in different ways... in particular, I've seen it go completely dead by attempting to erase once it was already worn out Mar 07 06:54:57 like what would happen if you were to attempt to reflash it Mar 07 06:55:08 It did happen while trying to reflash the EMMc with a newer version Mar 07 06:55:14 exactly Mar 07 06:55:28 It immediately fails because it dosen't recognize the EMMc Mar 07 06:56:52 like, the only other explanation would be actual hardware damage, but that would be unlikely unless something actually happened to the beaglebone that could explain that Mar 07 06:57:22 The only possible sort of physical damage may be from power-outtages Mar 07 06:57:57 I've never heard of that causing physical damage Mar 07 06:58:41 we literally never perform clean shutdowns (we embed the BBB in a product that has an on/off switch that just cuts power) Mar 07 06:59:33 (though we do reconfigure the eMMC into a pseudo-SLC mode, intended to increase endurance and reliability, including robustness against power failure) Mar 07 07:00:52 (at the cost of losing 50% of storage space) Mar 07 07:01:39 How do you configure it in pseudo-SLC mode? Mar 07 07:03:45 this can be done using mmc-utils, though the procedure is somewhat delicate and tricky, and since it involves writing one-time-programmable registers (i.e. irreversible actions) I actually added a custom command to mmc-utils that performs a bunch of sanity checks and then performs the relevant steps Mar 07 07:04:19 https://github.com/dutchanddutch/mmc-utils/commit/d550d3e2edaa4518af99ffdc101a32e93c5d37a5 Mar 07 07:05:31 of course we also put some effort into eliminating unnecessary writes to eMMC (such as logging) **** ENDING LOGGING AT Tue Mar 08 02:59:57 2022