Help zJTAG doesn't recognize chip id of RTL 8186 based device

This site is best viewed in a modern browser with JavaScript enabled.

Help zJTAG doesn't recognize chip id of RTL 8186 based device

[deleted]

Hi everyone, this is my first post so I'm gonna present myself, I'm Dario, I'm an italian student, and this is the first time in my life I'm trying to use JTAG

I have some electronics knowledge, but it's all theoretical from my university lessons. I've never actually put my hands on a device.
So let's see what's my problem here.
I have a very old D-Link DWL G700AP, it's been in my closet for something like 5 years, and thought "hey what better occasion to learn something new using old bricks?"
This device is based on a RealTek RTL 8186 SoC, finding its datasheet wasn't too much hard, I could trace the JTAG pins and solder a pinout header on the PCB. There's also a JTAG_ENABLE pulled down pin that needs to be set on high, I soldered it against +Vcc (3.3).
After that, I purchased a TUMPA Lite, installed the FTD2XX drivers following the wiki guide, downloaded zJTAG, plugged in the device, plugged in the TUMPA-Lite, and then ran the following command:

C:\zjtag-1.8>zjtag.exe -probeonly /verbose /cable:3
        ==============================================
               zJTAG EJTAG Debrick Utility v1.8 RC3
        ==============================================
cableid=3, cabletype=0
Dev 0:
 Flags=0x2
 Type=0x8
 ID=0x4038a99
 LocId=0x82
 SerialNumber=TITL0615
 Description=USB Multi-Protocol Adapter Lite
 ftHandle=0x0
 Set I/O speed to 30000 KHz
USB TAP device has been initialized. Please confirm VREF signal connected!
Press any key to continue... ONCE target board is powered on!
Detected IR chain length = 0
There are 32 device(s) in the JTAG chain
 IDCODE for device 1 is 0x00000000 (IR length:0)
 IDCODE for device 2 is 0x00000000 (IR length:0)
 IDCODE for device 3 is 0x00000000 (IR length:0)
 IDCODE for device 4 is 0x00000000 (IR length:0)
 IDCODE for device 5 is 0x00000000 (IR length:0)
 IDCODE for device 6 is 0x00000000 (IR length:0)
 IDCODE for device 7 is 0x00000000 (IR length:0)
 IDCODE for device 8 is 0x00000000 (IR length:0)
 IDCODE for device 9 is 0x00000000 (IR length:0)
 IDCODE for device 10 is 0x00000000 (IR length:0)
 IDCODE for device 11 is 0x00000000 (IR length:0)
 IDCODE for device 12 is 0x00000000 (IR length:0)
 IDCODE for device 13 is 0x00000000 (IR length:0)
 IDCODE for device 14 is 0x00000000 (IR length:0)
 IDCODE for device 15 is 0x00000000 (IR length:0)
 IDCODE for device 16 is 0x00000000 (IR length:0)
 IDCODE for device 17 is 0x00000000 (IR length:0)
 IDCODE for device 18 is 0x00000000 (IR length:0)
 IDCODE for device 19 is 0x00000000 (IR length:0)
 IDCODE for device 20 is 0x00000000 (IR length:0)
 IDCODE for device 21 is 0x00000000 (IR length:0)
 IDCODE for device 22 is 0x00000000 (IR length:0)
 IDCODE for device 23 is 0x00000000 (IR length:0)
 IDCODE for device 24 is 0x00000000 (IR length:0)
 IDCODE for device 25 is 0x00000000 (IR length:0)
 IDCODE for device 26 is 0x00000000 (IR length:0)
 IDCODE for device 27 is 0x00000000 (IR length:0)
 IDCODE for device 28 is 0x00000000 (IR length:0)
 IDCODE for device 29 is 0x00000000 (IR length:0)
 IDCODE for device 30 is 0x00000000 (IR length:0)
 IDCODE for device 31 is 0x00000000 (IR length:0)
 IDCODE for device 32 is 0x00000000 (IR length:0)
