Debian on HP T5325 Thin Client

Gravelrash Wrote:
-------------------------------------------------------
> 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.

That's my plan too! The 512MB NAND is prrety nice, fits just right for this Debian rootfs:)

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

Gravelrash Wrote:
-------------------------------------------------------
> 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

I think those noise must have messed up the xmodem prot handshake somehow.

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

Here is the new DTB. Copy this file to your Debian rootfs /boot/dts. And use it to repack your uImage (booting with stock u-boot).

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

Hi,
alas family and work interfered... I had no time.

@Bodhi:
>> Here is the new DTB. Copy this file to your Debian rootfs /boot/dts.
Done.

>> And use it to repack your uImage (booting with stock u-boot).
Sorry, I do not understand, I found some references to mkimage but what should I do..?

Concerning env and mtd, I adjusted /etc/fw_env.config and set bootargs_usb:

root@debian:~
# fw_printenv bootargs_usb
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)
root@debian:~
# 
root@debian:~
# uname -a
Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel GNU/Linux
# cat /proc/mtd
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"
root@debian:~

You said uboot RC2 should be good for flashing already? I would not mind to do it and test, can you give directions of how to do it?

CV,

> >> And use it to repack your uImage (booting with
> stock u-boot).
> Sorry, I do not understand, I found some
> references to mkimage but what should I do..?

You've done it once previously above! embed the DTB into uImage:
http://forum.doozan.com/read.php?2,25473,26166#msg-26166

> You said uboot RC2 should be good for flashing
> already? I would not mind to do it and test, can
> you give directions of how to do it?

rc2 is not ready to be flashed. I'll build a final version (tld-2), test the flashing on my box, and will upload it here with instruction.

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

Bodhi,
thanks:
>>You've done it once previously above! embed the DTB into uImage:
I feel ashamed, yes sure.

I just did it and rebooted, works.

Ok I tried while watching serial console

1) Linux #reboot: fine, kernel shutdown, uboot, kernel coming up again, works

2) Linux #halt: fine, kernel shutdown, device seems to power off (no blue led), I press power button, it starts fine

3) press power button while linux (4.4) running, no reaction

4) press and hold power button for approx. 5 secs while linux (4.4) running, device turns off, I press start button, it starts up again fine

5) unplug PSU while linux (4.4) running, replug PSU, device restarts automatically! Linux boots up fine

I did never see anything funny with stock uboot (like writes to NAND, or going into recovery mode or anything, just straight boots).

My env:

HP>> printenv
[U-boot variables]
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
run_diag=no
in_mfg=no
console=console=ttyS0,115200 mtdparts=spi_flash:0x80000@0(uboot)ro,0x80000@0x800                                                        00(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
usb_bootargs=root=/dev/ram rw
bootusb=usb start;fatload usb 0 0x800000 /boot/uImage.usb;fatload usb 0 0x110000                                                        0 /boot/uInitrd.usb
usbboot=setenv bootargs $(usb_bootargs); run bootusb; bootm 0x800000 0x1100000
pcieTune=yes
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/m                                                        tdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x20                                                        00000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=f4:ce:46:24:94:de
load_usb=usb start; ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1  0x                                                        1100000 /boot/uInitrd
bootcmd_usb=setenv bootargs $(bootargs_usb); run load_usb; bootm 0x800000 0x1100                                                        000
ethact=egiga0
bootdelay=0
bootcmd=run bootcmd_usb
thinpro_bootargs=root=/dev/sda1 rw init=/init video=xgifb splash quiet
thinpro=ide reset; ext2load ide 0:1 0x200000 /boot/uImage; wol; setenv bootargs                                                         $(thinpro_bootargs); bootm 0x200000
mfgmode=setenv bootdelay 3; setenv in_mfg yes;setenvh GotoWOL Yes; setenvh WOLEn                                                        abled No; setenv bootcmd run mfgboot; saveenv; reset
mfgbootargs=setenv bootargs root=/dev/sdb1 rw init=/init ip=dhcp rootdelay=8 $(c                                                        onsole) udevtimeout=8
mfgboot=usb start; ext2load usb 0:1 0x2000000 /boot/uImage; run mfgbootargs; boo                                                        tm 0x2000000
product=setenv bootdelay 1; setenv in_mfg no;setenvh GotoWOL No; setenvh WOLEnab                                                        led Yes; setenv bootcmd run thinpro; saveenv; reset
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_e                                                        nv)
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes

Environment size: 2309/4092 bytes

[PUE variables]
manufacturer=Hewlett-Packard
product_name=hp t5325
vendor=mitac
mac=f4:ce:46:24:94:de
uuid=30e4158e-bb5b-11d4-a168-f4ce462494de
serial=CN3109302R

