dCore Import Debian Packages to Mountable SCE extensions > Allwinner A10

A10 boot files

(1/13) > >>

athouston:
I have a working MK802 1GB stick using the boot from sd card method. I am investigating how to load it on the internal nand but I am confused about some of the file relationships. I also want to try and implement TCL on other devices so I am trying to get "really techo".

My mmcblk0p1 partition contains the following files:

boot.scr
script.bin
uCore
uEnv.txt
uImage

The files I "dd'd" to the card were:

A10Core.img
sunxi-spl.bin
u-boot.bin
script.bin

What file became what (ie. what translation occurred) and what are the files for.

Thanks in advance..

roberts:
sunxi-spl.bin
u-boot.bin
boot.scr
script.bin
uCore
uEnv.txt
uImage
All of the above are in A10Core.img. The current A10Core.img is for the Marsboard A10.

sunxi-spl.bin
u-boot.bin
These two files are the board specific boot loader files, used to initially boot from sdcard.
They are typically static and are located at specific sector and offset locations.

--- Code: ---dd if=sunxi-spl.bin of=/dev/sdX bs=1024 seek=8
dd if=u-boot.bin of=/dev/sdX bs=1024 seek32

--- End code ---

boot.scr
script.bin
uCore
uEnv.txt
uImage
The aove are the release files, They are visible in the first partition.
boot.scr is used by u-boot to boot the kernel and initrd.
script.bin is also typically board specific describiing features that the board supports..
uImage is the kernel, uCore is the rootfs as an initrd compressed cpio.
uEnv.txt is for additional boot parameters (extraargs), i.e, to declare the location of tce directory tce=, the timezone specs, tz= ...

athouston:
OK. So we put the A10core image on the target and replace the Marsboard u-boot and sunxi files with the board specific versions.

Q1. Are the u-boot and sunxi files the standard files that come on the target device or do we modify them for TCL.
Q2. What happens to sunxi-spl.bin. I cannot see it on either of the TCL partitions or on any of the MK802 nand partitions.

The only other question is regarding the actual boot process.

When we power on the device the chip firmware must have a command to load a program at a specific location in order to start the boot process. On a device with onboard nand this location is obviously somewhere there. When we boot from the external sd card how do we tell the chip to use this boot location.

roberts:
Re: Q1
The hardware section see http://tinycorelinux.net/5.x/armv7/hardware/  was made by compiling u-boot for Allwinner. It contains a list of supported hardware.
https://github/com/hno/uboot-allwinner

Re: Q2
Not seen as it is written to specific sector see prior dd command.

boot.scr is a set of commands for u-boot. It determines what and how to boot. This allwinner version looks at the first fat partition from external sdcard for script.bin and also the kernel. It is "compiled" and "decompiled" with mkimage command.

script.bin is a configuration file of hardware specifics "compiled" with fex2bin and "decompiled" bin2fex

Typically you can use the script.bin from your specific board.

uEnv.txt can override some boot paramters specified in boot.scr and is where Core specific boot parameters are located.

persian:
Would you please describe for me, how can I change or define the Marsboard pins setting for gpio or SPI functions?

Navigation

[0] Message Index

[#] Next page