Debian on HP T5325 Thin Client

Gravelrash,

It is in the first post of the u-boot thread: http://forum.doozan.com/read.php?3,12381

Quote

=======================================================
Last Updated 13 Nov 2015

I've uploaded 2015.10-tld-1 U-Boot images for Pogo E02, GoFlexNet, GoFlex Home, Dockstar, Pogo V4/Mobile, iConnect, Netgear Stora, Sheevaplug, NSA320, NSA325, NSA310S/320S (same image), and NSA310.

Important Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction here in this thread. The latest u-boot image released here should be used for UART booting, if your box is the type that supports it (these do not: Dockstar, Pogo E02, iConnect).

To download ARM kwboot binary for UART booting at Dropbox:
kwboot
md5:
0efd011bdb244436e432a8de33e639a1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

definitely the hardware (Prolific clone). The result is consistent with the x64 system when using it on an orangepi

gravelrash@4320 ~ $ ssh root@orangepi.local
root@orangepi.local's password: 
Linux orangepi 3.4.39 #41 SMP PREEMPT Sun Jun 21 13:09:26 HKT 2015 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@orangepi:~# cd /scripts/
root@orangepi:/scripts# ./kw
Sending boot message. Please reboot the target...\^Z
[1]+  Stopped                 ./kw
root@orangepi:/scripts# ./kw

root@orangepi:/scripts# ./pogoconsole 
^A^X to exit

picocom v1.7

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,

Terminal ready
�
       _   _     .____    
      | |_| |    |  _ \  
      |  _  |    | (_))   
      | |-| |    | |      
      |_| |_|    |_|  ..  
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** LOADER **
 ** BOARD: DB-88F6281A-BP LE 

U-Boot 1.1.4 (Jan  8 2010 - 14:03:56) MIC version : 3.4.19-16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CD4E0

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM CS[1] base 0x10000000   size 256MB 
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
[1024kB@f8000000] Flash:  1 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

Edited 3 time(s). Last edit at 03/05/2016 06:00PM by Gravelrash.

Gravelrash,

> root@orangepi:/scripts# ./kw
> Sending boot message. Please reboot the
> target...\^Z
> [1]+ Stopped ./kw
> root@orangepi:/scripts# ./kw
>
>
I've just noticed this. How come you have a Control-Z above? was that entered by you after waiting a while and saw nothing?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> I've just noticed this. How come you have a
> Control-Z above? was that entered by you after
> waiting a while and saw nothing?

Yes.

left it each time for a minute or so after power on.



Edited 1 time(s). Last edit at 03/05/2016 07:39PM by Gravelrash.

> definitely the hardware (Prolific clone). The
> result is consistent with the x64 system when
> using it on an orangepi

Could be the hardware. I always have 2 serial converters, one Sililconlabs CP2xxx and one Prolific PL3xxx. When in doubt, I would swap the converter to make sure I'm not screwed by a $3 board :) And I really like the Nokia cable (Prolific) with the plastic sleeve, it is most likely to be the authentic one, so I save it as the portable serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

xxx@vmdebian8:~/Downloads
$ sudo kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-2-rc1.t5325.mtd0.kwb -p
Sending boot message. Please reboot the target.../
Sending boot image...
  0 % [......................................................................]
...
 98 % [..............................................................]
[Type Ctrl-\ + c to quit]


U-Boot 2015.10-tld-2-rc1 (Mar 04 2016 - 19:10:16 -0800)nHP Thin Client T5325


SoC:   Kirkwood 88F6281_A1
SPI:   ready
DRAM:  512 MiB (ECC not enabled)
WARNING: Caches not enabled
SF: Detected M25P80 with page size 256 Bytes, erase size 64 KiB, total 1 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0 
T5325> dhcp
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 42
DHCP client bound to address 192.168.178.84 (1014 ms)
*** Warning: no boot file name; using 'C0A8B254.img'
Using egiga0 device
TFTP from server 192.168.178.1; our IP address is 192.168.178.84
Filename 'C0A8B254.img'.
Load address: 0x800000
Loading: T T T T T 
Abort
T5325> ping 8.8.8.8     
Using egiga0 device
host 8.8.8.8 is alive
T5325> printenv
arcNumber=2846
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; reset
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
rootdelay=10
rootfstype=ext2
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; ide reset; setenv uenv_loaded 0; for devtype in usb ide; 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 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if $devtype part $disknum; then run uenv_read; fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 1326/65532 bytes
T5325>

