Remote debugging on STM32 using JLink doesn't work

[Hermann-Core]

OS: Windows 11 22H2
VSCode version: 1.77.0
CodeLLDB version: 1.9.0
Compiler: tiarmclang (clang)
Debuggee: elf file

I'm trying to use remote debug 2 binaries in an embedded ARM MCU (STM32F303) using JLink GDB server and CodeLLDB. Firstly I'm not able to load 2 debuggee files, It says that it is not possible but even with one executable file I dont know where the LLDB points to. I want it to flash my 2 binaries and debug them at the same debug session. I wonder if it's possible.
I also wonder if its possible to have the disassembly window and the registers view section using this extension

Verbose log

  Console is in 'commands' mode, prefix expressions with '?'.
Executing script: initCommands
Executing script: targetCreateCommands
Current executable set to 'C:\Users\herma\Bureau\Hermann\EBIKE\Codes\Firmware\bin\debug\bootloader.out' (arm).
Executing script: processCreateCommands

<   1> send packet: +

history[1] tid=0xd894 <   1> send packet: +

<  19> send packet: $QStartNoAckMode#b0

<   1> read packet: +

<   6> read packet: $OK#9a

<   1> send packet: +

<  86> send packet: $qSupported:xmlRegisters=i386,arm,mips,arc;multiprocess+;fork-events+;vfork-events+#2e

<  89> read packet: $PacketSize=4000;qXfer:memory-map:read-;QStartNoAckMode+;hwbreak+;qXfer:features:read+#b1

<  26> send packet: $QThreadSuffixSupported#e4

<   6> read packet: $OK#9a

<  27> send packet: $QListThreadsInStopReply#21

<   6> read packet: $OK#9a

<  13> send packet: $qHostInfo#9b

<   4> read packet: $#00

<  10> send packet: $vCont?#49

<   4> read packet: $#00

<  27> send packet: $qVAttachOrWaitSupported#38

<   4> read packet: $#00

<  23> send packet: $QEnableErrorStrings#8c

<   6> read packet: $OK#9a

<  16> send packet: $qProcessInfo#dc

<   4> read packet: $#00

<   6> send packet: $qC#b4

<   4> read packet: $#00

<  16> send packet: $qfThreadInfo#bb

<  13> read packet: $m0000dead#bb

<  16> send packet: $qsThreadInfo#c8

<   5> read packet: $l#6c

<   5> send packet: $?#3f

<   7> read packet: $S05#b8

<  16> send packet: $qProcessInfo#dc

<   4> read packet: $#00

<  41> send packet: $qXfer:features:read:target.xml:0,3fff#b0

<6037> read packet: $l



  arm
  
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
  
  
    
    
    
    
    
    
  
  
    
    
    
    
    
    
    

    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
<  16> send packet: $qfThreadInfo#bb
 <  13> read packet: $m0000dead#bb
 <  16> send packet: $qsThreadInfo#c8
 <   5> read packet: $l#6c
 <  19> send packet: $p0;thread:dead;#56
 <   7> read packet: $E01#a6
 <  16> send packet: $qProcessInfo#dc
 <   4> read packet: $#00
 <  16> send packet: $qProcessInfo#dc
 <   4> read packet: $#00
 <  16> send packet: $qProcessInfo#dc
 <   4> read packet: $#00
 <  12> send packet: $qOffsets#4b
 <   4> read packet: $#00
 <  26> send packet: $qStructuredDataPlugins#02
 <   4> read packet: $#00
 <  13> send packet: $qSymbol::#5b
 <   6> read packet: $OK#9a
 <  16> send packet: $qfThreadInfo#bb
 <  13> read packet: $m0000dead#bb
 <  16> send packet: $qsThreadInfo#c8
 <   5> read packet: $l#6c
 <  16> send packet: $qfThreadInfo#bb
 <  13> read packet: $m0000dead#bb
 <  16> send packet: $qsThreadInfo#c8
 <   5> read packet: $l#6c
 <  18> send packet: $g;thread:dead;#1d
 < 140> read packet: $000000002200000022000000220000000000000000000000000000000000000000000000000000000000000000000000000000004011002003b300082eb5000800000041#4f
 <  29> send packet: $qMemoryRegionInfo:800b52e#da
 <   4> read packet: $#00
 <  16> send packet: $jThreadsInfo#c1
Stop reason: signal SIGTRAP
 <   4> read packet: $#00
Stop reason: signal SIGTRAP
 <   8> send packet: $x0,0#04
 <   4> read packet: $#00
 <  16> send packet: $m800b400,200#b9
 <1028> read packet: $ffe7009801300090ede7bff35f8f02b080bd80b588b00790069105920798c0680390079880680399401a029002980599884212d9ffe70798406803990844019001980699059a00f0fdf8bff35f8f0398059908440799c8601fe0029804900798406803990844019001980699049a00f0e9f805980299401a049007984068019001980699029a1144049a00f0dbf8bff35f8f04980799c860ffe708b080bd80b582b0009000980138b0f1807f03d3ffe70120019019e0009801384ef21401cef2000108604ff0ff300f2100f037f84ef21801cef20001002008604ef21002cef20002072111600190ffe7019802b080bd80b586b005900491039241f28850c2f200000190ffe70198007818b9ffe7fff72effffe7ffe7eff311804ff0200181f31188009005980499039afff7c8fe0290009880f31188029806b080bd82b08df8070000919df9070000280ad4ffe7009800019df907104ef20042cef2000288540be0009800019df8071001f00f014ef61452cef200028854ffe702b0704784b003900398006902900398c068019002980199884209d8ffe7039880680199401a029908440138009005e002990198c04308440090ffe7009804b0704780b582b00020019041f64010c0f20100fff767ffffe741f24061c2f20001002000f001f8f7e780b584b003900291029800f01bf8019003980299019afff77aff04b080bd#e1

arm-ti-none-eabi

Here is what I get from the Source windows. I dont know what it is

[vadimcn]

Here is what I get from the Source windows. I dont know what it is

When codelldb cannot locate debug info for a memory region, it defaults to displaying disassembly.

I would suggest you to first seek tutorials on embedded debugging with LLDB (maybe there's even one for your board?). Once you have the magical incantations figured out, you should be able to switch to codelldb for GUI.

...A while ago I was able to debug an embedded target via OpenOCD. IIRC it required some extra setup, like using image load ... to specify module positions in memory.