habibie, This is entirely feasible. 12V was converted to 5V in that power supply board. But usually when people use the 3.5" HDD they have an enclosure which typically has its own 12V power source.by bodhi - Off-Topic
syong Wrote: ------------------------------------------------------- > @bodhi, > > Have you looked at the source of flashcp binary > from stock OS yet? Syong, Not yet. Is it in the GPL source tree?by bodhi - Debian
habibie, > I think this is the default settings on OpenWRT > where its uImage kernel file already includes the > .dtb file. But, I don't know how to modify the > bootcmd_usb= line on my existing uExt.txt > file without the dtb file and am hoping you can > help. I see. In that case, bootcmd_usb=run bootargs_usb; ext2load $bootdev $device $u_image_addr $u_imagby bodhi - uBoot
FYI, In a few weeks, when I got the hardware, I will start testing this kernel.by bodhi - Debian
@syong, The reason I want to see the flashcp binary fromstock OS is: when you look at the HP recovery USB, they restore stock u-boot using flashcp. So I just want to test that version. Linux kernel 4.5 seems to take care of the SPI flash correctly (it detects the addressing mode of the flash in the driver, ie. 3-byte or 4-byte). So flashing it should work. But somehow we can't. The erby bodhi - Debian
notoneofmyseeds, If you install a new rootfs then skip wheezy 3.16. Just create a jessie rootfs instead: Quotehttp://forum.doozan.com/read.php?2,12096 Updated 20 Feb 2016: This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1. After booting into this 4.4 rootfs, install kernel 4.6: Quotehttp://forum.doozan.com/read.php?2by bodhi - Debian
Tushar Wrote: ------------------------------------------------------- > Hi Bodhi, > > Thanks for replying. I'm setting up the Pogoplug > (Series 4). The system currently running on > official Archlinux. > > > # uname -a > Linux alarm 4.4.10-1-ARCH #1 PREEMPT Fri Apr 22 > 23:34:48 MDT 2016 armv5tel GNU/Linux > > > > I downloaded andby bodhi - uBoot
habibie, > > Is it possible to boot using ONLY uImage kernel > file without its .dtb file? No it's not posible. If you want to boot with FDT kernel, and using uImage only, then you have to append the DTB to uImage. Use the example in Debian kernel. Quote4b. Boot with DTB file embedded in the kernel image (no U-Boot envs changes are needed if your system already booting oby bodhi - uBoot
This did not look like pinctrl problem. It looks like the firmware was not loaded in your installation. Which kernel are you using? uname -aby bodhi - Debian
syong Wrote: ------------------------------------------------------- > bodhi, > > If you looked at the source of flashcp, I think > you would rather use dd instead. Really, it's that bad? :)by bodhi - Debian
Hi pbg4, I think I did. It was carried over from 4.5. Please take look at the patch and let me know if I should remove it from the kernel and use the mainline.by bodhi - Debian
Tushar, Which box do you have? This u-boot can run either FDT or non-FDT kernel. So it really does not matter. As long as you flash the default env image, then it will figure out the rootfs is FDT or not. However this only apply to Debian rootfs. To figure out if this Arch rootfs is FDT or non FDT. Extract and prepare it first, and then look for the DTB folder. Assuming it is mounted asby bodhi - uBoot
I need some help figuring out the SPI flash, if anybody can boot into stock OS. Look for this binary cd / find . -name 'flashcp' And please post the binary if you found it.by bodhi - Debian
Thanks for reporting the typo Rainer. The file initrd.img-4.6.0-kirkwood-tld-1should be there after you run dpkg. Look in your /boot directory ls -l *4.6.0-kirkwood-tld* Do you see it? should look like this: -rw-r--r-- 1 root root 144044 May 18 03:01 config-4.6.0-kirkwood-tld-1 -rw-r--r-- 1 root root 7542748 May 19 21:48 initrd.img-4.6.0-kirkwood-tld-1 -rw------- 1 root root 231by bodhi - Debian
I've found that flashing new u-boot on this will work only after we run kwboot to boot the new u-boot and boot into Debian. So I'll need to revise the instruction for flashing that way. Unless I can figure out why the SPI flash seems to act a different way... Perhaps becasue the old driver in stock u-boot vs the new driver in the new u-boot. Looks like CV has confirmed this, tooby bodhi - uBoot
You can install the latest LInux kernel and Debian rootfs on USB. Take a look at this thread: http://forum.doozan.com/read.php?2,12096by bodhi - Debian
Kernel linux-4.6.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link. NOTE: I would like to see reports from Zyxel NSA320 users in particular, whether it was successful or there is any problem.by bodhi - Debian
syong, > I can not find your source for the t5325 uBoot. I have not pushed it to the u-boot GitHub. I was debating myself whether to rebase my repo to u-boot to 2016.05 and release all at the same time :)by bodhi - Off-Topic
bobafetthotmail Wrote: ------------------------------------------------------- > > If it is messy, let's clean it up, together. :) > > the approach of HP's t5325 u-boot is beyond > stupid. > > The firmware rewrites envs each power off, the > system then does not "power down" but reboots and > the new envs bring it into a "ninja low-poby bodhi - Off-Topic
Unfortunately, no. The driver works only intermittently currently. So not sure we'll get the final version that I can trust.by bodhi - Debian
bobafetthotmail Wrote: ------------------------------------------------------- > >there is no urgency for releasing a new u-boot, > > Yeah, as it is now it will probably be fine until > kirkwoods are obsolete (considering their average > role, that's at least a decade), any more work on > it will be to add device support. > > I mean, it has all useful drby bodhi - Debian
> But bodhi didn't update the env image to use it, > he seems to be stuck in the past :P Leisurely pace :)) > > @Bodhi update the standard envs with "load" pls, > it's very nice. I was procastinating :) I was hoping to do it at the same time I release new u-boot. But there is no urgency for releasing a new u-boot, so yes I'll update new env imaby bodhi - Debian
> For the > new uBoot, wol seems the most interesting. Not :) The approach HP uses for T5325 u-boot to do WOL is pretty messy.by bodhi - Off-Topic
> Is that message from stock uboot code? I think it is from kernel bootlog and stock u-boot.by bodhi - uBoot
bobafetthotmail Wrote: ------------------------------------------------------- > another useful post from bodhi about bad blocks > http://forum.doozan.com/read.php?2,7806,13250#msg- > 13250 > > Might be a good idea to make a post you can add to > the list of tutorials Thanks! I forgot about this post.by bodhi - uBoot
root@Nsa310s:~# uname -a Linux Nsa310s 4.6.0-kirkwood-tld-1 #3 PREEMPT Mon May 16 22:49:40 PDT 2016 armv5tel GNU/Linux root@Nsa310s:~# dmesg | grep 'eth' | grep link [ 2.843967] mv643xx_eth: Set the PHY to fix link down [ 23.713376] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 25.600179] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex,by bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > jay Wrote: > -------------------------------------------------- > ----- > > hi, i have a problem at a goflexnet: > > > > [ 1256.923314] usb 1-1: reset high-speed USB > > device number 2 using orion-ehci > > [ 1257.094226] sd 1:0:0:0: tag#0 FAILED > > Result: hostbyte=DIDby bodhi - Debian
jay Wrote: ------------------------------------------------------- > hi, i have a problem at a goflexnet: > > [ 1256.923314] usb 1-1: reset high-speed USB > device number 2 using orion-ehci > [ 1257.094226] sd 1:0:0:0: tag#0 FAILED > Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE > [ 1257.102558] sd 1:0:0:0: tag#0 Sense Key : > Unit Attention > [ 1257.109by bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > Last post was moved to its own topic. > > If you have problem booting and need help, please > make a new topic. This is the kernel release > thread !by bodhi - Debian