argent88, > Reverting cables worked!! :D Congrats :) > Here's what I see now! > > U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:22) Arch > Linux ARM > Seagate GoFlex Net It's an older but good Arch built u-boot.by bodhi - Debian
argent88, > Little fact, hope this gets me out of troubles: > When OMV or Windows 10 are making boot I see the > three lights of the usb to serial thing all on, > when they are done the last one, T, which stands > for TX, shuts. Is it worth making notice? It does not sound meaningful. > > Tried Putty on windows 10, tried minicom on OMV, > had no results tby bodhi - Debian
Hi Ron, > Sorry for my > ignorance and lack of knowledge Not at all! Usually for a Kirkwood box (such as this one) that I'm supporting has 2-part installation: New kernel and rootfs: https://forum.doozan.com/read.php?2,12096 New u-boot: https://forum.doozan.com/read.php?3,12381 And you would install both from stock OS. However, for this EA4500 box, I only haveby bodhi - Debian
argent88 Wrote: ------------------------------------------------------- > I see no result in the putty screen. > Tried it with and without ArchLinuxARM USB stick. > No result. Try swapping TX and RX wire at the GoFlex Net port. The PLxxx and the CPxxx serial module pins are configure differently. With the PLxxx you need to connect TX to RX, RX to TX. But with the CPxxx you nby bodhi - Debian
balanga, QuoteI'm trying to run kwboot through the gdb degugger and would like to identify the exact point at which it stops. I was not previously aware of this special handshake sequence which I presume is not getting sent or acknowledged.. You are really wasting time doing this. We knew that your GF Home can be kwboot using another Linux box. And kwboot works the same way in any *nixby bodhi - uBoot
argent88 Wrote: ------------------------------------------------------- > When I connect it via serial or in any process > should the Goflexnet be on? > Shall I connect it to the current? Is the serial module converter plugged into your PC or laptop? Which version is this module? CP2xx or PL3xx? Warning: Don't connect the 3.3V. Should connect only TX, RX, and GND. On yoby bodhi - Debian
balanga, > There is no log as such The log is what you see on your terminal, verbatim, ie. copy/paste. In a troubleshooting session, I want to see what you see, not what you think you see. Because it is often misleading. I would like to avoid misunterstanding the problem from your interpretation. I want to see exactly what you see on the screen. Even if nothing happened when you eby bodhi - uBoot
balanga, > > > > Please post the log your attempt to connect > with > > kwboot. > > > It simply stops with the prompt:- > > Please reboot the target into UART boot > mode.../ > That's not a log! When I ask for a log, please post it. That's how we save time going back and forth. I want to see the log for every question, if pby bodhi - uBoot
argent88 Wrote: ------------------------------------------------------- > I tried making the USB stick as you said. No > success. > I have myself a serial to USB cable. What shall I > do? > Argent See the bold thread in the Wiki that I’ve posted above: https://forum.doozan.com/read.php?2,61959,61974#msg-61974by bodhi - Debian
balanga Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > balanga, > > > > - BootROM starts > > - BootROM senses the serial port for a special > > handshake sequence, and if sucessful, starts > > receiving uboot image from the serial port > using >by bodhi - uBoot
balanga, kwboot has nothing to do with Linux or FreeBSD. These kernels do not come in to play until later. The ARM boxes such as these Kirkwood plugs power on sequence is: - Power on - BootROM starts - BootROM senses the serial port for a special handshake sequence, and if sucessful, starts receiving uboot image from the serial port using xmodem protocol. - After bootROM has receivedby bodhi - uBoot
A. Create USB rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2, following the instruction in: https://forum.doozan.com/read.php?2,12096 Scroll down to section: 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 sysvinit . To boot with systemd, sby bodhi - Debian
Looks like this is the Arch envs on Aug 20, 2015: https://github.com/archlinuxarm/PKGBUILDs/blob/a9347b2ee39082289e4747518d929cab462328fe/alarm/uboot-kirkwood/uboot-goflexnet.txt bootcmd=run startboot;run bootubi bootdir=/boot bootfilem=uImage bootfilez=zImage bootubi=echo Trying to boot from NAND ...;if run mountubi; then ubifsload ${loadaddr} /boot/zImage;ubifsload ${fdtaddr} /boot/by bodhi - Debian
Argent, > How do I find the log of my installation? Is it on > the USB stick? No, the log here means copying whatever on the terminal screen and save it to a text file. > Oct 2015 This hopefully made it easier, it is relatively modern. But it would be much helpful if you can retrieve the a file named "uboot-goflexhome.env" or "uboot-goflexnet.env" from Arby bodhi - Debian
Argent, If you keep the log of your installation back then, then post it here. Without the log, it still should be not be too difficult. But you need to remember the year and preferably also the month when you install Arch Linux. This is to identify the u-boot version on your box right now. Arch rootfs files structure setup is slightly different. So in older version of its u-boot, the enby bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > Finally found one at a "reasonable" price.... its > coming from Israel and all in it should be $40 > (US)... heres hoping it works and i can start to > play > > :) Cool :)by bodhi - Off-Topic
JT, > It looks like the > -p parameter makes all the > difference Awesome :) it really does. Because without the -p parameter, it would not expect the SPI header, when there is a header in the image being sent (so the image looks invalid to the bootROM). root@jt-ubuntu:/home/jt# ./kwboot > -B 115200 -b > gdrv/uboot.2017.07-tld-1.nsa325.mtd0.kwb -t -p > /dev/ttyUSby bodhi - Debian
renojim Wrote: ------------------------------------------------------- > Ok, I do think it's a timing issue and not some > kind of Secured Boot issue. I don't think the > kwboot command used is the problem. Using > Tera Term to > send the "enter command line debug mode" pattern > (0xDD, 0x11, 0x22, 0x33, ... 0x77) over and over > for a few secondby bodhi - Debian
Could somebody post the serial console log of you kwboot attempt (including the command how you executed it). I've just realized I have missed that part. We just talked about how it failed :) What JDS did above was the wrong way to execute this image: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb You need -p like this: ./kwboot -t -B 115200 /dev/tby bodhi - Debian
JT, > Right, but didn't the NSA325 support kwboot? Yes. The NSA 325 did not have a bootROM version identified, so we thought it does not have kwboot. And at the end, it has kwboot supports. However, most other Kirkwood boxes with bootROM 1.21 do supports kwboot, so I hope we just did not get the right timing (like the Pogo V4 in the beginning). From what I've seen, the Seby bodhi - Debian
@JT, I don't think this box Secure Boot is on. We had quite a few Kirkwood boxes that don't have kwboot capability. This is a Kirkwood just like the NSA325. @Leggo, We already have a Kirkwood rootfs, you'd install it just like other boxes. The thing to look for is which DTB you are going to use to allow it to boot into Debian. I would start with the NSA325 or something simby bodhi - Debian
For each mtd on the list cat /proc/mtd You would do nanddump --noecc --omitoob -f mtd0.gfh /dev/mtd0 nanddump --noecc --omitoob -f mtd1.gfh /dev/mtd1 and so on.by bodhi - Rescue System
JDS420 Wrote: ------------------------------------------------------- > I'll give it another try with different timings. > Is there a way to delay uboot from starting right > away; like a delayed boot envar? Not possible to delay u-boot from starting. If nothing telling the bootROM to load u-boot from UART, it will load u-boot from flash and start it.by bodhi - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > > That's said it all :) > > It was a memorable time, 1999 up until New Years. > I was in IRC with Brit friends and knew 5 hours > earlier nothing broke over there, so all was going > to be good.by bodhi - Off-Topic
JDS420 Wrote: ------------------------------------------------------- > No, most of the time the commands being sent > interrupted the normal boot and left it at the > uboot prompt This told me that the kwboot command was too late or completly ignored. No handshake attempt has occured.by bodhi - Debian
JDS420 Wrote: ------------------------------------------------------- > I tried maybe 300+ times until I got frustrated > and walked away Then I think UART booting might not be supported. Did the xmodem error occur each time?by bodhi - Debian
habibie, Quote> You’re a masochist :))) > TBH, I really was very disappointed that the Y2K did not happen to any of my Linux desktop computers. I sure would like to find out what that would have done. Alas, you don't always get what you want. If you think being honest is a masochist and better than dishonest, then be it. It's a joke :) QuoteGravelrash Wrote: we hby bodhi - Off-Topic
JT, > I believe I saw three different errors (I wish I > had saved the session(s)). Most of the time it > was exactly what JDS reported (Protocol error). I > can't remember exactly what the other error > messages said. Sometimes I got a dozen or so "+" > signs before the error, but I never saw anything > more than 0%. Interesting! Usually if itby bodhi - Debian
Thank JDS420 and JT! Pin 1 is marked on the board with a thick white mark. Next to the Ethernet port. Ouside the box facing in - left-to-right 1. 3.3V 2. RXD 3. TXD 4. GND Only TXD, RXD, and GND should be connected.by bodhi - Debian
JDS420 Wrote: ------------------------------------------------------- > For anyone who wants to know, the serial pinout is > written right above the header in my picture. > > > > Edit: the 3rd part is a swap partition What does stands for? TXD, RXD, GND? ...by bodhi - Debian