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

Ferrum

nein das ist schlecht

simkard

why ???

simkard

Well, I managed to replace all the necessary resistors with the needed values.
So far, so good, I'm seeing 256MB RAM in the WebUI port 60080 > Device Information.
Self-test is ok too.

What am I supposed to do next ?

1. Change Serial Number ?
2. USB restore ?
3. Both with first [1] then [2] ?

Thanks

simkard

I went and read some informations on multiple sites/forums/etc ...

It seems that my next step after restoring 256MB RAM visibility is to modify the serial number from "1120134" to "1801201" in order to convert from device "ICOM A1" to "ICOM A2".

Fact is that I can't find any 24C02 EEPROM on the PCB/motherboard (type "FT_icom next_plus" with no white markings for ICs references).

I'm stuck at that stage, what are the options before attemping firmware upgrade (SYSTEM + APPLICATION images //OR// USB restore) ?

===== EDIT =====
Well seems like I have a ICOM NEXT ... which had the same troubles as an ICOM A2 (resistors, etc ...) but I'm having a hard-time choosing what is the correct firmware update files I'm supposed to drop in.

I have these files :
===== For ICOM NEXT =====

• ICOM_Next-rootfs-012322.tar.gz
• ICOM_Next-app-012322.tar.gz

====================

===== For ICOM A-A2 =====

• ICOM-BootImage-01-33-00.bin
• ICOM-ApplicationImage-01-52-00.bin

====================

From what I can see in the ICOM webUI port 60080 > Update Firmware, the actual versions are these ones :

• Current PACKAGE IMAGE version: 03.15.00
• Current SYSTEM IMAGE version: 01.26.00
• Current APPLICATION IMAGE version: 01.41.00

Can someone please tell me what I am supposed to drop in for the update here ?

TumKos

24C02 You still need to connect the recovery button, otherwise icom will not work

Изображения

IMG_1995.jpg (21.0 Кб, 29 просмотров)

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

TumKos

This will not solve the problem of bad blocks.

simkard

Questions are :

1. Does solving bad blocks is mandatory ?
2. What will be solved doing the USB restore ? (PCI enumeration, bad blocks, etc ...)
3. Is it mandatory to change the SERIAL NUMBER from "1120134" to "1801201" (or anything of a higher value like "1801202", "1801203", etc ...)
4. If modifying the 24C02 EEPROM is mandatory, where is this IC located on my PCB version "SP269-B1" / "SP269-B1S" ? (Ferrum seems to point me to a SMD titled H216 ... seems strange to me as the same chip on PCB version "SP101-B", "SP168-B", "SP168BA" or "SP269" is titled "2402 ... WP"
5. In order to do the USB RESTORE, it seems that onboard button is not enough and there is a need to do a modification ? (what is it / where are the soldering points / etc ... ?)

Thanks

Ferrum

There will be no step-by-step explanations. If you can't do what is written without further instructions, then you don't need to do it

simkard

Or maybe you were talking about other threads like these ?

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