EmBitz - Using EBlink

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

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" ?

EBlink Live variables with other IDE

Fri, 22 Mar 2024 15:49:23 +0100

Hi,
I think live variables are one of the biggest advantages of EBlink, and it works great with EmBitz.
But i am trying to integrate it into my workflow, and got really stuck using live variables without EmBitz.
Is there any information on how to use live variables with eblink?

I guess a real documentation on this does not exist, but i think even only looking at the parts of the
sourcecode where embitz does the live variables configuration and polling would help me greatly.

Thanks in advance!

debug problem

Sat, 16 Mar 2024 10:16:43 +0100

Hi,
When i put a breakpoint in while routine, embitz ide doesn't show runing row. how can i solve this ?

STLink Update

Fri, 08 Mar 2024 19:40:50 +0100

A piece of advice to all enthusiasts.

When you work on a Discovery board or a Nucleo..

Always update your board with ST-Link Utility to the latest version.

I got fooled again with a board with which EB-Link crashed every 2 minutes. After the update, no problem.

Enjoy Embitz!!!!

EBLink error: no interface found

Wed, 21 Feb 2024 19:46:21 +0100

Hi, I am a complete newbie. I have just loaded EmBitz 2.62 and EBlink 5.12 on Win 11 pro.

I have an ST Nucleo board ( STM32F303 ) connected to my PC. This board has a built in ST-Link.

I can compile a simple test program, but when I try to Flash Target, I get a 'No interface found' error.

I would much appreciate being pointed in the right direction as to what steps I have missed in the
installation or what I have not configured correctly.

Thanks!

STM32L5/U5 Flash option restore

Wed, 03 Jan 2024 13:24:47 +0100

The STM32L5 and U5 devices have been added to the EBlink scripts. The scripts support both single- and dual-bank mode.

The ability to switch from bank mode to the EBlink command line has also been added to the flash script of these devices.

Code:
eblink -E setDualBank(0|1)  // 0 = single and 1 =  dual bank

If you lost access to your device due to wrong flash options (even Cube programmer is not working) then you can restore the factory default with

Code:
eblink -E restoreDualBankMode()

EBlink doesn't connect

Wed, 01 Feb 2023 14:04:56 +0100

Hello, I try to connect to ATSAMC21 MCU using EBlink but without success.

Here are project settings:

And this is a log:

Code:
EBlink version 4.7-[13] by Gerard Zagema

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

Interface      : STlink

Device found at bus 1:28

Interface USB# : 55FF6C064883545237160887

Interface at  1:28 - :

Interface type : STlink/V2

STlink Frmware : V2.J29.S7

STlink connect : Under reset

Unknown/unexpected STLINK status code 0x9

STlink connect : Try again with active reset

Unknown/unexpected STLINK status code 0x9

STlink connect : connect under reset failed, try without reset

Error initializing interface STlink

Target power perhaps?

STlink connect : Hot plugging

Unknown/unexpected STLINK status code 0x9

Target voltage : 3.23V

The PCB is definitely connected and powered, ST-Link is also Ok, I have tested it.

What could be wrong here?

Program option bytes on STM32G4xx

Tue, 22 Nov 2022 11:59:13 +0100

I've previously been working with STM32F411 but recently switched to STM32G473, so I need to learn new things.
STM32G473 have dual-bank FLASH, configurable via the option bytes as single- or dual-bank. Factory default is dual-bank.
I will use singe-bank mode and therefore need to somehow program the option bytes.

My first attempt was to embed the option bytes via the source code into the .hex file, to be flashed when writing/updating the firmware on the CPU. I was able to do this with the help of the linker script. STM32CubeProgrammer will take the generated .hex file and write the option bytes along with the rest of the firmware. This works. I copy/paste the code here in case someone else have use for it:

In the source code:

Code:
#include 

#include "stm32g4xx_hal.h"

/// User and read protection option bytes

#define OPTR_CONTENT \

  (1 << 31) |

  OB_IRH_ENABLE |

  OB_NRST_MODE_INPUT_ONLY |

...

/// Option byte array (single-bank or bank 1) located at the correct address in memory based on the section definition in the linker script

uint32_t application_option_bytes_singlebank_or_bank1[6 * 2] __attribute__((section(".option_bytes_bank1_section"))) =

{

  (uint32_t)(OPTR_CONTENT),          ~(uint32_t)(OPTR_CONTENT), 

  (uint32_t)(PCROP1_START_CONTENT),  ~(uint32_t)(PCROP1_START_CONTENT), 

  (uint32_t)(PCROP1_END_CONTENT),    ~(uint32_t)(PCROP1_END_CONTENT), 

  (uint32_t)(WRP1A_CONTENT),         ~(uint32_t)(WRP1A_CONTENT), 

  (uint32_t)(WRP2A_CONTENT),         ~(uint32_t)(WRP2A_CONTENT), 

  (uint32_t)(SEC1_CONTENT),          ~(uint32_t)(SEC1_CONTENT),

};

/// Option byte array (bank 2) located at the correct address in memory based on the section definition in the linker script

uint32_t application_option_bytes_bank2[5 * 2] __attribute__((section(".option_bytes_bank2_section"))) =

