Here is the pre-released version for HP Thin Client T5325 U-Boot-2015.10
Please see the HP Thin Client Debian working thread for how to install/setup the latest Debian kernel/rootfs for this box. The working thread is where the discussion and testing for this box have been done. Please post any question about u-boot in the working thread (this u-boot thread will be reopened for questions/comments once it is officially released)
Download at Dropbox
uboot.2015.10-tld-2.t5325.bodhi.tar
md5
ac89dbd287c5a7e9d10410756dbadedf
sha256
ab5543a28db6c0c05815c5ab829a727d042b09cabe2cc7799b72aae40d86dcf5
There are 2 files in the tarball
Please try UART booting with kwboot before flashing. Once it can be booted with kwboot, proceed to the instruction below.
WARNING: please proceed at your own risk. If you can't test this u-boot with UART booting then be aware of the risk of bricking the device should something goes wrong during installation (power outage, typos,..). And once the new u-boot is installed, it will not be possible to boot stock OS.
Also, it's a good idea to backup your current stock mtds for future restoration, should you decide to go back to stock.
Installation
The installation must be done while Debian or stock OS running. However, if installation is from stock OS, the Debian rootfs should be on USB drive and already mounted in the box before starting installation. The steps below assume that the Debian rootfs is mounted at /media/sdb1
1. Save current u-boot envs. This should be saved to a folder on the Debian rootfs so that it can be referenced during installation, or during recovery if something went bad during installtion.
2. Verify the Debian rootfs envs set up. Modify or add the fw_env.config file with the content below.
cat /media/sdb1/etc/fw_env.config
3. Verify the MTD flash definition in the current running system. Note the mtd0 and mtd2 definition, they must be identical to your current mtd0 and mtd2. Refer to the working thread for instruction if your MTD flash definition is not as shown below.
dmesg | grep spi
4. Flash u-boot to mtd0. If your running system does not have flashcp then use one in the rootfs: /media/sdb1/usr/sbin/flashcp
If there is any error, stop here and post at the working thread for help in recovery
5. Flash u-boot default envs to mtd2.
If there is any error, stop here and post at the working thread for help in recovery
6. Reference your saved current_envs.txt in step 1 and restore box specific info in u-boot envs.
a. Modify envs (replace xx below with your box specific settings)
b. Remove envs
Note:
The env dtb_file is removed with assumption that your rootfs has the T5325 DTB embedded inside uImage.
If booting with the latest Debian rootfs and using separate T5325 DTB (uImage is kept as original without DTB embedded inside it) then
7. Done.
Upon reboot, on serial/net console, u-boot banner should show
Please see the HP Thin Client Debian working thread for how to install/setup the latest Debian kernel/rootfs for this box. The working thread is where the discussion and testing for this box have been done. Please post any question about u-boot in the working thread (this u-boot thread will be reopened for questions/comments once it is officially released)
Download at Dropbox
uboot.2015.10-tld-2.t5325.bodhi.tar
md5
ac89dbd287c5a7e9d10410756dbadedf
sha256
ab5543a28db6c0c05815c5ab829a727d042b09cabe2cc7799b72aae40d86dcf5
There are 2 files in the tarball
uboot.2015.10-tld-2.t5325.mtd0.kwb uboot.2014.07-tld-3.environment.64K.img
Please try UART booting with kwboot before flashing. Once it can be booted with kwboot, proceed to the instruction below.
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-2.t5325.mtd0.kwb -p
WARNING: please proceed at your own risk. If you can't test this u-boot with UART booting then be aware of the risk of bricking the device should something goes wrong during installation (power outage, typos,..). And once the new u-boot is installed, it will not be possible to boot stock OS.
Also, it's a good idea to backup your current stock mtds for future restoration, should you decide to go back to stock.
Installation
The installation must be done while Debian or stock OS running. However, if installation is from stock OS, the Debian rootfs should be on USB drive and already mounted in the box before starting installation. The steps below assume that the Debian rootfs is mounted at /media/sdb1
1. Save current u-boot envs. This should be saved to a folder on the Debian rootfs so that it can be referenced during installation, or during recovery if something went bad during installtion.
cd /media/sdb1 fw_printenv > current_envs.txt
2. Verify the Debian rootfs envs set up. Modify or add the fw_env.config file with the content below.
cat /media/sdb1/etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors # HP T5325 Thin Client /dev/mtd2 0x00000 0x10000 0x10000
3. Verify the MTD flash definition in the current running system. Note the mtd0 and mtd2 definition, they must be identical to your current mtd0 and mtd2. Refer to the working thread for instruction if your MTD flash definition is not as shown below.
dmesg | grep spi
[ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env) earlyprintk=serial [ 1.577638] m25p80 spi0.0: m25p80 (1024 Kbytes) [ 1.582271] 5 cmdlinepart partitions found on MTD device spi0.0 [ 1.588221] Creating 5 MTD partitions on "spi0.0":dmesg | grep 0x0 | grep '"'
[ 1.593062] 0x000000000000-0x000000080000 : "uboot" [ 1.599248] 0x000000080000-0x0000000c0000 : "sdd_firmware" [ 1.606064] 0x0000000c0000-0x0000000d0000 : "uboot_env" [ 1.612592] 0x0000000d0000-0x0000000e0000 : "permanent_uboot_env" [ 1.619970] 0x0000000e0000-0x0000000f0000 : "hp_env"cat /proc/mtd
dev: size erasesize name mtd0: 00080000 00010000 "uboot" mtd1: 00040000 00010000 "sdd_firmware" mtd2: 00010000 00010000 "uboot_env" mtd3: 00010000 00010000 "permanent_uboot_env" mtd4: 00010000 00010000 "hp_env"
4. Flash u-boot to mtd0. If your running system does not have flashcp then use one in the rootfs: /media/sdb1/usr/sbin/flashcp
flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb /dev/mtd0Expected output
Erasing blocks: 8/8 (100%) Writing data: 512k/0k (100%) Verifying data: 512k/0k (100%)
If there is any error, stop here and post at the working thread for help in recovery
5. Flash u-boot default envs to mtd2.
flashcp -v uboot.2014.07-tld-3.environment.64K.img /dev/mtd2Expected output
Erasing blocks: 1/1 (100%) Writing data: 64k/0k (100%) Verifying data: 64k/0k (100%)
If there is any error, stop here and post at the working thread for help in recovery
6. Reference your saved current_envs.txt in step 1 and restore box specific info in u-boot envs.
a. Modify envs (replace xx below with your box specific settings)
fw_setenv arcNumber '2846' fw_setenv mtdparts 'mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)' fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx' fw_setenv ipaddr 'xxx.xxx.x.xx' fw_setenv serverip 'xxx.xxx.0.xxx' fw_setenv devices 'usb ide'
b. Remove envs
fw_setenv dtb_file fw_setenv mtdids fw_setenv partition fw_setenv machid
Note:
The env dtb_file is removed with assumption that your rootfs has the T5325 DTB embedded inside uImage.
If booting with the latest Debian rootfs and using separate T5325 DTB (uImage is kept as original without DTB embedded inside it) then
fw_setenv dtb_file '/boot/dts/kirkwood-t5325.dtb'
7. Done.
Upon reboot, on serial/net console, u-boot banner should show
U-Boot 2015.10-tld-2 (Mar 09 2016 - 16:49:35 -0800) HP Thin Client T5325