7 Note: There are currently two variants of the TX53 module, that
8 require slightly different U-Boot configurations. They are
9 distinguished through the last digit of the module name. Replace
10 the '?' in the following description with the corresponding
11 number from your TX51 module.
12 E.g. TX53-8031 => 'make tx53-xx31_config'
18 tar -xjf /cdrom/U-Boot/u-boot-src.tar.bz2
23 export CROSS_COMPILE=arm-cortexa8-linux-gnueabi-
24 make tx28-4?xx_config (see above Note!)
30 If you want to replace a working U-Boot with a new version, you can
31 load the new U-Boot image via TFTP and program it like any other flash
33 nand erase.part u-boot;nand write.trimffs ${fileaddr} u-boot ${filesize}
35 If you want to revive a bricked module, U-Boot can be downloaded via
36 USB with the 'sbloader' tool in recovery boot mode (Jumper ST3
37 on Starterkit-5 baseboard closed). See TX28-U-Boot.pdf for details.
43 Environment variables:
45 cpu_clk <CPU freq [MHz]>
46 touchpanel {tsc2007|edt-ft5x06}
47 otg_mode [host|device|none]
48 video_mode <video mode as understood by Linux fb_find_mode() function>
49 e.g.: VGA-1:640x480MR-24@60
50 baseboard {stk5-v3|stk5-v5} selects type of baseboard
51 splashimage either: memory address (e.g. ${loadaddr}) of a BMP file
52 to be displayed instead of the built-in logo. Since NAND
53 flash is not accessible in a memory mapped fashion,
54 U-Boot will try to load the contents of the flash
55 partition 'logo.bmp' to the address given with
58 or: the name of an MTD partition, that contains a raw
59 dump of the frame buffer contents which will be loaded
62 splashpos (when 'splashimage' contains a memory address) the
63 position ('x,y') on the screen at which the BMP image
65 Setting splashpos to 'm,m' will center the image on the
68 Note: Some variables (like 'cpu_clk' or 'splashimage') may render the
69 board unbootable if incorrectly set. Therefore these variables
70 will not be evaluated in case the board has been reset through a
71 watchdog reset or a character is available on the serial console
72 during startup to give the user a chance to recover from this