(I did "dhcp", was to layz to setenv ip, mask, gateway)

T5325> setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x80000@0(uboot),0x80000@0x80000(root)'
T5325> saveenv
Saving Environment to SPI Flash...
SF: Detected M25P80 with page size 256 Bytes, erase size 64 KiB, total 1 MiB
Erasing SPI flash...Writing to SPI flash...done                                
T5325> 
T5325> printenv bootargs_usb
bootargs_usb=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi_flash:0x80000@0(uboot),0x80000@0x80000(root)
T5325>

And you are right "boot" did not find a USB device, it booted the stock ThinPro linux.



Edited 1 time(s). Last edit at 03/06/2016 11:07AM by CV.

@CV,

> Saving Environment to SPI Flash...
> SF: Detected M25P80 with page size 256 Bytes,
> erase size 64 KiB, total 1 MiB
> Erasing SPI flash...Writing to SPI flash...done
>

You are an adventurous person :) this could potentially mess up your u-boot envs. Since you have serial console and can kwboot, it's can be fixed if need be. Try booting back to stock u-boot and see if the envs are still readable.

The good test : Now I know that this build can handle all both flash types that the T5325 has.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/06/2016 02:50PM by bodhi.

All,

I am still a little bit unsure about the SATA/USB issue. The stock u-boot GPL is a mess to read.

But it should be clear up soon that later today I will pick up my T5325 :) and that will help me solve the last puzzle about USB/SATA.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Another test with stock u-boot and new Debian.

- boot the box into Debian.
- Watch the serial console. And shutdown:

shutdown -h now

or

poweroff

Did it shutdown cleanly?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I have been getting clean with reboot

Not clear otherwise

The DTS GPIO Power off looks suspect. That's why I wonder if it would cause problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Here is a rc2 test version. Please try with kwboot.

./kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-2-rc2.t5325.mtd0.kwb   -p

Interrupt serial console after u-boot was loaded. And

Check out USB and SATA

usb start
ide reset

Setup for booting Debian USB rootfs

setenv usb_root 'LABEL=rootfs'
setenv rootfstype ext3

And

boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-2-rc2.t5325.mtd0.kwb -p

Sending boot message. Please reboot the target.../
Sending boot image...
  0 % [......................................................................]
  2 % [......................................................................]
....]
 95 % [......................................................................]
 98 % [................................................................]
[Type Ctrl-\ + c to quit]


U-Boot 2015.10-tld-2-rc2 (Mar 06 2016 - 21:43:00 -0800)
HP Thin Client T5325

SoC:   Kirkwood 88F6281_A1
SPI:   ready
DRAM:  512 MiB (ECC not enabled)
WARNING: Caches not enabled
SF: Detected M25P80 with page size 256 Bytes, erase size 64 KiB, total 1 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0 
T5325> setenv usb_root 'LABEL=rootfs'
T5325> setenv rootfstype ext3
T5325> boot
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: SM22 Firm: I052 Ser#: (03)xxxxxxxx-xxxxxxxx
            Type: Hard Disk
            Capacity: 463.6 MB = 0.4 GB (949536 x 512)

Partition Map for USB device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	30527488  	xxxxxxxx-xx	83 Boot
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **

Partition Map for IDE device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	63        	949473    	00000000-01	83 Boot
loading envs from ide 0 ...
** File not found /boot/uEnv.txt **
3166549 bytes read in 373 ms (8.1 MiB/s)
7179935 bytes read in 478 ms (14.3 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-03-04   5:19:38 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3166485 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: HP t5325 Thin Client

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/07/2016 05:05AM by bodhi.

bodhi Wrote:
-------------------------------------------------------
>

> [    0.000000] Machine model: HP t5325 Thin
> Client
>

Nice to see yours turned up so quickly!,
I have ordered a Nokia cable and when it lands i will be able to assist with the kwboot testing once i have soldered the header accordingly

It's a box from an East Coast USA eBay seller. It has the header installed (looks like manufactered). I believe has been modded or the OS damaged because I could not boot into the stock OS. I connected 3 wires, just barely enough for serial console :). The microJST headers will also arrive soon in a few days (eBay seller but shipping is from SanFrancisco US, only cost a buck more than shipping from China).

The USB/SATA power problem was similar to the Zyxel 320S 2nd HDD. The power GPIO definition from the DTS we have did not match up, but when I can control the serial console, it was not too difficult to find out that's the GPIO 47.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/07/2016 01:44PM by bodhi.

I have this recovery disk extracted: HPTC Imgr.tar.gz

./boot:
.  ..  uImage.dove.usb  uImage.usb  uInitrd.dove.usb  uInitrd.usb

./images:
.  ..  ThinPro-T5A32014-2016-01-28.dd.gz

./uboot:
.  ..  u-boot-3.4.19_V16.bin


.:
.  ..  boot  images  init.sh  settings.ini  uboot  

./boot:
.  ..  uImage.dove.usb  uImage.usb  uInitrd.dove.usb  uInitrd.usb

./images:
.  ..  ThinPro-T5A32014-2016-01-28.dd.gz

./uboot:
.  ..  u-boot-3.4.19_V16.bin

But could not find the instruction to create the USB recover disk. Anybody has it?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi

to create the recovery usb - you first logon to the thinclient

swap to the administrative user from the standard user

then from control panel create it there.

i have the link for the manual somewhere gimme a few minutes

This link is very useful - pages 29 - 31
http://h20566.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c01940143



Edited 1 time(s). Last edit at 03/07/2016 04:56PM by Gravelrash.

@bodhi

format the usb key to fat32, ideally a partitiion less than 2GB

label it as "HPTC Imgr" minus the quotes

and extract the gzip you have to the usb key as per attached screenshot



Edited 1 time(s). Last edit at 03/07/2016 04:53PM by Gravelrash.

if you are still struggling send me a P.M.....

bodhi Wrote:
-------------------------------------------------------
> It's a box from an East Coast USA eBay seller. It
> has the header installed (looks like
> manufactered). I believe has been modded or the OS
> damaged because I could not boot into the stock
> OS. I connected 3 wires, just barely enough for
> serial console :). The microJST headers will also
> arrive soon in a few days (eBay seller but
> shipping is from SanFrancisco US, only cost a buck
> more than shipping from China).
>
> The USB/SATA power problem was similar to
> the
> Zyxel 320S 2nd HDD. The power GPIO
> definition from the DTS we have did not match up,
> but when I can control the serial console, it was
> not too difficult to find out that's the GPIO 47.

the board comes with headers already in place, im taling about the modification to the nokia cable..

Thanks Gravelrash, I will try the recovery when I got home today. I want to make sure that the stock OS can be used as a rescue system. Otherwise we will need to use part or whole of that 512MB and install a new one.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

To set the mtdparts and envs location so that Debian recognizes the correct layout.

In Debian rootfs

cat /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

And then adjust the u-boot envs for it.

1. If booting with stock u-boot

In serial console

setenv bootargs_usb '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)'

2. If kwbooting with new u-boot uboot.2015.10-tld-2-rc2.t5325.mtd0.kwb

In serial console

setenv usb_root 'LABEL=rootfs'
setenv rootfstype ext3
setenv mtdparts 'mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)'

-----------

Verify:

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"

EDIT:

corrected typo in fw_env.config

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 03/09/2016 08:47PM by bodhi.

I finally got the cables. I see the party isn't over yet, can I come in?

It seems these boxes try to use WoL and/or some kind of auto-resume from powerloss and they do so in a way that prevents kwboot. Shutting them down by pulling the power cord have them autoboot or switch into that mode afterwards.

If I power this box down with the power button I get this on TTL:

(note that this happens AFTER it has booted already, so it does not really shut down, it reboots, set new envs and then goes into some kind of Ninja Stealth Mode waiting for eth, no lights are on when this happens, it looks powered down)

_   _     .____    
      | |_| |    |  _ \  
      |  _  |    | (_))   
      | |-| |    | |      
      |_| |_|    |_|  ..  
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** LOADER **
 ** BOARD: DB-88F6281A-BP LE 

U-Boot 1.1.4 (Jan  8 2010 - 14:03:56) MIC version : 3.4.19-16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CD4E0

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM CS[1] base 0x10000000   size 256MB 
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
[1024kB@f8000000] Flash:  1 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  1 \0x08\0x08\0x08 0 

Reset IDE: 
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: SM22 Firm: I052 Ser#: (03)5526888-20080228
            Type: Hard Disk
            Capacity: 463.6 MB = 0.4 GB (949536 x 512)