Environment size: 146/4092 bytes

[HPE variables]
UbootVersion=0x03041916
UbootReleaseDate=01082010
AssetNumber=0
AssetLocation=0
WOLEnabled=Yes
InitialNumlock=On
ClockSpeed=1200
GotoWOL=No

Environment size: 140/4092 bytes
HP>>

Edit: don't know if its relevant: I fdisk'ed the internal SSD, I got annoyed with accidental boot to then ThinPro Linux.



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

I just tried, fw_setenv does not work for me:

I try to set a new variable, it is not there when I fw_printenv it.

# fw_setenv cvtest 'Bodhi rocks'
root@debian:~
# fw_printenv cvtest
## Error: "cvtest" not defined
root@debian:~
#
root@debian:~
#

My env:

root@debian:~
# cat /etc/fw_env.config
# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
#
# Dockstar:
# /dev/mtd0 0xc0000 0x20000 0x20000

# Bodhi: HP T5325 Thin Client
/dev/mtd2 0x00000 0x1000 0x10000

root@debian:~
# 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"
root@debian:~
#

Anything wrong there?

looks like someone sanitised your uboot envs before you got it.

CV Wrote:
-------------------------------------------------------
> Bodhi,
> thanks:
> >>You've done it once previously above! embed the
> DTB into uImage:
> I feel ashamed, yes sure.
>
> I just did it and rebooted, works.
>
> Ok I tried while watching serial console
>
> 1) Linux #reboot: fine, kernel shutdown, uboot,
> kernel coming up again, works
>
> 2) Linux #halt: fine, kernel shutdown, device
> seems to power off (no blue led), I press power
> button, it starts fine
>
> 3) press power button while linux (4.4) running,
> no reaction
>
> 4) press and hold power button for approx. 5 secs
> while linux (4.4) running, device turns off, I
> press start button, it starts up again fine
>
> 5) unplug PSU while linux (4.4) running, replug
> PSU, device restarts automatically! Linux boots up
> fine
>
> I did never see anything funny with stock uboot
> (like writes to NAND, or going into recovery mode
> or anything, just straight boots).
>
> My env:
>

> HP>> printenv
> [U-boot variables]
> baudrate=115200
> loads_echo=0
> ipaddr=10.4.50.165
> serverip=10.4.50.5
> rootpath=/mnt/ARM_FS/
> netmask=255.255.255.0
> run_diag=no
> in_mfg=no
> console=console=ttyS0,115200
> mtdparts=spi_flash:0x80000@0(uboot)ro,0x80000@0x80
> 0                                                 
>       00(root)
> CASset=min
> MALLOC_len=1
> ethprime=egiga0
> bootargs_root=root=/dev/nfs rw
> bootargs_end=:::DB88FXX81:eth0:none
> image_name=uImage
> usb_bootargs=root=/dev/ram rw
> bootusb=usb start;fatload usb 0 0x800000
> /boot/uImage.usb;fatload usb 0 0x110000           
>                                             0
> /boot/uInitrd.usb
> usbboot=setenv bootargs $(usb_bootargs); run
> bootusb; bootm 0x800000 0x1100000
> pcieTune=yes
> standalone=fsload 0x2000000 $(image_name);setenv
> bootargs $(console) root=/dev/m                   
>                                     tdblock0 rw
> ip=$(ipaddr):$(serverip)$(bootargs_end)
> $(mvPhoneConfig); bootm 0x20                      
>                                  00000;
> ethmtu=1500
> mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
> mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2
> :3),mtu=1500
> usb0Mode=host
> yuk_ethaddr=00:00:00:EE:51:81
> netretry=no
> rcvrip=169.254.100.100
> loadaddr=0x02000000
> autoload=no
> ethaddr=f4:ce:46:24:94:de
> load_usb=usb start; ext2load usb 0:1 0x800000
> /boot/uImage; ext2load usb 0:1  0x                
>                                        1100000
> /boot/uInitrd
> bootcmd_usb=setenv bootargs $(bootargs_usb); run
> load_usb; bootm 0x800000 0x1100                   
>                                     000
> ethact=egiga0
> bootdelay=0
> bootcmd=run bootcmd_usb
> thinpro_bootargs=root=/dev/sda1 rw init=/init
> video=xgifb splash quiet
> thinpro=ide reset; ext2load ide 0:1 0x200000
> /boot/uImage; wol; setenv bootargs                
>                                        
> $(thinpro_bootargs); bootm 0x200000
> mfgmode=setenv bootdelay 3; setenv in_mfg
> yes;setenvh GotoWOL Yes; setenvh WOLEn            
>                                            abled
> No; setenv bootcmd run mfgboot; saveenv; reset
> mfgbootargs=setenv bootargs root=/dev/sdb1 rw
> init=/init ip=dhcp rootdelay=8 $(c                
>                                        onsole)
> udevtimeout=8
> mfgboot=usb start; ext2load usb 0:1 0x2000000
> /boot/uImage; run mfgbootargs; boo                
>                                        tm
> 0x2000000
> product=setenv bootdelay 1; setenv in_mfg
> no;setenvh GotoWOL No; setenvh WOLEnab            
>                                            led
> Yes; setenv bootcmd run thinpro; saveenv; reset
> 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_e                    
>                                    nv)
> stdin=serial
> stdout=serial
> stderr=serial
> mainlineLinux=no
> enaMonExt=no
> enaCpuStream=no
> enaWrAllo=no
> pexMode=RC
> disL2Cache=no
> setL2CacheWT=yes
> disL2Prefetch=yes
> enaICPref=yes
> enaDCPref=yes
> sata_dma_mode=yes
> netbsd_en=no
> vxworks_en=no
> disaMvPnp=no
> enaAutoRecovery=yes
> 
> Environment size: 2309/4092 bytes
> 
> [PUE variables]
> manufacturer=Hewlett-Packard
> product_name=hp t5325
> vendor=mitac
> mac=f4:ce:46:24:94:de
> uuid=30e4158e-bb5b-11d4-a168-f4ce462494de
> serial=CN3109302R
> 
> Environment size: 146/4092 bytes
> 
> [HPE variables]
> UbootVersion=0x03041916
> UbootReleaseDate=01082010
> AssetNumber=0
> AssetLocation=0
> WOLEnabled=Yes
> InitialNumlock=On
> ClockSpeed=1200
> GotoWOL=No
> 
> Environment size: 140/4092 bytes
> HP>>
>

