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
freestyle, Set this in serial console, and boot into Debian setenv console 'console=ttyS0,115200 mtdparts=orion_nand:0x100000@0(uboot),0xff00000@0x100000(root)' Once you are in Debian see if you can list your mtd again correctly. I've made 2 adjustments: to make it RW, and to make mtd0 1MB (previously it was 0.75 MB) Tthen flash u-boot and default env image following theby bodhi - Debian
I've just reattached the script. Please try again.by bodhi - uBoot
ElMariachi, Sorry wrong source file! let me try again.by bodhi - uBoot
Please post output of cat /proc/cmdline cat /proc/mtdby bodhi - Debian
On another Linux box, mount the Debian rootfs that you meant to run on this box and put the attached u-boot script in the /boot folder (if it was mounted at /media/sdb1): cp -a uboot.2016.05-tld-1.environment.scr /media/sdb1/boot/ kwboot this box and interrupt serial console, run the script loading commands: usb start ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scby bodhi - uBoot
ElMariach, > Ok. I stored all partitions of my modded device > and also stored all printenv and fw_printenv > variables into files. Then I bootet another > GoFlexNet device. > There I checked partiton table (all same), checked > for bad blocks (none) and flashed all mtd files > back into the regarding partiton. After this I > checked "mtd_parts", it wasby bodhi - uBoot
freestyle Wrote: ------------------------------------------------------- > Ok, i write this setenv and save env, now i try to > update U-boot > > > root@debian:~# cat /etc/fw_env.config > # MTD device name Device offset Env. size > Flash sector size Number of sectors > /dev/mtd0 0xc0000 0x20000 0x20000 > This is the settings to use witby bodhi - Debian
ElMariachi Wrote: ------------------------------------------------------- > > - fw_printenv is Debian command. printenv is > > u-boot command. They are the same. > > I assumed they where same until I discovered, that > I get very different results when comparing both > using both commands in rescue system. I have > attached both to the last post, could you pleaby bodhi - uBoot
For these mtds. You can just dump the entire partition and save each to a file. nanddump --noecc --omitoob -f mtd0 /dev/mtd0 nanddump --noecc --omitoob -f mtd1 /dev/mtd1 nanddump --noecc --omitoob -f mtd2 /dev/mtd2 nanddump --noecc --omitoob -f mtd3 /dev/mtd3 After dumping, look at the size of each mtd file to verify they are correct. Later to restore do this for each mtd. Use cat /prby bodhi - uBoot
marcogaio Wrote: ------------------------------------------------------- > OK. There's some way to ''save'' the current uboot > environment? In serical console: printenv and copy/paste the output to a text file. > > > > Follow the instruction and create th Debian 4.4 > > rootfs on a single ext3 partition on USB: > > http:/by bodhi - Debian
Tushar Wrote: ------------------------------------------------------- > Hi Bodhi, > > I'm using a pogoplug v4. Now, I want to setup my > system with only one external USB HDD where I like > to keep rootfs on first partition while 2nd > partition should hold my (NAS/SAMBA) files. What > should I do? any suggestion? > > Thanks. Please post this questioby bodhi - uBoot
marcogaio Wrote: ------------------------------------------------------- > First post here, sorry me if i say some dumb > thing. I'm a rather log linux/debian user, but > i've a little experience on ARM, mostly OpenWRT. > > Someone gift me a ix4-200d. The machine was in > decent shape, who land me say that was retired > because ''does not workby bodhi - Debian
ElMariachi Wrote: ------------------------------------------------------- > I don't know if one of the three GFNs I got here > is 'unbrickable', but I got UART and also an old > JTAG lying around. And I'm planning on buying the > bus pirate soon, btw. I think we are ready for > some serious trouble here ;) If you can boot with kwboot (UART) then there iby bodhi - uBoot