Trouble unbricking WRT54G v3.1

Discussion in 'Cisco/Linksys Wireless Routers' started by imqqmi, Jun 23, 2007.

  1. imqqmi

    imqqmi LI Guru Member

    Hi folks,

    I have trouble unbricking a WRT54G v3.1.

    Symptoms: No pings anwered at even when pc network card is set at fixed ip and 10MB/half duplex. Blinking led.

    What I've tried and failed so far:
    - resetting 5secs or 30secs
    - Shorting pins 15&16, 5&6 and 16&17 of the flash while plugging the powercord in
    - I've modified a HP RS232<->USB cable to connect to the serial port of the router with success. It dumps the following repeatedly (after the exception it seems to reboot):

    CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
    Build Date: Fri May 27 13:33:52 CST 2005 (root@localhost.localdomain)
    Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
    Initializing Arena
    Initializing Devices.
    No DPN
    rndis0: Broadcom USB RNDIS Network Adapter (P-t-P)
    CPU type 0x29007: 216MHz
    Total memory: 16384 KBytes
    Total memory used by CFE:  0x80300000 - 0x803A2F80 (667520)
    Initialized Data:          0x803391B0 - 0x8033B5A0 (9200)
    BSS Area:                  0x8033B5A0 - 0x8033CF80 (6624)
    Local Heap:                0x8033CF80 - 0x803A0F80 (409600)
    Stack Area:                0x803A0F80 - 0x803A2F80 (8192)
    Text (code) segment:       0x80300000 - 0x803391B0 (233904)
    Boot area (physical):      0x003A3000 - 0x003E3000
    Relocation Factor:         I:00000000 - D:00000000
    Boot version: v3.5
    The boot is CFE
    mac_init(): Find mac [00:14:BF:3C:FD:87] in location 0
    eou_key_init(): Find key pair in location 0
    The eou device id is same
    The eou public key is same
    The eou private key is same
    **Exception 8: EPC=8032535C, Cause=00000008 (TLBMissRd)
                    RA=803116A0, VAddr=00000430
            0  ($00) = 00000000     AT ($01) = 80340000
            v0 ($02) = 00000001     v1 ($03) = 00000000
            a0 ($04) = 00000000     a1 ($05) = 8035E910
            a2 ($06) = 8035D938     a3 ($07) = 8035D93C
            t0 ($08) = 8035E930     t1 ($09) = 00001000
            t2 ($10) = 00043650     t3 ($11) = 00000001
            t4 ($12) = 00000000     t5 ($13) = 00000000
            t6 ($14) = 9FC02278     t7 ($15) = 9FC037F4
            s0 ($16) = 8035E910     s1 ($17) = 8033E0C8
            s2 ($18) = 803A2968     s3 ($19) = 00000003
            s4 ($20) = 8033E2A8     s5 ($21) = 803A2A90
            s6 ($22) = 803A2A98     s7 ($23) = 803A2AA0
            t8 ($24) = 01000000     t9 ($25) = 00000000
            k0 ($26) = 00000006     k1 ($27) = 00000000
            gp ($28) = 803411B0     sp ($29) = 803A28D8
            fp ($30) = 00000000     ra ($31) = 803116A0
    Can anyone tell me what Exception (TLBMissRd) means? I assume it could be a crc error or memory read error. How can I resolve this issue? Would building a jtag cable be a solution or is the board too screwed up?

    I've googled for a while now and can't seem to find an answer.


    TRASTARO LI Guru Member

  3. imqqmi

    imqqmi LI Guru Member


    Thank you for your reply. Unfortunately no answer pinging either.

    I'll try a ping program that can ping a range of ips, see if that brings something up.
  4. imqqmi

    imqqmi LI Guru Member

    I used fping, it could not find anyting other than my pc. I'm fresh out of idea's now, if anyone can point me in the right direction, it would be very much appreciated.
  5. imqqmi

    imqqmi LI Guru Member

    Ok, I've taken the plunge and built a jtag cable. After some stupid errors on my side constructing one, I finally got the jtag working. I've backed up all individual bin files (cfe, nvram and kernel) then erased the nvram which seems to have cured the problem. So the solution to an Exception 8 is to clear the nvram :)

    I guess I'll try putting a third party firmware in now :)

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice