Several Possibilities: 1.) When you write something to the file system, either a new file or modify a file, you need to type 'sync' on the command line to flush the buffers to the file system, otherwise you can loose the changes at unmount/shutdown.
2.) On the earlier Debian distributions, like 7.5, the uEnv.txt file is not in the 'root' partition, but is in the 'boot' partition, which is what I suspect is going on. "mount /dev/mmcblk1p2 disk" will mount the 'root' partition "mount /dev/mmcblk1p1 disk" will mount the 'boot' partition (or something like that, I'm working from memory) Since you can't mount two different partitions with the same name, if you try to mount them at the same time, you will need to call them something different, like disk1 and disk2 or disk_root and disk_boot. --- Graham == On Tue, Feb 10, 2015 at 3:28 AM, JS-BBB <[email protected]> wrote: > First of all apologies to the OP for crashing his thread :-) but it seems > to be the same issue. > > I have "initrd.img-3.8.13-bone47" (Debian) on the EMMC which becomes > visible after the above instructions, the disk directory is still on the SD > so I only need the "mount /dev/mmcblk1p2 disk" bit to access it and I can > see other stuff I had put in my own directory for test purposes > (bonescripts). > > However I can't see the original uEnv.txt file or the backup copy I had > made before the fatal bricking, is it possible they are hiding elsewhere > but boot or uboot directories of the EMCC? Copying the uEnv.txt from the SD > to the boot directory of the EMCC doesn't restore functionality but it is > possible that that files needs to be different than what's on the SD?? > > I have only started to mess around with the BBB and very lost! > > On Tuesday, February 10, 2015 at 9:34:27 AM UTC+11, Graham wrote: >> >> Well these instructions are for the later "single partition" Debian >> distributions. >> The 7.5, distribution has the uEnv.txt file in a separate "FAT" >> partition, so >> the mounting instructions are slightly different, if you need to get at >> the >> file in a different partition. >> >> --- Graham >> >> == >> >> On Mon, Feb 9, 2015 at 2:58 PM, JS-BBB <[email protected]> wrote: >> >>> Thanks Graham, that helped me too. Somehow the uEnv.txt file seemed to >>> have disappeared completely from the EMCC. I can still see other stuff I >>> put there but not that file. >>> >>> On Monday, February 9, 2015 at 6:17:12 AM UTC+11, [email protected] >>> wrote: >>>> >>>> >>>> I accidently modified uEnv.txt file located in eMMC of my Beaglebone >>>> black. Now the board is not booting. I can not even see BBB for serial >>>> connection from terra term (Windows 7 after drivers are installed). How can >>>> I get access to the board? If I can just access to uboot I could reflash or >>>> run it using nfs. Any ideas? >>>> >>> >>> -- 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.
