New to BBB/Angstrom, but not to Linux, in my last step before catastrophy I added an fstab entry to the eMMC root file system which made the gadget inoperable - partially, at least. What I did is
1. partitioned and formatted an SD as Linux/ext3, with one single partition, and a name like 'BBone' 2. added a proper uEnv.txt to the SD root 3. attached it and booted. Everything okay so far. Transferred some code to the SD, compiled it and ran the stuff - worked. 4. added a mount entry to the fstab, looking like 'LABEL=BBone /opt ext3 <defaults, maybe> 0 2'. (Sorry I don't remember the exact entry contents) 5. rebooted, and cried loud: the bone OS didn't start up its USB-IP stack, so I couldn't access it via TCP/IP any more, neither it did some DHCP request on the ethernet interface. It just does its well-known heartbeat pattern with the USRx-LED, so it is running in a certain way. It's off-line. My question, now, is how to get it connected again on the shortest way. For me there are a few possibilities: 1. Buy and attach UI-devices (screen, keyboard, etc) and do the fix via :0 2. Install an OS to the SD, boot from there and fix the eMMC fstab 3. Connect to the serial debug line - dunno what expects me there, but:complicated, as there are 3.3V levels AFAIK Any recommendation and/or information very appreciated Max -- 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/groups/opt_out.