Probing bus ... Done
CPU Chip ID: 00000000000000000000000000000000 (0x00000000)
*** Unknown or NO CPU Chip ID Detected ***
*** Possible Causes:
    1) Router/Modem is not Connected.
    2) Router/Modem is not Powered On.
    3) Improper JTAG Cable.
    4) Unrecognized CPU Chip ID.
Notice: You are using FT2232H based cable without frequency (clock speed) diviso
r flag.
        Most router's CPU cannot handle highest clock speed, thus you will have
to slow down the clock to make it work.
C:\zjtag-1.8>

I've tried every combination of /L1:X until /L1:11, the response is always the same: CPU Chip ID 0x00000000... then I stopped
Does anybody know how to proceed? I want to smash this thing

I've attached a picture of the two little buddies together

// EDIT
Adjusting the title

[deleted]

OpenOCD team member Paul Fertser has TUMPA and TUMPA-lite test/development units. I think you could use his help.
Could you please try FreeNode IRC server, #openocd channel. irc://chat.freenode.net/openocd
You can Connect now using Freenode webchat, no IRC client needed.
Alternatively you can e-mail him. His e-mail address is fercerpav (at) gmail.com
Please post feedback here if you solve your problem, for other users to benefit.

[deleted]

I successfully contacted Paul Fertser on IRC, in fact he promptly helped me to set up the configuration files for the RTL8186 and flash memory.
Sadly OpenOCD doesn't fully support Lexra cores (as the code needed to fully support it lies on a patch that still isn't merged on the master branch).
As soon as I'll solve my problems I'll post the solution in here!
For now

[deleted]

Thanks for the feedback/update. Looking forward to see your success.
Please Don't forget to keep us posted about developments, as you promised.

rudar wrote: I successfully contacted Paul Fertser on IRC, in fact he promptly helped me to set up the configuration files for the RTL8186 and flash memory.
Sadly OpenOCD doesn't fully support Lexra cores (as the code needed to fully support it lies on a patch that still isn't merged on the master branch).
As soon as I'll solve my problems I'll post the solution in here!
For now

[deleted]

I think my tumpa-lite is broken.
I was dumping memory with OpenOCD and then it stopped working.
I rebooted the pc and restarted OpenOCD, still wouldn't work.
I tried shorting rx/tx serial pins and writing on a terminal, no echo.
Sometimes lsusb doesn't even see it when I plug it in.
It didn't even last a week >

[deleted]

sad to hear that, but I do not represent TIAO.
You should contact them :
http://www.csbooth.com/helpdesk/
I strongly suggest TUMPA v2 instead of Tumpa-Lite. Paul knows why.

TheOne

rudar wrote: I think my tumpa-lite is broken.
I was dumping memory with OpenOCD and then it stopped working.
I rebooted the pc and restarted OpenOCD, still wouldn't work.
I tried shorting rx/tx serial pins and writing on a terminal, no echo.
Sometimes lsusb doesn't even see it when I plug it in.
It didn't even last a week >

sorry to hear that, a replacement was sent to you already.
thanks

rudar

Did someone delete my account? I had to register again

Updates:
I received the new TUMPA-Lite, first thing I noticed that doesn't happen (but happened with the previous one) is that once the device is unplugged from USB the leds immediately turn off (with the previous one leds would stay lit for a few minutes and slowly fade, maybe that was the problem that made it die so quickly).
I took quite some time to run some tests on another device, then finally I was looking back at the D-Link GWL-G700AP (RTL 8186).
But this time while I was soldering JTAG_ENABLE against +Vcc, I pulled a little too hard and the golden ring on the PCB came off -.-
I tried soldering the pins from the SoC but since my tools sucks (very rusted soldering iron, oxidized tin, no flux, no solder wick) I shorted several pins of the chip

This will have to wait until I find some time to buy the proper equipment and fix this soldering madness.
Sorry volkan-k but you'll have to wait a little more for some zJTAG testing >_<

[deleted]

Forum had maintenance, admin reverted backup and some new accounts got lost, nothing personal. You are always welcome here.