Joey, > It's the most cost-efficient upgrade to a Pogoplug > v3 (likely v4 mobile when I get the right > capacitors too!) I can think of... Is the 3.5" toaster with USB 3.0 interface more expensive than this gadget?by bodhi - Off-Topic
desigabri, What you need to do is to start the serial console, power up, interrupt serial console, and run these commands: printenv boot Post here the entire serial console log (from the u-boot banner until the boot process stops).by bodhi - uBoot
Hi CV, Let's take a breather! I think we are at the point that I've learned enough about this box to be able to start working on the new u-boot. It would not have been enough info without looking at the new kernel running like it is now. What you can do to benefit everybody is running the new kernel and check out the system to see if it does what it suppose to do with memory,by bodhi - Debian
@Gravelrash, How is your T5325 project? is the serial working?by bodhi - Debian
Val532, Is the problem with 3.18 or 4.4? Send or post your patch and the config file for kernel 4.4, I'll see if I can build it.by bodhi - Debian
Cool!!! Let's revisit this envs tomorrow.by bodhi - Debian
CV, > Yes, gives all zeros: > HP>> md ff00003c > ff00003c: 00000000 00000000 00000000 00000000 This is neither good or bad. It means we just don't have an indicator if UART booting is supported. > Well, kwboot does handshake, as I can see all the > UBOOT logs and kernel logs, and even allows me to > login to the t5325 ("kwboot is acting like a &gby bodhi - Debian
Ah, that's bad news! However, let's go through the checklist - Is your Linux box ARM? if it is then use the one I uploaded: QuoteTo download ARM kwboot binary for UART booting at Dropbox: kwboot md5: 0efd011bdb244436e432a8de33e639a1 2. Did you check the bootROM version in serial console md ff00003c 3. If the box has UART booting, then kwboot will handshake with theby bodhi - Debian
CV Wrote: ------------------------------------------------------- > > > > 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:by bodhi - Debian
Let me look at that again. I think there is an error on my part.by bodhi - Debian
I'm compiling the kwboot for OSX. But it seems to have some problem.by bodhi - uBoot
@CV, Very good. I think this will work. Change fw_env.config: cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors # # HP T5325 Thin Client /dev/mtd0 0xc0000 0x10000 0x10000 And do fw_printenvby bodhi - Debian
@syong, Do you have information about the installation the kext for this CP2102? It seems it is Apple non-approved kext?by bodhi - uBoot
@CV, > Sorry, to late, I already had done it, you see it > in my printenv. > But I can provide it from another t5325 on monday, > "unspoiled". No need to. Gravelrash already supplied this up thread. But it would be good if you post your curren u-boot envs. This is for confirmation and for others to use. And then I'll add this to kernel support list. For newby bodhi - Debian
Steve, I saw that you are using the CP210x serial converter. To make it work, you have to install driver. It would be helpful to add to your first post: - Mac OSX version - Siliconlabs driver version - When you install the Siliconlabs driver, how did you make it work. IOW, does this driver have kext (the Prolific PL driver does). And did you need to do anything extra to make it work?by bodhi - uBoot
@cv, Don't do saveenv yet. Boot with serial console, interrupt it, and get the stock envs listing and the commands available: printenv help And then setenv and boot setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10' setenv load_usb 'usb start; ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1 0x1100000 /boot/uInitrd' setenvby bodhi - Debian
cv, Quoteroot@debian:~# uname -a Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel GNU/Linux Cool :) Now check out everything make sure that the system works as you expect like in stock kernel. QuoteWarning: Bad CRC, using default environment This is expected. The basic rootfs does not have the right address for the stock u-boot envs. Let me take a lby bodhi - Debian
codier, > The main reason is I want to upgrade my kernel > from 3.17 to 4.4. Do I need to upgrade my uboot in > this case? No need to. Just be carfeful with the jump from 3.17 to 4.4. Backup your rootfs first!by bodhi - uBoot
Thanks for the info mieki!by bodhi - Debian
Steve, If you can run kwboot with my build tld-2 from this post: http://forum.doozan.com/read.php?3,23331,26068#msg-26068 1. See if your 3.5" Toshiba HDD is initialized OK in the 2nd slot. Interrupt serial console after kwboot has loaded. Do the poke, and ide reset mw.l f1010104 c70e0ffd ide reset I expect there will be no timeout error. Let it boot into Debian bootby bodhi - uBoot
bobafetthotmail Wrote: ------------------------------------------------------- > @bodhi: why fatload in the envs? that uboot has > ext2load too as said here > https://pointless.net/blog/2014/04/17/debian-wheez > y-hp-t5352-thin-client/ > I'm half sure that Debian cannot run from fat > filesystem (although you can make a fat partition > for boot folder only, but iby bodhi - Debian
Steve1987 Wrote: ------------------------------------------------------- > bodhi, > > correct me if I am wrong, but OS X and Linux are > not binary-compatible. I tried running > MickyWicky's binaries just in case though, and > they don't run. > > MickyWicky, could you give me some pointers on > compiling kwboot? I really want to do this :) Steby bodhi - uBoot
@cv, Booting Debian with stock u-boot. Download the rootfs tarball and create it on a USB. See http://forum.doozan.com/read.php?2,12096. Follow the instruction very closely (being root user, rootfs label,...). QuoteUpdated 24 Feb 2015: This rootfs is the first Debian jessie rootfs in my Kirkwood kernel/rootfs release series, and to keep in sync with kernel Linux-3.18.5-kirkwood-tld-by bodhi - Debian
cv, Yes try UART booting, but don't use the nsa325 u-boot. Use the 2015.10 sheevaplug u-boot: http://forum.doozan.com/read.php?3,12381 The kwboot binary link is in the above thread. The serial console on the Dockstar, connect to the T5325 and ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -pby bodhi - Debian
cv, Do you have rootfs 3.18.5 running on another Kirkwood box?by bodhi - Debian
codier , > Can I skip it as I want to keep using my current > env? you helped me alot for this when I was > flashing 2014.07 version and I screwed up the > env. If you are running 2014.07 u-boot, already flashed its default envs, then there is no need to flash the new defaults. it will work fine! BTW, that version is not that much different from the new 2015.10 version.by bodhi - uBoot
@Gravelrash, So how did it go with the serial console?by bodhi - Debian
> There are files in > /lib/modules/4.4.0-kirkwood-tld-1/ but no > directory named 'build' or 'source'. This is easy, just create them while being root user.by bodhi - Debian
sebr, Which command did you use to remove them? was it with dpkg --purge package-name sometime the traces of the installation is still in the pre/post directory if not purged.by bodhi - Debian
QuoteBut I get that we need a known safe baseline. I think this is needed. I forgot , the devices env needs to be put back (we set it to usb to eliminate problem, but it should be set to both types of disks) setenv devices 'usb ide' When you run scan_disk, the timeout error will come back. But normally it will be OK, since your rootfs disk is USB.by bodhi - uBoot