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



Search Forums

(Advanced Search)

Forum Statistics
» Members: 978
» Latest member: barabek
» Forum threads: 856
» Forum posts: 5,089

Full Statistics

Latest Threads
Download/Debugging Silabs...
Forum: Debug interface scripting
Last Post: Polarisru
Yesterday, 01:38 PM
» Replies: 4
» Views: 1,122
Burning flash and debuggi...
Forum: Debug interface scripting
Last Post: Polarisru
Yesterday, 01:33 PM
» Replies: 0
» Views: 26
Embitz with GCC-ARM
Forum: ArmGCC - EmBlocks
Last Post: Tony201800
30-11-2018, 12:01 AM
» Replies: 0
» Views: 147
emBitz, MK66, Debugger an...
Forum: EmBitz IDE
Last Post: Workalot
27-11-2018, 10:40 AM
» Replies: 1
» Views: 181
EBLINK: STM32L496ZG not s...
Forum: Debug interface scripting
Last Post: vargham
22-11-2018, 09:36 AM
» Replies: 1
» Views: 375
warning: implicit declara...
Forum: ArmGCC - EmBlocks
Last Post: bbennett
17-11-2018, 09:02 PM
» Replies: 1
» Views: 183
Print diagnostic messages...
Forum: EmBitz IDE
Last Post: AVI-crak
13-11-2018, 03:27 PM
» Replies: 0
» Views: 145
The case for CAN
Forum: General
Last Post: DD4DA
02-11-2018, 11:09 AM
» Replies: 3
» Views: 653
Does Embitz support Emwin...
Forum: EmBitz IDE
Last Post: ray911
25-10-2018, 06:03 AM
» Replies: 2
» Views: 473
EmBitz 0.42 and 1.11, iss...
Forum: EmBitz IDE
Last Post: kadim
09-10-2018, 03:50 AM
» Replies: 12
» Views: 4,735

  impact of -eb_lib on static functions
Posted by: jheissjr - 19-12-2017, 05:02 PM - Forum: EmBitz IDE - Replies (1)

There seems to be two different behaviors concerning static functions when "Exclude Standard Libraries" is enabled (the -eb_lib flag).

void compute_floor()
   double floor = floor(1.3);  // no error, successful compile

static void compute_floor()
   double floor = floor(1.3);  // "undefined reference to 'floor' "

The built-in functions such as floor() are not linked when static functions include them inside the function.  Compiling stops during the linking stage.  I'm going to check gcc documentation because I believe I have a misunderstanding.  How is -eb_lib implemented so I can search the correct terms?  Does it enable certain gcc flags?

Print this item

  Using GDB with EMBitz
Posted by: Günter Strack - 19-12-2017, 09:31 AM - Forum: EmBitz IDE - Replies (3)


I'm building my EmBitz project to different platforms (STM32F446, STM32F103, Windows). For the latter, I utilized an unused Compiler Setting (in my case ARM Generic Toolchain), replaced the Names of Executables and Paths with an existing installation of MinGW64 and applied all necessary compiler and linker settings, to build my target for Windows (with SDL graphics interface). This works like a charm. The result is an *.exe-file, which can be run under Windows and Debugged with the GDB in Windows command line interface.

However, unfortunately, I did not manage to get GDB working with EmBitz (starting the executable and allowing debugging of the *.exe file).

Since the debuggers for embedded targets are based on GDB, I don't think there is a general limitation.

So: Can I get some advice how to embed the windows GDB in EmBitz?


Print this item

  Simple SD-card driver for SPL?
Posted by: peterb - 18-12-2017, 02:35 PM - Forum: General - Replies (2)

I'm looking for a simple, low level SD card driver with SPL for STM32 devices without SDIO interface. Just simple initialize and block read/write/erase functions with SPI bus, no need of any filesystem, INT or DMA, etc. I found a very similar driver what I need, but in C++ with HAL:
My C++ knowledge is very poor/old/dusty, so what do you think, how hard work would be to port this code to simple C with SPL?
Or can somebody suggest some similar SD card driver written for SPL?

Print this item

  Multiple linker scripts
Posted by: AlexNL - 16-12-2017, 11:25 PM - Forum: EmBitz IDE - Replies (2)

Hello! Thanks you for great IDE!!
So, my question is: Can i have separate linker script files for debug and release. I tried setup this in project property, but it doesn't work. 

Attached Files Thumbnail(s)
Print this item

  STLinkGDB Debugger Server is closed/terminated
Posted by: kriisi - 15-12-2017, 10:31 AM - Forum: ARM gdb - Replies (1)

