• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 16 subscribers
  • Views 7942 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Fatal error: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 10) @ Off 0x5. Error while identifying Cortex-M

Lillian Lee
Intellectual 300 points
Other Parts Discussed in Thread: CC2640

Hi,

Today I met a problem when I tried to burn the project into CC2640.

Please help, thanks!

I copied the log info below:

Mon Aug 24, 2015 09:31:26: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.2\arm\config\debugger\TexasInstruments\CC26xx.dmac
Mon Aug 24, 2015 09:31:26: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.2\arm\config\flashloader\TexasInstruments\FlashCC26xx.mac
Mon Aug 24, 2015 09:31:27: JLINK command: ProjectFile = C:\Work\code\MegaHealthSmartBand\Projects\ble\SimpleBLEPeripheral\CC26xx\IAR\Application\CC2640\settings
\CC2640App_FlashROM.jlink, return = 0
Mon Aug 24, 2015 09:31:27: Device "CC2640F128" selected.
Mon Aug 24, 2015 09:31:27: DLL version: V4.98e, compiled May 5 2015 11:00:52
Mon Aug 24, 2015 09:31:27: Firmware: J-Link V9 compiled Apr 21 2015 18:10:40
Mon Aug 24, 2015 09:31:27: JTAG speed is initially set to: 32 kHz
Mon Aug 24, 2015 09:31:27: TotalIRLen = 10, IRPrint = 0x0011
Mon Aug 24, 2015 09:31:27: Found Cortex-M3 r2p1, Little endian.
Mon Aug 24, 2015 09:31:27: FPUnit: 6 code (BP) slots and 2 literal slots
Mon Aug 24, 2015 09:31:27: CoreSight components:
Mon Aug 24, 2015 09:31:27: ROMTbl 0 @ E00FF000
Mon Aug 24, 2015 09:31:27: ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB000 SCS
Mon Aug 24, 2015 09:31:27: ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
Mon Aug 24, 2015 09:31:27: ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
Mon Aug 24, 2015 09:31:27: ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
Mon Aug 24, 2015 09:31:27: ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 003BB923 TPIU-Lite
Mon Aug 24, 2015 09:31:27: SYSRESETREQ has confused core. Trying to reconnect and use VECTRESET.
Mon Aug 24, 2015 09:31:27: Warning: Failed to reset CPU. VECTRESET has confused core.
Mon Aug 24, 2015 09:31:28: Warning: CPU did not halt after reset.
Mon Aug 24, 2015 09:31:28: Warning: CPU could not be halted
Mon Aug 24, 2015 09:31:28: Core is locked-up, trying to disable WDT.
Mon Aug 24, 2015 09:31:28: Warning: CPU did not halt after reset.
Mon Aug 24, 2015 09:31:29: Warning: CPU could not be halted
Mon Aug 24, 2015 09:31:29: Warning: CPU did not halt after reset.
Mon Aug 24, 2015 09:31:29: Warning: CPU could not be halted
Mon Aug 24, 2015 09:31:29: Warning: Could not set S_RESET_ST
Mon Aug 24, 2015 09:31:36: Fatal error: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 10) @ Off 0x5. Error while identifying Cortex-M
device. Wrong AHB ID. Expected 0x04770001, found
0x00000000 Session aborted!
Mon Aug 24, 2015 09:31:36: Unloaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.2\arm\config\flashloader\TexasInstruments\FlashCC26xx.mac

  • 0
    TI__Guru** 105180 points
    Hello,

    This appears to be an issue with JLink. I've seen other similar reports with BLE 2.1. I suggest using a supported XDS programmer as JLink support with CC26xx is limited.

    Best wishes
  • 0 in reply to JXS
    Intellectual 300 points
    Dear JXS,
    Thanks for your reply! :)
    I can download the project to my board for the first time and it can run start from Main(). But later I can't download the project anymore with the error above. If it's an issue with JLink, why does it can work normally for the first time?
    Thanks again.
    Best regards!
    Lillian
    20150824
  • 0 in reply to JXS
    Intellectual 300 points
    Dear JXS,
    I installed ccs6.1 and use XDS programmer to download the project to CC2640. There's still connection error came out:
    Error connecting to the target:
    (Error -151 @ 0x0)
    One of the FTDI driver functions used during
    the connect returned bad status or an error.
    The cause may be one or more of: invalid XDS100 serial number,
    blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
    Use the xds100serial command-line utility in the 'common/uscif'
    folder to verify the XDS100 can be located.
    (Emulation package 5.1.641.0)
    Please help, thanks!
    Lillian
    20150826
  • 0 in reply to Lillian Lee
    Intellectual 300 points
    Is it an issue with XDS tool? The version is XDS100V2.