bodhi, it is working! U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 Thx man! You are the best!by Pentim - uBoot
bodhi, so far so good: Step 6. Erasing 128 Kibyte @ 60000 -- 100 % complete Step 7. Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x60000 what to do as next?by Pentim - uBoot
bodhi, can I restart the device after points 6 and 7? Or it will break something?by Pentim - uBoot
Hi bodhi, here you are: Step 1. cat /etc/fw_env.config # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundand # environment sector is assumed present. # Notice, that the "Number of sectors" is ignored on NOR. # MTD device name Device offset Env. size Flash sector size Number of sectors # Nby Pentim - uBoot
Hi bodhi, so I was able to boot with UART U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized on egiga0 What is tby Pentim - uBoot
Hi everyone, first of all thx for all your work, you are doing a great job! I'm trying to install uboot on my zyxel NSA320 device, but during the check for the bad blocks I'm getting this message: Scanning device for bad blocks Bad eraseblock 4 at 0x000000080000 Could you please advice me, what I have to do now?by Pentim - uBoot