I have been working several months with my STM32L1xxx project with Embitz 1.11 on Windows 10. Some times I have needed to restart the IDE to get the debugger working. Now however I have tried all my different projects, two different debuggers (different cables too) and I have restarted IDE several times (and the target) and I have restarted windows and changed STLinks USB port. Now I'm out of ideas since there are no error messages to study.
With STM32 ST-LINK Utility I can still connect to target and program the sw. Just the Embitz debugger wont work.
Device manager says the debugger is working fine and there are no errors in windows events.
Only thing I haven't tried is installing Embitz again or using some other manufacturers debugger.
From JTAG I have only six wires connected (VCC, GND, TRST, TMS, TCLK, TDO ).

Print this item

Sad EbMonitor stopped working
Posted by: OliviliK - 15-12-2017, 02:47 AM - Forum: EmBitz IDE - Replies (12)

I can do single stepping and all other debugging commands in my F407 project.  I have enabled the EbMonitor in tools and linker settings like in all other projects where EbMonitor is working.

Could the problem be in the loader file?  In past, I did use loader files provided by EmBitz.  Now, I am generating all source files and loader file with CubeMX.  I can see that the old project map files have the _read and _write symbols.  In the new project map file, there are no duplicate definitions for these.  Actually, there are no _read and _write symbols.

How can I fix this?

Print this item

  transferring data to the console via SWO
Posted by: jheissjr - 12-12-2017, 02:33 PM - Forum: EmBitz IDE - Replies (4)

I really like the new EBmonitor.  I have one question about it so far.  If one were to write data to the ITM register in the Cortex-M core, will the data appear in the console?

void main()
 ITM->PORT[0] = 'H';
 ITM->PORT[0] = 'i';

Print this item

  Custom Tools Don't Stay Open
Posted by: troyerta - 08-12-2017, 06:24 PM - Forum: EmBitz IDE - Replies (1)


I'm using an external compiler, and want to make some git integration options and whatnot. 

Embitz seems to be able to run .bat scripts from the Tools setup. It's really pretty cool.

However, I cannot seem to get any of the "Launching Options" to act distinctly from each other. This is inconvenient.

I can so far launch my console (Console2) from the .bat script, and call my own compiler tools and whatnot, but the window that Embitz launches ALWAYS disappears, no matter which of the launching options I choose. This is bad for reading compiler results after compilation completion.

I tried editing my .bat to include the standard '/B' and '/k', and 'pause &' flags, but none of them seem to work.

My problem would be solved if the radio buttons under "Launching Options" actually worked, I think.

Right now, my executable in the 'Edit tool' window is my batch file, and there are no parameters.

Maybe it could also be solved if I chose my executable as Console2.exe, and used my .bat file as the parameter from the 'Edit tool' window?

I'm thinking the parameters field expects windows cmd params, and not Console2 params. 

Anyone have any ideas for how I can keep my compiler results console window open?

Print this item

  Desperate for help with STM32L152
Posted by: stevegembitz - 07-12-2017, 07:33 PM - Forum: ArmGCC - EmBlocks - Replies (3)

Somebody please help I am going round in circles.

I've been using Embitz for well over a year with no problems using an STM32F429 procesor and the latest ST  HAL libraries.

However I am trying to do a project using the STM32L152 processor which is a Cortex-M3 core.

If I put "-mfloat-abi=soft" in the compile flags I get "-mfloat-abi=soft and -mfloat-abi=hard may not be used together".
If I get rid of the "-mfloat-abi=soft" everything compiles but it then fails at the link stage with the linker errors each file with
"xxx.o uses VFP register arguments, .\build\project.elf does not".
I've managed to get an mbed 152 project e.g. Nucleo_blink_led_152 sort of working although I couldn't debug
it... to be pursued.

Any help or guidance would be gratefully appreciated.

Print this item

  J-Link, ST-Link capabilities
Posted by: jheissjr - 06-12-2017, 09:44 PM - Forum: EmBitz IDE - No Replies

SWD mode on a debug probe has several capabilities.  J-Link and ST-Link use the SWO pin as a UART type interface where the application on the Cortex sends printf data to a PC console. 

There are notes that the probes also have SWV event and data tracing, and software instrumented tracing.  I would like to understand, what is event and data tracing?  What is interrupt and exception event logging?  Is this data available from the macrocell, is it code the user inserts in an program?

A last follow up last question, are there any thoughts on adding J-Trace support for instruction and data tracing?

Attached Files Thumbnail(s)
Print this item