7 Note: There are currently six variants of the TX6 module, that
8 require slightly different U-Boot configurations. They are
9 distinguished through the 'TX6' suffix 'Q' or 'U' and the
10 numerical suffix of the module name. Replace the '?' in the
11 following description with the corresponding digits from your
13 E.g. TX6Q-1010 => 'make tx6q-1010_config'
19 tar -xjf /cdrom/U-Boot/u-boot-src.tar.bz2
21 Alternatively you can access the current source via the git repository:
22 git://git.karo-electronics.de/karo-tx-uboot.git master
28 export CROSS_COMPILE=arm-cortexa9-linux-gnueabi-
29 make tx6?-??1?_config (see above Note!)
35 If you want to replace a working U-Boot with a new version, you can
36 load the new U-Boot image via TFTP or SD-Card and write it to flash
37 with the 'romupdate' command.
39 If you want to revive a bricked module, U-Boot can be downloaded via
40 USB with the 'sbloader' tool in recovery boot mode (Bootmode jumper ST3
41 on Starterkit-5 baseboard closed). See TX6_U-Boot.pdf for details.
43 e.g.: /cdrom/Flashtools/Linux/sbloader/sbloader-x86_32 -m -s /cdrom/U-Boot/target/u-boot-tx6q-1010.bin
44 (This command can be used from within the ARMSK-VM)
48 For Windows users the application MfgTool allows the (re-)flashing of
49 U-Boot. For more information either see:
51 \U-Boot\TX6Q_U-Boot.pdf
52 \STK5_TX6Q_Quickstart_Guide.pdf
53 \Flashtools\Windows\Mfgtools-TX6...
59 Environment variables:
60 boot_mode selects which boot script will be used by 'bootcmd' to
61 boot the application (Linux)
63 nand: (default) load kernel from NAND partition 'linux'
64 and mount rootfs (fstype UBIFS)
65 from partition 'rootfs'.
66 mmc: load kernel from file 'uImage' on first
67 partition (FAT) on (first) SD/MMC card
68 and mount rootfs (fstype autodetected)
69 from second partition.
70 net: load kernel image via tftp (file uImage)
71 and mount rootfs via NFS. This requires
72 the additional variables 'nfsroot'
73 (path to rootfs on NFS server) and
74 'nfs_server' (hostname or IP address of
75 NFS server) to be set.
76 jffs2: (legacy) load kernel from NAND partition 'linux'
77 and mount rootfs (fstype JFFS2)
78 from partition 'rootfs'.
80 cpu_clk <CPU freq [MHz]> CPU clock frequency set after boot.
82 touchpanel {tsc2007|edt-ft5x06|egalax_ts} type of touchpanel.
83 No touchpanel will be enabled when unset.
85 otg_mode [host|device|none] operation mode of the USBOTG port
87 video_mode <one of the display names from the Glyn Family Concept or
88 a video mode as understood by Linux fb_find_mode() function
89 (e.g.: 640x480MR-24@60)>
90 LCD interface will be disabled when unset.
92 baseboard {stk5-v3|stk5-v5} selects type of baseboard
93 'stk5-v5' setting disables USB Host mode on USBOTG port
94 and redefines the LCD0 pin as CAN transceiver control pin.
95 Strings not starting in 'stk5' prevent the STK5 specific
96 pad initialization to be done.
98 splashimage either: memory address (e.g. ${loadaddr}) of a BMP file
99 to be displayed instead of the built-in logo. Since NAND
100 flash is not accessible in a memory mapped fashion,
101 U-Boot will try to load the contents of the flash
102 partition 'logo.bmp' to the address given with
105 or: the name of an MTD partition, that contains a raw
106 dump of the frame buffer contents which will be loaded
109 splashpos (when 'splashimage' contains a memory address) the
110 position ('x,y') on the screen at which the BMP image
112 Setting splashpos to 'm,m' will center the image on the
115 Note: Some variables (like 'cpu_clk' or 'splashimage') may render the
116 board unbootable if incorrectly set. Therefore these variables
117 will not be evaluated in case the board has been reset through a
118 watchdog reset or <CTRL-C> is detected on the serial console
119 during startup to give the user a chance to recover from this
120 situation. You should press and hold <CTRL-C> before applying
121 power to the module, for this to work.