EmBitz - Bug report

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

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.

STM32C0 bug C0 should be c0

Tue, 08 Oct 2024 05:38:29 +0200

Dear Gerard,

  I found bug in STM32C0 support in eblink scripts in latest deb archive simple casing problem
(all families are lowercase but C0 is specified uppercase in stm32.script and Linux is case
sensitive in files)

Simple change in stm32.script will fix problem:

["M0+", [["l0", [ 0x417, 0x425, 0x447, 0x457 ]],
         ["gx", [ 0x466, 0x456, 0x460, 0x467 ]],
         ["C0", [ 0x443, 0x453 ]]]],

to

["M0+", [["l0", [ 0x417, 0x425, 0x447, 0x457 ]],
         ["gx", [ 0x466, 0x456, 0x460, 0x467 ]],
         ["c0", [ 0x443, 0x453 ]]]],

it is for EBlink version 5.13-[190]

and it works now ! Thanks for Your nice part of software :-)

Best regards,

   Frantisek Burian

STM32L4P5: wrong RAM-Size

Wed, 17 Jul 2024 18:19:38 +0200

file: stm32l4.script

line 99: ram_size = 0x18000 (96k)

but:
STM32L4P/Q5: RAM-Size is 320k
STM32L4R/S5: RAM-Size is 640k

--> debugger can't show upper RAM

ine 99 should be:
if ( deviceId==471 ) ram_size = 0x5000; else ram_size = 0xa000;

Regards

STM32L4P5: Can't access target device [solved]

Tue, 28 May 2024 12:58:34 +0200

solved:

file: stm32l4.script

missing '&' iin line 95 throws error - should be '&&'

great work - regards

F7/F4 flash errors [solved]

Mon, 03 Jan 2022 23:20:56 +0100

I have 2 projects in C++ I'm working actively at this time, and they are for debugging my graphic library.

STM32F746G-DISCO
and
STM32F4DISCOVERY

I'm using the built-in St-link on both of them!
Project can be downloaded without problem with 1.11 and work like a charm..

But with 2.3 and EB-Link 4.5
I get those error (Please note the sector is always at random)
I'm running Windows 10. I Have uninstall Embitz and the EB-Link and have reinstalled them. Problem is persisting.

I also noticed that debugging is slower than it was with 1.11 and EB-link

Thank for any tips!!

2022-01-03 17_05_52-Window.png (Size: 12.84 KB / Downloads: 526)

2022-01-03 17_05_36-Window.png (Size: 11.48 KB / Downloads: 523)

Installer overwrites PATH on Windows [solved]

Mon, 29 Nov 2021 22:03:56 +0100

I have installed EmBitz 2.0 with EBlink on two Windows PCs, and in both cases the EBlink-Path overwrites the system's environment variable PATH instead of appending to it (what I think would be the expected behaviour).

The last time I used the installer downloaded an hour ago.

If I can provide more information to help, just let me know. But as of now I'm unsure about what could be relevant.

eprintemps