Cubietruck boot process

[popel_ok]

Dear All,

 

I have used Igors Debian Wheezy Image for a long time and now and found nothing to complain about. Just for the case I tried to create a backup of my sd card and created an image using dd if=/dev/sdX of=/backup.img

And now the "unforseen" happened and I needed to create a new sd card. When copying the image back with dd if=/backup.img of=/dev/sdX I will get a newly created image but I am not able to boot anymore using this card. And it is getting even worse. When interrupting the boot process and issuing the relevant boot commands (run loadkernel; run setargs; bootm 0x48000000) in uBoot directly the system is running perfectly whereas the unattended boot with the same sd card results in a non repsonding system which stops at loading the IPV6 stack. No error message and nothing else I could use as a starting point for unvestigations.

But now back to my question:

Is there a short summary about the boot process for the A20. As far as I understood there is a simple boot loader starting uBoot from sd card (at least in my current coniguration). But which configuration is uBoot really using and what about the uEnv.txt file? Where does uBoot find this one and which one is actually used?

 

For my specific case I assume that the uEnv.script or cubietruck.bin as it is called in my environment is not correctly choosen and this results in the system not completely booting.

 

Any help and explanation is highly appreciated. Many thanks for your help.

 

Regards,