1888432 bytes read
Checking Button Status: off
Checking GotoWOL Status: on, setting to off
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
Entering WOL mode
--------------
Scaling down CPU freq
PEX is Powered Off - 2
USB is Powered Off - 3
SDIO is Powered Off (clock only) - 4
TSU is Powered Off (clock only) - 5
XOR0 is Powered Off (clock only) - 8
Audio is Powered Off (clock only) - 9
SATA0 is Powered Off - 14
SATA1 is Powered Off - 15
XOR1 is Powered Off (clock only) - 16
CESA is Powered Off (clock only) - 17
Giga1 is Powered Off (clock only) - 19
TDM is Powered Off (clock only) - 20
Setting PHY interrupt mode
Setting GPIOs as input
Setting GPIOs mask
Setting main high interrupt mask

Checking link...
No link, waiting for cable insertion.

That's obviously a WoL thing. It's pretty cool tho, they power down all devices and go in stealth mode.
This is going to be informative if you have u-boot sources, as that mode seems to do quite a few low-level things.

Then I press power button again, and I get this:

Button Pressed, WOL canceled! 
Restarting device...

And then it reboots, showing normal uboot output.


If I ask them nicely to shut down from the GUI they fully power down and let me kwboot them afterwards.


Also, it seems like my units have not been reset, so in their firmware I cannot go in admin mode as I don't know the password. I can see the names/settings of the accounts of employees using them. :)

It's not crucial as I'm not going to use their stock firmware anyway, but If anyone can provide a image I can flash on my box or some instructions to reset them...

Btw, my boxes show this flash if kwbooted with your u-boot:

SF: Detected SST25VF080B with page size 256 Bytes, erase size 64 KiB, total 1 MiB



Edited 1 time(s). Last edit at 03/08/2016 06:43AM by bobafetthotmail.

bobafetthotmail Wrote:
-------------------------------------------------------
> I finally got the cables. I see the party isn't
> over yet, can I come in?

:-) The more the merrier to this party!!

> 1888432 bytes read
> Checking Button Status: off
> Checking GotoWOL Status: on, setting to off
> [/code]

That matches with what mine does

> If I ask them nicely to shut down from the GUI
> they fully power down and let me kwboot them
> afterwards.

Ill try that and see if mine behaves the same way - thats the only thing i didnt do, when checking my units out and i had real problems with getting kwboot to work on my box - i believe i may have a "faulty" console connector, so im going to try this out!!

bobafetthotmail,

> I finally got the cables. I see the party isn't
> over yet, can I come in?

:) welcome to the party. It's not late, as there are many things we have not figured out yet.

>
> It seems these boxes try to use WoL and/or some
> kind of auto-resume from powerloss and they do so
> in a way that prevents kwboot. Shutting them down
> by pulling the power cord have them autoboot or
> switch into that mode afterwards.
>
> If I power this box down with the power button I
> get this on TTL:
>
> (note that this happens AFTER it has booted
> already, so it does not really shut down, it
> reboots, set new envs and then goes into some kind
> of Ninja Stealth Mode waiting for eth, no lights
> are on when this happens, it looks powered down)

Nice!

> Un-Protected 1 sectors
> Erasing Flash...
> .
> Erased 1 sectors
> Writing to Flash... done

This is not so nice. They keep writing to this sector.

> It's not crucial as I'm not going to use their
> stock firmware anyway, but If anyone can provide a
> image I can flash on my box or some instructions
> to reset them...
>

Try booting with Debian rootfs on USB, the setup was figured out above.


> Btw, my boxes show this flash if kwbooted with
> your u-boot:
>
> SF: Detected SST25VF080B with page size 256 Bytes,
> erase size 64 KiB, total 1 MiB

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@All,

There are a few things need to be fixed in the mainline kernel 4.4 DTS. I've fixed most and will post a new DTB later today.

- Power off (try to do shutdown and watch serial console)
- No LED control (also is there other LED besides the power button?).
- Also WOL does not work yet. I'm not sure if DTS is a culprit.

Other non-DTS-related issue: I can't chainload back to stock u-boot. This might be a potential problem for users who want to keep stock OS and run with new u-boot.

As far as new u-boot, I think it is OK. I will upload a new version that is good enough be flashed. There are still a few things to be worked on such as LED control (flashing sequence), and button command, and some bugs fixed.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 3 time(s). Last edit at 03/09/2016 05:22AM by bodhi.

looking forward to flasing the new uboot

i have removed as much WOL references as i can find anyways. if you can post a minimal set of boot arguments for your new uboot as well that would be "AWESOME!!" I will remove all the stock ones and add only yours


