OMAP L137

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

  • OMAP L137

    Hi I am trying to connect to a OMAP L137 EVM using a JLink Plus and the script
    This is what comander reports

    SEGGER J-Link Commander V6.31h (Compiled Apr 5 2018 16:04:47)
    DLL version V6.31h, compiled Apr 5 2018 16:04:28

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V10 compiled Mar 29 2018 17:45:34
    Hardware version: V10.10
    S/N: xxxxxx
    License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    VTref = 3.354V


    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core. <Default>: ARM9
    Type '?' for selection dialog
    Device>
    Please specify target interface:
    J) JTAG (Default)
    TIF>
    Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    JTAGConf>
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>
    Device "ARM9" selected.


    Connecting to target via JTAG
    TotalIRLen = 6, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x9B7DF02F, IRLen: 06, TI ICEPick
    TotalIRLen = 6, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x9B7DF02F, IRLen: 06, TI ICEPick

    ****** Error: CPU-TAP not found in JTAG chain

    TotalIRLen = 6, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x9B7DF02F, IRLen: 06, TI ICEPick
    TotalIRLen = 6, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x9B7DF02F, IRLen: 06, TI ICEPick

    ****** Error: CPU-TAP not found in JTAG chain

    Cannot connect to target.
    J-Link>

    Any suggestions ?
    Thank you
    developerR

  • Hello,

    Thank you for your inquiry.
    The OMAP-137 device is not supported by J-Link. The OMAP-138 is however.
    If they are similar enough you could try to select OMAP-L138 instead of ARM9 in J-link commander.
    Simply specifying ARM9 will not work for this specific device as special handling is needed.

    Best regards,
    Nino
    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 Nino

    I thought it set
    CPU=ARM926EJS;
    from the script
    ####################################################
    tried

    Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    JTAGConf>
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>
    Device "OMAP-L138" selected.


    Connecting to target via JTAG
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    ****** Error: AM18xx (connect): Cannot find ICE-Pick (IRLen mismatch)

    TotalIRLen = 6, IRPrint = 0x01
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    ****** Error: AM18xx (connect): Cannot identify CPU core. Read JTAG Id 0x07926001, expected 0x00000000
    AM18xx (connect): Cannot find ICE-Pick (IRLen mismatch)
    Cannot connect to target.
    J-Link>
    Thanks for your help

  • Hello,

    what script do you mean?
    There is no script that we provide for the L138 device.
    Simply select the device name and connect should work without any scripts for the L138. If the L137 hardware is similar enough it should also work.

    Best regards,
    Nino
    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.

  • Hello,

    The script that you are referring to is ancient and is no longer compatible with the OMAP-L138 initialization in the current J-Link software.
    We do not recommend using it for OMAP-L138.
    Please understand that we can't offer support for old JLinkScripts that are not provided through the official release channels.
    As there is little market interest for the L137 and our resources are currently booked with more pressing projects we will not be adding support for that device at this point in time.

    However you can use the Script as baseline to implement support on your own. The L137 is a dual Core SoC so the Cores most likely need to be enabled through the ICEPick first.
    For more information consult the target devices manual and TI.

    Best regards,
    Nino
    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.