Leggo, I sent you PM on a different topic :)by bodhi - Debian
Leggo, http://forum.doozan.com/read.php?2,25473,26166#msg-26166 To keep it simple I specified the embedded DTB approach. But as usual we should use separate DTB. I will modify u-boot thread to include that.by bodhi - Debian
I've uploaded u-boot and envs images and installation instruction in this thread: http://forum.doozan.com/read.php?3,26562by bodhi - Debian
This is the official released version for HP Thin Client T5325 U-Boot-2017.07-tld-1. ================================== Last Updated 05 Nov 2017 Download U-boot and defautl envs images at Dropbox uboot.2017.07-tld-1.t5325.bodhi.tar (shorten link) or https://www.dropbox.com/s/yqo9wyn785zvvlw/uboot.2017.07-tld-1.t5325.bodhi.tar md5: 778555396c3dc74717bf1a0fe9ddf824 sha256: 73c0ad2by bodhi - uBoot
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 LEby bodhi - Debian
flyyboyy Wrote: ------------------------------------------------------- > Also forgot to mention that based on this > statement (in Debian 3.16.0 rootfs instructions): > > > (If unsure how to set this u-boot env on the > installation target, then don't worry, it can be > safely skipped. . . > > I skipped them. > > > So is it okay to skip thby bodhi - uBoot
azraleus Wrote: ------------------------------------------------------- > Some time ago @shv published > http://pogoplug.cwsurf.de/ox820-sata-uboot.tar.gz > which is needed (if I understand it correctly) to > make bootable SATA drive with debian. > Unfortunately, I found that this link is no longer > valid. Does anyone have this archive and would be > so kind and publby bodhi - uBoot
pld, It should be set to CONFIG_MTD_NAND_ORION=yby bodhi - Debian
Instruction and binaries will be posted soon in a few hours :)by bodhi - Debian
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?by bodhi - Debian
Micky Wicky Wrote: ------------------------------------------------------- > Wasn't it GPIO 33? I forgot how chrlee come up with that mask. GPIO 33 might not be correct, but I'll put that in the code and see what'll happen.by bodhi - uBoot
flyyboyy, > I installed Debian 3.16.0 rootfs on a USB stick It's root/root. If you can't get in, then prepare the rootfs again. Remember to follow the instruction very closely.by bodhi - uBoot
CV, Yes, that was the good thing about UART booting, allow you to live dangerously :)by bodhi - Debian
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.by bodhi - Debian
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.by bodhi - Debian
Micky Wicky Wrote: ------------------------------------------------------- > Happy to test, as always. Do you have madmin's explanation which GPIO was poke in the poke command? I forgot the number.by bodhi - uBoot
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 kirkwoodby bodhi - Debian
marcint43 Wrote: ------------------------------------------------------- > FYI: > mac addres starts with: 60:d8:19:xx:xx:xx > > Company Hon Hai Precision Ind. Co.,Ltd. > Address Shanghai 201613 CHINA That's Hon Hai MAC address starts with 60:d8:19by bodhi - Debian
marcint43, Look for this original MAC address. Perhaps it is inside the box. WOL will not work without it.by bodhi - Debian
pld Wrote: ------------------------------------------------------- > Found it!! > > > # diff .config* > 5361c5361 > < CONFIG_CRYPTO_DEV_MV_CESA=m > --- > > # CONFIG_CRYPTO_DEV_MV_CESA is not set > > mv_cesa has to be disabled (in the kernel > configuration!) in order to marvell_cesa to work. > Blacklisting is not enough. Nice :)by bodhi - Debian
marcint43, The NSA325 has 2 different MAC addresses (Zyxel changed it). So when you run etherwake, it should use the Marvell MAC address (look for it outside on the box case, or in original boot log if you have the log). Mostl likely, it starts with 4C:9E etherwake 4C:9E:FF:xx:xx:xxby bodhi - Debian
sparks, Thanks for the solution writeup! this is exactly what sLOID should do, IMO. There might be a way to keep this permanent.by bodhi - Debian
Hi pld, > It's not about sources or patches. It's about the > kernel configuration. I did compile linux-4.4.3 > patched with the patch taken from > linux-4.4.0-kirkwood-tld-1-bodhi.tar.bz2 and the > config from: > https://github.com/archlinuxarm/PKGBUILDs/tree/mas > ter/core/linux-kirkwood-dt > > CESA works as expected. Cool! thanks for figuriby bodhi - Debian
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. 5by bodhi - Debian
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. Onby bodhi - Debian
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 noby bodhi - Debian
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).by bodhi - Debian
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 ttlby bodhi - Debian
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 >by bodhi - Debian
sLOID Also, the easiest fix is to get ntp/ntpdate working. I think you're trying to do to much to fix this. ntp is a real solution.by bodhi - Debian