[solved] uEnv.txt empty

[xanb]

It works, sorry. The uEnv.txt which counts is IN microSSD not in my SATA disk.

Thanks, a lot.

[ap82]

@xanb Can you please tell me how you solved this. Its driving me crazy. I am trying to use my cubietruck from weeks now but no use. Tried debian,lubuntu server images......but prefer arch. Been using arch on raspberry pi and works wonderful.

I can boot from sd card. I don't want to use nand. I just want to move my rootfs to a hdd connected to sata port. I used the instructions from the link below. Everything works fine except moving rootfs to hdd. And uEnv.txt is empty.

http://archlinuxarm.org/forum/viewtopic.php?f=33&t=6413&start=130#p39680

[WarheadsSE]

You only need to change the root= location of the cmdline args.

[ap82]

@WarheadsSE thanks for your reply. But I still don't follow. command line arguments....to change where?....are you talking about the serial console?

[ap82]

Tried the command line args

$this->bbcode_second_pass_code('', ' sudo screen /dev/ttyUSB0 115200 root=/dev/sda1 ')


But it still boots from sd card. I shutdown the board connected it again without the sata cable using the same command and it booted the same way. So not sure if that command makes any difference.


Any help with this would be really appreciated as been trying this from weeks with no success.

[xanb]

After an upgrade to $this->bbcode_second_pass_code('', 'alarm/uboot-a20-olinuxino-micro 2015.01-1 [installed]') (see diff) uEnv.txt settings are ignored. I boot now from the SD. So now:
$this->bbcode_second_pass_code('', '
[root@alarm boot]# dmesg | grep root
[ 0.000000] Kernel command line: console=ttyS0,115200 root=PARTUUID=76e8d7a4-01 rw rootwait
[ 3.286944] Waiting for root device PARTUUID=76e8d7a4-01...
[ 5.040598] VFS: Mounted root (ext4 filesystem) on device 179:1.
[root@alarm boot]#
')
but I have:
$this->bbcode_second_pass_code('', '
[root@alarm boot]# cat uEnv.txt
mmcroot=/dev/sda1 rw rootwait
mmcrootfstype=ext4
optargs=elevator=noop ethaddr=00:CE:39:B7:74:4E rootfstype=ext4
[root@alarm boot]#
')

I filed a bug but as normally they do, they closed it without any explanation.

[xanb]

@ap82, I touched the file uEnv.txt in the /boot directory:
$this->bbcode_second_pass_code('', '
[root@alarm boot]# cat uEnv.txt
mmcroot=/dev/sda1 rw rootwait
mmcrootfstype=ext4
optargs=elevator=noop ethaddr=00:CE:39:B7:74:4E rootfstype=ext4
[root@alarm boot]#
')
but with the new uboot package, this is not working any more. Sorry for the delay. I just was not subcribed.

[starfry]

@xanb - you have to use "boot.txt" now. I had the same problem; see this thread for more.

You have to add your kernel parameters to the line "setenv bootargs" in "boot.txt" and then generate "boot.scr" from that using "mkscr". The "uEnv.txt" is no longer read.

$this->bbcode_second_pass_code('', '
$ cd /boot
$ vi boot.txt
(makes changes)
$ ./mkscr
')

HTH.

[xanb]

Thank you very much. I will try it. You will receive my news.
@ArchLinuxARM admins: you could have warned about that terrible change somehow. The Archlinux guys warn in the web page.

[xanb]

The original boot.txt is:
$this->bbcode_second_pass_code('', '
part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs console=${console} root=PARTUUID=${uuid} rw rootwait

if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux.img; then
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
bootz ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi

if load ${devtype} ${devnum}:${bootpart} 0x48000000 /boot/uImage; then
if load ${devtype} ${devnum}:${bootpart} 0x43000000 /boot/script.bin; then
setenv bootm_boot_mode sec;
bootm 0x48000000;
fi;
fi
')

My uEnv.txt is:
$this->bbcode_second_pass_code('', '
mmcroot=/dev/sda1 rw rootwait
mmcrootfstype=ext4
optargs=elevator=noop ethaddr=00:CE:39:B7:74:4E rootfstype=ext4
')

How can I pass the information from uEnv.txt to boot.txt? Special syntax?