https://www.embitz.org/forum/ Sun, 15 Nov 2026 05:40:53 +0000 MyBB https://www.embitz.org/forum/showthread.php?tid=214 Sun, 01 Dec 2024 18:59:10 +0100 sp9skp]]> https://www.embitz.org/forum/showthread.php?tid=214 Me again  

Can you add supoort for STM32WLE5CC?

Thanks!]]> Me again  

Can you add supoort for STM32WLE5CC?

Thanks!]]> https://www.embitz.org/forum/showthread.php?tid=200 Wed, 26 Jun 2024 12:37:49 +0200 sp9skp]]> https://www.embitz.org/forum/showthread.php?tid=200
Is there any chance/addon to support STM8 MCUs?

Thanks.]]>
Is there any chance/addon to support STM8 MCUs?

Thanks.]]> https://www.embitz.org/forum/showthread.php?tid=186 Sun, 28 Jan 2024 18:58:09 +0100 altomaltes]]> https://www.embitz.org/forum/showthread.php?tid=186 Barebones means zero dependencies, thus, no CMSYS, for host device and OTG on boards that allow this.
It can be used as a library, shares the same link file among boards and exploits several ways to achieve less configurarion and lower the entropy of the project.
Althougt it can be mixed with regular CMSYS projects, it needs a little more config. Probably I will do.

For anyone interested:

 https://github.com/altomaltes/libOTG-stm32f4]]> Barebones means zero dependencies, thus, no CMSYS, for host device and OTG on boards that allow this.
It can be used as a library, shares the same link file among boards and exploits several ways to achieve less configurarion and lower the entropy of the project.
Althougt it can be mixed with regular CMSYS projects, it needs a little more config. Probably I will do.

For anyone interested:

 https://github.com/altomaltes/libOTG-stm32f4]]> https://www.embitz.org/forum/showthread.php?tid=184 Tue, 23 Jan 2024 10:58:25 +0100 embitz]]> https://www.embitz.org/forum/showthread.php?tid=184 EmBitz 2.65

• System viewer now highlight changes of expanded sub registers
  
• EBlink 6.21 (added EBmon cli, GDB proxy and now with 32/64 bits windows builds)
  

Embitz installer]]> EmBitz 2.65

• System viewer now highlight changes of expanded sub registers
  
• EBlink 6.21 (added EBmon cli, GDB proxy and now with 32/64 bits windows builds)
  

Embitz installer]]> https://www.embitz.org/forum/showthread.php?tid=171 Wed, 07 Jun 2023 16:28:40 +0200 Alex]]> https://www.embitz.org/forum/showthread.php?tid=171 "Never change a running system"...
But now I wanted to update from EmBitz 1.11 to 2.60

On 2.60, opening existing project (from 2.11) it displays:
"this project file was saved with an older version of EmBitz.
This version doesn't have the capabilities to convert, please update this version..."

Should I install some intermediate (which one?) version first ?

If I close the message, my project appears. It seems to compile, but not to debug. So, maybe it is due to this conversion?

Many thanks,
   Alex,]]> "Never change a running system"...
But now I wanted to update from EmBitz 1.11 to 2.60

On 2.60, opening existing project (from 2.11) it displays:
"this project file was saved with an older version of EmBitz.
This version doesn't have the capabilities to convert, please update this version..."

Should I install some intermediate (which one?) version first ?

If I close the message, my project appears. It seems to compile, but not to debug. So, maybe it is due to this conversion?

Many thanks,
   Alex,]]> https://www.embitz.org/forum/showthread.php?tid=168 Tue, 25 Apr 2023 10:54:36 +0200 embitz]]> https://www.embitz.org/forum/showthread.php?tid=168
This version is shipped with EBlink 4.8  which has now the capability to skip the voltage check by manually overruling the voltage on the CLI.  EBlink also supports now NXP and SAM3 with thanks to forum member jdubois.

The EmBitz modifications are a lot of bug fixes for the SVD viewer as well as some minor bug fixes. The probe interface supports the new EBlink voltage override.

This version still uses the GCC 9. I did some tests with the GCC 10.3 but discovered that the link time optimization is not that mature as 9 is. The generated code  with 10 without LTO is a bit more efficient so it was a hard decision which one to integrate. It's open for debate so if you have your thoughts, drop a comment below.

Have fun!

  EmBitz_2.60.zip (Size: 99.22 MB / Downloads: 13) ]]>
This version is shipped with EBlink 4.8  which has now the capability to skip the voltage check by manually overruling the voltage on the CLI.  EBlink also supports now NXP and SAM3 with thanks to forum member jdubois.

The EmBitz modifications are a lot of bug fixes for the SVD viewer as well as some minor bug fixes. The probe interface supports the new EBlink voltage override.

This version still uses the GCC 9. I did some tests with the GCC 10.3 but discovered that the link time optimization is not that mature as 9 is. The generated code  with 10 without LTO is a bit more efficient so it was a hard decision which one to integrate. It's open for debate so if you have your thoughts, drop a comment below.

Have fun!

  EmBitz_2.60.zip (Size: 99.22 MB / Downloads: 13) ]]> https://www.embitz.org/forum/showthread.php?tid=155 Wed, 01 Feb 2023 13:03:43 +0100 Polarisru]]> https://www.embitz.org/forum/showthread.php?tid=155 I also work on a EBlink script for these controllers.
