So I actually have 2 Beaglebone Blues and tried lots of stuff out. Also my host OS is pop!_os 18.04 (basically Ubuntu) and I don't really use Windows at all. And throughout this whole process I've only used the native linux ssh command and occationally the cloud9 ide, but that more so to test if it itself works, rather than issue commands.
>Ugh -- you seem to be using the USB host/client connection rather than > >a direct connection to your Internet router... > In regards to connections I've tried the following: - Micro USB from BBB to Host PC (two different cables) - Micro USB to phone charger (USB-A / 15W) and then over wifi only - Micro USB from Official Raspberry Pi Charger (5V 2.5A) and then over wifi only It seems, when you connect the USB, it creates an ethernet over usb connection, so this has been the most logical thign to use to try and issue commands via SSH, although as above, I've tried doing it only via WiFi as well and same issue. The distributions I've tried are: - Stock pre-installed (ie. from factory, dated 2017 from memory) - AM3358 Debian 10.3 2020-04-06 4GB SD IoT <https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz> - AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher <https://debian.beagleboard.org/images/bone-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz> - Debian 9.5 2018-10-07 4GB eMMC IoT Flasher <https://debian.beagleboard.org/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz> - Ubuntu 18.04.4( https://rcn-ee.com/rootfs/2020-03-12/elinux/ubuntu-18.04.4-console-armhf-2020-03-12.tar.xz) Always the same result - reverting to read-only when doing writes with WiFi on - except when I tried to modify the kernel parameters as previous post with the vm.min_free_kbytes paramter - which did seem to work for a long time - but after doing an apt update/upgrade it soon reverted to read-only as well, which was disappointing. The only thing I have left to try is a 2.1mm 12V power supply, which I have to go hunt and find one, I will let you know if that works, but I think I will need to return these boards. It seems a bit silly that you'd have to use a 12V PSU just to be able to use the WIFI on such a device properly, when there are no issues like this on a Raspberry Pi/O-Droid/Jetson, etc with much lower spec'd PSUs. On Tuesday, June 9, 2020 at 3:17:59 AM UTC+10, Dennis Bieber wrote: > > On Sun, 7 Jun 2020 17:21:59 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user > me-OZSSi2IBlpFBDLzU/[email protected] <javascript:> wrote: > > > >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 > > I'd consider that to be a red-herring... You are retrieving an > update > to the Cloud9 core, so the update process shuts down Cloud9 -- that may be > a problem IF you are using a Cloud 9 session to invoke the updates... > Instead use a SSH session -- PuTTY if you have it, Win10 "ssh" command as > an alternative > > -=-=-=- > Microsoft Windows [Version 10.0.19041.264] > (c) 2020 Microsoft Corporation. All rights reserved. > > C:\Users\Wulfraed>ssh debian@beaglebone > The authenticity of host 'beaglebone (fe80::d239:72ff:fe18:3ee5%16)' can't > be established. > ECDSA key fingerprint is > SHA256:PLZds8/FuHaVEqsTatoE6YFgSC+cakdD0OfPqEoTDQ8. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'beaglebone,fe80::d239:72ff:fe18:3ee5%16' > (ECDSA) to the list of known hosts. > Debian GNU/Linux 10 > > BeagleBoard.org Debian Buster IoT Image 2020-04-06 > > Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > > default username:password is [debian:temppwd] > > debian@beaglebone's password: > > The programs included with the Debian GNU/Linux system are free software; > the exact distribution terms for each program are described in the > individual files in /usr/share/doc/*/copyright. > > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent > permitted by applicable law. > Last login: Sat May 30 17:12:05 2020 from fe80::c932:bd85:577:9922%eth0 > debian@beaglebone:~$ > -=-=-=- > {Ugly part of Win10 ssh command is that I haven't figured out how to force > an update if the key changes [which happens often, just changing between > SD > and eMMC boots]; PuTTY gives a warning but lets one accept the new key} > > > >Setting up ti-pru-cgt-installer (2.1.5-0rcnee1~jessie+20180514) ... > >--2020-06-08 00:17:34-- > > "Jessie"? Are you really still running Debian 8? Beagle images > have > been "Stretch" (Debian 9) for a few years, and upgraded to "Buster" > (Debian > 10) in the last 6 months or so. > > Or is the repository using an old file? (Or does it just name it > for > the OS release... version and date match... > > -=-=-=- > debian@beaglebone:~$ sudo apt search pru-cgt > [sudo] password for debian: > Sorting... Done > Full Text Search... Done > ti-pru-cgt-installer/unknown,now 2.1.5-0rcnee1~buster+20180514 all > [installed] > TI PRU C/C++ CODE GENERATION TOOLS > > debian@beaglebone:~$ > -=-=-=- > > > > > > 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’ > > > > 36MB for /shell script/ is HUGE. Busybox tarball itself is only > just > over 2MB. The only busybox stuff I show is: > > -=-=-=- > debian@beaglebone:~$ sudo apt search busybox > Sorting... Done > Full Text Search... Done > busybox/stable 1:1.30.1-4 armhf > Tiny utilities for small and embedded systems > > busybox-static/stable 1:1.30.1-4 armhf > Standalone rescue shell with tons of builtin utilities > > busybox-syslogd/stable 1:1.30.1-4 all > Provides syslogd and klogd using busybox > > udhcpc/stable 1:1.30.1-4 armhf > Provides the busybox DHCP client implementation > > udhcpd/stable 1:1.30.1-4 armhf > Provides the busybox DHCP server implementation > > debian@beaglebone:~$ > -=-=-=- > > and none of those are actually installed... > > > >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 > > A manual fetch (wget > > http://downloads.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.5/ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_installer.sh > > ) does confirm 37MB... I'm going to have to assume TI has packed the > actual > tools into something like a BASE 64 encoding, stored inline in the script. > > FYI: most recent version seems to be 2.3.3 > > > >Connection to 192.168.7.2 closed by remote host. > >Connection to 192.168.7.2 closed. > > Ugh -- you seem to be using the USB host/client connection rather > than > a direct connection to your Internet router... Sticking an Internet > Connection Sharing path adds additional complications (my system isn't > even > set up to allow that -- 192.168.7.x is only desktop <> Beagle; I must have > a CAT-5 cable to my router to do Internet stuff). I'd consider the use of > the USB connection and/or Cloud9 while during updates to the OS to be > problematic. > > > > -- > Dennis L Bieber > > On Tuesday, June 9, 2020 at 3:17:59 AM UTC+10, Dennis Bieber wrote: > > On Sun, 7 Jun 2020 17:21:59 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user > me-OZSSi2IBlpFBDLzU/[email protected] <javascript:> wrote: > > > >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 > > I'd consider that to be a red-herring... You are retrieving an > update > to the Cloud9 core, so the update process shuts down Cloud9 -- that may be > a problem IF you are using a Cloud 9 session to invoke the updates... > Instead use a SSH session -- PuTTY if you have it, Win10 "ssh" command as > an alternative > > -=-=-=- > Microsoft Windows [Version 10.0.19041.264] > (c) 2020 Microsoft Corporation. All rights reserved. > > C:\Users\Wulfraed>ssh debian@beaglebone > The authenticity of host 'beaglebone (fe80::d239:72ff:fe18:3ee5%16)' can't > be established. > ECDSA key fingerprint is > SHA256:PLZds8/FuHaVEqsTatoE6YFgSC+cakdD0OfPqEoTDQ8. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'beaglebone,fe80::d239:72ff:fe18:3ee5%16' > (ECDSA) to the list of known hosts. > Debian GNU/Linux 10 > > BeagleBoard.org Debian Buster IoT Image 2020-04-06 > > Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > > default username:password is [debian:temppwd] > > debian@beaglebone's password: > > The programs included with the Debian GNU/Linux system are free software; > the exact distribution terms for each program are described in the > individual files in /usr/share/doc/*/copyright. > > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent > permitted by applicable law. > Last login: Sat May 30 17:12:05 2020 from fe80::c932:bd85:577:9922%eth0 > debian@beaglebone:~$ > -=-=-=- > {Ugly part of Win10 ssh command is that I haven't figured out how to force > an update if the key changes [which happens often, just changing between > SD > and eMMC boots]; PuTTY gives a warning but lets one accept the new key} > > > >Setting up ti-pru-cgt-installer (2.1.5-0rcnee1~jessie+20180514) ... > >--2020-06-08 00:17:34-- > > "Jessie"? Are you really still running Debian 8? Beagle images > have > been "Stretch" (Debian 9) for a few years, and upgraded to "Buster" > (Debian > 10) in the last 6 months or so. > > Or is the repository using an old file? (Or does it just name it > for > the OS release... version and date match... > > -=-=-=- > debian@beaglebone:~$ sudo apt search pru-cgt > [sudo] password for debian: > Sorting... Done > Full Text Search... Done > ti-pru-cgt-installer/unknown,now 2.1.5-0rcnee1~buster+20180514 all > [installed] > TI PRU C/C++ CODE GENERATION TOOLS > > debian@beaglebone:~$ > -=-=-=- > > > > > > 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’ > > > > 36MB for /shell script/ is HUGE. Busybox tarball itself is only > just > over 2MB. The only busybox stuff I show is: > > -=-=-=- > debian@beaglebone:~$ sudo apt search busybox > Sorting... Done > Full Text Search... Done > busybox/stable 1:1.30.1-4 armhf > Tiny utilities for small and embedded systems > > busybox-static/stable 1:1.30.1-4 armhf > Standalone rescue shell with tons of builtin utilities > > busybox-syslogd/stable 1:1.30.1-4 all > Provides syslogd and klogd using busybox > > udhcpc/stable 1:1.30.1-4 armhf > Provides the busybox DHCP client implementation > > udhcpd/stable 1:1.30.1-4 armhf > Provides the busybox DHCP server implementation > > debian@beaglebone:~$ > -=-=-=- > > and none of those are actually installed... > > > >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 > > A manual fetch (wget > > http://downloads.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.5/ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_installer.sh > > ) does confirm 37MB... I'm going to have to assume TI has packed the > actual > tools into something like a BASE 64 encoding, stored inline in the script. > > FYI: most recent version seems to be 2.3.3 > > > >Connection to 192.168.7.2 closed by remote host. > >Connection to 192.168.7.2 closed. > > Ugh -- you seem to be using the USB host/client connection rather > than > a direct connection to your Internet router... Sticking an Internet > Connection Sharing path adds additional complications (my system isn't > even > set up to allow that -- 192.168.7.x is only desktop <> Beagle; I must have > a CAT-5 cable to my router to do Internet stuff). I'd consider the use of > the USB connection and/or Cloud9 while during updates to the OS to be > problematic. > > > > -- > Dennis L Bieber > > On Tuesday, June 9, 2020 at 3:17:59 AM UTC+10, Dennis Bieber wrote: > > On Sun, 7 Jun 2020 17:21:59 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user > me-OZSSi2IBlpFBDLzU/[email protected] <javascript:> wrote: > > > >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 > > I'd consider that to be a red-herring... You are retrieving an > update > to the Cloud9 core, so the update process shuts down Cloud9 -- that may be > a problem IF you are using a Cloud 9 session to invoke the updates... > Instead use a SSH session -- PuTTY if you have it, Win10 "ssh" command as > an alternative > > -=-=-=- > Microsoft Windows [Version 10.0.19041.264] > (c) 2020 Microsoft Corporation. All rights reserved. > > C:\Users\Wulfraed>ssh debian@beaglebone > The authenticity of host 'beaglebone (fe80::d239:72ff:fe18:3ee5%16)' can't > be established. > ECDSA key fingerprint is > SHA256:PLZds8/FuHaVEqsTatoE6YFgSC+cakdD0OfPqEoTDQ8. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'beaglebone,fe80::d239:72ff:fe18:3ee5%16' > (ECDSA) to the list of known hosts. > Debian GNU/Linux 10 > > BeagleBoard.org Debian Buster IoT Image 2020-04-06 > > Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > > default username:password is [debian:temppwd] > > debian@beaglebone's password: > > The programs included with the Debian GNU/Linux system are free software; > the exact distribution terms for each program are described in the > individual files in /usr/share/doc/*/copyright. > > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent > permitted by applicable law. > Last login: Sat May 30 17:12:05 2020 from fe80::c932:bd85:577:9922%eth0 > debian@beaglebone:~$ > -=-=-=- > {Ugly part of Win10 ssh command is that I haven't figured out how to force > an update if the key changes [which happens often, just changing between > SD > and eMMC boots]; PuTTY gives a warning but lets one accept the new key} > > > >Setting up ti-pru-cgt-installer (2.1.5-0rcnee1~jessie+20180514) ... > >--2020-06-08 00:17:34-- > > "Jessie"? Are you really still running Debian 8? Beagle images > have > been "Stretch" (Debian 9) for a few years, and upgraded to "Buster" > (Debian > 10) in the last 6 months or so. > > Or is the repository using an old file? (Or does it just name it > for > the OS release... version and date match... > > -=-=-=- > debian@beaglebone:~$ sudo apt search pru-cgt > [sudo] password for debian: > Sorting... Done > Full Text Search... Done > ti-pru-cgt-installer/unknown,now 2.1.5-0rcnee1~buster+20180514 all > [installed] > TI PRU C/C++ CODE GENERATION TOOLS > > debian@beaglebone:~$ > -=-=-=- > > > > > > 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’ > > > > 36MB for /shell script/ is HUGE. Busybox tarball itself is only > just > over 2MB. The only busybox stuff I show is: > > -=-=-=- > debian@beaglebone:~$ sudo apt search busybox > Sorting... Done > Full Text Search... Done > busybox/stable 1:1.30.1-4 armhf > Tiny utilities for small and embedded systems > > busybox-static/stable 1:1.30.1-4 armhf > Standalone rescue shell with tons of builtin utilities > > busybox-syslogd/stable 1:1.30.1-4 all > Provides syslogd and klogd using busybox > > udhcpc/stable 1:1.30.1-4 armhf > Provides the busybox DHCP client implementation > > udhcpd/stable 1:1.30.1-4 armhf > Provides the busybox DHCP server implementation > > debian@beaglebone:~$ > -=-=-=- > > and none of those are actually installed... > > > >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 > > A manual fetch (wget > > http://downloads.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.5/ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_installer.sh > > ) does confirm 37MB... I'm going to have to assume TI has packed the > actual > tools into something like a BASE 64 encoding, stored inline in the script. > > FYI: most recent version seems to be 2.3.3 > > > >Connection to 192.168.7.2 closed by remote host. > >Connection to 192.168.7.2 closed. > > Ugh -- you seem to be using the USB host/client connection rather > than > a direct connection to your Internet router... Sticking an Internet > Connection Sharing path adds additional complications (my system isn't > even > set up to allow that -- 192.168.7.x is only desktop <> Beagle; I must have > a CAT-5 cable to my router to do Internet stuff). I'd consider the use of > the USB connection and/or Cloud9 while during updates to the OS to be > problematic. > > > > -- > Dennis L Bieber > > On Tuesday, June 9, 2020 at 3:17:59 AM UTC+10, Dennis Bieber wrote: > > On Sun, 7 Jun 2020 17:21:59 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user > me-OZSSi2IBlpFBDLzU/[email protected] <javascript:> wrote: > > > >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 > > I'd consider that to be a red-herring... You are retrieving an > update > to the Cloud9 core, so the update process shuts down Cloud9 -- that may be > a problem IF you are using a Cloud 9 session to invoke the updates... > Instead use a SSH session -- PuTTY if you have it, Win10 "ssh" command as > an alternative > > -=-=-=- > Microsoft Windows [Version 10.0.19041.264] > (c) 2020 Microsoft Corporation. All rights reserved. > > C:\Users\Wulfraed>ssh debian@beaglebone > The authenticity of host 'beaglebone (fe80::d239:72ff:fe18:3ee5%16)' can't > be established. > ECDSA key fingerprint is > SHA256:PLZds8/FuHaVEqsTatoE6YFgSC+cakdD0OfPqEoTDQ8. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'beaglebone,fe80::d239:72ff:fe18:3ee5%16' > (ECDSA) to the list of known hosts. > Debian GNU/Linux 10 > > BeagleBoard.org Debian Buster IoT Image 2020-04-06 > > Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > > default username:password is [debian:temppwd] > > debian@beaglebone's password: > > The programs included with the Debian GNU/Linux system are free software; > the exact distribution terms for each program are described in the > individual files in /usr/share/doc/*/copyright. > > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent > permitted by applicable law. > Last login: Sat May 30 17:12:05 2020 from fe80::c932:bd85:577:9922%eth0 > debian@beaglebone:~$ > -=-=-=- > {Ugly part of Win10 ssh command is that I haven't figured out how to force > an update if the key changes [which happens often, just changing between > SD > and eMMC boots]; PuTTY gives a warning but lets one accept the new key} > > > >Setting up ti-pru-cgt-installer (2.1.5-0rcnee1~jessie+20180514) ... > >--2020-06-08 00:17:34-- > > "Jessie"? Are you really still running Debian 8? Beagle images > have > been "Stretch" (Debian 9) for a few years, and upgraded to "Buster" > (Debian > 10) in the last 6 months or so. > > Or is the repository using an old file? (Or does it just name it > for > the OS release... version and date match... > > -=-=-=- > debian@beaglebone:~$ sudo apt search pru-cgt > [sudo] password for debian: > Sorting... Done > Full Text Search... Done > ti-pru-cgt-installer/unknown,now 2.1.5-0rcnee1~buster+20180514 all > [installed] > TI PRU C/C++ CODE GENERATION TOOLS > > debian@beaglebone:~$ > -=-=-=- > > > > > > 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’ > > > > 36MB for /shell script/ is HUGE. Busybox tarball itself is only > just > over 2MB. The only busybox stuff I show is: > > -=-=-=- > debian@beaglebone:~$ sudo apt search busybox > Sorting... Done > Full Text Search... Done > busybox/stable 1:1.30.1-4 armhf > Tiny utilities for small and embedded systems > > busybox-static/stable 1:1.30.1-4 armhf > Standalone rescue shell with tons of builtin utilities > > busybox-syslogd/stable 1:1.30.1-4 all > Provides syslogd and klogd using busybox > > udhcpc/stable 1:1.30.1-4 armhf > Provides the busybox DHCP client implementation > > udhcpd/stable 1:1.30.1-4 armhf > Provides the busybox DHCP server implementation > > debian@beaglebone:~$ > -=-=-=- > > and none of those are actually installed... > > > >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 > > A manual fetch (wget > > http://downloads.ti.com/codegen/esd/cgt_public_sw/PRU/2.1.5/ti_cgt_pru_2.1.5_armlinuxa8hf_busybox_installer.sh > > ) does confirm 37MB... I'm going to have to assume TI has packed the > actual > tools into something like a BASE 64 encoding, stored inline in the script. > > FYI: most recent version seems to be 2.3.3 > > > >Connection to 192.168.7.2 closed by remote host. > >Connection to 192.168.7.2 closed. > > Ugh -- you seem to be using the USB host/client connection rather > than > a direct connection to your Internet router... Sticking an Internet > Connection Sharing path adds additional complications (my system isn't > even > set up to allow that -- 192.168.7.x is only desktop <> Beagle; I must have > a CAT-5 cable to my router to do Internet stuff). I'd consider the use of > the USB connection and/or Cloud9 while during updates to the OS to be > problematic. > > > > -- > Dennis L Bieber > > -- 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/0ff16c26-2d42-4bee-b7a6-c9753f6d5eb1o%40googlegroups.com.
