Update:
I 'located' the uSD card - in the //dev (devices, I guess) folder; I simply
by noted what changed as I inserted the uSD card and looking at the folder
contents before ('ls dev' command) and after) In my case (pretty standard,
I guess) I saw 'mmcblk1p1' was added as I inserted the card (for others
having similar issue to myself : mmc=multimedia card, 'blk1' = block device
1 (the eMMC is, I think 'blk0') and the 'p1' = partition 1)
I then created a folder in //dev to 'house' the folder & file contents of
the uSD. In fact I created a folder called 'card' in 'media' which was
already within the root folder. So, I now have a folder : //media/card.
Just for my future reference (and because it made me feel good to 'own' :-)
the folder), I then created a realm.txt file within my new folder to remind
me when and why I created the folder...
I then 'mounted' the uSD card and 'linked' its contents to my new folder
with :
mount /dev/mmcblk1p1 on /media.card
Terminal responded with :
mount: you didn't specify a filesystem type for /dev/mmcblk1p1
I will try ext4
/dev/mmcblk1p1 on /media/card type ext4 (rw)
When I then listed the contents of the uSD card with 'ls /media/card',
Terminal returned the folders and files within the uSD card root folder -
Yahaay !
OK... so far so good...
I then located the uEnv.txt file again (BUT, now on the uSD card) and
opened it with a view to editing the required 'flash the eMMC' line. I was,
however, confronted with :
GNU nano 2.2.6 File:
uEnv.txt
Modified
loadximage=echo debug: [/boot/vmlinuz-${uname_r}] ... ; load mmc 0:1
${loadaddr} /boot/vmlinuz-${uname_r}
loadxfdt=echo debug: [/boot/dtbs/${uname_r}/${fdtfile}] ... ;load mmc 0:1
${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxrd=echo debug: [/boot/initrd.img-${uname_r}] ... ; load mmc 0:1
${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize ${filesize}
loaduEnvtxt=load mmc 0:1 ${loadaddr} /boot/uEnv.txt ; env import -t
${loadaddr} ${filesize};
check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;
loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run
loadxfdt;
mmcargs=setenv bootargs console=tty0 console=${console} ${optargs}
${cape_disable} ${cape_enable} root=/dev/mmcblk0p1
rootfstype=${mmcrootfstype} ${cmdline}
uenvcmd=run loadall; run mmcargs; echo debug: [${bootargs}] ... ; echo
debug: [bootz ${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr}] ... ; bootz
${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr};
cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
As you'll see, the line was already un-remmed...
Anyways, I powered down the BBB with the 'Boot' button depressed and, still
depressed, fired it back up again. When I saw all 4 Usr LEDs light up I
removed my finger from the 'Boot' button. Nothing very different happen...
same old heartbeat and sporadic others... no flashing occurred. After 45-60
seconds I'm confronted with 'just' the heartbeat LET and nothing else...
Ideas please ?
--
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/c1e19e45-08ca-47fc-9217-6ab3dd934cba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
