Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 41
» Latest member: hull
» Forum threads: 18
» Forum posts: 110

Full Statistics

Online Users
There are currently 10 online users.
» 0 Member(s) | 9 Guest(s)

Latest Threads
Update for EmBitz 1.11
Forum: Using EmBitz
Last Post: Mink
23-10-2020, 03:24 PM
» Replies: 6
» Views: 1,665
stm32F7 exception after f...
Forum: Bug report
Last Post: vdaniel
21-10-2020, 09:05 PM
» Replies: 28
» Views: 549
st-link selection via ser...
Forum: Using EBlink
Last Post: embitz
08-10-2020, 10:02 AM
» Replies: 7
» Views: 342
EBLink Support for STMF30...
Forum: Bug report
Last Post: vdaniel
07-10-2020, 07:33 AM
» Replies: 19
» Views: 522
EBlink on STM32G4 dependa...
Forum: Scripts
Last Post: embitz
06-10-2020, 11:43 AM
» Replies: 2
» Views: 1,001
Errors when linking math ...
Forum: ARM GCC toolchain
Last Post: pdaragon
26-09-2020, 02:53 PM
» Replies: 2
» Views: 184
EmBitz batch build
Forum: Using EmBitz
Last Post: PDonchev
24-09-2020, 01:34 PM
» Replies: 4
» Views: 511
Quotes in variable expans...
Forum: Bug report
Last Post: Mink
23-09-2020, 11:57 AM
» Replies: 5
» Views: 318
No autocompletion for reg...
Forum: Bug report
Last Post: Mink
19-09-2020, 04:05 PM
» Replies: 0
» Views: 152
IDE does not find impleme...
Forum: Bug report
Last Post: Mink
19-09-2020, 03:57 PM
» Replies: 0
» Views: 108

  stm32F7 exception after flashing
Posted by: vdaniel - 14-10-2020, 06:05 PM - Forum: Bug report - Replies (28)

Hi, I am testing STM32F722.

When before to start the EBLink Debug "Session Start/Stop", I program the chip by ST_LINK Utility, the debugger
works Ok, but when I started Debug directly, I see:

Interface speed: 3300KHz
Target detected: Cortex-M7 (r1p1) with FPv5_SP
HW breakpoints : 8
HW watchpoints : 4
Fault unwind : Enabled
STmicro family : STM32F72x/73x
Detected FLASH : 0x80000
Configured RAM : 0x80000
GDB listening ( @ 2331)
GDB connected
Flashing sector 0, address: 0x08000000, length: 0x8000
Flashing sector 1, address: 0x08008000, length: 0x8000
Flashing sector 2, address: 0x08010000, length: 0x8000
Flashing sector 3, address: 0x08018000, length: 0x3BD8
Reset: system
Target Exception!

[LR]: 0x080170C3
[PC]: 0x08015658

Additional Info:
-Undefined instruction


Print this item

  EBLink Support for STMF303K8
Posted by: vdaniel - 01-10-2020, 08:22 AM - Forum: Bug report - Replies (19)

When I try to start debugging with the Eblink3.1.0, I receive an error message:

Incompatible EBlink version 2.0
Please update

The previous 3.0.3 and 3.0.4 did not support the STMF303K8, but without this message.


Print this item

  Errors when linking math lib.
Posted by: pdaragon - 25-09-2020, 07:59 PM - Forum: ARM GCC toolchain - Replies (2)

I try to import a Keil project published by Semtech (firmware of the LoRa SX1261 evaluation kit).
I almost succeeds, but face 5 remaining errors when the linker searches for <math.h> following functions: rint, round, floor, ceil.
I tried to change several options in "Linker setttings/Library selection", but without success.
Please could you help.
I attach the .ebp project with this post (STM32L476RG HAL source files has been removed to limit zip file size to less than 1Mb).
Thanks and regards

Attached Files
.zip   NUCLEO_476RG.zip (Size: 703.43 KB / Downloads: 1)
Print this item

  st-link selection via serial
Posted by: resonantworks - 24-09-2020, 09:53 PM - Forum: Using EBlink - Replies (7)

Is it possible to choose the active debug probe which EBlink uses by serial number on the command line?
I usually have 3+ st-links connected at the same time since I work with hardware which has 3 separate stm32s which communicate with each other via uart.

Print this item

  No autocompletion for registers
Posted by: Mink - 19-09-2020, 04:05 PM - Forum: Bug report - No Replies

No autocompletion for registers which are referenced by the pointer.

[Image: attachment.php?aid=9]

Attached Files Thumbnail(s)
Print this item

  IDE does not find implementation of functions
