Hi Tarmo, I tried a 12V 5A switch mode power supply - still no dice.
I even flashed it using this PSU, switched to USB to add WiFi credentials, and then put it back to 12V and SSH'd in via WiFi. Still has the same issue with read-only. I really think it must be a hardware problem, I might go have a look at the board gerbers/cad files and see if I can spot anything, perhaps it could be something as benign as the eMMC/Wifi chips having being on the same power plane (most likely I assume?), and when WiFi requires more current during a transmission, it's unable to source enough, which could cause voltage to drop or not enough current supplied to eMMC, which then causes the error? This would be why adding a beefier PSU would help I guess - but if for some reason the traces are really thin or something, or not enough vias or not not enough shielding... who knows :-) I guess the absolute very last thing you could try, would be clearing the eMMC and re-writing bootloader and everything from scratch - but what's the point? This issue *ALSO* happens when I'm booted to the SD card - so to me that seems like it's something with the WiFI chip causing havoc in other parts of the board (maybe RAM/CPU ??) Thanks for the help anyway guys! On Monday, June 8, 2020 at 5:54:02 PM UTC+10, Tarmo wrote: > > Hi, > > On 08.06.20 03:21, [email protected] <javascript:> wrote: > > Alright seems like I spoke too soon again: > > > > during an upgrade I got this: > > > > > > Warning: Stopping cloud9.service, but it can still be activated by: > > cloud9.socket > > c9-core-installer:Stopping:cloud9.socket > > > c9-core-installer:extracting:c9-core_3.1.3543+git20170407-v4.8.2-build.tar.xz > > > groupadd: group 'cloud9ide' already exists > > c9-core-installer:Installed > > Setting up ti-pru-cgt-installer (2.1.5-0rcnee1~jessie+20180514) ... > > --2020-06-08 00:17:34-- > > > http://downloads.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.5/ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_installer.sh > > > Resolving downloads.ti.com (downloads.ti.com)... 23.37.140.249 > > Connecting to downloads.ti.com (downloads.ti.com)|23.37.140.249|:80... > > connected. > > HTTP request sent, awaiting response... 200 OK > > Length: 37320342 (36M) [application/x-sh] > > Saving to: ‘ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_installer.sh’ > > > > ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_insta > > 13%[============> > > > ] 4.98M 270KB/s in 12s > > > > Cannot write to ‘ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_installer.sh’ > > (Input/output error). > > Bus error > > dpkg: error processing package ti-pru-cgt-installer (--configure): > > subprocess installed post-installation script returned error exit > > status 135 > > Connection to 192.168.7.2 closed by remote host. > > Connection to 192.168.7.2 closed. > > > > > > So looks like it's still the same problem I would assume. I will try > > again and with 256kb min memory, but to be honest this looks more and > > more like something really wrong with the hardware - very unreliable and > > certainly would not give me confidence if this was running a drone or > > anything in the air. > > Getting on some thin ice now, but the next best guess would be a flaky > power supply. Unplug devices connected to BB-s USB ports, supply power > to BB via the 5V barrel plug (and a quality power brick) or from a good > powered USB hub. > > -- > Kind regards, > Tarmo > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/697dcda6-6ef1-4a69-bdbf-0429d346f064o%40googlegroups.com.
