[ferrum]

There is nothing individual in 24c02. It can be read and written by many programmers and you will not be able to destroy the data. I use VVDI PROG but you can use XPROG or another programmer you have. The RESTORE file will fit from 3.15.04 or newer firmware. You can use any soket suitable for this type of case TSSOP

[BMWF750GS]

There is nothing individual in 24c02. It can be read and written by many programmers and you will not be able to destroy the data. I use VVDI PROG but you can use XPROG or another programmer you have. The RESTORE file will fit from 3.15.04 or newer firmware. You can use any soket suitable for this type of case TSSOP

---

Hello Mr. Ferrum! does 24C02 have to be disassembled and programmed or can it be programmed directly on the circuit board with test clips! My ICOM P has 4 red lights because of writing 24C02 on the circuit board!

[ferrum]

Of course, you can't do this internally. Check power supply 3.2v

[Cowboy]

Hello! The process of changing the ICOM serial number has been completed successfully. I must say that desoldering the memory is not an easy operation because everything is tiny and it is easy to blow off other components. Fortunately, everything went without surprises.
I placed the memory for reading and writing on a printed circuit board. The location now appears as ICOM A2 in ICOM configuration manager. Once again, thanks to ferrum for your help.
Regards

[sebadium]

hi guys please help

Builddate 2013-07-16 12:26
mount: mounting /dev/mtdblock/config on /config failed
mount: mounting /dev/mtdblock/config on /config failed
=> Updating boot image 1
=> Updating app image 1
mount: mounting /dev/mtdblock/app1 on /app failed
tar: write error: No space left on device
umount: cannot umount /app: Invalid argument
=> Resetting u-boot parameters
Serialnumber: 1120134
Write mac: 00:01:A9:00:EE:E9
=> Cleaning up /config...
=> Set restore.bin counter...
=> Setting flags
Success (EEPROM)
Success (EEPROM)
Success (EEPROM)
Success (EEPROM)
Success (EEPROM)
Success (EEPROM)
=> Done.
umount: cannot umount /config: Invalid argument
Success (ATMEL)
=> DONE

---

---

hi guy after i try everything, i only can use usb with the restore 17mb but the log show me errors, i already check the r119 and its the correct one i dont know what more i can do, the problem its i can see the ip, received 0

[ferrum]

Your log shows that the program is corrupted. Without a 29GL064 replacement, you won't be able to restore.
It is necessary to replace it with the programmed 29GL064 and clean the K9F2G08 and then do the restoration

[sebadium]

thanks Ferrum for the reply.

can i buy new 29GL064 and replace it?
and about K9F2G08 you mean formatting

[kimz]

I am trying to update ICOM A2 to the latest version.
From the browser level, update of bootimage from 1.28 to 1.29 goes smoothly, but with applicationimage from 1.44 to 1.45 one LED lights up in red and one in green, the update was unsuccessful. Recovery from usb level also didn't work so I decided to replace the Samsung NAND with a new one. After soldering and inserting a pendrive (I tried two different ones, formatted to fat32)
With restore bin, the icom starts with all red LEDs, but when I click 3 times nothing happens, after 10 - 15 seconds the green LEDs turn on and the icom goes to normal operation. On the old nand the effect was the same, the LEDs go red but the update does not start. I tried various restore files from 3-15-04 and 3-15-09 and the same. I also tried to change the serial in 24c02, after this operation, the interface is visible as A2, not A1 as before, but I still have the same problem of updating from the browser, updating from ista or pendrive. Any advice?

[ferrum]

29GL064 must be programmed before replacement.
K9F2G08 You can erase or solder a clean new

The fact that the update fails and the LEDs are lit in different colors during the update indicates a problem with the mega16. The fact that the recovery does not start with the button may have the cause of an error in the button chain up to mega16. Check the resistance on the board indicated in the photo, there were cases when it was absent and caused the button to work poorly.

[kimz]

What a knowledge! Without the second ICOM, I would never have thought of it, thank you.

For me, it was not at all, after soldering the 100k resistor, recovery from USB began immediately. However, after a few tries, I stop at three blinking green LEDs and one red LED. This is log from usb:

Builddate 2014-04-17 16:25
=> Updating boot image 1
=> Updating app image 1

Looks same like update via web, it's stop on app image. After soldering new Samsung same issue. Will I have to replace the new 29GL064?