Bodhi, Wiped flash again and tried with your envs: Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x200000@0(u-boot),-(ubifs)' Marvell>> mtdparts=pxa3xx_nand-0:0x200000@0(u-boot) Marvell>> mtdids=nand0=pxa3xx Kernel log: T1] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x64 [ 4.953966][ T1] nand: Micron MT29F64G08CBABAWP [ 4.959436][ T1by whitepawn - Debian
Bodhi, Before starting to avoid any conflict previous writes i erased nand chip again. I have tried with your mtd envs: Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x200000@0(u-boot),0x20000@0x00180000(u-boot-env),-(ubifs)' Marvell>> mtdparts=pxa3xx_nand-0:0x200000@0(u-boot),0x20000@0x00180000(u-boot-env) Marvell>> mtdids=nand0=pxa3xx Marvell>> pby whitepawn - Debian
Bodhi, QuoteBodhi Looks like there was error in the initializtion so they are read-only. [ 10.037570][ T1] mtd: partition "u-boot" doesn't end on an erase/write block -- force read-only [ 10.048169][ T1] 0x000000180000-0x0000001a0000 : "u-boot-env" [ 10.053714][ T1] mtd: partition "u-boot-env" doesn't start on an erase/write block boundby whitepawn - Debian
Bodhi, Thank you for your fast reply. I have scrubbed then erased whole NAND.After scrubbing, my placebo "bad blocks" are gone.I still have some of them but i assume it is normal in such big NAND.Attached log in attachment. After clearing NAND issues i have set up my envs like below: Marvell>> mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env) Marvelby whitepawn - Debian
Bodhi, I managed to detect 8gb flash with your recommendation: QuoteBodhi whitepawn, Look for ./board/mv_ebu/common/mv_hal/nfc/mvNfc.c I have edited nand_ids.c {"NAND 8GiB 3,3V 16-bit Custom", 0x64, 0, 8192, 0, LP_OPTIONS16}, First it complained about 8 bit config which is LP_OPTIONS then i changed it to LP_OPTIONS16 no more complains from u-boot. And edited mnNfc.c tby whitepawn - Debian
Tme, If you are using isolated power bricks or using plugs without earth (which always connects GND) GND must be connected. If your PC and Nas power brick connects same outlet with earthing you don't need to connect GND because it is connected Via earthing internally so you won't need to connect extra ground. Regards.by whitepawn - Debian
Bodhi, Please see this about serial pinout.TX and RX is enough for console.GND and VCC are not used if AkkJaa uses USB to serial adapter which is self powered by itself in his case. Also board itself has 4 pinheader internally but i havent tested yet. I can upload my own connection photos if you are needed. Regards.by whitepawn - Debian
bodhi Wrote: ------------------------------------------------------- > whitepawn, > > > U-Boot 2011.12 (Sep 16 2020 - 23:34:16) > Marvell > > version: v2011.12 2014_T2.0p1 > > 06/23/2015 ReadyNAS-102 V2.0 > > Cool! > > You should tried this kwboot with the original > NAND before desolder/solder new NAND :) Bodhi, Yes you are right but &qby whitepawn - Debian
All, First i get really pissed off to netgear because they didn't share u-boot source code, since i get mad to netgear i was desoldered 8gb flash and resoldered 128mb and removed SPI flash mod while doing this surgery i realized why i should not download their entire GPL source codes and look each one by one in first place? I couldn't give up easy. I didn't have much hope but aby whitepawn - Debian
I see bodhi, anyway thank you very much for your support.by whitepawn - Debian
Bodhi, I will request uboot GPL source code from netgear but i am not sure they will share it. Thank you for your support. Regards. EDIT: Just found seagate 2 bay nas U-boot GPL for Armada 370: https://www.dropbox.com/s/3pkfcgw4xkjibu8/u-boot.tar.bz2?dl=0 Is this the right one?by whitepawn - Debian
Bodhi, I see, mainline uboot is not an option.Where can i find stock u-boot and their build environment scripts could you share a link? Regards.by whitepawn - Debian
Bodhi, I have tried synology stock u-boot but it didn't work.So i have searched online and found this github page which patches DDR3 ram header stuff. I have patched synology stock u-boot with my original mtd backup payload DDR header and it makes DDR Training successfully. root@whitepawnxeon:/home/jigsaw/Downloads# kwboot -t -B 115200 /dev/ttyUSB0 -b synologyubootmodded.bin -p Senby whitepawn - Debian
Bodhi, Thank you for your suggestions. Since i am impatient guy i have soldered 8Gigabytes of NAND to device and i couldn't find Any u-boot backups for above listed devices which have chance to work with RN102. Has anyone have mtd backups for above devices? Anyway here is the full bootlog after soldering new flash: root@whitepawnxeon:/home/jigsaw/Downloads# kwboot -t -B 115200 /devby whitepawn - Debian
Bodhi, It seems working with my mtd0 backup.Mirabox bootloader is not working in this device.With mirabox bootloader loading recover.bin was painfully slow.It loaded recover.bin in almost 1 hour:)but it is my ignorance because i have never used kwboot and i was thinking "it must take a while like unbuffered JTAG."Also i used my x86 box for kwboot, not rPi because rPi3 built in serial iby whitepawn - Debian
Bodhi, I have tried with another box (x86) with USB2.0, It loaded image in first try.No garbled unreadable text output from console.Here is the output: jigsaw@whitepawnxeon:~/Downloads$ sudo su password for jigsaw: root@whitepawnxeon:/home/jigsaw/Downloads# kwboot -t -B 115200 /dev/ttyUSB0 -b recover.bin -p Sending boot message. Please reboot the target...-^C root@whitepawnxeonby whitepawn - Debian
I soldered micron flash (MT29F32G08CBACA) to my A13 tablet rip-off development PCB to preprogram it with RN102 u-boot but it seems this debian version R18 cannot recognized second flash.Maybe some kind of dtb required for it i don't know.I can only see nand0 on dev folder.So this idea was dead end.But i have photos of second flash soldering process in my dropbox folder (A13 NAND) if someoneby whitepawn - Debian
I use this program with an old machine runs windows xp.(I also use JTAG with parallel port on this machine.) I had problems with later windows versions.Windows version seems a bit user friendly in my opinion.When i bought this device in 2013, seller also give me license with my hardware id. Just took a photo of my programmer and attached to post.CH341A has many variants that you may know.Itby whitepawn - Debian
Hi bodhi, Thank you for instructions. Here is the bootlog: [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 [ 0.000000] CPU: ARMv7 Processor [561f5811] revisionby whitepawn - Debian
Bodhi, It will be a good execise please share DTS with instructions and i will try with both 4mb and 16mb spi flashes. Maybe i can use this device to program SPI flashes:)(joking) Also another question for these tablet pcb boards and NAND flashes i have, i was have a serial connection and i saw u-boot booting android maybe i can write netgear uboot to new NAND (old tablet NAND) with allwinby whitepawn - Debian
bodhi Wrote: ------------------------------------------------------- > whitepawn, > > What is the SPI chip model? Bodhi, It's a spansion FL032PIF this was just on my scrapyard which was removed from Tplink 703N.I have soldered it for testing purposes.This flash is 32 Megabit which is 4 Megabytes only but i have also 128 megabit chip which is in my Tplink MR3020.I can solby whitepawn - Debian
Hi 1000001101000, Thank you for your reply, nice information.I have just found GPIO 48 by the way and updated dropbox folder with my findings. You may be right for unknown pins (49 50 51 52) as now but not for found ones: -GPIO 63 64 65 and 48 are not pulled ground or vcc, they are not wired to anything. -GPIO 32 47 are pulled to vcc via 4.7kohm resistor.They are not wired to anything excepby whitepawn - Debian
Hi all, Trond thank you very much for your tests it is very useful for me. I will try to boot from USB2.0 device with swap on HDD. About SDIO GPIO pins i have found only GPIO 47 which is SD0_CLK but unable to find remaining 5 pins.Maybe Netgear didn't expose pins, the way i may understand this to x-ray this pcb. Any suggestions anyone? Regards.by whitepawn - Debian
Hi Bodhi, You were right about bootloader it can't recognize SPI flash and sf command doesn't work. Before reading your post i have already soldered parts to PCB so its shame about bootloader and me. I have good news also before soldering flash I have tested GPIO numbers of 32,63,64 and 65 below script can enable high or low these pins. From OpenWRT script "static":by whitepawn - Debian
Hi Trond, Thank you very much for testing USB stuff.I assume it is a flash controller (Inside of USB disk) issue because i investigated hardware USB data pins are soldered directly to CPU itself.USB to SATA seems good option too.If you have time please try with USB SSD Drive also.It seems our box is picky about flash drives. I have found a USB which was old 8GB one sandisk branded seems ok foby whitepawn - Debian
Bodhi, I have also tried with Kingston and Toshiba drives which are USB3.0 same result happened so i went to store and bought new Sandisk 16 GB 2.0 flash disk and cloned my existing Sandisk USB3.0 to it. Same results are happened with new Sandisk USB 2.0 also but more late then USB 3.0 Sandisk.(With USB 3.0 Lets say 2 minutes, wtih USB 2.0 15 minutes.Here is dmesg: root@debian:~# dmesg [by whitepawn - Debian
Hi bodhi again, I was able to get log for my orion-ehci problem with my serial cable: Debian GNU/Linux 10 debian ttyS0 debian login: root Password: Last login: Wed Sep 2 16:18:37 PDT 2020 from 192.168.2.134 on pts/1 Linux debian 5.8.5-mvebu-370xp-tld-1 #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020 armv7l The programs included with the Debian GNU/Linux system are free software; theby whitepawn - Debian
bodhi Wrote: ------------------------------------------------------- > whitepawn, > > > I have just booted your fresh kernel 5.8.5 > > release. > > Looks perfect! > > Both BTRFS and Fan control are configured as > loadable module in this kernel. You might try to > load them manually with modprobe to see if they > work well. > > Thenby whitepawn - Debian
Hi Bohdi, I have just booted your fresh kernel 5.8.5 release.It boots fine.Thank you for your great efforts.Respect man. Here is my instructions on existing 4.20 kernel: cd /boot/ ls wget https://www.dropbox.com/s/81g4f67bf2hurzj/linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2 tar -xjf linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2 tar -xf linux-dtb-5.8.5-mvebu-370xp-tld-1.tar dpkg -i linuxby whitepawn - Debian
Thanks bodhi. One more issue:BTRFS seems not included in kernel.I have existing drives with BTRFS with 8TB data on it so i really wanted to use with it. root@debian:~# cat /proc/filesystems nodev sysfs nodev rootfs nodev ramfs nodev bdev nodev proc nodev cpuset nodev cgroup nodev cgroup2 nodev tmpfs nodev devtmpfs nodev debugfs nodev tracefs nodev securityfs nodev sockfs nodby whitepawn - Debian