rkachowski, I need to see how the envs got reset to in stock OS: fw_printenvby bodhi - Debian
Maarten, ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.pogo_v4.mtd0.kwb -p > Sending boot message. Please reboot the > target.../ > Sending boot image... > 0 % [.+.+xmodem: Protocol error This actually looks good. It's the Pogo V4 quirk. You need to recall (up arrow) the kwboot command above and execute it again, repeatedly a few times, until the handshby bodhi - uBoot
balanga, Since you have decided not to use Arch u-boot, don't use Arch definition of 2 mtds. You might as well set it to the traditional definition of 4 mtd partitions: fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'by bodhi - uBoot
Shogun, > I have a GoFlexHome that I recall installing > ArchLinuxARM onto years ago. > Is it possible to get this to boot a flash drive > instead of its internal OS? It is definitely possible. 1. "years ago", do you remember which year? it is important to know the time period. Because ALARM has 2 different u-boot version over the years. We do too. At the earby bodhi - uBoot
Thanks for uploading prahal! > On my side I learned that one ought not to run > picocom in parallel to kwboot ... else kwboot > upload has errors "+" instead of "." and ends up > freezing. Indeed! kwboot is a serial console terminal by itself (after loading u-boot image). So running picocom along side would interfere with it, and there is no reason to do sby bodhi - uBoot
rkachowski, 1. So I guess you don't have serial console? if you do then it'll be much easier to see what was wrong. Quote> 3. setup usb with > Debian-4.12.4-mvebu-tld-1-rootfs-bodhi.tar.bz2 - > single partition ext3 with label 'rootfs' 2. Were you root user while you created rootfs like described above? Boot into stock OS, insert and mount the USB rootfsby bodhi - Debian
balanga, Quote> I'm trying to update u-boot on a GoFlexHome dock > according to instructions here:- > > https://forum.doozan.com/read.php?3,12381 > > I've downloaded > uboot.2017.07-tld-1.goflexhome.bodhi.tar from > https://bitly.com/2zQWP4Y , and made sure I made > the appropriate tools. > > /etc/fw_env.config has been copied > &by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > I created an Arch Linux bootable USB stick for my > GoFlexHome unit the other day and it only required > the rootfs to be extracted and was bootable. In > contrast a number of additional steps are needed > before making Debian installation bootable. With > Arch Linux /boot only contains uImage and &by bodhi - uBoot
Indeed, the USB partition is not recognized USB: scanning bus for devices... 1 USB Device(s) found Waiting for storage device(s) to settle before scanning... 0 Storage Device(s) found USB part made: print_part of 0 ## Unknown partition tableby bodhi - Debian
balanga Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > If you have serial console then you would > execute > > > > ver > > > > > > Without serial console, you can grep the mtd0 > > inside Linux shell to find the version string: > > &gby bodhi - uBoot
rkachowski , I will take a look later today.by bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?2,41874by bodhi - Debian
heiko, > Have you a suggestion for a cheep good hdd with 1 > or 2 tb for the 24/7. In the old days, my cheap and good HDD is Hitachi. But the company have been acquired, so I don't know how good they still are nowadays. The brand that people like for 24/7 is WD Caviar Red, you should research that.by bodhi - Debian
LeggoMyEggo, The commands are the same for Kirkwood box Generate the uImage with DTB embedded inside: cd /media/sdb1/boot cp -a zImage-4.12.1-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-goflexnet.dtb >> zImage.fdt mv uImage uImage.orig mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.12.1-kirkwood-tld-1 -d zImage.fdt uImage sync So substituteby bodhi - Debian
LeggoMyEggo, > One small issue with embedding the > armada-370-mirabox.dtb in uImage, the > Linux-4.12.4-mvebu-tld-1 file does not exist in > the boot directory of the premade Debian rootfs > ('Debian-4.12.4-mvebu-tld-1-rootfs-bodhi.tar.bz2') > nor is it in the linux update > ('linux-4.12.4-mvebu-tld-1-bodhi.tar.bz2'). How > do I embed dtb usby bodhi - Debian
balanga, > At the moment I'm unable to use my serial cable to > access my unit and can't be sure about which > U-Boot I'm using. If you have serial console then you would execute ver Without serial console, you can grep the mtd0 inside Linux shell to find the version string: grep -a --null-data U-Boot /dev/mtd0ro Note: when you run this grep command, itby bodhi - uBoot
balanga, > Sorry for all these nooby questions, but I seem to > have a mental block when it comes to U-Boot. This is why it has been very difficult to help you. When you have mental block like that, abadon all you have read about u-boot. Pretend you know nothing, and follow instruction to install the latest u-boot for your box: https://forum.doozan.com/read.php?3,12381 Do eaby bodhi - uBoot
LeggoMyEggo, Good to see you posting again! > The device successfully boots on the stock 3.2.36 > Debian Wheezy 4 Gb rootfs which is on a micro-sd > card internal on the motherboard and is considered > a USB drive (not sure why internal is USB and > external is MMC). It is an internal USB card reader. > > Am assuming because of stock u-boot being so old,by bodhi - Debian
saschbaer, Cool :) Now you can read helge's thread to see how the new Debian rootfs can be booted on USB. 1. Create the Debian rootfs on USB first: https://forum.doozan.com/read.php?2,12096 QuoteUpdated 24 Jul 2017: Basic Debian stretch Kirkwood rootfs for most Kirwood plugs: - tarball size: 188M - install size: 488M - The init system used in this rootfs is sysvinitby bodhi - Debian
========= helge's log ** MARVELL BOARD: DB6702A-GMtech LE U-Boot 1.1.4 (Jun 5 2013 - 10:49:39) Marvell version: 3.6.0 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFB00 Soc: 88F6702 A1 CPU running @ 1000Mhz L2 running @ 500Mhz SysClock = 400Mhz , TClock = 166Mhz DRAM (DDR2) CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAMby bodhi - Debian
saschbaer, You already have the correct RXD and TXD connection when you used minicom, and could interrupt stock u-boot at countdown. And when kwboot slows down, it senses some character at the port that it can't recognize. So it is not RXD/TXD. I think the bad news is most likely your box does not support UART booting (same as some of the Kirkwood boxes such as Dockstar, Pogo E02,...)by bodhi - Debian
saschbaer, Quote* MARVLL BARD: DB702A-GMtech LE U-Boot 1.1.4 un 5 213 - 10:49:39) Marvell ersi3.6.0 UBoot code: 00600000 > 0067FFF0 BSS: -> 006CB00by bodhi - Debian
heiko, I've verified that both HDD works fine, with and without serial console attached. Perhaps we should take a look at your problem a little bit closer. Make sure no USB drive is plugged in. Boot into Debian with 1 HDD with rootfs on it, like you did before. After login, plug in the 2nd HDD, and mount it.. Assuming your rootfs is sda1, and the 2nd HDD is sdb1. And the 2nd HDDby bodhi - Debian
This is a quite good price. I've been supporting this box since January 2017 with the latest kernel and roofs: https://forum.doozan.com/read.php?2,32146 Excellent NAS with dual 3.0 Gbps SATA, Marvell Armada 380 SoC 1.3 GHz CPU, DDR3 512 MB Memory. If you want a best NAS for this low price, this is it. Note: the specs said it is SATA II. But it seems to run my HDD at 6.0 Gbps, I hby bodhi - Off-Topic
saschbaer, Dowload the NSA310S u-boot: https://forum.doozan.com/read.php?3,12381 Read this UART booting mentioned in that thread: QuoteUART Booting: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction here in this thread. The latest u-boot image released here should be used for UART booting, if yoby bodhi - Debian
saschbaer Wrote: ------------------------------------------------------- > I remember I entered a set of envs for using nc > without Serial terminal. > With that I changed the Server and Client IP and > entered the NC commands as posted. > Any possibility to undo that action? No way to undo that without knowing what a good set of envs is supposed to be. And netconsoleby bodhi - Debian
1. Google for this box name, hopefully that in some forum, someone has the same box in working order, and you can ask for a listing of the current envs. 2. If 1 fails, contact the manufacturer or visit their website to find the recovery Firmware. 3. If 1 and 2 fail (I will not be surpised because either the box might be too old, or nobody has hacked it), come back and we'll try the UARby bodhi - Debian
saschbaer, > Im not sure what you mean with list and log... I > just did the printenv which is listed in here. What you listed were the u-boot internal envs. That's what u-boot uses when encountered a bad CRC checksum, or a bad NAND sector where the envs are stored. What actually stored in that NAND sector is the envs that used for booting. Thus, you could not boot because thby bodhi - Debian
Yeah, it is expected. I knew this was misconfigured, we've discussed this a while ago :) With too many plugs, I don't recall right away the idiosyncracy of each. This cannot be solved, atm. In the next kernel release, the LED will be green right after the kernel booted. This is set in the DTS. If you use the right DTB, then all LEDS are available in /sys/class/leds. And controlleby bodhi - uBoot
ingmar_k Wrote: ------------------------------------------------------- > Well, time's the only issue- Otherwise I would > post more often. > > Do I really need to pay Lenovo for that code? > Nobody around, who still has the source backed up > somewhere? I've PM prahal and arvati, but has not got any answer yet.by bodhi - uBoot