cancel
Showing results for 
Search instead for 
Did you mean: 

"Error in final launch sequence" with Cube IDE 2.0.0 and J-Link Plus

IB_AH
Visitor

Hello,

i have project with a'n STM32H743II on a custom board. I use a J-Link Plus to debug and download the program, everthing was working fine. When i updated to version 2.0.0  downloading the program elf file failed. After initialization sequence and downloading the first block the debugger stops, because it can't load the elf file, but the file exists and the path is correct. 

Message window:

IB_AH_0-1769511875037.png

Debugger console output:

 

SEGGER J-Link GDB Server V8.80 Command Line Version

 

JLinkARM.dll V8.80 (DLL compiled Oct 22 2025 11:56:02)

 

Command line: -port 2331 -s -device STM32H743II -endian little -speed 4000 -if swd -vd

-----GDB Server start settings-----

GDBInit file: none

GDB Server Listening port: 2331

SWO raw output listening port: 2332

Terminal I/O port: 2333

Accept remote connection: localhost only

Generate logfile: off

Verify download: on

Init regs on start: off

Silent mode: off

Single run mode: on

Target connection timeout: 0 ms

------J-Link related settings------

J-Link Host interface: USB

J-Link script: none

J-Link settings file: none

------Target related settings------

Target device: STM32H743II

Target device parameters: none

Target interface: SWD

Target interface speed: 4000kHz

Target endian: little

 

Connecting to J-Link...

J-Link is connected.

Firmware: J-Link V13 compiled Dec 18 2025 15:14:00

Hardware: V13.00

S/N: 53002221

Feature(s): GDB

Checking target voltage...

Target voltage: 3.30 V

Listening on TCP/IP port 2331

Connecting to target...

Connected to target

Waiting for GDB connection...Connected to 127.0.0.1

GDB client (conn. 852) requested target.xml from GDB Server

Reading common registers:

Read register 'r0' (4 bytes) from hardware: 0x240035A4

Read register 'r1' (4 bytes) from hardware: 0x00000000

Read register 'r2' (4 bytes) from hardware: 0x681D678C

Read register 'r3' (4 bytes) from hardware: 0xAA535E0F

Read register 'r4' (4 bytes) from hardware: 0x00000000

Read register 'r5' (4 bytes) from hardware: 0x00000000

Read register 'r6' (4 bytes) from hardware: 0x00000000

Read register 'r7' (4 bytes) from hardware: 0x2001FFB0

Read register 'r8' (4 bytes) from hardware: 0x00000000

Read register 'r9' (4 bytes) from hardware: 0x00000000

Read register 'r10' (4 bytes) from hardware: 0x00000000

Read register 'r11' (4 bytes) from hardware: 0x00000000

Read register 'r12' (4 bytes) from hardware: 0x00000000

Read register 'sp' (4 bytes) from hardware: 0x2001FFB0

Read register 'lr' (4 bytes) from hardware: 0x0800D01F

Read register 'pc' (4 bytes) from hardware: 0x08011684

Read register 'xpsr' (4 bytes) from hardware: 0x01000003

Read 4 bytes @ address 0x08011684 (Data = 0x61BB681B)

Reading register 'msp' = 0x2001FFB0

Reading register 'psp' = 0x00000000

Reading 64 bytes @ address 0x2001FFC0

WARNING: Failed to read memory @ address 0xE0BBF6C6

Reading 64 bytes @ address 0x2001FF80

Received monitor command: ReadAPEx 0x0 0xF8

O.K.:0xE00FE003

Received monitor command: ReadMemAP 0x0 0xE00FEFD0 0x8 0x0

O.K.:0x00000000,0x00000000,0x00000000,0x00000000,0x00000050,0x00000004,0x0000000A,0x00000000

Received monitor command: reset

Resetting target

Downloading 664 bytes @ address 0x08000000 - Verified OK

GDB closed TCP/IP connection (Socket 852)

Restoring target state and closing J-Link connection...

Shutting down...

 

I have installed the older versions 1.16 and 1.19 in parallel and here is everything ok.

Then i checked the elf file with the CubeProgrammer:

IB_AH_1-1769513175258.png

I have the same error message when the program is compiled with older CubeIDE versions. At the moment i can't find any errors in the linker script.

This is the output of the 'elf viewer":

IB_AH_2-1769513639886.png

Any clarification or recommendation would be appreciated.

Thank you.

 

0 REPLIES 0