[SOLVED] Cant access STM32 : Could not measure IR len. TDO is constant high

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

  • [SOLVED] Cant access STM32 : Could not measure IR len. TDO is constant high

    Hi,

    I am getting the error message above on J-Link Lite, while trying to access STM32F417 with J-Link SW 5.12g.

    I get proper connection, on the same target but from a different PC that runs version 4.96.


    The J-Link commander gives the following messages:



    SEGGER J-Link Commander U5.12g (Compiled May 27 2816 16:58:24)
    DLL version U5.12g. compiled May 27 2816 16:57:47
    Connecting to J-Link Uia USB...0.K.
    Firmware: J-Link ARM Lite V8 compiled Oct 29 2014 09:03:16
    Hardware uersion: U8.00
    S/N: 228286226
    License(s): CDB
    UTref = 3.254U
    Type "connect" to establish a target connection, ’?’ for help
    -Link)connect E
    Please specify deUice / core. (Default): STM32F417IC
    Type ’?’ for selection dialog
    Device)
    Please specify target interface:
    J) JTQC (Default)
    3) SWD
    TIF>
    Specify position in JTAG chain (IRPre,DRPre) : -1.-1 => fluto-detect
    JTAGConf>
    specify target interface speed [kHz]. (Default): 4000 kHz
    speed
    Device "STM32F417IC" selected.
    Could not measure total IR len. TDO is constant high.
    STM32 (connect): Can not attach to CPU. Trying connect under reset.
    Could not measure total IR len. TDO is constant high.
    Could not measure total IR len. TDO is constant high.
    STM32 (connect): Can not attach to CPU. Trying connect under reset.
    Could not measure total IR len. TDO is constant high.
    Error: STM32: Connecting to CPU Uia connect under reset failed.
    Could not measure total IR len. TDO is constant high.
    STM32 (connect): Can not attach to CPU. Trying connect under reset.
    Could not measure total IR len. TDO is constant high.
    Could not measure total IR len. TDO is constant high.
    [img]c:\avishai\segger_problem.jpg[/img]


    Pleeease help
    Avishai ?(

    The post was edited 1 time, last by avishai_h ().

  • Hi,


    does it work if you select SWD instead of JTAG?


    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,


    could you post screenshots of J-Link Commander of both a working(V4.96) and a non working(V5.12g) session?

    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.
  • SWD uses the same pins as JTAG.......
    If you have JTAG wired you *also have* SWD wired. SWD uses TCK + TMS of JTAG as SWCLK and SWDIO (SWDIO is *not* the same pin as SWO, which is not required for debugging).

    According to your first post, you are using a J-Link LITE. There is no STM32F4 based board shipped with J-Link LITE right now.
    So you do not comply to the license of J-Link LITE:
    segger.com/jlink-lite-arm.html


    Best regards
    Alex
    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.