> > *I've flashed my BBB with the > https://rcn-ee.net/deb/testing/2014-08-19/console/BBB-eMMC-flasher-debian-7.6-console-armhf-2014-08-19-2gb.img.xz > <https://rcn-ee.net/deb/testing/2014-08-19/console/BBB-eMMC-flasher-debian-7.6-console-armhf-2014-08-19-2gb.img.xz> > image found on the page you gave. However, now there is no drive when I > plug in the BBB to my PC using the BBB client port. Normally a drive shows > up on my computer with uEnv.txt and other files, but there is no drive this > time. I tried searching around a bit but couldn't find anything to help me > troubleshoot. Is this an expected behavior for the newer image or might > something be wrong? Is this a result of me choosing the console image this > time around? I'd like to start small and install the things I need as I go. > How else would I edit the uEnv.txt file?*
If you're using Windows, the reason for this is that Windows will view this new image's set of drivers, as different from the last image you used. This is one case where Windows falls flat on its face. You can try and visit MSUpdate, and manually searching for updates to see if this will correct its self. Another possible cause is that this is a testing image, and everything may not work the way it is expected to. I'm current using the same image, but the standalone version. It works, but is not exactly the same being that it is the stand alone versus emmc flasher. You can log in to the BBB via the debug console, or you should be able to ssh via ethernet if that is an option for you. I would say try ssh'n in via the 192.168.7.2 USB interface, but it is likely that this ( g_ether ), and g_serial are also both broken on the host side. -- 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]. For more options, visit https://groups.google.com/d/optout.
