Welcome! Log In Create A New Profile

Advanced

HP T5325 Thin Client U-Boot-2016.05-tld-1

Posted by bodhi 
HP T5325 Thin Client U-Boot-2016.05-tld-1
March 10, 2016 05:56PM
This is the official released version for HP Thin Client T5325 U-Boot-2016.05-tld-1.

Download U-boot and defautl envs images at Dropbox

uboot.2016.05-tld-1.t5325.bodhi.tar
md5:
f8620b407a27da0f160edd13ee44c421
sha256:
c3c22d2f6224a2f7d0aa8650617cae100c3a7884ca6e4bbc0149cc209b8b4682

The above u-boot tarball contains the u-boot image only.

uboot.2016.05-tld-1.environment.bodhi.tar
md5:
3823eef10011b864859d31a76470e0e3
sha256:
c8db95a4225e8d78bdaaaa372bd5a87e4b98f3448dd9c62fc96c72b2df1a997c

The above envs tarball includes 3 files:

uboot.2016.05-tld-1.environment.img (the default envs image to be flashed on other Kirkwood box, not used here)
uboot.2016.05-tld-1.environment (the content of the default envs in text format)
uboot.2016.05-tld-1.environment.64K.img (small envs image to be flashed on HP T5325 only).


Please try UART booting with kwboot before flashing. Once it can be booted with kwboot, proceed to the installation instruction below.

./kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-1.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.


A. Installation from stock OS

Prerequisites

The Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs must be prepared in advance on a USB drive on a single Ext3 partition and already mounted in this box before starting installation. The installation steps below assume that the following 4 prerequisites have been met:

