EmBitz - All Forums

Flashing main application overwrites bootloader for STM32F413 (solved elf reader bug)

Tue, 23 Jun 2026 13:58:59 +0200

Hello friends!

We recently ported from STM32G473 (natively supported by EmBitz/EBlink) to STM32F413 (not natively supported). So I added CPU ID 0x463 and the new 1.5 MByte memory map to EBlink scripts. Attached .zip files for EBlink version 6.21.

The linker scripts memory map looks like this:

Code:
MEMORY

{

  PAGE0            (rx) : ORIGIN = 0x08000000, LENGTH = 16K                  /* FLASH page 0                                */

  BOOTLOADER_START (rx) : ORIGIN = 0x08000000, LENGTH = 16K - 20              /* Bootloader startup code + interrupt vectors  */

  BOOTLOADER_FW_ID (rx) : ORIGIN = 0x08003FEC, LENGTH = 20                    /* Bootloader firmware identification block    */

  PAGE1            (rx) : ORIGIN = 0x08004000, LENGTH = 16K                  /* FLASH page 1 - Misc parameters              */

  PAGE2            (rx) : ORIGIN = 0x08008000, LENGTH = 16K                  /* FLASH page 2 - Misc parameters              */

  MAINAPP_FLASH    (rx) : ORIGIN = 0x0800C000, LENGTH = 16K + 64K + (10 * 128K) /* Main Application FLASH memory 1360 kByte  */

  BOOTLOADER_FLASH (rx) : ORIGIN = 0x08160000, LENGTH = 128K                  /* Bootloader FLASH memory 16 + 128 kByte      */

  OPT_B            (rw) : ORIGIN = 0x1FFFC000, LENGTH = 16                    /* Options bytes single-bank                    */

  RAM            (rwx) : ORIGIN = 0x20000000, LENGTH = 320K                  /* Main RAM memory                              */

}

I.e. Bootloader lives on pages 0 and 15.
Misc. user data is on pages 1...2.
Main application lives on pages 3...14.

When compiling both Bootloader and Main application, the produced .hex files are correct. When flashing the .hex files with STM32CubeProgrammer, it will write to the expected pages and leave the other untouched. This is working correctly.

When writing Bootloader with EmBitz / Flash / Flash target, everything goes fine.
But when writing Main application, also page 0, 1, and 2 are overwritten. When looking more closely at those 3 overwritten pages, they seems to contain the raw content of the main application .elf file. For example the ".ELF" signature is stored at address 0x08000000. Attached picture of the beginning of 0x08000000.

This happens for both EmBitz 2.63 and 2.65 that I have been using.

Any help appreciated!

Here is the EBlink output when writing Bootloader:

EBlink version 6.21-[299] by Gerard Zagema

Interface USB# : 54FF6A066684565547522187
Interface type : STlink/V2
Target voltage : 3.24V
Interface speed: 4000KHz

Target detected: Cortex-M4 (r0p1) with FPv4_SP
HW breakpoints : 6
HW watchpoints : 4
Fault unwind : Active (level 2)
STmicro family : STM32F413
Detected FLASH : 1536KB
Configured RAM : 320KB
Reset: system
Checking current flash content
Reset: system
Flashing sector 0, address: 0x08000000, length: 0x4000
Flashing sector 15, address: 0x08160000, length: 0x1710C
Flash verify
Flasher starts target
Reset: system

Here is the EBlink output when writing main application:

EBlink version 6.21-[299] by Gerard Zagema

Interface USB# : 54FF6A066684565547522187
Interface type : STlink/V2
Target voltage : 3.24V
Interface speed: 4000KHz

Target detected: Cortex-M4 (r0p1) with FPv4_SP
HW breakpoints : 6
HW watchpoints : 4
Fault unwind : Active (level 2)
STmicro family : STM32F413
Detected FLASH : 1536KB
Configured RAM : 320KB
Reset: system
Checking current flash content
Reset: system
Flashing sector 0, address: 0x08000000, length: 0x4000
Flashing sector 1, address: 0x08004000, length: 0x4000
Flashing sector 2, address: 0x08008000, length: 0x4000
Flashing sector 3, address: 0x0800C000, length: 0x4000
Flashing sector 4, address: 0x08010000, length: 0x10000
Flashing sector 5, address: 0x08020000, length: 0x20000
Flashing sector 6, address: 0x08040000, length: 0x20000
Flashing sector 7, address: 0x08060000, length: 0x20000
Flashing sector 8, address: 0x08080000, length: 0x20000
Flashing sector 9, address: 0x080A0000, length: 0x3090
Flash verify

STM32F413_EBlink_6.21_scripts.zip (Size: 3.82 KB / Downloads: 3)

after_application_flashing.png (Size: 59.41 KB / Downloads: 27)

