I have done the SATA mod, very ghetto style... SATA cable cut, split and directly soldered to the board. Mechanical stability not great, I will search for a machting SATA connector (footprint B I think). Log: U-Boot 2015.10-tld-2 (Mar 09 2016 - 16:49:35 -0800) HP Thin Client T5325 SoC: Kirkwood 88F6281_A1 SPI: ready DRAM: 512 MiB (ECC not enabled) WARNING: Caches not enabled Sby CV - Debian
Hi Pld / Bodhi, you write >> After loaging cryptodev: I don't find module cryptodev in the new kernel 4.5. Am I overlooking something or does it need to get from somewhere else? Where did you get it from, Pld?by CV - Debian
Just wanted to say hello to everybody! Greetings from me, my t5325 and kernel 4.5 cv@debian:~$ uname -a Linux debian 4.5.0-kirkwood-tld-1 #4 PREEMPT Fri Mar 18 21:36:04 PDT 2016 armv5tel GNU/Linux cv@debian:~$ Sofar everything also works with new the kernel. Module "marvell_cesa" is loaded. Tonight I will check sata booting - soldering the tiny caps was a pita but seems toby CV - Debian
Hi Gravelrash, I do not remember every step I did, but I managed to get a graphical login started automatically upon boot using lightdm. (First I had tried gdm3, but did not get it to work) -I (re-)installed packages systemd, systemd-sysv, lightdm -at one point I had a error message concerning D-Bus not being able to start something, I made "chmod o+x /usr/lib/dbus-1.0/dbus-daemon-lby CV - Displays
: kwbooted new uboot, then linux, then flash worked! @Bodhi: I just tried to flash new uboot to my second box - did'nt work, see below errors: the NAND of my second box seems to readonly..!!! Note: my stock /proc/mtd looked different, like that of Gravelrash, uboot was in mtd3, I think. But I thought this wouldn't matter as "setenv bootargs_usb 'console=ttyS0,1by CV - Debian
I just installed my second box which is still on stock uboot and linux. # dmesg | grep -i xgi [ 0.000000] Kernel command line: root=/dev/sda1 rw init=/init video=xgifb splash quiet [ 0.920000] XGIfb: Options <NULL> [ 0.920000] XGIfb: Relocate IO address: 1000 [00001030] [ 0.920000] XGIfb: Enable PCI device [ 0.920000] XGIfb: SR14=41 DramSzie 1000000 ChannelNum 1 [by CV - Debian
>> so far from x i have learned that we need the staitc linked .so module that comes with the xgi driver package ether from wheezy or self compiled to load x and a halfway decent xorg config, not output to screen as yet. still working on it I am also trying, what I can say so far that it does in effect output a VGA signal, my monitor tells me 640x480 60Hz. And this signal comes actiby CV - Debian
@Bodhi: Thank you! Just flashed new uboot - everything perfect!!!! But... if even HP managed to ASCII art its logo , you could also have been a bit less prosaic... a measly U-Boot 2015.10-tld-2 (Mar 09 2016 - 16:49:35 -0800) HP Thin Client T5325" JUST won't cut it ... : ____ ___ __________ __ ___________.________________ ________ .________by CV - Debian
@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 workby CV - Debian
Aha - upon reboot (without kwboot) now I see this infamous stock uboot write to nand: _ _ .____ | |_| | | _ \ | _ | | (_)) | |-| | | | |_| |_| |_| .. _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \_by CV - Debian
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.by CV - Debian
>> 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 rby CV - Debian
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 secby CV - Debian
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 staby CV - Debian
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:by CV - Debian
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 % [..............................................................] U-Boot 2015.10-tld-2-rc1 (Mar 04 2016 - 19:10:by CV - Debian
@Bodhi: >> Please get output of flinfo in serial console too: HP>> flinfo Bank # 1: Flash Base Address : 0xf8000000 Flash Model : Numonyx-25P80 Manufacturer ID : 0x20 Device Id : 0x2014 Sector Size : 64K Number of sectors : 16 Page Size : 256 Write Protection : All HP>> So I have another type of flash chipby CV - Debian
@Gravelrash: your and my stock uboot version are the same, look at my attached putty.log somewhere higher up. I really do not understand why kwboot does not work for you - I took the kwboot from bodhis github and compiled it myself for 32bit - maybe you should also get the source and compile? Edit: and maybe try on a 32bit linux, a Virtual Box VM will work, I tried, USB attaching the serialby CV - Debian
@Gravelrash: >>to install the test uboot in intend to mangle around with the HP recovery disk and see if it cant be installed that way. Well, For me kwbooting the new uboot looks easier and safer than flashing and reflashing possibly multiple times... and really, kwboot works for me each and every time when i do it as i decribed: i first start kwboot, then cold boot t5325 and it woby CV - Debian
@Gravelrash: for me this works best - totally shutdown the t5325 (unplug PSU!) - start kwboot - plugin PSU, sometimes then it directly starts, sometimes i need to press power on Another thing wich helped me, but probably has nothing to do with kwboot as that interacts earlier with (uboot or a loader before that? ) was to set bootwait to 5. 1 was to short a time for me to get a keypressby CV - Debian
Hi Bobba! I'll test these things, and report. Sofar I can say that it works stable as a fileserver, tftp, smb, nfs, isci target. X and sound not yet tested, will do.by CV - Debian
Good Morning Bodhi! Yesterday I had a quick look at the uboot sources in your Github - I wanted to try to setup a build environment for u-boot. But I need to read up a lot on that, linux crossbuilding etc. Do you maybe have a pointer to a guide on that..? And I also did not find my way around the uboot sources really, I thought that maybe I could find the files and configuration for theby CV - Debian
Bodhi, ok, at what timezone are you (what is your tommorrow)? (I am in Germany, GMT+1)by CV - Debian
YESSSSSS! Bodhi, You are the man Eagle Eyes spotting the error!!! Sheevaplug uboot kwbooted!!!!!!! Oh joy!!!! cveit@cvnbdelli8600:~/Downloads/t5323$ ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -p Sending boot message. Please power/reset the target...- Sending boot image... 0 % [.............................................................by CV - Debian
But taking a step back and looking at the overall situation so far: -the stock HP uboot env can be modified from uboot itself: good -the stock HP uboot can be set to boot from USB: good -you provided a very well working kernel 4.4.0-kirkwood: very good! (so far stable, good network throughput, I will continue to test) -along with a root filesystem that can apt-get updated and all: vby CV - Debian
bodhi Wrote: ------------------------------------------------------- > Ah, that's bad news! However, let's go through the > checklist > > - Is your Linux box ARM? if it is then use the one No, its x86, an old DELL Laptop Pentium M 32bit. That's why I compiled kwboot from C. > 2. Did you check the bootROM version in serial > console > > >by CV - Debian
Ok, trying kwboot now: -I only have a 32bit Linux box ATM, so I got kwboot sources from GitHub "https://github.com/dns42/u-boot" and compiled it on my box "gcc kwboot.c" (renamed a.out to kwboot) -got uboot.2015.10-tld-1.sheevaplug.mtd0.kwb from suggested link "uboot.2015.10-tld-1.sheevaplug.bodhi.tar, md5 0e3ac5428ee25dd812a77cc9cb541758" -turned off T5325by CV - Debian
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/mtd0 0xc0000 0x1000 0x10000 root@debian:~# fw_printenv baudrate=115200 loads_echo=0 rootpath=/mnt/ARM_FS/ run_diag=no console=console=ttyS0,115200 mtdparts=spi_flash:0x80000by CV - Debian
root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00010000 "spi0.0" root@debian:~# ls -l /dev/mtd* crw------- 1 root root 90, 0 Feb 26 14:23 [0m[01;33m/dev/mtd0[0m crw------- 1 root root 90, 1 Feb 26by CV - Debian
Here is mtdinfo -a: root@debian:~# mtdinfo -a Count of MTD devices: 1 Present MTD devices: mtd0 Sysfs interface supported: yes mtd0 Name: spi0.0 Type: nor Eraseblock size: 65536 bytes, 64.0 KiB Amount of eraseblocks: 16 (1048576 bytes, 1024.0 KiB) Minimum input/output unit size: 1by CV - Debian