Is it interesting for you to add it to future releases?
Regards,
Alex]]> I also work on a EBlink script for these controllers.
Is it interesting for you to add it to future releases?
Regards,
Alex]]> https://www.embitz.org/forum/showthread.php?tid=144 Tue, 15 Nov 2022 12:56:40 +0100 matsb]]> https://www.embitz.org/forum/showthread.php?tid=144
First of all, thanks for great tool!!!
But I have to report a little hickup.

I'm working with STM32 micros and is using STLINK/V2.
I have the old patched EmBitz 1.11 on my PC (Windows 10).
I have also been using EmBitz 2.00 for quite some time.

Now I tried to install EmBitz 2.50. 
During installation, installer asked if I want to unistall the old EBlink. I don't understand why it would need to do that, and I don't remember what I selected. I have thought that the different EmBitz versions and their tools could co-exist, but maybe I'm wrong?
Anyhow, EmBitz 2.50 was installed with default everything.

BUT, now EBlink is not found by EmBitz 2.50 when trying to access the "Flash" menu in EmBitz. 
The folder "C:\Program Files (x86)\EmBitz\2.50\share\EBlink" exist, but it is empty.

I have tried multiple times, uninstalled both 2.00 and 2.50, then reinstalled 2.50. Always the same thing, EBlink folder is empty after installation is complete.
I took a closer look at the EBlink folder during installation, and the EBlinkInstaller.exe can be seen there, and it expands into some files and folders "packages", "scripts", "win32", etc. but when the installer is done, the whole folder is wiped clean.

Then I manually ran EBlinkInstaller.exe and installed it into that folder "C:\Program Files (x86)\EmBitz\2.50\share\EBlink", after all the installers where done.
Now EmBitz shows that EBlink is present, but when trying to connect to a target, it can't find "stm32-auto.script", even though I can see the script in "C:\Program Files (x86)\EmBitz\2.50\share\EBlink\scripts".

Interface USB# : 54FF6A066684565547522187
Interface type : STlink/V2
STlink connect : Under reset
Target voltage : 3.27V
Interface speed: 4000KHz
Target detected: Cortex-M4 (r0p1) with FPv4_SP
HW breakpoints : 6
HW watchpoints : 4
Fault unwind  : Active break (level 2)
Can't load device script: stm32-auto.script


Any ideas how I can get this to work?

---

Update:
I uninstalled 2.50 and installed 2.00. EBlink folder is NOT wiped clean in this installation, but that stm32-auto.script is not found, when connecting to a STM32. So problem has now migrated to EmBitz 2.00...]]>
First of all, thanks for great tool!!!
But I have to report a little hickup.

I'm working with STM32 micros and is using STLINK/V2.
I have the old patched EmBitz 1.11 on my PC (Windows 10).
I have also been using EmBitz 2.00 for quite some time.

Now I tried to install EmBitz 2.50. 
During installation, installer asked if I want to unistall the old EBlink. I don't understand why it would need to do that, and I don't remember what I selected. I have thought that the different EmBitz versions and their tools could co-exist, but maybe I'm wrong?
Anyhow, EmBitz 2.50 was installed with default everything.

BUT, now EBlink is not found by EmBitz 2.50 when trying to access the "Flash" menu in EmBitz. 
The folder "C:\Program Files (x86)\EmBitz\2.50\share\EBlink" exist, but it is empty.

I have tried multiple times, uninstalled both 2.00 and 2.50, then reinstalled 2.50. Always the same thing, EBlink folder is empty after installation is complete.
I took a closer look at the EBlink folder during installation, and the EBlinkInstaller.exe can be seen there, and it expands into some files and folders "packages", "scripts", "win32", etc. but when the installer is done, the whole folder is wiped clean.

Then I manually ran EBlinkInstaller.exe and installed it into that folder "C:\Program Files (x86)\EmBitz\2.50\share\EBlink", after all the installers where done.
Now EmBitz shows that EBlink is present, but when trying to connect to a target, it can't find "stm32-auto.script", even though I can see the script in "C:\Program Files (x86)\EmBitz\2.50\share\EBlink\scripts".

Interface USB# : 54FF6A066684565547522187
Interface type : STlink/V2
STlink connect : Under reset
Target voltage : 3.27V
Interface speed: 4000KHz
Target detected: Cortex-M4 (r0p1) with FPv4_SP
HW breakpoints : 6
HW watchpoints : 4
Fault unwind  : Active break (level 2)
Can't load device script: stm32-auto.script


Any ideas how I can get this to work?

---

Update:
I uninstalled 2.50 and installed 2.00. EBlink folder is NOT wiped clean in this installation, but that stm32-auto.script is not found, when connecting to a STM32. So problem has now migrated to EmBitz 2.00...]]> https://www.embitz.org/forum/showthread.php?tid=140 Sat, 29 Oct 2022 09:26:28 +0200 embitz]]> https://www.embitz.org/forum/showthread.php?tid=140 https://www.embitz.org/forum/showthread.php?tid=106 Fri, 17 Dec 2021 10:56:52 +0100 embitz]]> https://www.embitz.org/forum/showthread.php?tid=106 Keeping that old stuff is very time consuming.]]> Keeping that old stuff is very time consuming.]]>