Linux Ubuntu 24.04/Mint 22.1 Instalation Problem (solved > 6.21)

Thu, 11 Jun 2026 16:30:08 +0200

Hello everyone!

I trying to install EBlink on a machine running Linux Mint 22.1 and the dpkg return some errors. Tested on Ubuntu 24.04 and return the same errors.

Despite the error, Eblink appears to be installed correct and works correctly. After installation, we might encounter some problems trying to use the debugging tools because the udev rules were not installed. I didn't have any problems because I already had the udev rules installed for stlink. I found a workaround to remove the error after a reinstallation by tricking the installer into running the command "touch /usr/share/eblink/80-eblink.rules". After that the reinstallation runs without errors.

svd files for core specific registers

Mon, 16 Feb 2026 18:21:26 +0100

I recently used STM32 CubeIDE. While this is annoying slow when using embitz before, i found one thing that i did not encounter before. There are system register definitions beyond the STM32 specific SFRs, that affect the ARM core itself, like SCB, which e.g. contains a register holding the last address when a crash occured. In the normal MCU .vcd files, these ARM specific registers seem to be missing. How to show these registers in embitz?

Best regards
Michael

How multi core - Newb questions

Tue, 25 Nov 2025 16:44:15 +0100

I have managed to create new project from scratch for stm32h7, got both of them working. Now i want to setup simultaneous debugging for both cores. Please guide me in setting up the CM4 project to debug and how to do simultaneous debugging?

Installation without admin rights

Tue, 14 Oct 2025 11:49:24 +0200

Hello,
Is it possible to have an installation process without admin rights on Windows ?
Thank you for your great job !
Stéphane

EBlink squirrel error on stm32f3 - The index 'ntrfApi' does not exist

Mon, 13 Oct 2025 15:49:48 +0200

Hello,
I try to programm an Evaluation board with a STM32F303VE and an integrated STLink V2:
https://www.st.com/en/evaluation-tools/s...umentation

When I click on the debugger button under Embitz, I have the following error:
Squirrel Error
The index 'ntrfApi' does not exist
stm32_device[65] in 'stmicro/stm32f3.script'

Even if I try debugging in Power Shell to launch the EBLink alone with this command :
.\eblink.exe -v 7 -I stlink -S stm32 -G

The same error appears:
EBlink version 6.02-[201] by Gerard Zagema

Using EB_SCRIPT_PATH = C:\Program Files (x86)\EmBitz\EBlink\scripts

Interface : STlink
Interface USB# : 36FF71063447313049172557
Interface at 1:40 - :
Interface type : STlink/V2
STlink Frmware : V2.J46.S0
Target voltage : 3.21V
Interface speed: 4000KHz
Try DAP_AP 0.
Read CPU id on DAP_AP 0
CPU id found (0x410FC241)
Target selected: Cortex-M

Target detected: Cortex-M4 (r0p1) with FPv4_SP
HW breakpoints : 6
HW watchpoints : 4
Fault unwind : Active (level 2)
Search script stm32.script in path: C:\Program Files (x86)\EmBitz\EBlink\scripts
Script found: stm32.script
Squirrel debug main©[17] {stm32.script}
Squirrel debug main®[167] {stm32.script}
Squirrel debug ebMain©[62] {stm32.script}
Squirrel debug findDevice©[90] {stm32.script}
STmicro device : 0x446
Search script stmicro/stm32f3.script in path: C:\Program Files (x86)\EmBitz\EBlink\scripts
Script found: stmicro/stm32f3.script
Squirrel debug main©[15] {stmicro/stm32f3.script}
Squirrel debug main®[104] {stmicro/stm32f3.script}
Squirrel debug stm32_device©[56] {stmicro/stm32f3.script}
Squirrel debug stm32_device(e)[65] {stmicro/stm32f3.script}
Squirrel debug stm32_device®[65] {stmicro/stm32f3.script}
Squirrel debug findDevice®[113] {stm32.script}
Catch{..} at ebMain[68] in "stm32.script"

Squirrel Error
The index 'ntrfApi' does not exist
stm32_device[65] in 'stmicro/stm32f3.script'
Squirrel debug ebMain®[69] {stm32.script}

What can I do to correct this error ?

Thank you,

Stéphane

undefined __errno build problem

Thu, 05 Jun 2025 15:18:44 +0200

Hi,
When i try to build my stm32 project, i get the error below:

"In function `sqrtf': wf_sqrt.c.text.sqrtf+0x80): undefined reference to `__errno' "

How can i fix this error?

How to debug EBlink scripts

Fri, 16 May 2025 07:04:49 +0200

EBlink version 6.00 and beyond, does support Squirrel script debugging and tracing.