>
> Edit: don't know if its relevant: I fdisk'ed the
> internal SSD, I got annoyed with accidental boot
> to then ThinPro Linux.

>> looks like someone sanitised your uboot envs before you got it.

No, it was me, but I did not or only partially succeed, this "mfg" stuff and some more somehow reappeared:

# fw_printenv | grep mfg
in_mfg=no
mfgmode=setenv bootdelay 3; setenv in_mfg yes;setenvh GotoWOL Yes; setenvh WOLEnabled No; setenv bootcmd run mfgboot; saveenv; reset
mfgbootargs=setenv bootargs root=/dev/sdb1 rw init=/init ip=dhcp rootdelay=8 $(console) udevtimeout=8
mfgboot=usb start; ext2load usb 0:1 0x2000000 /boot/uImage; run mfgbootargs; bootm 0x2000000
product=setenv bootdelay 1; setenv in_mfg no;setenvh GotoWOL No; setenvh WOLEnabled Yes; setenv bootcmd run thinpro; saveenv; reset
root@debian:~

That's why I wiped the thinpro linux - maybe it does something to the NAND (I booted to thinpro linux accidentally a few times,
USB stick was not inserted).

I'll try to get rid of these env variables it once more with stock uboot - alas I can't do it from Linux as fw_setenv does not work for me...

Does it for you?

CV Wrote:
-------------------------------------------------------

> I'll try to get rid of these env variables it once
> more with stock uboot - alas I can't do it from
> Linux as fw_setenv does not work for me...
> 
> Does it for you?

No,

i have put it down to either some issue with my box as i cant be certain that the partitions are as they were intended, being a second hand unit or to this still being in the "development stage"

CV,

> I'll try to get rid of these env variables it once
> more with stock uboot - alas I can't do it from
> Linux as fw_setenv does not work for me...
>

Don't change envs in Linux, I think I've mentioned it previously. You don't need it now, you can change them in stock u-boot. Which is the correct place to do it, since you are still on stock.

Once I uploaded the final version, you can flash it along with a default envs image. And then change them in Linux.

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

CV,

> 1) Linux #reboot: fine, kernel shutdown, uboot,
> kernel coming up again, works
>
> 2) Linux #halt: fine, kernel shutdown, device
> seems to power off (no blue led), I press power
> button, it starts fine
>
> 3) press power button while linux (4.4) running,
> no reaction
>

So far so good.

> 4) press and hold power button for approx. 5 secs
> while linux (4.4) running, device turns off, I
> press start button, it starts up again fine

Very good test!

This is something I don't like, since you are running Debian 4.4 and we should have full control of the button. Oviously we don't, since it's not set up to activate the button like that yet.

