Request JTAG support for IFC6410 on MedusaBox

[KoryHerzinger]

After seeing that the MedusaBox supported the Qualcomm APQ8064, I purchased one to program the eMMC device on my IFC6410. (I was going to post a link to the InForce product page for this board, but apparently forum rules prevent me from doing so... google "IFC6410" for more info...)

Apparently the MedusaBox software doesn't recognize the CPU on either version of the IFC6410 that I have:

IFC6410 Rev P1 (1.3GHz APQ8064)
Selected device model: Auto
Connecting. Please wait...
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S64 revision C.
Detected TAP ID: 4BA00477, IR Length = 4.
Detected TAP ID: 107160E1, IR Length = 11.
ERROR[010]: Unsupported device CPU. Core ID = 107160E1.

IFC6410 Rev P19 (1.7GHz APQ8064)
Selected device model: Auto
Connecting. Please wait...
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S64 revision C.
Detected TAP ID: 4BA00477, IR Length = 4.
Detected TAP ID: 207100E1, IR Length = 11.
ERROR[010]: Unsupported device CPU. Core ID = 207100E1.

Is it possible to add support for this hardware, or is there a way to convince the software that this device is the APQ8064 (which it is)?

[Octopus box]

Hello.
We have prepared and sent You test Software version. Please try to connect with this Software version and write here the result.

[KoryHerzinger]

Much appreciated! I'm able to connect to these devices, but only intermittently:

• If I don't set the device model to Qualcomm/APQ8064 and just let the software try to auto-detect the device, I get this error:
  
  Selected device model: Auto
  Connecting. Please wait...
  Medusa JTAG Firmware version 1.1.0.
  Medusa JTAG Hardware S64 revision C.
  Detected TAP ID: 4F1F0F0F, IR Length = 4.
  Detected TAP ID: 107160E1, IR Length = 11.
  JTAG speed : Auto (RTCK).
  VREF level : 1.82 V
  CPU : Qualcomm APQ8064
  Core ID : 107160E1
  ERROR[008]: Unknown flash device. Device No:ID = 0:00000000.
  ERROR[035]: Target device has been powered off during connect.
  
• A good deal of the time, I get something similar to this when I try connecting:
  
  Selected device model: Qualcomm APQ8064
  Connecting. Please wait...
  Medusa JTAG Firmware version 1.1.0.
  Medusa JTAG Hardware S64 revision C.
  Detected TAP ID: 4BA00477, IR Length = 4.
  Detected TAP ID: 207100E1, IR Length = 11.
  Medusa JTAG Firmware version 1.1.0.
  Medusa JTAG Hardware S64 revision C.
  JTAG speed : 1000 KHz.
  VREF level : 1.84 V
  CPU : Qualcomm APQ8064
  Core ID : 207100E1
  ERROR[002]: Failed to load Medusa Device Server to target RAM.
  Selected device model: Qualcomm APQ8064
  Connecting. Please wait...
  Medusa JTAG Firmware version 1.1.0.
  Medusa JTAG Hardware S64 revision C.
  MI: Medusa JTAG init failed.
  Selected device model: Qualcomm APQ8064
  Connecting. Please wait...
  Medusa JTAG Firmware version 1.1.0.
  Medusa JTAG Hardware S64 revision C.
  ERROR[030]: TDO is constant high. Please check target device connection.
  MI: Medusa JTAG init failed.
  
• If I'm eventually able to connect, I'll try doing a read or write to the eMMC device, but it never completes the operation and terminate prematurely with a message like this:
  
  Selected device model: Qualcomm APQ8064
  Connecting. Please wait...
  ERROR[034]: RTCK signal does not respond. Defaulting to 1 MHz.
  Medusa JTAG Firmware version 1.1.0.
  Medusa JTAG Hardware S64 revision C.
  Detected TAP ID: 4BA00477, IR Length = 4.
  Detected TAP ID: 207100E1, IR Length = 11.
  Medusa JTAG Firmware version 1.1.0.
  Medusa JTAG Hardware S64 revision C.
  MI: Halting target, attempt 1.
  JTAG speed : 1000 KHz.
  VREF level : 1.84 V
  CPU : Qualcomm APQ8064
  Core ID : 207100E1
  MI: Loading Medusa Device Server V1.2.
  MI: Starting...
  MI: Received status 0x0000F00F, cycle 0.
  MI: Received server capabilities 0x00000191.
  MI: Detailed server caps: FLASH, WDOG, A64, IOCTL
  MI: Watchdog configuration: 0xB800010C, 0x00000001... ok
  MI: Server init.
  MI: Received flash ID 0xE0450001.
  MI: Flash geometry set.
  MI: Recheking settings... ok
  Server caps : 00000191
  Storage Device: ******* eMMC SEM04G
  Device ID : 00450001
  Block size : 512 bytes
  Blocks : 7733248
  Storage size : 3776 Mb
  Connect successful.
  Opening "ifc6410-stock-android" file...
  Writing BOOT section. Please wait...
  MI: Server status 0x0000000D (not STAT_IDLE).
  ERROR[018]: Logical block operation failed at 12144 Kb (Hex address 0x00BDC000). Reason: Synchronization failed.
  Disconnected
  

All of these issues seem to indicate a problem with the JTAG wiring harness, but I've been through 3 different JTAG harnesses... I'm pretty sure our harness is good. Continuity is good and the wiring is correct. I noticed that the orange cable with the RJ45 connector is not shielded... could this pose a problem? I wouldn't think so at 1-10MHz.

Any help or guidance would be much appreciated! Thanks!

[Octopus box]

Try to set lower Jtag speed. Make Jtag wires as short as possible and try again.

[KoryHerzinger]

Thank you for the guidance. A shorter JTAG harness has indeed improved the stability of the connection.