Welcome! Log In Create A New Profile

Advanced

HP T5325 Thin Client Debian

Posted by Gravelrash 
JRD McLAREN
Re: HP T5325 Thin Client Debian
April 13, 2017 01:42PM
So ...
Stock ubot & envs are inside ..
and LAN work ... :)

but, it is not so easy, as it seems to be..

For the first time, I will try back serial uboot, from mtd3 image via flash-write command.
No success, verify failed.
Then try to flash from original HP Uboot update file, and still no "happy end" ..
..and after reboot, I have "one nice piece of electo-garbage" .. oh yes, it is bricked...

We started "rescue mission" ....
Desolder flash, read images from working one, split it ... and try to flash via programer.
..but...
Desoldered flash is not accessible or read&verify errors ocured.
We try to erase it. After two (or three) forced retries, we have accessible flash.
After this "procedure", we have fully accessible, readable and writable flash ..

(yes, It is strange ..)
Re: HP T5325 Thin Client Debian
April 15, 2017 08:51AM
Hey. When I try to update Uboot, the following errors occur.

[root@router]~# flash_unlock /dev/mtd3
flash_unlock: error!: could not open: /dev/mtd3
              error 13 (Permission denied)
[root@router]~# flash_unlock /dev/mtd0
flash_unlock: error!: could not unlock device: /dev/mtd0

              error 95 (Operation not supported)

What could be the problem?

[root@router]~# uname -a
Linux router 3.16.0-4-kirkwood #1 Debian 3.16.39-1+deb8u2 (2017-03-07) armv5tel GNU/Linux

[root@router]~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00010000 00001000 "u-boot env"
mtd1: 00010000 00001000 "permanent u-boot env"
mtd2: 00010000 00001000 "HP env"
mtd3: 00080000 00001000 "u-boot"
mtd4: 00040000 00001000 "SSD firmware"

[root@router]~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=63764,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=102740k,mode=755)
/dev/sdb1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/sda1 on /boot type ext2 (rw,relatime)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)



Edited 1 time(s). Last edit at 04/15/2017 08:53AM by WMLex.
Re: HP T5325 Thin Client Debian
April 15, 2017 04:15PM
WMLex,

I have only provided installation instruction from stock OS. Try booting into stock OS and install from there.

Not a lot of people have this device, so nobody has remined me to write section B :) It is possible, I just need to refresh my memory again and write it.

Quote

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.

-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 04/15/2017 04:22PM by bodhi.
JRD McLAREN
Re: HP T5325 Thin Client Debian
April 16, 2017 07:42AM
WMLex, try mtdinfo -a command.
root@hpt5325:/etc# mtdinfo -a
Count of MTD devices:           5
Present MTD devices:            mtd0, mtd1, mtd2, mtd3, mtd4
Sysfs interface supported:      yes

