<p><br>
El 26/12/2011 05:03, "Tom Cubie" <<a href="mailto:tangliang@allwinnertech.com">tangliang@allwinnertech.com</a>> escribió:<br>
><br>
> On 12/26/2011 11:01 AM, Bari Ari wrote:<br>
> > On 12/25/2011 08:13 PM, Tom Cubie wrote:<br>
> >> i have pushed a new branch 'lichee-dev' to the tree. Currently<br>
> >> lichee-dev support sun4i and sun5i, it breaks all other machines in<br>
> >> the branch :( because we used a private nand lib which support many<br>
> >> types of nand flash. The same nand lib used in the allwinner linux<br>
> >> kernel, to be compatible with the current system(packaging, flashing<br>
> >> image etc...), we keep it. I think in the future we will need to write<br>
> >> the mtd nand driver and change the nand to mtd.<br>
> >><br>
> >> To build u-boot for A10, run 'make sun4i CROSS_COMPILE=<br>
> >> arm-linux-gnueabi-' in the u-boot directory.<br>
> >><br>
> >> <a href="http://git.rhombus-tech.net/?p=u-boot.git;a=shortlog;h=refs/heads/lichee-dev">http://git.rhombus-tech.net/?p=u-boot.git;a=shortlog;h=refs/heads/lichee-dev</a><br>
> >><br>
> > Are there instructions for flashing u-boot somewhere? I know we don't<br>
> > have hardware yet but does the A10 have options for where the init and<br>
> > bootloader are stored or expected to be after reset via pin-straps or is<br>
> > it hardwired?<br>
> ><br>
> > The flashrom folks might be interested in supporting this as well since<br>
> > this project should be very popular soon.<br>
> ><br>
> > -Bari<br>
> ><br>
> > _______________________________________________<br>
> > arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
> > <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
> > Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
> ><br>
><br>
> The problem is here. The A10 is a very 'closed chip'. There is a brom in<br>
> the chip, which can not be modified. This brom will load program from<br>
> external storage(nand, mmc), which we call boot0 in allwinner. Brom will<br>
> check the header of boot0, and get hardware information from boot0. The<br>
> hardware information is in a config file called sys_config.fex. A pc<br>
> tools will read the config file, and write the hardware information to<br>
> the head of boot0. After boot0 is booted up, it will continue to load<br>
> another loader boot1, boot1 init all other hardware and provides<br>
> hardware abstracts and services. According to the boot OS, boot1 loads<br>
> an arm elf program, boot.axf. For booting linux, boot.axf loads the<br>
> u-boot and jumps to the u-boot. Then u-boot will take over.<br>
><br>
> So, the whole boot process is:<br>
><br>
> brom -> boot0 -> boot1 -> boot.axf -> u-boot -> kernel</p>
<p>Hi Tom, can you share these specs so we can write a free&open compiler for these files?<br>
</p>