I checked the net for some informations about your lacie net space and found only this: uboot for lacie. At this point it seems there is no newer uboot than ~2012 and no support for debian. i saw that the original uboot support booting only from partition 10 and fallback from partition 6, so be careful. see here: QuoteThe LaCie stock U-Boot comes with a huge limitation: at reset, U-Boot reiniby joerg_999 - uBoot
1.) Quotefratzicu Some bumps along the way: > nand write 0 flash.bin 0 DCC write failed, expected end address 0x00100814 got 0x5a For this to work I needed to change the openocd board script wspace.cfg to -work-area-phys 0x10000000 to 0x10000 (I saw it on a blog, don't know the signifficance but it works) This print error is known - you should take this config here: $_TARGETNAME conby joerg_999 - uBoot
No, this test was without encryption. I have to test with encryption (the cpu should have enough power) and also the NFS speed and let you know the results.by joerg_999 - Off-Topic
Hi fratzicu, i dont know the special conditions of your lacie box but it looks like you suceed installing openocd and put the wright parameters. i also dont know whats your exact target, but if you want to flash new uboot for kirkwood devices you have to take the matching one. (in my case it was a Pogo E02) After three times overthinking and checking your plan you should go further.... Fiby joerg_999 - uBoot
i did copy a large videofile (8Gig) via samba in OMV.by joerg_999 - Off-Topic
i bought one last week and tried first with armbian, (works also well, but no display and Petit-boot support) than debian live with Petit Boot and openmediavault. Super fast but like you told above: only USB 2.0 port and the housing of a goflexnet is much more smaller and nicer than this. But with this one you can also use 3,5" Disks and not only 2,5". One point wich is a nice gadgby joerg_999 - Off-Topic
Hi mrmazak i did this repair job in the middle of 2015, but it should work also with new raspbian an aktual openocd. The only thing i didnt try is with newer Pis. The last one was:(B,B+700Mhz, RPI2 900Mhz and RPI3 1200Mhz) with simply standard clock Speed of the Raspis. You shouldnt change anything in discription and workflow - folllow simply straight forward the instructions on page 1 (inkludby joerg_999 - uBoot
rayvt, your wife is right, but i spent the time to learn more about how to handle things like bootloader, envs and repair SBCs and routers with broken uboot. First i started to repair broken Pogos with Buspirate (very old, from 2012 and slow but works also fine) and later i tried to use the common Raspi erverybody have laying around. The result is this thread. But like bodhi noticed, your timby joerg_999 - uBoot
hello rayvt maybe the post1 starttime is old but its not outdated and works until now. first, care about this: the important thing is the status "ARM state > pogo_init > soft_reset_halt # normaly it works without, if it fails, press reset button on Pogo # You normally get this event (the important thing is the status "ARM state"): # target state: haltedby joerg_999 - uBoot
@chessplayer you can do it like i discribed in the "Lede on Pogo E02" but for step4 your choice should be "4b. LEDE-WIF upgrade" afterwards you should do step5, otherwise you cant get access to your envs. (4a is outdated and not longer working - runnig out of memory - with the newer Lede or openwrt) I tested this on Pogo E02 and with the suitable files also on GoflexNet. Aby joerg_999 - Rescue System
@ alonetrio i am on a businesstrip this days, but for the first i would compair the start sequences for both sbc´s like bodhi said: Startsequence Marvell/Sheevaplug (Pogo E02) and Startsequence Marvell/Netgear ms2110 and check the difference. PS: the -work-area-phys 0x10000000 \ is wrong in your config, it should be 0x100000 !!!!by joerg_999 - uBoot
Did you read this Install Procedure?: https://forum.openmediavault.org/index.php/Thread/21234-Install-OMV4-on-Debian-9-Stretch/ erasmus is for debian 8 and arrakis for debian 9. I didnt try arrakis for the moment, but i got running erasmus on debian 8 (Jessie) on the GFN some month ago. I think it was Jessie: Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with kernel 4.11.3by joerg_999 - Debian
radsfaninlv Wrote: ------------------------------------------------------- > I get the following for nand bad: > > > nand bad > > Device 0 bad blocks: > > > > No number at all perfect, you can continue the instructions (it means you have no bad blocks at all) --joerg_999by joerg_999 - Rescue System
bodhi Wrote: ------------------------------------------------------- > joerg, > > Good instruction :) > https://forum.doozan.com/read.php?4,56019,57849#msg-57849 > > I'll add this to the Wiki. If you like to clean > up further (perhaps make it a 2-part post, 1st > part response to dieter (for clarity), 2nd part > has instruction only). > > Pleby joerg_999 - Rescue System
Dieter Wrote: ------------------------------------------------------- > Dear bodhi and Joerg, > > I have no clue, what went wrong so far - but now > it is working, both, Debian & LEDE!! > (after following again the receipe above, was it > the wrong mtd1 entry?) > Thank you so much! > > I am a happy chappy now! :-) > > Regards, Dieter Yes i thiby joerg_999 - Rescue System
QuoteWhat I think you should do is to flash new u-boot envs image in LEDE, and reapply joerg envs setting (also at LEDE shell). You could try to fix them, but to start clean, flashing the correct default envs will be quicker. Quote# With the new u-boot, /etc/fw_env.config should be: # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x200by joerg_999 - Rescue System
Hallo dieter in this part you got an error you forgot to put "setenv" befor see here: DockStar> setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)' DockStar> setenv set_bootargs_lede 'setenv bootargs console=ttyS0,115200 $mtdparts' DockStar> setenv bootcmd_lede 'run set_bootargs_lede; ubi part ubi; ubi read 0x800000 kernel;by joerg_999 - Rescue System
hello dieter, you are right, this are the old envs. maybe i forgot to tell you you have to restart the dockstar once after flashing uboot in nand and interrupt start again reset than you can tftp boot the new envs and fllash them in nand. than do the rest of modification for uboot-envs for your dockstar like in my discription above: setenv ethaddr <ethaddr Userbox> setenv arcNumbby joerg_999 - Rescue System
why not upgrading to the latest uboot + uboot-envs ? (most of your problems will gone..) if you have serial console it is very easy to do that: # on Windows PC download tftp.zip, or use my dropbox downloadlink with all the needed files. (https://tftpd64.codeplex.com/downloads/get/1632548) # on Windows PC make a directory c:/TFTP and put all in there # unpack und start tftp # the kwb filesby joerg_999 - Rescue System
yes dieter i have changed the mtds because you dont need now a second stage bootloader and a seperate definition for the boot-envs so you have the fully nand for pakets in LEDE and never run out of space. I have defined the mtds only for: bootloader + envs starting at 0x0 size 0x100000 LEDE starting at 0x100000 size <till the end of nand> you should only define your mtds like this:by joerg_999 - Rescue System
your Pogo and boot-envs seems to be ok, bot not your USB Stickby joerg_999 - Rescue System
edinger Wrote: ------------------------------------------------------- > ...but the sysupgrade wont work: try over luci a normal sysupgrade like on a router and you will be happy --joerg_999by joerg_999 - Rescue System
Hello Dieter maybe i can help you, i wrote a short how2 for a dualbootsystem with debian on USB stick and LEDE in nand for dockstar: # NOTE you need serial console to do this job! # the most is in german, because i posted it in a german forum # but if necessary i can translate for you -------------------------------------------------------------------------------- # am Windows Rechner tftpby joerg_999 - Rescue System
no, i dont think so, the dtb file seems also correct: 10106 Feb 10 00:14 kirkwood-pogo_e02.dtb curios?!? SOLVED! maybe you was right Bodhi, i created a new filesystem and generate a new uImage / uInitrd with kernel 4.15.2 took the new dts files for Pogo and what can i say: it works. but it was not a wrong dtb file (same size same date....) maybe an other corruption in my filesystem. Thby joerg_999 - Debian
youre right i also own some orange pi one (best price value), some raspis of every generation (also the very new 3B+) let me think.... 2 Odroid C1 2 Odroid XU4H this one and the HC1 i like most at the moment 1 Odroid HC1 1 Cubietruck 3 Cubieboard2 1 BeagleBoneBlack and some old VIA C6 and C7 Igel for the rest i had to go downstairs.... but my first love startet with the Pogos E02 6 yby joerg_999 - Off-Topic
Kirkwoods? 6 x Pogo E02 3 x Goflexnet and tonns of other SBCs...by joerg_999 - Off-Topic
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 seems to be OK.by joerg_999 - Debian
Hello Bodhi like i told you, i always get an memory access error with fw_printenv / fw_setenv command with kernel linux-4.15.2-kirkwood-tld-1. here is the bootlog:U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700) Pogo E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop aby joerg_999 - Debian
Hi Bodhi I always get an memory access error with fw_printenv / fw_setenv command with kernel linux-4.15.2-kirkwood-tld-1-bodhi.tar.bz2 (11 Feb 2018). checked with older kernels and everthing was ok. i did all my checks on a POGO E02.... please can you conform. --joerg_999by joerg_999 - Debian