[SOLVED] Issues with Tiva TM4C1294NCPDT (ERROR: DAP error while reading AHB-AP IDR)

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Issues with Tiva TM4C1294NCPDT (ERROR: DAP error while reading AHB-AP IDR)

    Hi,
    i have issues flashing and debugging with my Segger j-link edu and mcu board with the Tiva TM4C1294NCPDT (SWD debug interface). All of the follwing is reproducible - i tried with several MCU's. I get the following output from Segger J-Flash:

    Source Code

    1. Application log started
    2. - J-Flash V5.12g (J-Flash compiled May 27 2016 16:58:02)
    3. - JLinkARM.dll V5.12g (DLL compiled May 27 2016 16:57:47)
    4. Reading flash device list [C:\Program Files (x86)\SEGGER\JLink_V512g\ETC\JFlash\Flash.csv] ...
    5. - List of flash devices read successfully (3179 Devices)
    6. Reading MCU device list [C:\Program Files (x86)\SEGGER\JLink_V512g\ETC\JFlash\MCU.csv] ...
    7. - List of MCU devices read successfully (5195 Devices)
    8. Opening project file [C:\Program Files (x86)\SEGGER\JLink_V512\Samples\JFlash\ProjectFiles\TI\TM4C1294NCPDT.jflash] ...
    9. - Project opened successfully
    10. Close project
    11. - Project closed
    12. Opening project file [C:\Program Files (x86)\SEGGER\JLink_V512\Samples\JFlash\ProjectFiles\TI\TM4C1294NCPDT.jflash] ...
    13. - Project opened successfully
    14. Connecting ...
    15. - Connecting via USB to J-Link device 0
    16. - Target interface speed: 4000 kHz (Fixed)
    17. - VTarget = 3.312V
    18. - ERROR: DAP error while reading AHB-AP IDR.
    19. - ERROR: Failed to connect.
    20. Could not establish a connection to target.
    Display All


    i tried several options:
    - using the icdi from the tiva tm4c1294xl launchpad
    - jlink command
    - using the segger jlink with ccs 6.1.1.00022:

    Source Code

    1. CORTEX_M4_0: GEL Output:
    2. Memory Map Initialization Complete
    3. CORTEX_M4_0: Error: Stat [ JLINKARM_IsHalted() call ] failed!
    4. CORTEX_M4_0: Unable to determine target status after 20 attempts

  • Hi Joscha,

    sorry for the delay in response.
    I just gave it a try with a TM4C129X Development Board and could not reproduce you issue.
    Connecting, erasing and programming works fine.

    i tried with several MCU's.

    Did you use several MCUs on the same board or did you test several boards?
    Could you please check the cable / the debug header of your board?
    Is checking the signals with a scope an option for you?

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi, i was able to establish a reliable connection (lesson learned: never trust internal pullups).
    I have some issues with my crystal oscillator now but i am able to connect to my board. The DAP error seems to be caused by the oscillatorsetup too.