a. The rootfs was extracted as is, and step 4 in the Debian rootfs installation is skipped (since we are going to boot with new u-boot, don't append DTB to uImage).
b. The tarball uboot.2015.10-tld-2.t5325.bodhi.tar has been downloaded and place in the /boot folder of the USB rootfs
c. The USB rootfs will be the only USB drive mounted in the T5325 box.
d. The installation must be done while stock OS running.

Steps:

1. Boot into stock, mount the Debian rootfs, extract u-boot images

mkdir /tmp/sdb1
mount -o noatime /dev/sdb1 /tmp/sdb1
cd /tmp/sdb1/boot
tar -xf uboot.2016.05-tld-1.t5325.bodhi.tar
tar -xf uboot.2016.05-tld-1.environment.bodhi.tar

2. Save your current u-boot envs and backup your current stock mtds for future restoration, should you decide to go back to stock

cd /tmp/sdb1/boot
fw_printenv > current_envs.text
dd if=/dev/mtd0 of=t5325.mtd0 bs=64k conv=sync
dd if=/dev/mtd3 of=t5325.mtd3 bs=512k conv=sync

3. Verify the MTD flash definition in your running stock OS. Note the mtd0 and mtd3 definition, they must be identical to your current mtd0 and mtd3.

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00010000 00010000 "u-boot env"
mtd1: 00010000 00010000 "permanent u-boot env"
mtd2: 00010000 00010000 "HP env"
mtd3: 00080000 00010000 "u-boot"
mtd4: 00040000 00010000 "SSD firmware"

4. Flash u-boot to mtd3

cd /tmp/sdb1/boot
flash_unlock /dev/mtd3
flashcp -v uboot.2016.05-tld-1.t5325.mtd0.kwb   /dev/mtd3

Expected Output

Erasing blocks: 8/8 (100%)
Writing data: 512k/512k (100%)
Verifying data: 512k/512k (100%)

If there is any error, stop here and post for help in recovery

5. Flash u-boot default envs to mtd0.

cd /tmp/sdb1/boot
flash_unlock /dev/mtd0
flashcp -v uboot.2016.05-tld-1.environment.64K.img  /dev/mtd0

Expected Output

Erasing blocks: 1/1 (100%)
Writing data: 64k/64k (100%)
Verifying data: 64k/64k (100%)

If there is any error, stop here and post for help in recovery

6. And add fw_env.config to your stock OS. And then reference your saved current_envs.txt in step 2 to restore box specific info in u-boot envs.

a. Add fw_env.config to your stock OS.

echo "/dev/mtd0 0x00000 0x10000 0x10000" > /etc/fw_env.config

b. Modify envs and also setup netconsole. Replace xx below with your box specific settings.

/tmp/sdb1/usr/bin/fw_setenv arcNumber '2846'
/tmp/sdb1/usr/bin/fw_setenv mtdparts 'mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)'    
/tmp/sdb1/usr/bin/fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'
/tmp/sdb1/usr/bin/fw_setenv devices 'usb ide'
/tmp/sdb1/usr/bin/fw_setenv dtb_file '/boot/dts/kirkwood-t5325.dtb'

Setup netconsole envs (to activate later in Debian).

/tmp/sdb1/usr/bin/fw_setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then ./run start_netconsole; fi'
/tmp/sdb1/usr/bin/fw_setenv ipaddr    'xxx.xxx.x.xxx'
/tmp/sdb1/usr/bin/fw_setenv serverip 'xxx.xxx.x.xxx'

c. Remove envs

/tmp/sdb1/usr/bin/fw_setenv mtdids 
/tmp/sdb1/usr/bin/fw_setenv partition 
/tmp/sdb1/usr/bin/fw_setenv machid


7. Done.

Upon reboot, on serial/net console, u-boot banner should show

U-Boot 2016.05-tld-1 (Jun 12 2016 ….)
HP Thin Client T5325

B. Installation from the latest Debian rootfs

TBD.


============== below are old posts, kept for posterity ===================

This is the official released version for HP Thin Client T5325 U-Boot-2015.10-tld-2.

Download U-boot 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 installation 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.

Prerequisites

The Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs must be prepared in advance on a USB drive on a single Ext3 partition and already mounted in this box before starting installation. The installation steps below assume that the following 3 prerequisites have been met:

a. The rootfs was extracted as is, and step 4 in the Debian rootfs installation is skipped (since we are going to boot with new u-boot, don't append DTB to uImage).
b. The tarball uboot.2015.10-tld-2.t5325.bodhi.tar has been downloaded and place in the /boot folder of the USB rootfs
c. The USB rootfs will be the only USB drive mounted in the T5325 box.


Installation

The installation must be done while stock OS running.

1. Boot into stock, mount the Debian rootfs, extract u-boot images

mkdir /tmp/sdb1
mount -o noatime /dev/sdb1 /tmp/sdb1
cd /tmp/sdb1/boot
tar -xf uboot.2015.10-tld-2.t5325.bodhi.tar

2. Save your current u-boot envs and backup your current stock mtds for future restoration, should you decide to go back to stock

cd /tmp/sdb1/boot
fw_printenv > current_envs.text
dd if=/dev/mtd0 of=t5325.mtd0 bs=64k conv=sync
dd if=/dev/mtd3 of=t5325.mtd3 bs=512k conv=sync

3. Verify the MTD flash definition in your running stock OS. Note the mtd0 and mtd3 definition, they must be identical to your current mtd0 and mtd3.

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00010000 00010000 "u-boot env"
mtd1: 00010000 00010000 "permanent u-boot env"
mtd2: 00010000 00010000 "HP env"
mtd3: 00080000 00010000 "u-boot"
mtd4: 00040000 00010000 "SSD firmware"

4. Flash u-boot to mtd3

cd /tmp/sdb1/boot
flash_unlock /dev/mtd3
flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb   /dev/mtd3

Expected Output

Erasing blocks: 8/8 (100%)
Writing data: 512k/512k (100%)
Verifying data: 512k/512k (100%)

If there is any error, stop here and post for help in recovery

5. Flash u-boot default envs to mtd0.

cd /tmp/sdb1/boot
flash_unlock /dev/mtd0
flashcp -v uboot.2014.07-tld-3.environment.64K.img  /dev/mtd0

Expected Output

Erasing blocks: 1/1 (100%)
Writing data: 64k/64k (100%)
Verifying data: 64k/64k (100%)

If there is any error, stop here and post for help in recovery

6. And add fw_env.config to your stock OS. And then reference your saved current_envs.txt in step 2 to restore box specific info in u-boot envs.

a. Add fw_env.config to your stock OS.

echo "/dev/mtd0 0x00000 0x10000 0x10000" > /etc/fw_env.config

b. Modify envs and also setup netconsole. Replace xx below with your box specific settings.

/tmp/sdb1/usr/bin/fw_setenv arcNumber '2846'
/tmp/sdb1/usr/bin/fw_setenv mtdparts 'mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)'    
/tmp/sdb1/usr/bin/fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'
/tmp/sdb1/usr/bin/fw_setenv devices 'usb ide'
/tmp/sdb1/usr/bin/fw_setenv dtb_file '/boot/dts/kirkwood-t5325.dtb'

Setup netconsole envs (to activate later in Debian).

/tmp/sdb1/usr/bin/fw_setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then ./run start_netconsole; fi'
/tmp/sdb1/usr/bin/fw_setenv ipaddr    'xxx.xxx.x.xxx'
/tmp/sdb1/usr/bin/fw_setenv serverip 'xxx.xxx.x.xxx'

c. Remove envs

/tmp/sdb1/usr/bin/fw_setenv mtdids 
/tmp/sdb1/usr/bin/fw_setenv partition 
/tmp/sdb1/usr/bin/fw_setenv machid


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

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 20 time(s). Last edit at 06/20/2016 05:59AM by bodhi.
Re: HP T5325 Thin Client u-boot-2015.10-tld-2 for testing
May 21, 2016 05:39AM
I've found that flashing new u-boot on this will work only after we run kwboot to boot the new u-boot and boot into Debian.

So I'll need to revise the instruction for flashing that way. Unless I can figure out why the SPI flash seems to act a different way... Perhaps becasue the old driver in stock u-boot vs the new driver in the new u-boot.

Looks like CV has confirmed this, too (I just did not pay attention this fact before :):
http://forum.doozan.com/read.php?2,25473,26717#msg-26717

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 05/22/2016 05:06AM by bodhi.
Re: HP T5325 Thin Client u-boot-2015.10-tld-2 for testing
May 29, 2016 05:12PM
I've released this HP Thin Client T5325 u-boot-2015.10-tld-2. Please see 1st post for new installation instruction.

Please post questions as you wish in this thread.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 2 time(s). Last edit at 05/29/2016 05:34PM by bodhi.
Re: HP T5325 Thin Client u-boot-2015.10-tld-2
May 30, 2016 11:48AM
Cool! Will try it soon If it possible to boot stock os from it.
Is there any changelog?
Re: HP T5325 Thin Client u-boot-2015.10-tld-2
May 30, 2016 04:29PM
xssa Wrote:
-------------------------------------------------------
> Cool! Will try it soon If it possible to boot
> stock os from it.
> Is there any changelog?

It is the same one that I uploaded before for testing (there was no change). I just made it an official release, with the installation instruction from stock. It is no longer in testing phase.

I would like to hear from users who try this u-boot on box with sst25vf080b flash and kernel 4.4+. kwboot this u-boot and boot into Debian on a USB stick. This test does not commit you to this u-boot or Debian.

To boot stock OS from the new u-boot is another subject that will take some time. Stock OS uses a customized init, so it might have some hardcoded kernel parameters.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client u-boot-2015.10-tld-2
June 01, 2016 09:11PM
bodhi Wrote:
-------------------------------------------------------
> xssa Wrote:
> --------------------------------------------------

> To boot stock OS from the new u-boot is another
> subject that will take some time. Stock OS uses a
> customized init, so it might have some hardcoded
> kernel parameters.

I have a T5325 and think where you got us now is better than we could have hoped for at the beginning. It's selfish but I would rather hope for your expertise and resources (aka time) with other boxes in particular updating the Pro kernel if that is ever possible with the obstacles you have outlined.

Like I said, kinda selfish

LeggoMyEggo's Google Plus Profile
Re: HP T5325 Thin Client u-boot-2015.10-tld-2
June 02, 2016 01:54AM
LeggoMyEggo Wrote:
-------------------------------------------------------
> better than we could have hoped for at the
> beginning. It's selfish but I would rather hope
> for your expertise and resources (aka time) with
> other boxes in particular updating the Pro kernel
> if that is ever possible with the obstacles you
> have outlined.
>
> Like I said, kinda selfish

Sure. I'll get back to the Pogo V3 soon. I think we've got this T5325 solved to the last mystery :) I kinda like this box, I think we got our money worth, thanks Gravelrash!. Especially with the display and the sound, those are new subjects here, and we've hacked it.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client u-boot-2015.10-tld-2
June 08, 2016 06:21PM
@all

A round of applause for you all!
Re: HP T5325 Thin Client u-boot-2015.10-tld-2
June 11, 2016 09:04PM
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
June 20, 2016 05:30AM
For anybody who has this T5325 box and only follows this thread. I've released 2016.05-tld-1 U-Boot images in the main u-boot release thread.. Please go there for general information about the new u-boot-2016.05-tld-1.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
August 01, 2016 11:37PM
I'm trying this thread on a T5325 and I am having an issue. When the bootcmd script attempts to run the load_initrd script it results in the following error:

loading uInitrd ...
EHCI timed out on TD - token=0xc0008d80
EHCI timed out on TD - token=0x40008d80
EHCI timed out on TD - token=0x40008d80
 ** ext4fs_devread read error - block

I've also tried the following:

T5325> ext4ls usb 0:1 /boot
<DIR>       4096 .
<DIR>       4096 ..
          140949 config-4.4.0-kirkwood-tld-1
         3154832 vmlinuz-4.4.0-kirkwood-tld-1
         7179935 uInitrd
         7179871 initrd.img-4.4.0-kirkwood-tld-1
         2240040 System.map-4.4.0-kirkwood-tld-1
<DIR>       4096 dts
         3154896 uImage
         7511582 linux-headers-4.4.0-kirkwood-tld-1_1.0_armel.deb
         3154832 zImage-4.4.0-kirkwood-tld-1
          532480 uboot.2016.05-tld-1.t5325.bodhi.tar
          204800 uboot.2016.05-tld-1.environment.bodhi.tar
<DIR>       4096 stock-backup
          524288 uboot.2016.05-tld-1.t5325.mtd0.kwb
          131072 uboot.2016.05-tld-1.environment.img
           65536 uboot.2016.05-tld-1.environment.64K.img
            2773 uboot.2016.05-tld-1.environment
T5325> ext4load usb 0:1 $load_initrd_addr /boot/uInitrd
EHCI timed out on TD - token=0x40008d80
EHCI timed out on TD - token=0x40008d80
EHCI timed out on TD - token=0x40008d80
 ** ext4fs_devread read error - block
T5325>

Any suggestions on what to try next?


Ray
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
August 02, 2016 12:22AM
Solved my problem by using another USB drive. The cheap 8GB Emtec stick I used appears to have been the issue. Now using a 4GB SanDisk drive with no issues.

Ray
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
August 02, 2016 01:01AM
rayknight Wrote:
-------------------------------------------------------
> Solved my problem by using another USB drive.
> The cheap 8GB Emtec stick I used appears to have
> been the issue. Now using a 4GB SanDisk drive
> with no issues.
>
> Ray

Cool! Sandisk USB brand is always the best for booting.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
August 02, 2016 01:04AM
HP T5325 appears to have an issue with fw_printenv. I've booted a USB drive prepared with Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 according to instructions and the following contents in the fw_env.config file:

/dev/mtd0 0x00000 0x10000 0x10000

Issuing the fw_printenv command results in the following:

root@debian:~# fw_printenv
Warning: Bad CRC, using default environment
bootargs=
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=3
baudrate=115200
stdin=serial,cros-ec-keyb
stdout=serial,lcd
stderr=serial,lcd

Does the fw_env.config file need to change? The mtdparts set in Step 6b doesn't seem to match the stock mtd partitions.

/tmp/sdb1/usr/bin/fw_setenv mtdparts 'mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)'

This appears to put uboot at mtd0 and sdd_firmware at mtd1 where the stock firmware had them at mtd3 and mtd4!

Ray
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
August 02, 2016 01:11AM
rayknight Wrote:
-------------------------------------------------------
> HP T5325 appears to have an issue with
> fw_printenv. I've booted a USB drive prepared
> with
> Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> according to instructions and the following
> contents in the fw_env.config file:
>
>
> /dev/mtd0 0x00000 0x10000 0x10000
>
>
> Issuing the fw_printenv command results in the
> following:
>
>
> root@debian:~# fw_printenv
> Warning: Bad CRC, using default environment
> bootargs=
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
> ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:$
> {hostname}::off; bootm
> bootdelay=3
> baudrate=115200
> stdin=serial,cros-ec-keyb
> stdout=serial,lcd
> stderr=serial,lcd
> 
>
>
> Does the fw_env.config file need to change? The
> mtdparts set in Step 6b doesn't seem to match the
> stock mtd partitions.
>
>
> /tmp/sdb1/usr/bin/fw_setenv mtdparts
> 'mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64
> K(uboot_env),64K(permanent_uboot_env),64K(hp_env)'
>    
>
>
> This appears to put uboot at mtd0 and sdd_firmware
> at mtd1 where the stock firmware had them at mtd3
> and mtd4!
>
> Ray

Yes, it was purposely redefined to make it saner. mtd0 is where u-boot should reside, but the location layout is the same.

The u-boot envs location is at 0xc00000 already in stock. So I redefined it to be mtd2. That way u-boot can be properly at mtd0 and location 0x0.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 10:21AM
Just a quick question.
What ipaddr and serverip should I put in netconsole?

/tmp/sdb1/usr/bin/fw_setenv ipaddr    'xxx.xxx.x.xxx'
/tmp/sdb1/usr/bin/fw_setenv serverip 'xxx.xxx.x.xxx'

Is it the fixed ip address I want to assign to t5325 in local network?
What is serverip? Router ip address?
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 10:29AM
kalehrl Wrote:
-------------------------------------------------------
> Just a quick question.
> What ipaddr and serverip should I put in netconsol
> e?
>
>
> /tmp/sdb1/usr/bin/fw_setenv ipaddr    'xxx.xxx.x.x
> xx'
> /tmp/sdb1/usr/bin/fw_setenv serverip 'xxx.xxx.x.xx
> x'
>
>
> Is it the fixed ip address I want to assign to t53
> 25 in local network?
> What is serverip? Router ip address?

ipaddr is the ip you want your t5325 to have in the local network

serverip is the ip address of the machine you want to use to connect to the t5325 from (the one you are using to connect by serial from probably)
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 12:25PM
Thank you. I installed the uboot following this thread and everything went fine.
No errors were reported. I also created Debian rootfs following another thread.
I used fw_setenv ipaddr '192.168.1.10' as it was previously assigned to t5325 by my router and fw_setenv serverip '192.168.1.2' which is the ip of my PC because I use it to connect to t5325 .
Upon reboot, I couldn't ssh to the box using 192.168.1.10. My router didn't give any other address to the box.
I connected it to a monitor to see what it displayed on it, but the monitor is just blank.
For 15 seconds, it's off and then it turns on but there is nothing on it, just blank, black picture.
There is some activity with the USB drive because its LED is flashing but after some time it's just on.
Funny enough, I can reboot the box by pressing ctl-alt-del.
Any ideas what may be the problem?
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 12:32PM
Can you connect through serial to the box?
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 12:34PM
Not yet because it will arrive at the beginning of the next week.
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 12:46PM
can you access it with netconsole?
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 02:10PM
What's that? I thought it was putty from windows accessing a remote box.
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 02:30PM
kalehrl Wrote:
-------------------------------------------------------
> What's that? I thought it was putty from windows a
> ccessing a remote box.


Netconsole (netcat) lets you access the box without a serial cable thru your network connection hence the different ip addresses as stated at the top of this topic in 6b. and what you set.

Here is an article that explains it. I do not vouch for the links to the downloads for it for windows.

https://linhost.info/2011/05/netcat-for-windows/
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 02:55PM
What is the default port?
I'm trying with this command line but nothing appears:
.\nc -l -u 192.168.1.10 -p 6666
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 03:39PM
kalehrl Wrote:
-------------------------------------------------------
> What is the default port?
> I'm trying with this command line but nothing appe
> ars:
>
> .\nc -l -u 192.168.1.10 -p 6666
>

This post describes running it. Once it is running on your pc restart your t5325 and see if you get anything.

http://forum.doozan.com/read.php?3,14,page=1
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 04:43PM
Let's back track a bit. neconsole will not work if you have not set it the env to start it.

/tmp/sdb1/usr/bin/fw_setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then ./run start_netconsole; fi'

The above line in my instruction set it up. But to activate it , you would need to do one extra step, which is seeting to preboot env to run preboot_nc. I left this out because a typo in this env would lock users out of the box.


By the way, this command has always worked for me:

.\nc -lup 6666 192.168.1.10  6666

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 05:18PM
bodhi Wrote:
-------------------------------------------------------
> Let's back track a bit. neconsole will not work if
> you have not set it the env to start it.
>
>
> /tmp/sdb1/usr/bin/fw_setenv preboot_nc 'setenv nc_
> ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; i
> f run if_netconsole; then setenv nc_ready 1; fi; d
> one; if test $nc_ready -eq 1; then ./run start_net
> console; fi'
>
>
> The above line in my instruction set it up. But to
> activate it , you would need to do one extra step,
> which is seeting to preboot env to run preboot_nc.
> I left this out because a typo in this env would l
> ock users out of the box.
>
>
> By the way, this command has always worked for me:
>
>
> .\nc -lup 6666 192.168.1.10  6666
>

So did I mess him up by having him enter his ip's?
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 06:25PM
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 06:29PM
I see I was wrong! Sorry :)

This is u-boot installation instruction:

Quote

10. Set up netconsole. It's important to set up neconsole if you don't already have serial console connected. If you've flashed the default environments in step 8 then activate netconsole with the following envs:

fw_setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi'
fw_setenv preboot 'run preboot_nc'
fw_setenv ipaddr '192.168.0.xxx'
fw_setenv serverip '192.168.0.yyy'

where the 192.168.0.xxx is this plug IP address, and 192.168.0.yyy is the IP address of the netconsole server where it will monitor the output from the this plug (adjust them to the real values in your own local network settings).

I did change the instruction and forgot about it :))

So at this point netconsole was activated.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 2 time(s). Last edit at 07/29/2017 06:32PM by bodhi.
Re: HP T5325 Thin Client U-Boot-2016.05-tld-1
July 29, 2017 07:12PM
so if it is running he should be able to see it boot and get a login prompt right?
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: