Sounds like you need to set the appropriate dtb file.by rayknight - uBoot
bodhi Wrote: > Interesting! what OS are you running on these > plugs? are they all running the latest Linux or > some with stock? Actiontec MI424WR rev I (stock OS, still in my backlog for hacking, 88F6560 based) Actiontec SG200 (stock OS, still in my backlog for hacking, 88F6560 based) Buffalo Kuro-box Pro (currently Debian 8.5, has been running a version of Debian since aboutby rayknight - Off-Topic
I'm an addict :-) These are just my Marvell based devices, I also have many other ARM based systems: Actiontec MI424WR rev I Actiontec SG200 Buffalo Kuro-box Pro Buffalo WZR-AG300NH Cisco ON100 Cloud Engines Pogoplug E01 Cloud Engines Pogoplug E02 x 3 Cloud Engines Pogoplug 4 A1 Cloud Engines Pogoplug 4 A3 D-Link DIR-665 D-Link DNS-320 Globalscale DreamPlug HPt5325 Iomega Icby rayknight - Off-Topic
I just acquired a sealed PogoPlug Series 4 (POGO-V4-A3-01). It appears that I'm going to have to open it up to acquire access as the Enable SSH option no longer appears after registering at my.pogoplus.com/activate. The curl trick doesn't appear to work either. Any other suggestions before I break it open and solder on the pins for serial access?by rayknight - Off-Topic
Is there source available for the stock firmware? You will need to determine how the display is driven and source code for the stock firmware would be one way of determining this.by rayknight - uBoot
Tried booting to a fresh USB drive created from Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Then followed the instructions for installing the Kirkwood U-Boot. I had to install mtd-utils, but after that the instructions were successful and I'm now booting straight into the USB drive!!! I guess starting from a fresh install of Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 may haby rayknight - uBoot
Here are the results you asked for (1st without USB drive, then with USB drive): U-Boot 2014.10 (Jan 02 2016 - 02:37:49)M Pogo E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 PogoE02> printenv arcNumber=3542 baudrate=115200 bootargs=console=ttyby rayknight - uBoot
I just acquired a Pogoplug E01 the original Cloud Engines plug. The internal board is manufactured by GlobalScale Technologies and indicates a REV3.0 It is a 1.2Ghz 88F6281 with 512MB Hynix NAND and 256MB Elpida RAM. There is only a single USB 2.0 and Gigabit Ethernet via the 88E1116R. There is also an on-board battery. Stock U-Boot is 1.1.4 CloudEngines (3.4.16). Stock linux kernel is 2.6by rayknight - uBoot
I can do that tonight, but a little history might be helpful. I acquired this PogoPlug after someone else attempted to install OpenWrt. They were not successful as the boot fails to load an OS. I was able to manually enter commands to boot Debian from USB. The installed u-boot appears to have a limit on the length of an environment variable which made the task more difficult. So yes I manuaby rayknight - uBoot
Results: root@debian:~# fw_printenv | grep -i dtb root@debian:~# fw_printenv bootcmd bootcmd=run bootcmd_uenv; run bootcmd_usb; run bootcmd_nand; reset root@debian:~# fw_printenv mtdparts mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) root@debian:~# ls -l /boot/dts/*e02* -rw-r--r-- 1 root root 10446 May 18 2016 /boot/dts/kirkwood-pogo_e02.dtb root@debian:~# unamby rayknight - uBoot
Having a problem loading the latest u-boot to a Pogoplug E02. I managed to boot to the latest Debian rootfs (upgraded to Debian 8.5) on a USB flash drive. Expected the proper binaries to already be installed. fw_printenv and fw_setenv are available, but the crucial flash_erase is not available. So I unpacked linux-tools-installation-bodhi.tar.gz to a temp directory and the tried executing flaby rayknight - uBoot
I had serial access to mine a couple of years ago when I was playing with it. Your postings have prompted me to go digging around for my HP T5325 and see if I can update to a newer Debian release.by rayknight - Debian
I have one of these and the stock firmware is Debian Lenny. You can see the entry I created on wikidevi about 2 years ago for more details (https://wikidevi.com/wiki/HP_t5325).by rayknight - Debian
Looking at the source code available from Seagate at http://www.seagate.com/support/downloads/item/central-gpl-fw-master-dl/ it appears to be using the same kernel source as the Seagate Business NAS which indicates a Cavium Econa CNS3420 processor.by rayknight - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Serial as in SATA? I ask because that was one of > the descriptions at NewEgg, but it seems they > intentionally mis-label Pogoplugs. Some of the PogoPlugs do have an internal SATA port. The Pogoplug Pro and some of the BXX series that use the PLX Technology NAS7820 processor have an internal SATAby rayknight - Displays
bodhi Wrote: ------------------------------------------------------- > megov Wrote: > -------------------------------------------------- > ----- > > I think, it is ignore the handshake. The > original > > kwboot stuck in a loop, > > waiting for NAK (as I can suppose from code). I > > add some debug > > hexdump to stderr code into kwboot_tty_recby rayknight - uBoot
bodhi Wrote: ------------------------------------------------------- > rayknight Wrote: > -------------------------------------------------- > ----- > > I currently have 2 Kirkwood based systems not > > covered by the latest Kirkwood builds. <SNIP> > > I would make sure that UART booting is working > with these. You can use a referenced board u-booby rayknight - uBoot
I currently have 2 Kirkwood based systems not covered by the latest Kirkwood builds. 1. Cisco ON100-K9 Marvell 88F6282 @ 1.6 GHz, 512MB Flash, 512MB RAM, stock U-Boot 1.1.4 2. D-Link DNS-320 Marvell 88F6281 @ 800 Mhz, 128MB Flash, 128MB RAM, stock U-Boot 1.1.4 The D-Link appears to have a Device Tree available in the latest kernels, but I don't believe the Cisco has one. What addby rayknight - uBoot
Thanks for the reply bodhi. However, after further web searches I believe I am closer to what I actually want. I found some posts on the Arch Arm Linux forums and then some pointers to github for Pogoplug_V3_Emdebian_Debian which also had directions for creating a bootable SATA disk. I can now directly boot the SATA disk I created. I will be studying the scripts and I should be able to figureby rayknight - uBoot
I'm attempting updating my 1st PogoPlug Pro with the latest U-Boot and have run into an issue. I followed the instructions at the first post, but skipped step 9 and 10 because I still have the stock firmware installed. Now when I boot I can no longer interact via my serial console. I get the following from serial port: U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27) Boot device: NAND Aby rayknight - uBoot
Could someone clarify what is the best way to get latest kernel and rootfs on a stock PogoPlug Pro? Do I install the new uBoot first or the kernel/rootfs? Is there an available Rescue Image for the oxnas based systems? Is it possible to boot from eSATA? Ideally I would like to have an accessable rescue system on NAND and Boot Debian from the eSATA port. Thanks Rayby rayknight - Debian