Posted by: Mink - 19-09-2020, 03:57 PM - Forum: Bug report - No Replies

IDE does not find implementation of functions.

[Image: attachment.php?aid=8]

This is due to conditional compilation. That is, the HAL library uses many such expressions.

// all file code stm32f4xx_hal_gpio.c
EmBitz does not support search define in include header files.

Attached Files Thumbnail(s)
Print this item

  Quotes in variable expansion
Posted by: Mink - 15-09-2020, 12:04 AM - Forum: Bug report - Replies (5)

EmBitz supports variable expansion such as the ${PROJECT_DIR}, ${TARGET_OUTPUT_DIR} and others.
If there is a space in the path, quotes are added and this is a very bad idea!
For example, let the project be in the folder

С:\MyProjects\STM32\Test Blink\

If you use variable expansion in the tool (e.g. flashing a hex file using EBlink).
This will mess up the command line which will be like this

"С:\MyProjects\STM32\Test Blink\"bin\Release\"Test Blink".hex

It is necessary that the quotes are not automatically added if there are spaces in the path. Then this tool will work fine.

-I stlink,swd -S stm32-auto -F file="${PROJECT_DIR}${TARGET_OUTPUT_DIR}${TARGET_OUTPUT_BASENAME}.hex"

Now this is not possible if there are spaces in the file path.

Print this item

  EmBitz batch build
Posted by: PDonchev - 08-09-2020, 05:30 PM - Forum: Using EmBitz - Replies (4)

I'm trying to build several projects from a .bat file, but unfortunately after completing the build process the following dialog box appears:
[Image: embitz-abort-dialog.png]
I have to click Yes and manually close the EmBitz window. Is it possible to avoid this?

Attached Files Thumbnail(s)
Print this item

  Update for EmBitz 1.11
Posted by: Mink - 01-09-2020, 04:21 PM - Forum: Using EmBitz - Replies (6)

While we all wait for the new version EmBitz 2.0, i decided to make an update for EmBitz 1.11.
First of all, this is an update of the libraries and the list of supported microcontrollers.
Download the file here https://www.dropbox.com/s/upmp6r1fuqltrz...z_1.11.zip

Select STM32 when creating a project to use this update.


Libraries available CMSIS, SPL, HAL, LL. Note that the HAL library is partially LL dependent. Therefore, if you select only HAL, some modules will be disabled (the list of disabled modules can be found in the stm32XXxx_hal_conf.h file).

To install this update, just unzip the archive into the folder with EmBitz 1.11.
Typically a path in x64 Windows

C:\Program Files (x86)\EmBitz\1.11\
The x86 Windows path
C:\Program Files\EmBitz\1.11\

This update requires EBlink. Current version 2.8 https://www.dropbox.com/s/fefp18w932vxii...z_1.11.zip
For installation, unpack into the EmBitz folder.

I have also updated the compiler to the current version. https://www.dropbox.com/s/yr86grco7g21io...tz_1.11.7z
This is an optional update. Install only if you need a new compiler or you need STM32L5 microcontrollers. They have an ARM Cortex-M33 core, which is not supported by the compiler GCC 5.4 from the distribution EmBitz 1.11.

Please note that EB monitor does not work with this compiler. Use Semihosting.

To use this compiler, you must select it in the window Tool settings (opens from the menu Setting -> Tools...).


Path compiler

Here are some examples of projects created using this update. https://www.dropbox.com/s/ekhxrimq1ibce98/Examples.7z


Update v1.1 https://www.embitz.org/forum/thread-12-p...html#pid45

Print this item

  CMSIS-DAP/DAPLink debug probes
Posted by: splin - 20-08-2020, 01:02 AM - Forum: Debugging and debug plugins - Replies (3)

Are these natively supported or would these have to used with OpenOCD? It would seem to be preferable to be able to use an open, non-proprietry debug/programming probe rather than having to buy a new probe for different manufacturer's Cortex devices.

For example, I have an LPC-Link2 which can be flashed with CMIS-DAP DAPLink firmware which presumably I should be able to use to program Nuvoton Mini51 serries devices rather than having to buy their nu-link product? ([EDIT] the Nu-link probe is probably not supported by EBlink so OPENOCD would be required losing EBlink's advantages).

Are there significant performance differences between most debug probes (other than the expensive Segger products)?

[EDIT] This CMIS-DAP probe is only 12.99 Euros and supports Jtag as weill as SWD though I'm not sure how big an advantage that is in practice:

LTek debug probe

Is Jtag faster than SWD? Are there any Cortex devices that don't support SWD?

Print this item