Hi, thank you very much. I'll do that as soon as I get home. Right now I'm on vacation. Kind regards.by fratzicu - Debian
And there is also a part of u-boot with some board names in it: zdc@ZDC-PC:~/Desktop$ hexdump -s 0x70200 -C u-boot-1mb.bin 00070660 ff ff ff ff ff ff ff ff ff ff ff ff 5c 18 07 06 |............\...| 00070670 20 17 07 06 0c 16 07 06 5c 14 07 06 f8 12 07 06 | .......\.......| 00070680 8c 15 07 06 dc 13 07 06 30 12 07 06 a4 10 07 06 |........0.......| 00070690 68 11 07 06 70 0b 07 0by fratzicu - Debian
Hi, After Bodhi suggested, I create here a topic having as purpose adding support for Lacie wireless space in openwrt. So here are the basic informations of the device: from https://wikidevi.wi-cat.ru/LaCie LaCie Wireless Space Marvell 88F6281 (Kirkwood) 1x @800MHz 256 128 1 1x Eth. 10/100, 3x Eth. 10/100/1000 switch, 3x USB 2.0 host, 1x Wi-Fi b/g/n from http://lacie-nas.org/dokby fratzicu - Debian
Great! I have all the requested info and I will post the new thread soon. Kind regards.by fratzicu - uBoot
So it seems my u-boot layout is ================================================================================ ## uboot layout (mtd0) ## ================================================================================ offset Block 0 (128K) 0x0 ------------| | Block 1 (128K) 0x20by fratzicu - uBoot
Reading the first MB dumped into the file, I found that the env variables start from 0xa0000 and stop at BFFFF (c0000). There is also an interesting part of the stock u-boot image - it starts from 0x0 and goes to 0x65573 with bytes - then a lot of FF... - then from 0x70200 again some information with board names and other things until 0x73FFF(0x74000) - here I think there are infos aby fratzicu - uBoot
Ok. so I have this stock mtd partitions from stock u-boot console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root) Creating 4 MTD partitions on "nand_mtd": 0x00000000-0x00100000 : "u-boot" 0x00100000-0x00400000 : "uImage" 0x00400000-0x00800000 : "uInitrd_m" 0x00800000-0x08000000 : "root" I opened opeby fratzicu - uBoot
I just want to thank you and tell yoy that i'm a medical doctor, s pulmonologist working in covid and I do that as a hobby to release my stress. Thank youby fratzicu - uBoot
Great, Thank you. I'll test that and then I will try to test some kernel loading. I still didn't master the u-boot commands and scripts. I saved the stock printenv. It has some chains with ifs and elses. I read that the kernel needs some bootqrgs passed by u-boot for console tonput the output on screen. I'll document myself a little nit and then I'll come back. My yoal is mby fratzicu - uBoot
Hi, Thank you for answering and helping me. So I should find the expected location of the env in the source code for u-boot used to compile it, right? If I give the command saveenv then the env variables should be saved at the expected location and the error should be gone. It is trie that when I reflash the compiled 2013 u-boot I erase the whole first 1 Mb (from offser 0x0 with size 0x100000by fratzicu - uBoot
Hi, 1) I tried to flash any u-boot.kwb from bodhi (for example the one for seagate dockstar) but the device doesn not boot. It boots with the compiled u-boot using the lacie-nas wiki (2013 version) designed for wireless space. U-boot tries to load /boot/uImage from USB. This is the output U-Boot 2013.04-00574-gfbf87b182 (Mar 20 2021 - 19:21:55) Wireless Space SoC: Kirkwood 88F6281_A1by fratzicu - uBoot
Hi, I erased the whole flash and then flashed back the entire flash but: 1) at some point there was some mentionof marked bad blocks (I used nand check_bad_blocks 0 and those mentions of bad blocks dissappeared in nand info). But I don't know if I should use nand raw_access 0 enable or not). 2) I wrote the whole flash but didn't use the option oob_softecc_kw (could this be the probby fratzicu - uBoot
joerg_999 Wrote: ------------------------------------------------------- > 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 bodhis uboot for kirkwood > devices you have to take the matching one. (iby fratzicu - uBoot
Hi guys, Now I am ready to explore the porting of u-boot last version to this device called lacie wireless space. SO I compiled the u-boot 2013.04 using instructions from http://lacie-nas.org/doku.php?id=uboot. In this version there is a config for this device that is not maintained in the latest version. I don't know how to bring this config to the last version building of u-boot. Maby fratzicu - uBoot
Hi, So it seems that I mastered the reading / erasing / writing to nand flash of wireless space with openocd. 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 signifficaby fratzicu - uBoot
Hi, So it seems that I mastered the reading / erasing / writing to nand flash of wireless space with openocd. 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 signifficaby fratzicu - uBoot
Hi, Today I think I succeeded to connect to lacie wireless space using jtag port with the standard arm pinout (20 pin). I used the following config files: board: /usr/share/openocd/scripts/board/sheevaplug.cfg in which I modified interface :tumpa.cfg interface: /usr/share/openocd/scripts/interface/tumpa.cfg (source ) in /usr/share/openocd/scripts/board/sheevaplug.cfg target: /usr/share/opeby fratzicu - uBoot
Thank you. I'll do that.by fratzicu - uBoot
Hi, Today I think I succeeded to connect to lacie wireless space using jtag port with the standard arm pinout (20 pin). I used the following config files: board: /usr/share/openocd/scripts/board/sheevaplug.cfg in which I modified interface :tumpa.cfg interface: /usr/share/openocd/scripts/interface/tumpa.cfg (source ) in /usr/share/openocd/scripts/board/sheevaplug.cfg target: /usr/share/opeby fratzicu - uBoot
Hi, CPU is ARM926EJ-S rev 1 (v5l) Flash is NAND FLASH SAMSUNG K9F1G08U0B-PCB0 and it seems to have 128 Mb I found it on http://www.linux-mtd.infradead.org/nand-data/nanddata.html. Vendor 0xec, chip id 0xf1 Ram is hynix h5ps1g83efr s6c 031ak and there are 2 chips of 128 Mb it seems. I have a JTAG TUMPA device https://www.diygadget.com/tiao-usb-multi-protocol-adapter-jtag-spi-i2by fratzicu - uBoot
Lacie wireless space serial, jtag, openwrt Hi, I recently bought a lacie wireless space device just for fun. https://www.lacie.com/de/de/support/netw…wireless-space/ The device is listed in Lacie wiki but does not have its own entry http://lacie-nas.org/doku.php The serial pinout is the same as other lacie devices (pin 1 being the squared one). There is a J2 connector and I think itby fratzicu - uBoot
Hi, I know it has mainline u-boot suport. I even compiled a 2013 image. The latest version of u-boot does not have support for wireless space.bI read somewhere that kwboot and serial debricking might not work with wireless sapce. I can load and flash it but i'm afraid it will be bricked if something goes wrong. I succeeded to connect with openocd through jtag using tumpa device and sheevapby fratzicu - uBoot
Hi, thank you. I don't know if kwvoot would work. Probably yes. But I woild like to be able to flash the existing flash d image in case of any failure. For now, I couldn't find a good, veryfied u-boot partition dump of wireless space device so if it would be bricked with openocd/jtag I could flash it. Kwboot can save the existing u-boot partition?by fratzicu - uBoot
Hi, I am new to this forum but have some history with certain devices and other forums. I started this topic because I received a Lacie wireless space device and woild like to set it up with new u-boot and openwrt. I would need some help with it. First, I compiled a version of u-boot from 2013.07. The config for this device was not kept in the mainline u-boot distribution.I wander if it is pby fratzicu - uBoot