7 Note: There are currently seven 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?-????_config (see above Note!)
35 For all TX6 modules except TX6Q-1020:
36 -------------------------------------
37 If you want to replace a working U-Boot with a new version, you can
38 load the new U-Boot image via TFTP or SD-Card and write it to flash
39 with the 'romupdate' command.
41 If you want to revive a bricked module, U-Boot can be downloaded via
42 USB with the 'sbloader' tool in recovery boot mode (Bootmode jumper ST3
43 on Starterkit-5 baseboard closed). See TX6_U-Boot.pdf for details.
45 e.g.: /cdrom/Flashtools/Linux/sbloader/sbloader-x86_32 -m -s /cdrom/U-Boot/target/u-boot-tx6q-1010.bin
46 (This command can be used from within the ARMSK-VM)
50 The TX6Q-1020 is equipped with eMMC instead of NAND flash.
51 The bootloader, U-Boot environment and DTB is stored in the first boot
52 partition of the eMMC device. The command to update the bootloader
53 TX6Q U-Boot > set autostart n
54 TX6Q U-Boot > tftp u-boot-tx6q-1020.bin
55 TX6Q U-Boot > mmc open 0 1
56 TX6Q U-Boot > mmc write ${fileaddr} 0 400
57 TX6Q U-Boot > mmc close 0 1
62 For Windows users the application MfgTool allows the (re-)flashing of
63 U-Boot. For more information either see:
65 \U-Boot\TX6Q_U-Boot.pdf
66 \STK5_TX6Q_Quickstart_Guide.pdf
67 \Flashtools\Windows\Mfgtools-TX6...
73 Environment variables:
74 boot_mode selects which boot script will be used by 'bootcmd' to
75 boot the application (Linux)
77 nand: (default) load kernel from NAND partition 'linux'
78 and mount rootfs (fstype UBIFS)
79 from partition 'rootfs'.
80 mmc: load kernel from file 'uImage' on first
81 partition (FAT) on (first) SD/MMC card
82 and mount rootfs (fstype autodetected)
83 from second partition.
84 net: load kernel image via tftp (file uImage)
85 and mount rootfs via NFS. This requires
86 the additional variables 'nfsroot'
87 (path to rootfs on NFS server) and
88 'nfs_server' (hostname or IP address of
89 NFS server) to be set.
90 jffs2: (legacy) load kernel from NAND partition 'linux'
91 and mount rootfs (fstype JFFS2)
92 from partition 'rootfs'.
94 cpu_clk <CPU freq [MHz]> CPU clock frequency set after boot.
96 touchpanel {tsc2007|edt-ft5x06|egalax_ts} type of touchpanel.
97 No touchpanel will be enabled when unset.
99 otg_mode [host|device|none] operation mode of the USBOTG port
101 video_mode <one of the display names from the Glyn Family Concept or
102 a video mode as understood by Linux fb_find_mode() function
103 (e.g.: 640x480MR-24@60)>
104 LCD interface will be disabled when unset.
106 baseboard {stk5-v3|stk5-v5} selects type of baseboard
107 'stk5-v5' setting disables USB Host mode on USBOTG port
108 and redefines the LCD0 pin as CAN transceiver control pin.
109 Strings not starting in 'stk5' prevent the STK5 specific
110 pad initialization to be done.
112 splashimage either: memory address (e.g. ${loadaddr}) of a BMP file
113 to be displayed instead of the built-in logo. Since NAND
114 flash is not accessible in a memory mapped fashion,
115 U-Boot will try to load the contents of the flash
116 partition 'logo.bmp' to the address given with
119 or: the name of an MTD partition, that contains a raw
120 dump of the frame buffer contents which will be loaded
123 splashpos (when 'splashimage' contains a memory address) the
124 position ('x,y') on the screen at which the BMP image
126 Setting splashpos to 'm,m' will center the image on the
129 Note: Some variables (like 'cpu_clk' or 'splashimage') may render the
130 board unbootable if incorrectly set. Therefore these variables
131 will not be evaluated in case the board has been reset through a
132 watchdog reset or <CTRL-C> is detected on the serial console
133 during startup to give the user a chance to recover from this
134 situation. You should press and hold <CTRL-C> before applying
135 power to the module, for this to work.