{

  (uint32_t)(PCROP2_START_CONTENT),  ~(uint32_t)(PCROP2_START_CONTENT), 

  (uint32_t)(PCROP2_END_CONTENT),    ~(uint32_t)(PCROP2_END_CONTENT), 

  (uint32_t)(WRP1B_CONTENT),         ~(uint32_t)(WRP1B_CONTENT), 

  (uint32_t)(WRP2B_CONTENT),         ~(uint32_t)(WRP2B_CONTENT), 

  (uint32_t)(SEC2_CONTENT),          ~(uint32_t)(SEC2_CONTENT),

};

In the linker script:

Code:
MEMORY

{

...

  OPT_B1 (rw) : ORIGIN = 0x1FFF7800, LENGTH = 48              /* Options bytes single-bank or bank 1 */

  OPT_B2 (rw) : ORIGIN = 0x1FFFF808, LENGTH = 40              /* Options bytes bank 2 */

...

}

SECTIONS

{

...

  /* Options bytes single-bank or bank 1 */

  .option_bytes_bank1_section : 

  {

      KEEP(*(.option_bytes_bank1_section*))

  } > OPT_B1

  /* Options bytes bank 2 */

  .option_bytes_bank2_section : 

  {

      KEEP(*(.option_bytes_bank2_section*))

  } > OPT_B2

...

}

BUT, unfortunately this does not work with EBlink 4.7 in EmBitz 2.50:

Quote:EBlink version 4.7-[13] by Gerard Zagema

Interface USB# : 54FF6A066684565547522187
Interface type : STlink/V2
STlink connect : Under reset
Target voltage : 3.25V
Interface speed: 4000KHz
Target detected: Cortex-M4 (r0p1) with FPv4_SP
HW breakpoints : 6
HW watchpoints : 4
Fault unwind : Active break (level 2)
STmicro family : STM32G47/48xx
Detected FLASH : 0x80000
Configured RAM : 0x20000
Reset: system
Try to flash a non-flash region! Address 0x1FFF7800
Try to flash a non-flash region! Address 0x1FFFF808
Checking current flash content
Flash programming done
Flash verify done
Flasher starts target
Reset: system

And I guess the reason is in EBlink/scripts/stmicro/stm32gx.script

Quote://///////////////////////////////////////////////////
//
// STM32Gx
//
// ToDo: - option programming
//

I've looked briefly at the script code and I would not know where to start, if I try to implement this myself.
Are there any plans of implementing this anytime soon?

What are my alternatives? Suggestions are appreciated as this is a new CPU for me and I'm learning.
At the moment I'm in development, and can set the options with STM32CubeProgrammer, but eventually I will be getting factory empty CPU's and by then I need to get them flashed as conveniently as possible, that was why I initially tried to embed the option bytes directly in the .hex file.

Use EBlink with ST-LINK2 on Atmel SAM3X8E CPU

Thu, 27 Oct 2022 01:03:49 +0200

Hello

I tri to use EBLink with an ST-Link2 connected to an old Arduino Due (Atmel SAM3X8E)

When starting EBlink it seems to detect a Cortex M3, which is correct. But then there is an error:

"Can't detect MCU vendor"

There is also a message to eventually disable the "dr" option, but this has no effect (I started both the stm32gdg and stm32hotplug versions)

How can I get the ST-Link to accept non ST hardware?

EBlink Install Fail

Wed, 09 Mar 2022 01:40:06 +0100

At time of EBlink install (4.5, build 9) during Embitz 2.30 installation, a prompt dialog box appears with...

"Cannot create target folder"
"(Probably missing access rights)"

I wonder what a fix could be, machine is Windows 10 Pro 21H1.

Workalot

How to use default probe environment variable

Thu, 09 Dec 2021 02:52:00 +0100

I am running Windows10 and attempted to set the default environment variables
The one I am stuck on is EB_DEFAULT_PROBE
The others seem to be working, but this one is troublesome.

Any suggestions or help.

many thanks.
bri

programming 1.8V controller

Tue, 30 Nov 2021 16:26:44 +0100

Hi,

I'm using STM32F466 at 1.8V with Embitz 2.0. Sometimes it happens that ST-Linkv2 reads out "only" 1.79V and EBlink refuses to program the chip.
It would be nice if EBlink would accept 100mV tolerance here.

EBLink Debugger Problems

Fri, 06 Aug 2021 16:29:20 +0200

Hello,

currently i'm having some trouble with EBLink and debugging a nucleo board. (I tried with latest st-link fw and V2.J34.M25; I'm also using latest eblink 4.0.6)

When i try to connect, i get an network error

eblink.png (Size: 42.83 KB / Downloads: 692)

When i change from port 4242 to 4244 (just tried this one number), i can connect and my application runs.

But if i do anything in EB (Setting breakpoint, halting application etc), eblink crashes. (Error: Connection with target lost)

Code:
Exception condition detected on fd 580

Debugger finished with status 1

mfg

STLink-V3MINI usage

Thu, 04 Mar 2021 08:34:32 +0100

I use STLink-V3MINI. According to documentation, it needs VCC (3.3) from the target device to recognize it.

But I noticed that the ST-LINK utility recognizes the target even when VCC is not connected.

Is it possible for the EBlink to work in the same way, ignoring if the VCC presents or not?

Thus the necessary number of STlink connector pins will become 3 instead of 4.
For some miniature applications, it will be a great advantage.

vdaniel