To use the script debugger, place EBlink in verbose level 7 (debug info) for function level debugging or level 8 (trace info) for line level debugging.
For verbose levels below 7, debugging is turned off and script breakpoints are ignored.

Invocation:
Debug level e.g. ./eblink -v7 -G
Trace level e.g. ./eblink -v8 -G

Example of breakpoint in script:

Code:
    foreach(arch in STMICRO)

      if(arch[0] == targetApi.getCpuName()){

          foreach(addr in arch[1]) {

              try{ 

                   devReg = intrfApi.read(addr)

                   brkPt()                <----------- Breakpoint

                   if(devReg) break

              }

              catch(e){}

          }

If the program is halted, all the local variables are printed and the user get the option to: Single-step, step-out, until exception or step to the end of current function
If the execution is main this means that the script file itself (no functions) is handled.

Example output debug level ( cli switch -v7 )

Quote:Search script auto.script in path: f:\software\EBlink\scripts
Script found: auto.script
Squirrel debug main©[9] {auto.script}
Squirrel debug main®[42] {auto.script}
Squirrel debug ebMain©[22] {auto.script}
Search script atmel.script in path: f:\software\EBlink\scripts
Script found: atmel.script
Squirrel debug main©[13] {atmel.script}
Squirrel debug main®[154] {atmel.script}
Squirrel debug findDevice©[59] {atmel.script}
Squirrel debug findDevice(e)[105] {atmel.script}
Squirrel debug findDevice®[105] {atmel.script}
Search script stm32.script in path: f:\software\EBlink\scripts
Script found: stm32.script
Squirrel debug main©[17] {stm32.script}
Squirrel debug main®[167] {stm32.script}
Squirrel debug findDevice©[90] {stm32.script}
STmicro device : 0x413
Search script stmicro/stm32f4.script in path: f:\software\EBlink\scripts
Script found: stmicro/stm32f4.script
Squirrel debug main©[8] {stmicro/stm32f4.script}
Squirrel debug main®[166] {stmicro/stm32f4.script}
Squirrel debug stm32_device©[111] {stmicro/stm32f4.script}
STmicro family : STM32F4x5/4x7
Detected FLASH : 1024KB
Configured RAM : 192KB
Search script stmicro/flash/f7_f4_f2.script in path: f:\software\EBlink\scripts
Script found: stmicro/flash/f7_f4_f2.script
Squirrel debug main©[10] {stmicro/flash/f7_f4_f2.script}
Squirrel debug main®[350] {stmicro/flash/f7_f4_f2.script}
Squirrel debug stm32_device®[166] {stmicro/stm32f4.script}
Squirrel debug findDevice®[114] {stm32.script}
Squirrel debug ebMain®[27] {auto.script}

Quote:Required script load: atmel.script
Search script atmel.script in path: f:\software\EBlink\scripts
Script found: atmel.script
Squirrel trace main©[13] {atmel.script}
Squirrel trace main(l)[13] {atmel.script}
Squirrel trace main(l)[14] {atmel.script}
Squirrel trace main(l)[15] {atmel.script}
Squirrel trace main(l)[17] {atmel.script}
Squirrel trace main(l)[20] {atmel.script}
Squirrel trace main(l)[21] {atmel.script}
Squirrel trace main(l)[22] {atmel.script}
Squirrel trace main(l)[24] {atmel.script}
Squirrel trace main(l)[30] {atmel.script}
Squirrel trace main(l)[58] {atmel.script}
Squirrel trace main(l)[119] {atmel.script}
Squirrel trace main(l)[154] {atmel.script}
Squirrel trace main®[154] {atmel.script}
Squirrel trace ebMain(l)[26] {auto.script}
Squirrel trace findDevice©[61] {atmel.script}
Squirrel trace findDevice(l)[61] {atmel.script}
Squirrel trace findDevice(l)[66] {atmel.script}
Squirrel trace findDevice(l)[105] {atmel.script}
Squirrel trace findDevice(e)[105] {atmel.script}
Squirrel trace findDevice®[105] {atmel.script}
Squirrel trace ebMain(l)[31] {auto.script}
Squirrel trace ebMain(l)[34] {auto.script}
Squirrel trace ebMain(l)[24] {auto.script}
Squirrel trace ebMain(l)[25] {auto.script}

Quote:Squirrel trace findDevice(l)[99] {stm32.script}
Squirrel trace findDevice(l)[99] {stm32.script}
Squirrel trace findDevice(l)[100] {stm32.script}
Squirrel trace findDevice(l)[101] {stm32.script}
Squirrel trace findDevice(l)[104] {stm32.script}

== BREAKPOINT ==
*FUNCTION [findDevice()] stm32.script line [104] <-- Call stack
*FUNCTION [ebMain()] auto.script line [26] <-- Call stack
-LOCALS: <-- start local variable(s) list
[arch] ARRAY
[@INDEX@] INTEGER( 3 )
[devReg] INTEGER( 268526611 )
[this] TABLE
[vendor] "stm32.script"
[@INDEX@] INTEGER( 1 )
[this] TABLE
Go, next Call, Return, Exception or Line? [g,c,r,e,l] <-- Command line input

Command line input:
g = continue (go)
c = run to next call of a function
r = run to the return of current function
e = run until exception trap
l = next script line

Mousing Live View?

Fri, 16 May 2025 00:42:37 +0200

Have forgot how to turn on "live view" when mousing over changing variables , how was this done?
Example:
MG6acc1+= MG6fc1; // 32bit up counter
MG6buff1= MG6acc1>>16; //16 top MSB up count stored in MG6buff1

I can see MG6acc1 counter values flying by but nothing in MG6buff1 when mousing over.

STM32F756BGT6 - No valid STmicro device ID found

Thu, 08 May 2025 20:44:59 +0200

The MCU is correctly detected via the ST-Link utility:

Code:
29:20 : ST-LINK SN : *

29:20 : V2J37S7

29:20 : Connected via SWD.

29:20 : SWD Frequency = 4,0 MHz.

29:20 : Connection mode : Connect Under Reset.

29:20 : Debug in Low Power mode enabled.

29:20 : Device ID:0x449 

29:20 : Device flash Size : 1MBytes

29:20 : Device family :STM32F74x/F75x

However, in EmBitz 2.64 using EBlink 6.02-[198], the following issue occurs:

Code:
EBlink version 6.02-[198] by Gerard Zagema

Interface USB# : *

Interface type : STlink/V2

Target voltage : 3.21V

Interface speed: 4000KHz

Target detected: Cortex-M7 (r0p1) with FPv5_SP

HW breakpoints : 8

HW watchpoints : 4

Fault unwind   : Active (level 2)

ERROR: No valid STmicro device ID found

I resolved the issue by editing the stm32.script file. Specifically, I replaced:
["M7", [0x5C001000],
with
["M7", [0xE0042000],

After this change, device detection in EmBitz started working correctly.

EBlink : can't load device-script : stm32auto.script

Tue, 18 Feb 2025 17:16:30 +0100

Hi,
Have installed EMBITZ 2.63(29) and EBLINK 5.30. For test I defined a small program for stm32f407VG disco using the project wizard. I included use of EBMonitor and ebmon.c and .h were added to the project. In the generated main.c  source I added for test of ebmonitor a printf("\f I am alive \n");
As expected the build was ok. However running Debug gives the the message :   "can't load device-script : stm32auto.script".
I've checked the 3 environment vars in windows 11 for EBlink. They are:
EB_SCRIPT_PATH C:\Program Files (x86) \EBLINK\scripts (here it actually resides)
EB_SCRIPT_ PROBE stlink
EB_SCRIPT_SCRIPT auto
which seems allright to me.
I am using STlink   V4.5

I have no clue were goes wrong, Would appreciate your advice.

Cop

collect2.exe: fatal error: CreateProcess: No such file or directory

Fri, 31 Jan 2025 15:58:47 +0100

Hi,

I have a project with a huge amount of files. When adding further files to the project compilation is successful but during linker phase I have this error:
"collect2.exe: fatal error: CreateProcess: No such file or directory"

On Windows the maximum length of the string (including all arguments) passed to CreateProcess() is 32768 characters and it looks like the final linker command exceeds that limit.
A suggested workaround would be to pass the inputs to the linker via a file.

Is there a similar or other workaround to this problem in Embitz?

Thank you!
Operton

Stm32F0 series debug problem

Wed, 15 Jan 2025 17:32:33 +0100

Hi,
While debugging an STM32F0 series processor with swd debug, when I place a breakpoint on any line and debug that line, the system resets itself. This does not happen with the STM32F1 series. Why?

Stm32L4: No reset exception catch after wakeup

Sun, 12 Jan 2025 19:34:34 +0100

Hello,
I have a battery powered project and want to test it with connected debugger.
The system goes to state "shutdown" and exits it by RTC every15s.
Exit means: "A power-on reset occurs when exiting from Shutdown mode."

Here my issue is, that EB halts after exit of shutdown at the reset vector and I need to press "F5" to continue.
I tried several debugger settings, like "don't stop at valid source info", "don't reset", "don't load app" and "don't run to main".
But no effect. It always halts.

What can I do ?
Is it possible to "hot plug" ?

EFM32GG

Fri, 03 Jan 2025 06:53:19 +0100

Error creating a new program for programming microcontroller type EFM32GG

  embitz3.png (Size: 26.6 KB / Downloads: 7)

  embitz5.png (Size: 17.28 KB / Downloads: 7)

  embitz4.png (Size: 5.29 KB / Downloads: 7)