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
renojim Wrote: ------------------------------------------------------- > I just got one of these myself to play with (even > though I really have no time :-) ). I didn't get > anywhere with kwboot. The "reset button" doesn't > seem to reset anything. The only effect I saw > that it has is that if you hold it in while you > apply power the LED staysby bodhi - Debian
habibie Wrote: ------------------------------------------------------- > Gravelrash Wrote: > ------------------------------------------------------- > > habibie Wrote: > > > ------------------------------------------------------- > > > bodhi Wrote: > > > > > > ------------------------------------------------------- > > > > Theby bodhi - Off-Topic
> I never bothered with it and was sort of > disappointed that it never happened on any of my > Linux desktop computers. You’re a masochist :)))by bodhi - Off-Topic
Remember the Y2K? System call conversion for year 2038: https://lwn.net/Articles/643234/ This works has been ongoing and will have something incorporated in kernel 4.18.x The Y2K panic was a lot of fun! Yours truly was one tasked to find and put in remedies (if necessary) for a particular million-line-of-code software system :))by bodhi - Off-Topic
lcg, > Thanks again bodhi, worked pretty well :-) and > booted into the rootfs. Cool! > However, for the rescue > system, using the previous variables does not > work and the rescue system does not boot: Yes, a little bit more needed to be done to retrofit the rescue envs. Boot into Debian and then, fw_setenv bootcmd 'run bootcmd_uenv; run scan_disk; ruby bodhi - Debian
balanga Wrote: ------------------------------------------------------- > How do I load environment variables from uEnv.txt > once I have booted up from kwboot and am at the > uBoot prompt? run bootcmd_uenvby bodhi - uBoot
Joey, > Me too I disagree with the transcript but "get" > what Habibie meant. We're cool - even so I was > saying "we can agree to disagree" long before a > more famous guy said it :-) I think we agree about it's too bad it was MS who bought GitHub (with their history). But I think GitHub had to sell, and as a private company they need to make thby bodhi - Off-Topic
lcg, > - the old one had a part about the rescue system > in the NAND (which worked till now very well!) -> > does this still works with the new environment or > do I have to change/ add variables? You will need to retrofit those rescue envs to the new envs. This could be done after you have rebooted into Debian. > - stderr, stdin, stdout are now "serial",by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > What you all said above is practically a > capitalism scheme. That said, the existence of > Linux is probably due to socialism. ATM, > capitalism looks like a dominant thing in this > world, not exactly like the world depicted in > StarTek world. I disagreed with this viewpoint completely. But toby bodhi - Off-Topic
Hi Ray, You've created the Wikidev page that stated that the Ethernet chip is 88E1318. Is that on the chip marking?by bodhi - Debian
"Embrace, extend, and extinguish". That's what M$ did and probably still doing :) When you look at Google, it is the same thing. They bought out promising startups and shelved the products. Voila, less competitors in the market that they are in. It is totally sucks. It is really hard for innovators to see their products come to fruition.by bodhi - Off-Topic