On 19.11.2012, at 17:18, Ciaran Farrell wrote:
On 19/11/12 12:13, Alexander Graf wrote:
On 19.11.2012, at 11:45, Ciaran Farrell wrote:
On 19/11/12 11:32, Alexander Graf wrote:
On 16.11.2012, at 15:56, Ciaran Farrell wrote:
home:babelworx:branches:openSUSE:12.2:ARM:Contrib:Cubox/JeOS-cubox -> openSUSE:12.2:ARM:Contrib:Cubox/JeOS-cubox
https://build.opensuse.org/request/diff/141568
Description: Get CuBox working w/o manual uboot intervention @@ -3,19 +3,39 @@ set -x
file=boot/boot.script +echo 'resetenv' >> $file +echo 'setenv kerneladdr 0x2000000' >> $file +echo 'setenv ramdiskaddr 0x3000000' >> $file +echo 'ext2load mmc 0:1 0x2000000 boot/linux.vmx' >> $file +echo 'ext2load mmc 0:1 0x3000000 boot/initrd.uboot' >> $file +echo -n 'setenv bootargs "' >> $file +echo 'console=ttyS0,115200 root=/dev/mmcblk0p2"' >> $file +echo 'bootm 0x2000000 0x3000000' >> $file +echo 'boot' >> $file Mind to explain why exactly you need this? Is $arcNumber not set up correctly on your local NVRAM?
Also, this still breaks after your first reboot, because the boot script gets regenerated on first boot.
Furthermore, this change only gets 12.2 working for you, but still fails on Factory. We should certainly find out why it doesn't work for you and get a generic solution up and rolling, so that Factory works too :). Sure, but I have absolutely no idea how to do that :-) The problem I was having with the original version of the bootscript was this: http://pastebin.com/hHxiZJ5C
It would boot as far as "Starting kernel ... Uncompressing Linux... done, booting the kernel." and then hang indefinitely. I blamed the errors: Loading file "/boot.scr" from mmc device 0:1 (mmcda1) 641 bytes read ## Executing script at 02000000 ## Error: "kerneladdr" not defined ## Error: "ramdiskaddr" not defined These are actually ok messages. The script checks for existence of these variables and defines them differently if they don't exist. The CuBox specific bit is where it checks for the $arcNumber and overrides that whole logic.
The only major difference I can see in your patch is that instead of running into that code path, you just replace all variable use with the same addresses the variables would expand to if you get into the $arcnumber==3905 case. You mean $arcnumber==13905, right? The test was:
'if itest 1$arcNumber == 13905; then'
I'm just double checking that it wasn't due to a typo..
$arcNumber==3905 :). The 1 is there so that the check with $arcNumber==3905 would expand to: itest 13905 == 13905 and with $arcNumber== to: itest 1 == 13905 so that we always have a valid integer comparison. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org