7 Note: There are currently six variants of the TX51 module, that
8 require slightly different U-Boot configurations. They are
9 distinguished through the first and last digit of the module
10 name suffix. Replace the '?' in the following description with
11 the corresponding numbers from your TX51 module.
12 E.g. TX51-8021 => 'make tx51-8xx1_config'
18 tar -xjf /cdrom/U-Boot/u-boot-src.tar.bz2
20 Alternatively you can access the current source via the git repository:
21 git://git.kernelconcepts.de/karo-tx-uboot.git master
27 export CROSS_COMPILE=arm-cortexa8-linux-gnueabi-
28 make tx51-?xx?_config (see above Note!)
34 If you want to replace a working U-Boot with a new version, you can
35 load the new U-Boot image via TFTP and program it like any other flash
37 nand erase.part u-boot;nand write ${fileaddr} u-boot ${filesize}
39 If you want to revive a bricked module, you can use one of the
40 flashtools provided with the BSP to reprogram the flash.
46 Environment variables:
48 cpu_clk <CPU freq [MHz]>
49 touchpanel {tsc2007|edt-ft5x06}
50 otg_mode [host|device|none]
51 video_mode <video mode as understood by Linux fb_find_mode() function>
52 e.g.: VGA-1:640x480MR-24@60
53 baseboard {stk5-v3|stk5-v5} selects type of baseboard
54 'stk5-v5' setting disables USB Host mode on USBOTG port.
55 strings not starting in 'stk5' prevent the STK5 specific
56 pad initialization to be done.
57 splashimage either: memory address (e.g. ${loadaddr}) of a BMP file
58 to be displayed instead of the built-in logo. Since NAND
59 flash is not accessible in a memory mapped fashion,
60 U-Boot will try to load the contents of the flash
61 partition 'logo.bmp' to the address given with
64 or: the name of an MTD partition, that contains a raw
65 dump of the frame buffer contents which will be loaded
68 splashpos (when 'splashimage' contains a memory address) the
69 position ('x,y') on the screen at which the BMP image
71 Setting splashpos to 'm,m' will center the image on the
74 Note: Some variables (like 'cpu_clk' or 'splashimage') may render the
75 board unbootable if incorrectly set. Therefore these variables
76 will not be evaluated in case the board has been reset through a
77 watchdog reset or a character is available on the serial console
78 during startup to give the user a chance to recover from this