got the following interesting output when loading kwboot, from my ssh monitoring console

. ok 
[ ok ] Starting system message bus: dbus.
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1224 (klogd)
. ok 

Debian GNU/Linux 8 hpt5325 ttyS0

hpt5325 login: �"fw�3UfwDUw3DUfwf�DUUwfwDU�"3DUfw�"3Uw�3Uw�"DUfw�3DUfw�"3DUfw�"DUfw�DUfw�"DUfw�3DUfw�"3DUfw�"3DUfw�"3DUfw�"DUfw�3DUfw�"3DUfw"3DUfw�"3DUfw�"DUfw�DUfw�"3DUfw"3DUfw�"3DUfw�"3DUfw�"3DUfw�"3U�"w�Uf�3DUfw�"3DUf�"3DUfw�"DUfw"3DUfw�"3DUfw�"3DUfw�"3DUfw�3DUfw�"DUfw�"DUfw�3DUfw�"3DUfw"3DUfw�"3Ufw�"DUfw�DUfw�"3DUfw�3DUfw�"3DUfw�"3Ufw�"DUf�"3DUfw�3DUfw�3DUfw�"3Dfw�3DUfw�"3DUw"3DUfw�3DUfw�"3DUfw�3DUf�"3DUfw�"3DUfw�"3Ufw�"3Ufw�"DUfw�"3DUfw"3DUfw�"DUfw�"DUfw�"3DUfw�"3DUfw"3DUfw�"3DUfw�"3DUfw�"3DUfw"Df�"3DUfw�3DUfw�3DUfw�3DUfw�"3DUf�"3DUfw3DUfw�DUfw�DUfw�"3DUf�"3DUfw�3DUfw�"3Dfw�3DUfw"3DUfw�"3DUfw�"3DUfw�DUfw�DUfw�"3DUfw�"DUfw�"3DUfw�"3DUfw�3DUf"3DUfw"3DUfw�"DUfw�3DUfw�3DUfw"3DUfw"3DUfw�"3Ufw�"3DUfw�DUf�"3DUfw�"3DUfw�3DUfw�"3Ufw�DUf�"3DUfw�"3DUfw""Dw�"3DUfw�"3DUf"3Df�"3DUfw�"DUfw�"DUfw�"3DUw�"3DUfw"3DUfw�"DUfw�DUfw�"3Ufw�"DUf�"3DUfw"3DUfw�"3DUfw�"DUfw�3DUfw�"3DUfw"3DUfw�"DUfw�"3Ufw�"DUfw�"3DUf"3DUfw�"DUfw�DUfw�3DUfw�"3DUfw"3DUfw�"3DUfw�"3Ufw�DUfw�"3DUf�"3DUfw�3DUfw�"3Ufw�3DUf"3DUfw�"DUfw�3DUfw�"DUfw�3DUfw"3DUfw�"3DUfw�"3fw�"3DUfw�3DUf"3DUfw�"3DUfw�"3DUfw�"DUfw�"3DUfw�"3DUfw"3DUfw�"3DUfw�"DUfw�3DUf�"3DUfw"3DUfw�"3Ufw�3DUfw�DUfw�"3DUfw�"3DUf

respwnintisefo5iues
NT:  o pcsseslftinthilvel

Edited 3 time(s). Last edit at 03/08/2016 02:21PM by Gravelrash.

bodhi Wrote:

> Other non-DTS-related issue: I can't chainload
> back to stock u-boot. This might be a potential
> problem for users who want to keep stock OS and
> run with new u-boot.

I dont see this as being a problem for the following reasons

most other hacks out there replace the onboard OS
When you use mainline debian following there installation, the changes to stock uboot remove the ability to boot back to the stock OS anyway!
The only thing that is usable from a recovery perspective is ssh if you have enabled it.

speaking for myself i intend to replace the stock os with your rootfs to allow a more flexible recovery system.

>This is not so nice. They keep writing to this sector.

planned obsolescence. How unexpected from HP.

>got the following interesting output when loading kwboot, from my ssh monitoring console

you mean that is over the network? It looks like garbled serial/TTL to me.

bobafetthotmail Wrote:
-------------------------------------------------------
> you mean that is over the network? It looks like
> garbled serial/TTL to me.

corrrect. thats what i saw on the ssh'd console. when i initiated the kwboot command from the ttl connection, interesting output i wasnt expecting - kinda proves that my issues are with the adaptor i am using