Author Topic: Replacing a flash chip  (Read 1146 times)

Lukapple

  • Full Member
  • ***
  • Posts: 202
Replacing a flash chip
« on: January 25, 2021, 04:56:03 AM »
Hi all!
I’ve a question about flash chips (this time not related to Moteinos).
Few days ago I did the firmware upgrade on my Zyxel firewall (model usg110). After that the firewall didn’t boot anymore, so I attached the cable to the console port to see what’s going on. From the logs I can see that it has problems with mounting the partition (Error: We can't mount /share/AP-image/FW2/wtp_image to /etc/zyxel/ftp/wtp_image partition). Reloading the firmware trough console didn’t help.
My prediction is that the flash is corrupt. I took the device apart and noticed that the flash chip (and flash controller) is soldered to the add-on PCB which can easily be removed (see attached photo).

I don’t have much experiences with the flash chips so my question here is if will it work if I just simply replace the flash chip with the new one (assuming that flash controller is ok) ? or do you need to program it before you attach it?

p.s. The device is out of warranty, so I have nothing to lose :)

Here is the console log:
Code: [Select]
.

U-Boot 2011.03 (Development build, svnversion: u-boot:422M, exec:exported) (Build time: Feb 21 2013 - 13:27:33)




BootModule Version: V1.10 | 02/21/2013 10:45:46

DRAM: Size = 1024 Mbytes



Press any key to enter debug mode within 3 seconds.



Enter Debug Mode


ZW110> atkz -f -l 192.168.2.200




-f -l 192.168.2.200

OK


ZW110>

ZW110> atgof




Booting...


Connect a computer to port 1 and FTP to 192.168.2.200 to upload the new file.



Firmware received ...
Start to check file system...
/dev/sda3: 11/20480 files (0.0% non-contiguous), 6720/81920 blocks
/dev/sda4: 11/23040 files (0.0% non-contiguous), 7044/92160 blocks
Done

Building ...

[Update Filesystem]
.Updating Code
./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|./.-.\.|../.-.\..

.done
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


[Update Kernel]
.Extracting Kernel Image
../

.done
.Writing Kernel Image ... done
.Validate Kernel Image ... done
Restarting system.


U-Boot 2011.03 (Development build, svnversion: u-boot:422M, exec:exported) (Build time: Feb 21 2013 - 13:27:33)




BootModule Version: V1.10 | 02/21/2013 10:45:46

DRAM: Size = 1024 Mbytes



Press any key to enter debug mode within 3 seconds.

.............................................................

Start to check file system...
/dev/sda6: 491/20480 files (0.8% non-contiguous), 36713/81920 blocks
/dev/sda7: 322/23040 files (9.9% non-contiguous), 17772/92160 blocks
Done
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

mount: mount point /etc/zyxel/ftp/wtp_image does not exist
Error: We can't mount /share/AP-image/FW2/wtp_image to /etc/zyxel/ftp/wtp_image partition
Kernel Version: V3.10.87 | 2020-12-01 05:01:44
ZLD  Version: V4.60(AAAA.1) | 2020-12-01 06:10:59
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000


*** NMI Watchdog interrupt on Core 0x01 ***
.$0.0x0000000000000000.at.0x0000000010008ce0
.v0.0xffffffff80e2e018.v1.0x0000000000000001
.a0.0xfffffffffffffffd.a1.0x0000000000000000
.a2.0xffffffff80da0000.a3.0x8000000002376600
.a4.0x8000000002376600.a5.0x8000000000336180
.a6.0x800000000030bec0.a7.0x0000000000000000
.t0.0x0000000010008ce0.t1.0x000000001000001f
.t2.0x000000000000000a.t3.0x80000000003dc000
.s0.0x8000000002376600.s1.0x0000000000000001
.s2.0xffffffff80d93e20.s3.0xffffffff80e0c500
.s4.0xffffffff808746e0.s5.0x0000000000000079
.s6.0x0000000000000000.s7.0x800000004f800000
.t8.0xffffffff814894c0.t9.0xffffffff80876138
.k0.0x0000000000000000.k1.0x0000000000000000
.gp.0x80000000003c0000.sp.0x80000000003c3b40
.s8.0xffffffff80d94f90.ra.0xffffffff8087d5b4
.err_epc.0xffffffff8087d5b8.epc.0xffffffff808746e0
.status.0x0000000010488ce4.cause.0x0000000040808800
.sum0.0x0000000000000000.en0.0x0000000000000000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x02 ***
.$0.0x0000000000000000.at.0x0000000010008ce0
.v0.0xffffffff80e2e018.v1.0x0000000000000001
.a0.0xfffffffffffffffb.a1.0x0000000000000000
.a2.0xffffffff80da0000.a3.0x8000000002380600
.a4.0x8000000002380600.a5.0x8000000000336080
.a6.0x800000000030bea0.a7.0x0000000000000000
.t0.0x0000000010008ce0.t1.0x000000001000001f
.t2.0x000000000000000a.t3.0x800000004f008000
.s0.0x8000000002380600.s1.0x0000000000000001
.s2.0xffffffff80d93e20.s3.0xffffffff80e0c500
.s4.0xffffffff808746e0.s5.0x0000000000000079
.s6.0x0000000000000000.s7.0x800000004f800000
.t8.0x0000000000000000.t9.0xffffffff80876138
.k0.0x0000000000000000.k1.0x0000000000000000
.gp.0x80000000003c8000.sp.0x80000000003cbb40
.s8.0xffffffff80d94f90.ra.0xffffffff8087d5b4
.err_epc.0xffffffff8087d5b8.epc.0xffffffff808746e0
.status.0x0000000010488ce4.cause.0x0000000040808800
.sum0.0x0000000000000000.en0.0x0000000000000000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x03 ***
.$0.0x0000000000000000.at.0x0000000010008ce0
.v0.0xffffffff80e2e018.v1.0x0000000000000001
.a0.0xfffffffffffffff7.a1.0x0000000000000000
.a2.0xffffffff80da0000.a3.0x800000000238a600
.a4.0x800000000238a600.a5.0x800000004f039e80
.a6.0x0000000000000000.a7.0xffffffff80e714d8
.t0.0x0000000010008ce0.t1.0x000000001000001f
.t2.0x000000000000000a.t3.0x80000000003ac000
.s0.0x800000000238a600.s1.0x0000000000000001
.s2.0xffffffff80d93e20.s3.0xffffffff80e0c500
.s4.0xffffffff808746e0.s5.0x0000000000000079
.s6.0x0000000000000000.s7.0x800000004f800000
.t8.0x0000000000000000.t9.0xffffffff80876138
.k0.0x0000000000000000.k1.0x0000000000000000
.gp.0x80000000003d0000.sp.0x80000000003d3b40
.s8.0xffffffff80d94f90.ra.0xffffffff8087d5b4
.err_epc.0xffffffff8087d5b8.epc.0xffffffff808746e0
.status.0x0000000010488ce4.cause.0x0000000040808800
.sum0.0x0000000000000000.en0.0x0000000000000000
*** Chip soft reset soon ***