Mittwoch, 10. September 2025, 00:47 UTC+2

Sie sind nicht angemeldet.

  • Anmelden
  • Registrieren

Edimax 2502 unbrick (dead after rs232 upgrade firmware )

koksik

Anfänger

Beiträge: 3

1

Sonntag, 7. Juni 2015, 12:10

Edimax 2502 unbrick (dead after rs232 upgrade firmware )

Hello. I tried the JP1 back to life EDIMAX-2502 and instead of Y: Upgrade Kernel and upload images_0.74c_Edimax_20100709.bin (X-modem) , is pressed Upgrade Firmware and my NAS does not turn on, that fan spins, the LED will not # Lights. Is the JTAG I can manage to put it.
Sorry in my english

AQUAR

Schüler

Beiträge: 116

Wohnort: Australia

2

Montag, 8. Juni 2015, 13:36

Do you still have access to the redboot bootloader?
If so I think you can try to reflash with the appropriate binaries.
Also maybe try openwrt binaries from the opengemini blog.

Not done this for a long time so my recollection is a bit rusty.

koksik

Anfänger

Beiträge: 3

3

Dienstag, 9. Juni 2015, 18:07

No access to rootboot on rs232 , waiting for jtag programer

AQUAR

Schüler

Beiträge: 116

Wohnort: Australia

4

Mittwoch, 10. Juni 2015, 12:59

The firmware flash option most likely did write bad code in the flash memory address space where redboot resides.
Seems You already know that JTAG flashing is the only way to unbrick the NAS box.
Not done JTAG myself but HWGuru may be able to help if you get into trouble.

Did you save any binaries with the MTD driver before the update disaster?

koksik

Anfänger

Beiträge: 3

5

Freitag, 12. Juni 2015, 18:00

ok . my nas is life ,but ethernet port not working led stats no light or blinking, how to repair

log on rs232

http://pastebin.com/vUX7F5VM

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »koksik« (12. Juni 2015, 18:29)

AQUAR

Schüler

Beiträge: 116

Wohnort: Australia

6

Montag, 15. Juni 2015, 13:57

Maybe first use redboot to flash the MTD partitions with known good kernel and ram binaries.
eg your previous firmware.
Don't have an edimax but are all the entry points for the MTD partitions correct for the edimax firmwares?

Other thought is to compare the log with that found on the open gemini blog.
Seems to me lots of drivers aren't being initialised.

Ähnliche Themen