mtd0
Name:                           u-boot env
Type:                           nor
Eraseblock size:                65536 bytes, 64.0 KiB
Amount of eraseblocks:          1 (65536 bytes, 64.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:0
Bad blocks are allowed:         false
Device is writable:             true

mtd1
Name:                           permanent u-boot env
Type:                           nor
Eraseblock size:                65536 bytes, 64.0 KiB
Amount of eraseblocks:          1 (65536 bytes, 64.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:2
Bad blocks are allowed:         false
Device is writable:             false

mtd2
Name:                           HP env
Type:                           nor
Eraseblock size:                65536 bytes, 64.0 KiB
Amount of eraseblocks:          1 (65536 bytes, 64.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:4
Bad blocks are allowed:         false
Device is writable:             true

mtd3
Name:                           u-boot
Type:                           nor
Eraseblock size:                65536 bytes, 64.0 KiB
Amount of eraseblocks:          8 (524288 bytes, 512.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:6
Bad blocks are allowed:         false
Device is writable:             false

mtd4
Name:                           SSD firmware
Type:                           nor
Eraseblock size:                65536 bytes, 64.0 KiB
Amount of eraseblocks:          4 (262144 bytes, 256.0 KiB)
Minimum input/output unit size: 1 byte
Sub-page size:                  1 byte
Character device major/minor:   90:8
Bad blocks are allowed:         false
Device is writable:             true

root@hpt5325:/etc#
Re: HP T5325 Thin Client Debian
April 18, 2017 09:22AM
Many thanks, everything worked out.
There was one more problem, I can not install a new debian stretch.
uImage
uInitrd
device usb 0:1
reading /boot/uImage
1 bytes read in 23 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
reading /boot/uImage
2054677 bytes read in 92 ms (21.3 MiB/s)
loading uInitrd ...
reading /boot/uInitrd
11680480 bytes read in 387 ms (28.8 MiB/s)
loading DTB /boot/dts/kirkwood-t5325.dtb ...
reading /boot/dts/kirkwood-t5325.dtb
11889 bytes read in 41 ms (282.2 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Debian kernel
   Created:      2017-04-07  19:08:13 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2054613 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   debian-installer ramdisk
   Created:      2017-04-07  19:08:13 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11680416 Bytes = 11.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
The previous version was installed without problems.
uImage
uInitrd
Re: HP T5325 Thin Client Debian
April 19, 2017 02:02AM
WMLex,

> Image Name: debian-installer ramdisk
> Created: 2017-04-07 19:08:13 UTC
> Image Type: ARM Linux RAMDisk Image (gzip com
> pressed)
> Data Size: 11680416 Bytes = 11.1 MiB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... Bad Data CRC
> Ramdisk image is corrupt or invalid

This problem usually is not because of the new kernel or Debian version. It is usually because you might have not synched the disk before reboot, or the roofs filesystem was corrupted.

Please describe how did you create this rootfs, and which kernels have been installled in this rootfs since you created it, and what procedure used in doing that. Even better if you can post the entire log of what you done.

-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 Debian
April 19, 2017 02:19AM
I did not create anything, I downloaded uImage and uInitrd.
http://ftp.debian.org/debian/dists/stretch/main/installer-armel/current/images/kirkwood/netboot/marvell/openrd-ultimate/
When I try to boot, the following error occurs.
The previous version was installed without problems.
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/openrd/
Re: HP T5325 Thin Client Debian
April 19, 2017 04:17AM
WMLex,

> I did not create anything, I downloaded uImage and
> uInitrd.

Ah! I see that you're not familiar with kernel installtion procedure.

The full GNU/Linux system includes a rootfs and a kernel installed on that rootfs. The USB partition that you're booting with must contain a rootfs. And then it's up to you to install a kernel to run inside that rootfs. Or if you use my rootfs (Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2) then the custom 4.4 kernel is already installed inside this rootfs.

You've download uImage and uInitrd only, but did not install the full kernel. For example, this is the installation command to install one of my customed kernels:
dpkg -i linux-image-4.8.0-kirkwood-tld-1_1.0_armel.deb
You can also run the Debian installer to install a mainline kernel (without patches as in my customed kernel).

When you download the uImage and uInitrd only, then sometime it will work. But a lot times it will not. Because the kernel headers might be different between versions.

-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 Debian
April 19, 2017 09:01AM
Unfortunately I can not boot from Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi
[    4.376788] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-label/rootfs does not exist.  Dropping to a shell!
modprobe: module i8042 not found in modules.dep
[   43.854574] uhci_hcd: USB Universal Host Controller Interface driver
[   43.871270] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   43.888658] usbcore: registered new interface driver usbhid
[   43.894456] usbhid: USB HID core driver


BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) [  102.537465] random: nonblocking pool is initialized
Full boot log attached to the message.

My environment.
T5325>  printenv
arcNumber=2846
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=3
bootdev=usb
device=0:1
devices=usb ide
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-t5325.dtb
ethact=egiga0
ethaddr=f4:ce:46:24:67:f7
if_netconsole=ping $serverip
ipaddr=10.4.50.147
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000\

load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdparts=mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)
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
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=10.4.50.5
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 2961/65532 bytes
Attachments:
open | download - bootlog.txt (18.1 KB)
Re: HP T5325 Thin Client Debian
April 19, 2017 09:39PM
WMLex,

1. Make sure you followed the instruction to create the Debian 4.4 rootfs very closely (being root, label the partion name as rootfs, single ext3 partition...).

2. If after verifying the rootfs creation, it still got stuck as above, try using a different thumb drive.

-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
JRD McLAREN
Re: HP T5325 Thin Client Debian
April 24, 2017 02:56PM
..so ...
is BTRFS supported ..?? .. in your kernel ..??

cause I have one box with debian, 32Mb Boot EXT2 (due to uboot)
and all other space on stock flash as BTRFS (aprox 460Mb)..
no thumb drive is needed..
Re: HP T5325 Thin Client Debian
April 24, 2017 05:07PM
JRD McLAREN Wrote:
-------------------------------------------------------
> ..so ...
> is BTRFS supported ..?? .. in your kernel ..??
>
> cause I have one box with debian, 32Mb Boot EXT2 (
> due to uboot)
> and all other space on stock flash as BTRFS (aprox
> 460Mb)..
> no thumb drive is needed..

Yes, it is supported.

-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 Debian
May 31, 2017 01:18AM
Is there any way to unbrick a T5325? I issued a fw_setenv command from my completed install (bodhi's 4.4.0), and the device no longer brings up uboot. I confimed my cable setup works, as I have another T5325 that still brings up uboot and bootstraps properly. I'm wondering if I might've corrupted /dev/mtd0 by chance. I've spent the last 2 days lurking and reading on the forums (this and others) before posting something.
Re: HP T5325 Thin Client Debian
May 31, 2017 03:21AM
csulaguy Wrote:
-------------------------------------------------------
> Is there any way to unbrick a T5325? I issued a fw
> _setenv command from my completed install (bodhi's
> 4.4.0), and the device no longer brings up uboot.
> I confimed my cable setup works, as I have another
> T5325 that still brings up uboot and bootstraps pr
> operly. I'm wondering if I might've corrupted /dev
> /mtd0 by chance. I've spent the last 2 days lurkin
> g and reading on the forums (this and others) befo
> re posting something.

Sure, you can connect serial console and use UART booting (loading u-boot using kwboot) to boot the box.

Download u-boot:
http://forum.doozan.com/read.php?3,12381

UART booting:
http://forum.doozan.com/read.php?3,7852,7852

If you have installed my released u-boot image and you think only the u-boot envs are messed up, you can use uEnv.txt capability to restore. No serial console is needed in this case.

-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/31/2017 03:24AM by bodhi.
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: