nope, there is still something missing. the client USB port does not identify itself by lsusb from the connected laptop. I am getting power from this port, but no usb bbb device identification.
I am happy to start over, but I don't know where. I want to flash a working debian image to my beaglebone blacks, rev B and C, with 2GB into the eMMC. console is fine---I don't need X. the 7.5 img.xz doesn't seem to work for me. I can't flash it. the 7.7 img.xz works, but now seems too basic (if it is just designed for flashing); and even with the above steps, I can't seem to get the client USB ident to work. actually, this is probably the last step I need. after getting the USB client magic (id, usb mass storage, and usb networking) to work, I would be operating a non-magical linux device that I could handle myself. (in someone else's port, I think you mentioned that the usb was not working, but the 1a70b1cb550bd8d0bf4f2c0d43e72cba image had this fixed already.) I think the RootStock-NG.sh and your .conf file are part of a (complex?) toolchain to build img.xz files. alas, I don't know this toolchain. looking at http://elinux.org/BeagleBoardDebian#Demo_Image, the only .img.xz file I saw that flashes the eMMC is: BBB-eMMC-flasher-debian-7.7-console-armhf-2014-10-29-2gb.img.xz robert---I know you are already doing a lot here, so please forgive my audacity: may I suggest offering a 7.7 .img.xz eMMC flasher that has the usb client port already working? if not, what steps need to be taken for the bbb USB client port to identify itself as a device to the connected desktop USB host? regards, /iaw -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
