JLink Pro & Codesourcery ARM EABI "Error in final launch sequence"

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

  • JLink Pro & Codesourcery ARM EABI "Error in final launch sequence"

    When attempting to debug a simple "hello" application, on a freescale EVK, the following message is displayed after a few seconds but before loading to function main:

    Problem Occurred->Details:


    Error in final launch sequence
    Failed to execute MI command:
    -target-select remote | arm-none-eabi-sprite -q 'jlink:///173000619' 'imx233evk'
    Error message from debugger back end:
    Remote communication error. Target disconnected.: Invalid argument.
    Remote communication error. Target disconnected.: Invalid argument.

    I started by using JLinkARM_V424 install then installed JLinkARM_V420h that was bundled with Codesourcery and received the exact same results. Are there any configuration files available to attempt running this in generic RDI mode or does something else need to be set for JLink mode?
  • Hi,

    Did you try J-Link commander to verify that general communication with the device is working?
    Due to a hardware / silicon limitation, connecting to the i.MX23-EVK is a little bit tricky,
    since the core needs a reset at the first time J-Link is connecting to it, otherwise the JTAG-DAP does not respond correctly.

    As a first step, could you please try the following?:
    Go to the installation dir of the J-Link software.
    Go to Samples\JLink\Scripts\ and copy iMX23.JLinkScript to the directory where J-Link commander and the DLL are located.
    Rename iMX23.JLinkScript to Default.JLinkScript, start J-Link commander and post the complete output.


    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.
  • Hi Alex,
    I ran the commander with script and received the following:




    DLL version V4.24, compiled Feb 17 2011 16:00:51
    Firmware: J-Link ARM-Pro V3.x compiled Jan 31 2011 18:46:52
    Hardware: V3.00
    S/N: 173000619
    Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
    IP-Addr.: 192.168.0.5 (DHCP)
    VTarget = 3.319V
    Info: iMX23 (ARM926EJ-S core) J-Link script
    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    WARNING: CPU core not found.
    No devices found on JTAG chain. Trying to find device on SWD.

    WARNING: CPU core not found.
    No device found on SWD.
    Did not find any core.
    Info: iMX23 (ARM926EJ-S core) J-Link script
    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    WARNING: CPU core not found.
    No devices found on JTAG chain. Trying to find device on SWD.

    WARNING: CPU core not found.
    No device found on SWD.
    Did not find any core.
    J-Link>



    I also ran the GDB server and had a little more success. Although, this does periodically fail also so I do believe there is a common underlying issue.



    Successful connect:

    J-Link connected
    Firmware: J-Link ARM-Pro V3.x compiled Jan 31 2011 18:46:52
    Hardware: V3.00
    S/N: 173000619
    Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB

    J-Link found 1 JTAG device, Total IRLen = 4
    JTAG ID: 0x079264F3 (ARM9)

    Connected to 127.0.0.1
    Reading all registers
    Read 4 bytes @ address 0x00000000 (Data = 0x7D5A1D0A)
    Downloading 1484 bytes @ address 0x00000000 - Verified OK
    Downloading 100 bytes @ address 0x000005CC - Verified OK
    Downloading 8 bytes @ address 0x00000630 - Verified OK
    Writing register (PC = 0x00000040)
    Read 4 bytes @ address 0x00000040 (Data = 0xEA000046)
    Read 4 bytes @ address 0x00000210 (Data = 0xE3A03000)
    Setting breakpoint @ address 0x00000210, Size = 4, BPHandle = 0x0001
    Starting target CPU...
    ...Breakpoint reached @ address 0x00000210
    Reading all registers
    Removing breakpoint @ address 0x00000210, Size = 4
    Read 4 bytes @ address 0x00000210 (Data = 0xE3A03000)
    Reading 64 bytes @ address 0x00003FC0



    Subsequent unsuccessful connect:

    J-Link connected
    Firmware: J-Link ARM-Pro V3.x compiled Jan 31 2011 18:46:52
    Hardware: V3.00
    S/N: 173000619
    Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
    WARNING: CPU core not found.

    J-Link found 0 JTAG device, Total IRLen = 0
    JTAG ID: 0x00000000 (ARM9)