-
Notifications
You must be signed in to change notification settings - Fork 333
Home
u-boot for Allwinner sunxi series of SoCs (A10, A13, A10s, and A20)
sunxi Stable branch. Supports A10, A13 and A10s
sunxi-current Development branch closely tracking upstream
wip/a20 Development branch where changes for A20 is being staged
lichee-dev NAND capable replacement for Allwinner A10 u-boot
lichee-dev-a20 NAND capable replacement for Allwinner A20 u-boot
lichee/ Unmodified mirrors of original Allwinner sources
v2013.04-sunxi Pending stable release.
v2013.01-sunxi Old release
v2013.01.01-sunxi Old release
v2012.10-sunxi Stable release. Board specific SPL to set correct DRAM parameters for the board.
v2011.09-sun4i Old release. SPL support för some 512MB systems, based on original Mele A1000 DRAM settings. Do not properly power the CPU core which may cause system instabilities.
You need a suitable gcc ARM Linux GNUEABI toolchain installed and added to your PATH.
Then compile u-boot for A10 by running
make 'boardtype' CROSS_COMPILE=arm-linux-gnueabihf-
See boards.cfg for a list of known board types.
As of 2013-07-19 the list contains
A10_MID_1GB
A10s-OLinuXino-M
A10s-OLinuXino-M_FEL
A13_MID
A13-OLinuXino
A13-OLinuXino_FEL
A13-OLinuXino_FEL_sdcon
A13-OLinuXinoM
A13-OLinuXinoM_FEL
A20-OLinuXino_MICRO
A20-OLinuXino_MICRO_FEL
Auxtek-T003
Auxtek-T004
ba10_tv_box
Coby_MID7042
Coby_MID8042
Coby_MID9742
Cubieboard
Cubieboard_FEL
Cubieboard_512
Cubieboard2
Cubieboard2_FEL
DNS_M82
EOMA68_A10
EOMA68_A10_SPL
EOMA68_A20
EOMA68_A20_SPL
Gooseberry_A721
H6
Hackberry
Hyundai_A7HD
INet97F-II
Mele_A1000
Mele_A1000G
Mele_A3700
Mini-X
Mini-X-1Gb
mk802
mk802-1gb
mk802_a10s
mk802ii
pcDuino
PoV_ProTab2_IPS9
PoV_ProTab2_IPS_3g
PoV_ProTab2_XXL
r7-tv-dongle
Sanei_N90
sun4i
sun4i_sdcon
sun5i
sun5i_uart1
sun5i_sdcon
uhost_u1a
wobo-i5
xzpad700
If your board is not listed then see "Adding a new A1x board" below
Board names ending with _FEL are configured for USB-Booting.
To build natively on ARM hard-float systems you may need to install soft-float GCC libraries. On Ubuntu ARM and the like install gcc-multilib package to get these. This is due to an u-boot upstream decision to always build u-boot soft-float on ARM.
A10 & A13 boots the SPL loader from block 8. This then loads actual u-boot from block 32 onwards, counted in 1KB blocks.
dd if=spl/sunxi-spl.bin of=/dev/sdc bs=1024 seek=8
dd if=u-boot.bin of=/dev/sdc bs=1024 seek=32
You also need to partition the card to store script.bin, uImage, boot.scr (optional) and rootfs partition there. First partition should start at sector 2048 to leave sufficient space for uboot & environment.
This version of u-boot support uEnv.txt, and will look for it in the first partition FAT /uEnv.txt or extX /uEnv.txt or extX /boot/uEnv.txt. uEnv.txt contains variables on the form variable=value, one per line. If the variable uenvcmd is set then u-boot will run the commands listed in this variable.
This version of u-boot supports boot.scr, and will look for it in the first partition FAT /boot.scr or extX /boot.scr or extX /boot/boot.scr. boot.scr contains your needed uboot commands for loading script.bin, kernel. initrd (optional), setting kernel parameters and booting.
To create boot.scr first make a u-boot script boot.cmd with the u-boot commands you need for booting your system. An example follows:
setenv bootargs console=ttyS0 root=/dev/mmcblk0p1 rootwait panic=10 ${extra}
ext2load mmc 0 0x43000000 boot/script.bin
ext2load mmc 0 0x48000000 boot/uImage
bootm 0x48000000
Then translate this to a boot.scr by using the mkimage command
mkimage -C none -A arm -T script -d boot.cmd boot.scr
If no boot.scr is found then it will fall back to load script.bin & kernel uImage from the first partition in FAT format
fatload mmc 0 0x43000000 script.bin && fatload mmc 0 0x48000000 ${kernel} && watchdog 0 && bootm 0x48000000
To add a new A1x based board to u-boot you need to collect some information about your board. The most reliable source of this information is to inspect the boot1 file header. Unfortunately it's not entirely trivial how to reach that.
If you have UART console with access to u-boot loaded from NAND then you can dump the boot1 file header by running
md.b 0x42400000 0x2084
send the resulting output to me ([email protected]) together with a copy of your script.bin and the name of your board.
Usually you can easily extract script.bin by holding down the key '2' on the console while booting and then connect to the device with USB cable. On most A1x devices the boot partition then shows up as a removable USB device.
If you have console access but your u-boot do not allow you to halt the boot procedure then you can try replacing uboot.bin with the generic sun4i(A10) or sun5i(A13) versions to exract the information.
If you don't have console access to u-boot but have a SD breakout board then you can push the generic sun4i_sdcon(A10) or sun5i_sdcon(A13) versions to enable u-boot console on the SD breakout board.
Be warned that you may need to livesuit the device to restore NAND u-boot version to boot the Android from NAND again.
The watchdog command can be used to set a watchdog timeout. A timeout of 0 disables the watchdog. The watchdog have an upper limit of approximately 20 seconds.
You can enable automatic watchdog support by building with CONFIG_WATCHDOG enabled. This makes the watchdog armed by default. Be warned that If the kernel is not up and running and poking the watchdog within the watchdog timeout (approximately 20 seconds) then the watchdog will automatically reboot the system.
baudrate=115200
scriptaddr=0x44000000
bootscr=boot.scr
bootenv=uEnv.txt
loadbootscr=fatload mmc 0 ${scriptaddr} ${bootscr} || ext2load mmc 0 ${scriptaddr} ${bootscr} || ext2load mmc 0 ${scriptaddr} boot/${bootscr}
loadbootenv=fatload mmc 0 ${scriptaddr} ${bootenv} || ext2load mmc 0 ${scriptaddr} ${bootenv} || ext2load mmc 0 ${scriptaddr} boot/${bootenv}
boot_mmc=fatload mmc 0 0x43000000 script.bin && fatload mmc 0 0x48000000 ${kernel} && watchdog 0 && bootm 0x48000000
bootcmd=if run loadbootenv; then \
echo Loaded environment from ${bootenv}; \
env import -t ${scriptaddr} ${filesize}; \
fi; \
if test -n ${uenvcmd}; then \
echo Running uenvcmd ...; \
run uenvcmd; \
fi; \
if run loadbootscr; then \
echo Jumping to ${bootscr}; \
source ${scriptaddr}; \
fi; \
run setargs boot_mmc;"
bootdelay=3
console=ttyS0,115200
kernel=uImage
loglevel=8
panicarg=panic=10
root=/dev/mmcblk0p2
setargs=setenv bootargs console=${console} root=${root} loglevel=${loglevel} ${panicarg} ${extraargs}
stderr=serial
stdin=serial
stdout=serial
How the SD-Card is used by u-boot-mmc, counted in 1KB blocks:
start size
0 8KB Unused, available for partition table etc.
8 24KB Initial SPL loader
32 512KB u-boot
544 128KB environment
672 352KB reserved
1024 - Free for partitions