This button seems to be hardwired :) I've never done this test on the other Kirkood boxes, I don't believe it works this way on those.

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

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

> This button seems to be hardwired :) I've never
> done this test on the other Kirkood boxes, I don't
> believe it works this way on those.

I cant speak for other kirkwood boxes, but i think in this instance it acts to trip the cpu, reminds me of the tricks we used to do with 286/386 processors. restart the cpu and not the entire PC.

My OrangePi offers a similar but not identical behaviour pattern

Gravelrash Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
>
> > This button seems to be hardwired :) I've never
> > done this test on the other Kirkood boxes, I
> don't
> > believe it works this way on those.
>
> I cant speak for other kirkwood boxes, but i think
> in this instance it acts to trip the cpu, reminds
> me of the tricks we used to do with 286/386
> processors. restart the cpu and not the entire PC.
>
>
> My OrangePi offers a similar but not identical
> behaviour pattern

I think you are right. Like in other PCs if you hold down the power button long enough it will trigger an emergency shudown. I should test this on my NSA310S.

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

Here is my tentative final version. I'm running with this image flashed to SPI mtd0.

So please try kwboot with it while I'm writing instruction after a final check out on my box.

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



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

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

Sorry there was a typo in this :) that's why CV saw the fw_printenv problem. Both numbers should be hex ten thousand.

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

Hi Bodhi,

>> Sorry there was a typo in this :) that's why CV saw the fw_printenv problem. Both numbers should be hex ten thousand.

Hm - I corrected it like you said but then I get

# fw_printenv
Warning: Bad CRC, using default environment

That might be because I did saveenv from Linux once and it messed something up?

EDIT: yep, once I kwbooted new uboot "uboot.2015.10-tld-2.t5325.mtd0.kwb", did a saveenv there,
added the missing 0 in fw_env.config, fw_printenv now works:

# uname -a
Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel GNU/Linux
root@debian:~
# fw_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
mtdparts=mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)
rootdelay=10
rootfstype=ext3
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay $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=LABEL=rootfs
root@debian:~
#

I know "You are an adventurous person :) this could potentially mess up your u-boot envs.",
but as kwboot works totally reliably for me and as it worked berore, I chanced it.. ;-)



Edited 1 time(s). Last edit at 03/10/2016 01:24AM by CV.

Aha - upon reboot (without kwboot) now I see this infamous stock uboot write to nand:

       _   _     .____    
      | |_| |    |  _ \  
      |  _  |    | (_))   
      | |-| |    | |      
      |_| |_|    |_|  ..  
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** 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
*** Warning - bad CRC, using default environment

[1024kB@f8000000] Flash:  1 MB

CPU : Marvell Feroceon (Rev 1)
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors

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 

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)


** Unable to read "/boot/uImage" from ide 0:1 **
Checking Button Status: off
Checking GotoWOL Status: off
## Booting image at 00200000 ...
Bad Magic Number
HP>> printenv
[U-boot variables]
bootdelay=0
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
run_diag=no
in_mfg=no
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=spi_flash:0x80000@0(uboot)ro,0x80000@0x80000(root)
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
usb_bootargs=root=/dev/ram rw
bootusb=usb start;fatload usb 0 0x800000 /boot/uImage.usb;fatload usb 0 0x1100000 /boot/uInitrd.usb
usbboot=setenv bootargs $(usb_bootargs); run bootusb; bootm 0x800000 0x1100000
thinpro_bootargs=root=/dev/sda1 rw init=/init video=xgifb splash quiet
thinpro=ide reset; ext2load ide 0:1 0x200000 /boot/uImage; wol; setenv bootargs $(thinpro_bootargs); bootm 0x200000
pcieTune=yes
bootcmd=run thinpro
mfgmode=setenv bootdelay 3; setenv in_mfg yes;setenvh GotoWOL Yes; setenvh WOLEnabled No; setenv bootcmd run mfgboot; saveenv; reset
mfgbootargs=setenv bootargs root=/dev/sdb1 rw init=/init ip=dhcp rootdelay=8 $(console) udevtimeout=8
mfgboot=usb start; ext2load usb 0:1 0x2000000 /boot/uImage; run mfgbootargs; bootm 0x2000000
product=setenv bootdelay 1; setenv in_mfg no;setenvh GotoWOL No; setenvh WOLEnabled Yes; setenv bootcmd run thinpro; saveenv; reset
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
disaMvPnp=no
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
ethaddr=f4:ce:46:24:94:de
ethact=egiga0
bootargs=root=/dev/sda1 rw init=/init video=xgifb splash quiet

