Thanks Ray for serial pins out & Joey for confirmation! This is interesting: QuoteJoey -4th edit- I connected it to router with Internet unplugged, got address reservation with router's DHCP. I couldn't quite get MON to show itself but I almost swear I saw it in DHCP list and I couldn't reserve it in time. I don't know about Bonjour but neither Win7 nor OSX snow Lby bodhi - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > > RESET! I hit reset for over 10 seconds and got > this right around that time: > Wow at least it outputted something, that's a > relief. Hey I don't know the ways of this, but > like the first poster, I set both my Device > Manager device AND puTTY to 115200 and it seemeby bodhi - Debian
armless, I've attached a new DTB here. 1. Boot into Debian, and replace the current DTB with this one /boot/dts/kirkwood-pogo_e02.dtb 2. Recreate uImage as you did before: append this new DTB to the original uImage 3. Reboot and this time remove mtdparts definition from bootargs setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10" Basicallyby bodhi - uBoot
FYI, my kwboot does not even start handshaking. So I think it is a faulty serial connection in some way.by bodhi - Debian
armless, > root@debian:~# cat /proc/mtd > dev: size erasesize name > mtd0: 08000000 00020000 "orion_nand" > > > root@debian:~# cat /proc/cmdline > "console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 > mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(root > fs),-(data) ro" > This is really odd! It meant that the mtparby bodhi - uBoot
> uboot flashing is the very last step, so I just have the script quit if crucial steps cannot be completed (making rootfs, finding important envs) and no damage will have been done. Cool. > They have many device-specific scripts though, so > they (should) know beforehand each device and its > quirks, I'm making a multi-device installer for > devices I don't eveby bodhi - uBoot
rayknight Wrote: ------------------------------------------------------- > You can't run the stock OS unless you pick up a > used unit that was previously deployed. A new > unit will attempt to download and install the > stock firmware. I am not really interested in stock OS. U-boot only. If you know what that means?by bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > @bodhi - it looks like uboot has silent > output..!.!.! > > taken from the manual > DHCP (required for initial startup only). > At initial startup, the OnPlus Network Agent must > obtain a LAN IP address using DHCP. > Once you are connected to the OnPlus Network Agent > and have starby bodhi - Debian
> Currently, the script filters and works only with > /dev/sdx drives bigger than a GB or so. I > think (correct me if I'm wrong) the minimum size > limit should be enough to filter out any NAND > partitions that for some weird reasons are listed > as /dev/sdx. I think that would be OK. There is no Kirwood box that has 1GB NAND. Also I think right here, the disk selby bodhi - uBoot
armless, I've modified step 3 above to include mtdparts in bootargs: http://forum.doozan.com/read.php?3,28772,29034#msg-29034 After booting into Debian, try fw_printenv cat /proc/mtd cat /proc/cmdlineby bodhi - uBoot
bobafetthotmail, > OK, I can have the script skip the question if it > detects only a single drive (thinking about it, it > is stupid to ask questions if there is a single > drive :) ), so as long as the newbie is following > your instructions ("only a single drive") he > should not get any question, while others that > need the feature still can use it. &by bodhi - uBoot
Joey, > The lights look healthy, they sequence through > stages and ends-up left amber solid and right > amber blinking. Thanks, that's what I wanted to know. Seems Gravelrash and I got bad luck. I'll take a look again during the weekend.by bodhi - Debian
> Have you checked to ensure you don't > have RX and TX reversed? :)) Funny, I've just advised other forum member about TX-RX crossing.by bodhi - Debian
armless, root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 08000000 00020000 "orion_nand" root@debian:~# This is because you've booted with a different u-boot, and u-boot envs. And the envs settign in that u-boot needs correction. > But the u-boot environment, as seen by Debian, > does have mtdparts indicating 4 partitions: > > > rby bodhi - uBoot
miko Wrote: ------------------------------------------------------- > YOU ARE GREAT!!!!! > Thank you. > 9 times and... done :) > Could you tell what next? :) > U-Boot 2015.10-tld-1 (Nov 06 2015 - 16:02:55 > -0800) > Pogoplug V4 > > SoC: Kirkwood 88F6192_A1 > DRAM: 128 MiB (ECC not enabled) > WARNING: Caches not enabled > NAND: 128 MiB > MMby bodhi - uBoot
bodhi Wrote: > Some module converter need reversing TX-RX, some > do not. The PL3xxx needs crossing RX to TX. The CP2xxx does not.by bodhi - uBoot
miko Wrote: ------------------------------------------------------- > Do you mean connect RX to TX? If yes: output is > 0 % [+++++++++++++++++xmodem: Bad > message When you see this xmodem bad message, recall the kwboot command and execute it again. And repeat this sequence for serval times. Some module converter need reversing TX-RX, some do not.by bodhi - uBoot
miko Wrote: ------------------------------------------------------- > Thank you for your answer. > I have tried to connect to pogoplug via piocom: > picocom v1.7 > > port is : /dev/ttyUSB0 > flowcontrol : none > baudrate is : 115200 > parity is : none > databits are : 8 > escape is : C-a > local echo is : no > noinit isby bodhi - uBoot
All, What is the behavior of the LEDs when you turn on the box? mine (the whole row) flashing. And I got no output from either serial header. I'm using 3 jumper wires and plugging the male ends into the holes (there is no solder button, just header holes on the board). I'm looping the ethernet cable from one port to the other as Gravelrash suggested. And I could not see whetheby bodhi - Debian
miko Wrote: ------------------------------------------------------- > :( > I have tried about 50 times. Always the same. > "Sending boot message. Please reboot the > target..." Then you should check your serial connection, hardware wise. And check your serial module converter connecting to a different box. And examine the serial header on the Pogo V4. It should work.by bodhi - uBoot
Miko, With the Pogo V4, you will need to keep doing what do did: Control-C to abort kwboot, and recall the command, execute kwboot again. Do this as many times as you can until the handshake occurs. It might take as many as 20 tries.by bodhi - uBoot
Chuck, Do what I asked above (get a serial console log) and we'll go from there: http://forum.doozan.com/read.php?3,29362,29412#msg-29412by bodhi - uBoot
In case anybody wondering, I've built kernel 4.7 without incidence. However it does not not have any thing interesting added, so decided not to release it and wait for 4.8.by bodhi - Debian
> That blparam works for the older kirkwood plugs in > Jeff's script only. For the new one like Zyxel, it > won't. By this I meant blparam is on those Kirkwood plugs (Dockstar, GF Net/Home, Pogo E02) stock OS. But newer ones like the Zyxel don't have it, IIRC.by bodhi - uBoot
Chuck, You need to describe a little bit more. Or just do the following. Boot with kwboot then interrupt serial console and printenv and then go ahead boot the USB rootfs (I assume you have already created the Debian 4.4 rootfs on USB). boot And post the entire log here.by bodhi - uBoot
> > >1. 2. 3. > > That's mostly because in that earlier version of > the script I had not implemented that yet, in the > current script (unreleased) I have already added > the right links. Cool! > >4. > > Thanks for this, I'll add blparam to the function > that tries various ways to get the envs we need. > Jeff had a blparamby bodhi - uBoot
ElMariachi, Everything looks OK!by bodhi - uBoot
Review & Comments 1. Do we need u-boot folder base URL? UBOOT_MTD0_BASE_URL="$MIRROR/u-boot-bodhi-latest" # .platform.mtd0.kwb will be appended to this I have individual URL for each of the u-boot image (see 1st post). I see that your implementation actually uses a base URL for the u-boot folder. We can not track individual box installation statistics if we use a base URL.by bodhi - uBoot
bobafetthotmail, Thanks for all the hard works! just reviewing it took quite a bit of time. I have gone through the 1st code review and have several comments/suggestions in the following post.by bodhi - uBoot
Quote- ------------------------------------------------------------------------- Debian Security Advisory DSA-3626-1 security@debian.org https://www.debian.org/security/ Salvatore Bonaccorso July 24, 2016 https://www.debian.org/security/faq - ------------------------------------------------------------------------- Packageby bodhi - Debian