Ремонт прошивка восстановление ICOM

simkard

Ok understood, on my ICOM this chip/IC has the following references :
H816
0281
> Is it the 24C02 I'm searching for ?
Couldn't find any reference document / datasheet about this one ... neither regarding the pinout.

[Только для зарегистрированных...]

By side of that, I managed to update the SYSTEM and APPLICATION images with latest ones and ICOM did the update steps pretty straightforward (lucky me )
Now I get the following versions :

• Current PACKAGE IMAGE version: 03.23.22
• Current SYSTEM IMAGE version: 01.33.00
• Current APPLICATION IMAGE version: 01.52.00

Anyway, I'm still getting the following in "dmesg" file :

• PCI: Probing PCI hardware
• PCI 0000:00:10.0: IRQ 5 for idsel 16 pin 1
• PCI 0000:00:10.2: IRQ 5 for idsel 16 pin 1
• PCI 0000:00:19.0: IRQ 6 for idsel 25 pin 1
• ...
• NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
• Scanning device for bad blocks
• Bad eraseblock 1 at 0x00020000
• Bad eraseblock 2 at 0x00040000
• Bad eraseblock 3 at 0x00060000
• Bad eraseblock 4 at 0x00080000
• Bad eraseblock 5 at 0x000a0000
• Bad eraseblock 134 at 0x010c0000
• Bad eraseblock 138 at 0x01140000
• Bad eraseblock 157 at 0x013a0000
• Bad eraseblock 175 at 0x015e0000
• Bad eraseblock 218 at 0x01b40000
• Bad eraseblock 438 at 0x036c0000
• Bad eraseblock 523 at 0x04160000
• Bad eraseblock 606 at 0x04bc0000
• Bad eraseblock 1135 at 0x08de0000
• Bad eraseblock 1447 at 0x0b4e0000
• NAND flash size = 256 MB
• Creating 4 MTD partitions on "NAND 256MiB 3,3V 8-bit":
• 0x00000000-0x07c00000 : "app1"
• 0x07c00000-0x0f800000 : "app2"
• 0x0f800000-0x10000000 : "config"
• 0x00000000-0x10000000 : "pe-nand"

Bad eraseblocks seem to be arranged like this :

• "app1" MTD partition : blocks from 1 to 5, 134, 138, 157, 175, 218, 438, 523 and 606
• "config" MTD partition : blocks 1135 and 1447

Anyway, it seems that I'm not getting these lines anymore in DMESG (which might be a good sign ?) :

• yaffs: dev is 32505862 name is "mtdblock6"
• yaffs: passed flags ""
• yaffs: Attempting MTD mount on 31.6, "mtdblock6"
• block 2 is bad
• block 3 is bad
• block 4 is bad
• block 5 is bad
• block 6 is bad
• block 135 is bad
• block 139 is bad
• block 158 is bad
• block 176 is bad
• block 219 is bad
• block 439 is bad
• block 524 is bad
• block 607 is bad
• yaffs: dev is 32505864 name is "mtdblock8"
• yaffs: passed flags ""
• yaffs: Attempting MTD mount on 31.8, "mtdblock8"

You think that the USB restore would solve out those bad eraseblocks ?
Seems strange to me, but at least I can try.
Anyway, I still need to be sure that I need to unsolder EEPROM or not as I managed to get it updated to latest version.

Thanks