Environment size: 2018/4092 bytes

[PUE variables]
manufacturer=Hewlett-Packard
product_name=hp t5325
vendor=mitac
mac=f4:ce:46:24:94:de
uuid=30e4158e-bb5b-11d4-a168-f4ce462494de
serial=CN3109302R

Environment size: 146/4092 bytes

[HPE variables]
UbootVersion=0x03041916
UbootReleaseDate=01082010
AssetNumber=0
AssetLocation=0
WOLEnabled=Yes
InitialNumlock=On
ClockSpeed=1200
GotoWOL=No

Environment size: 140/4092 bytes
HP>>

@Bodhi: I guess now I could setup stock uboot env again to usb boot debian 4.4, but I don't really care,
I kwboot your new uboot and boot from that.

(And I hope to flash new uboot it as soon as possible, to get rid of the stock thing! :-) )

CV,

Yes, that was the good thing about UART booting, allow you to live dangerously :)

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

All,

I can see there are 2 LEDs: power button, and another one right next to it (look like a video/audio indicator?).

Can you describe what is the LED behavior booting stock u-boot and stock OS? is any of the LEDs flashing at all during u-boot running? and during OS kernel loading?

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

The LED behaviour on my unit with stock uboot and OS is as follows

Power LED on at all times the system believes it is running, EXCEPT, when a graceful power off is issued from the standard OS. This LED then reinitialises when the Power button is pressed.

The LED you are describing is active whenever there is "disk activity" found when loading the onboard OS and flashes with the same behaviour as a HDD indicator on a typical desktop system.

H.T.H.


EDIT : .... grumble...grumble..... I cant do kwboot.... grumble...grumble... :o)



Edited 1 time(s). Last edit at 03/10/2016 10:51AM by Gravelrash.

as an aside to the abov - did you both manage to get the HP disk working? I have just reflashed another 3 i have laid my hands on with it..

@Gravelrash:
>> .... grumble...grumble..... I cant do kwboot.... grumble...grumble... :o)

As I can, I'll do some extra for you and send you the logs... ;-)

@Bodhi: As I can do kwboot... could I perhaps already wipe the stock uboot from NAND?

And as adventurous a devil I am, could I already dare a flash of your uboot?

I promise, I won't complain if it don't work - it's Germany here, I could'nt sue the pants off of you anyway if it breaks my device....
;-)

CV Wrote:
-------------------------------------------------------

> And as adventurous a devil I am, could I already
> dare a flash of your uboot?

Your level of adventurism makes my level of recklessness seem luddite by comparison. :o) :o)

(which is a compliment by the way, luddites were people who attempted to hold back technological advance)

Me too - I cant wait to issue the commands to obliterate this stock uboot.



Edited 1 time(s). Last edit at 03/10/2016 01:03PM by Gravelrash.

Instruction and binaries will be posted soon in a few hours :)

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

cross link
http://forum.doozan.com/read.php?2,25473,26550,page=6#msg-26550

Just my luck that it will be ready when im about to go to bed and working all weekend....

:headbang

:o)

Gravelrash Wrote:
-------------------------------------------------------
> The LED behaviour on my unit with stock uboot and
> OS is as follows
>
> Power LED on at all times the system
> believes it is running, EXCEPT, when a graceful
> power off is issued from the standard OS. This LED
> then reinitialises when the Power button is
> pressed.
>
> The LED you are describing is active
> whenever there is "disk activity" found when
> loading the onboard OS and flashes with the same
> behaviour as a HDD indicator on a typical desktop
> system.
>
> H.T.H.
>

Thanks. That's interesting. I'm trying to find a way to control these LEDs with GPIO without success. Even with information from the DTS, that said GPIO 21 is the only one LED.

I wonder if at the board level whether these LED pins are hardwired.

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

bodhi Wrote:

> I wonder if at the board level whether these LED
> pins are hardwired.

im going to say yes to that for the following reasoning

1 - this led flashes when i attempt to access or do access the usb drive
2 - the onboard flash is attached to and or controlled by a hdd controller

I've uploaded u-boot and envs images and installation instruction in this thread:
http://forum.doozan.com/read.php?3,26562

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

bodhi Wrote:
-------------------------------------------------------
> I've uploaded u-boot and envs images and
> installation instruction in this thread:
> http://forum.doozan.com/read.php?3,26562

When creating the rootfs for this operation, does one need to embed dtb into uImage or do your new env's provide for separate dtb booting? Regardless of separate or embedded, which dtb file should be used?



Edited 1 time(s). Last edit at 03/10/2016 05:30PM by LeggoMyEggo.