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

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 1,003
» Latest member: wbicaxias
» Forum threads: 859
» Forum posts: 5,100

Full Statistics

Latest Threads
Suggestions future releas...
Forum: EmBitz IDE
Last Post: bufran
Yesterday, 06:39 AM
» Replies: 137
» Views: 73,590
Does EmBitz support Nucle...
Forum: EmBitz IDE
Last Post: Lutz Kämmerling
17-02-2019, 10:35 PM
» Replies: 0
» Views: 29
loading to device without...
Forum: EmBitz IDE
Last Post: escalator
08-02-2019, 04:54 PM
» Replies: 18
» Views: 9,979
Introducing section withi...
Forum: ArmGCC - EmBlocks
Last Post: PDonchev
22-01-2019, 08:58 PM
» Replies: 1
» Views: 430
Kinetis MK66 & SVD
Forum: SVD (System view) files
Last Post: Workalot
16-12-2018, 04:39 AM
» Replies: 1
» Views: 470
Download/Debugging Silabs...
Forum: Debug interface scripting
Last Post: Polarisru
10-12-2018, 01:38 PM
» Replies: 4
» Views: 1,617
Burning flash and debuggi...
Forum: Debug interface scripting
Last Post: Polarisru
10-12-2018, 01:33 PM
» Replies: 0
» Views: 237
Embitz with GCC-ARM
Forum: ArmGCC - EmBlocks
Last Post: Tony201800
30-11-2018, 12:01 AM
» Replies: 0
» Views: 367
emBitz, MK66, Debugger an...
Forum: EmBitz IDE
Last Post: Workalot
27-11-2018, 10:40 AM
» Replies: 1
» Views: 423
EBLINK: STM32L496ZG not s...
Forum: Debug interface scripting
Last Post: vargham
22-11-2018, 09:36 AM
» Replies: 1
» Views: 606

 
  Does EmBitz support Nucleo-H743ZI?
Posted by: Lutz Kämmerling - 17-02-2019, 10:35 PM - Forum: EmBitz IDE - No Replies

Hi,
in the past I made several projects with the STM32F303 microcontrollers and I used the free EmBitz IDE.
Now I have the Nucleo-H743ZI board and I still want to use EmBitz IDE. But in the free Version the STM32H743 microcontroller
is not available. When I become member of EmBitz and downloading the newest IDE Version, would the STM32H743 microcontroller then be available?

Print this item

  Introducing section within a section in WinARM GCC tools.
Posted by: phani - 01-01-2019, 08:07 AM - Forum: ArmGCC - EmBlocks - Replies (1)

Hi,

This is generic question on using WinARM and GCC - not on EB specific IDE. Please pardon me if the post does not suit the thread.

I am using WinARM GCC tools for compiling, linking the code for LPC2378. This worked great until recently, where I need to put some signature in LPC2378 at particular location to make it Code read protection.

Earlier my .ld file looks like 
{
  ROM (rx) : ORIGIN = 0x00000000, LENGTH = (512k-4k)
  RAM (rw) : ORIGIN = 0x40000000, LENGTH = (32k-32)
}
and with LPC2378 requirement of putting the signature of 0x12345678 at location 0x1FC I modified the .ld file as below

MEMORY
{
  ROM (rx) : ORIGIN = 0x00000000, LENGTH = (512k-4k)
  RAM (rw) : ORIGIN = 0x40000000, LENGTH = (32k-32)
  CRP_ROM (rx) : ORIGIN = 0x000001FC, LENGTH = 4
}
SECTIONS
{
  /* place "myArray" inside "m_my_memory" */
  .crpsection :
  {
    . = ALIGN(4);
    KEEP(*(.crpsection*));
    . = ALIGN(4);
  } > CRP_ROM
  
  /* first section is .text which is used for code */
   .text :
  {
/* *crt0.o (.text) */           /* Startup code */
/*KEEP (crp.o(.constdata))*/
KEEP(*(.vectorg))
KEEP(*(.RESET))
KEEP(*(.SWI_HANDLER))
. = ALIGN(4);
KEEP(*(.init))             /* Startup code from .init-section */
*(.text .text.*)           /* remaining code */
*(.gnu.linkonce.t.*)
*(.glue_7)
*(.glue_7t)
*(.gcc_except_table)
*(.rodata)                 /* read-only data (constants) */
*(.rodata*)
*(.gnu.linkonce.r.*)
. = ALIGN(4);
  } > ROM
  
  /***** old: 
  .text :
  {
    *crt0.o (.text)            
    *(.text)                   
    *(.rodata)                 
    *(.rodata*)
    *(.glue_7)
    *(.glue_7t)
  } > ROM 

created a crp.c file with content
#define CRP1 0x12345678
__attribute__((section(".crpsection"))) unsigned int const Security_Value = CRP1;

and added this makefile
SRC =  $(TARGET).c monitor.c adc.c crp.c 

With this I get an error saying 
c:/winarm/bin/../lib/gcc/arm-elf/4.1.2/../../../../arm-elf/bin/ld.exe: section .crpsection [000001fc -> 000001ff] overlaps section .text [00000000 -> 0000b23b]
c:/winarm/bin/../lib/gcc/arm-elf/4.1.2/../../../../arm-elf/bin/ld.exe: main.elf: section .crpsection lma 0x1fc overlaps previous sections

Basically I want to reserve memory location 0x1FC for CRP value. This is basically putting a section inside a section. 

Is it possible to do this way in WinARM - GCC tools sets? Or is there any other way to do this? Generally I look at generated .bin file to see the signature of 0x12345678 at location 0x1FC.

Any thoughts/ suggestions are helpful Smile

With best regards,
Phani.

Print this item

  Kinetis MK66 & SVD
Posted by: Workalot - 13-12-2018, 10:05 AM - Forum: SVD (System view) files - Replies (1)

Detective Workalot is on the trail of the misbehaving Kinetis MK66 SVD file.

The attached 'mk66_svd_issue.txt' expresses findings.


(13-12-2018, 10:05 AM)Workalot Wrote: Detective Workalot is on the trail of the misbehaving Kinetis MK66 SVD file.

The attached 'mk66_svd_issue.txt' expresses findings.

Hmmm - where did the attachment get to?

Here is its content...

13-Dec-2018
-----------
Bogged down on why when debugging, the 'System Registers' window won't show
register values, reporting '(Target read error)'. However, some <peripheral>s
do show values.

For example the FTFE peripheral is reported (albeit incorrectly).

But some background. At...

    https://forum.segger.com/index.php/Threa...registers/

... I posed the question as to why peripheral registers could not be
viewed with JMEM. Well, JMEM reads in blocks and if there is a 'gap' in
the block addresses, the read fails. A 'gap' is an address where no
register exists.

Now I'm a wondering if this is the cause for '(Target read error)'. In the
case of FTFE peripheral, all registers are accessible including the reserved
registers. This was tested using the command line JLink utility...

    J-Link> mem8 0x40020000,0x2C    // Access entire space

... so, if one considers the SVD file for FTFE...

    <peripheral>
      <name>FTFE</name>
      <description>Flash Memory Interface</description>
      <prependToName>FTFE_</prependToName>
      <baseAddress>0x40020000</baseAddress>
      <addressBlock>
        <offset>0</offset>
        <size>0x2C</size>
        ......
     </peripheral>

... maybe '<size>0x2C</size>' has EmBitz instruct J-Link to read in 0x2C
bytes which is all good - there is no failure.

When we look at the PIT peripheral's layout however...

    /** PIT - Register Layout Typedef */
    typedef struct {
        __IO uint32_t MCR;
             uint8_t RESERVED_0[220];
        __I  uint32_t LTMR64H;
        __I  uint32_t LTMR64L;
             uint8_t RESERVED_1[24];
        struct {
            __IO uint32_t LDVAL;
            __I  uint32_t CVAL;
            __IO uint32_t TCTRL;
        __IO uint32_t TFLG;
        } CHANNEL[4];
    } PIT_Type;

... we find that a...

    J-Link>mem8 0x40037004,1    // PIT->RESERVED_0[0]

... fails with a 'Could not read memory'. So there is a 'gap' and the
read fails resulting in the PIT peripheral in the debug window showing
all '(Target read error)'s.

But, hang on, why does it not occur with other MCU platforms? EmBitz
is fine with SAM3X8E, STM32F407, LPC1837. Do they have contiguous
register space?

Print this item

  Burning flash and debugging for EFM32G222 and J-Link
Posted by: Polarisru - 10-12-2018, 01:33 PM - Forum: Debug interface scripting - No Replies

Hello,
I'm using EmBitz for some years already and is very satisfied with this IDE. I've already successfully worked with different families of MCUs (STM32F1/F4, Nordic nRF51822, Atmel ATSAMC21) and haven't had any problems with debugging and flashing controllers with ST-Link or J-link.
But now I want to start with EFM32 Gecko family from SiLabs and have a lot of problems with flashing these chips. I can actually flash them outside of EmBitz (with the native tool from Segger) and then everything is working, I can debug my firmware with EmBitz. But it seems not to be possible to flash chips with the EmBitz script. I have taken a look at the script, it seems to be the same script as the one for NXP, I've not found any serious differences. But it doesn't work. It can't enter the programming mode but is able to debug the chip. I have tried to change some settings but without any success.
May be somebody has solved this problem?
With best regards, Alex

Print this item

  Embitz with GCC-ARM
Posted by: Tony201800 - 30-11-2018, 12:01 AM - Forum: ArmGCC - EmBlocks - No Replies

Hello friends,

My apologies if this thread was already quizzed and answered. I am involved in a DIY project which includes bare metal dev on Pi 3 B+. I have downloaded and installed embitz 1.11 on WIndows 10. I also have a toolchain from ARM named: GCC-ARM-8.2-2018.08-x86_64-aarch64-elf.tar.xz.

I understand it's a toolchain for the linux platform. I would like to know how to get embitz configured to use this toolchain on WIndows 10. Is it even possible. I saw a youtube video where the presenter did what I am trying to do except that his toolchain was gcc-linux-arm.

If what I am trying to achieve is even remotely possible could someone please guide me of what I need to do to setup my environment.

Thanks,
Tony

Print this item

  emBitz, MK66, Debugger and Source Code Syncing
Posted by: Workalot - 21-11-2018, 12:39 AM - Forum: EmBitz IDE - Replies (1)

Have built a project based on NXP's MK66 MCU. I can download the program but the debugger brings up the wrong C source code (normally it would be the reset handler function or the main() function).

The Disassembly window however does show stepping through the reset handler code. 

"Debug->Interfaces->GDB server.Device family: generic".
"Debug->Interfaces->GDB server->Settings->Connect/Reset: -select USB -device MK66FN2M0xxx18 -if SWD -speed auto".
"Debug->Interfaces->GDB server->Settings->After connect: monitor reset <cr> load".

Even tried "Debug->Interfaces->GDB server->Settings->Before connect: dir ..\Source" to locate the startup file and main.c.

Workalot.

Print this item

  warning: implicit declaration of function 'memset'
Posted by: bbennett - 17-11-2018, 05:29 PM - Forum: ArmGCC - EmBlocks - Replies (1)

src\main.c|66|warning: implicit declaration of function 'memset' [-Wimplicit-function-declaration]|

I am using a nucleo F401RE with an ST x-nucleo-nfc03a1 (RFID board)
Also, I've been converting the code available from ST to the 401RE.

here is my main :
#include "stm32f4xx_conf.h"
#include "string.h"

typedef struct
{
  uint8_t one[5];
  uint8_t two[23];


}TEST;

int main(void)
{

  uint8_t check[10];
  memset(check, '=', 7);

  //TEST test;
  //memset(test.one, '-', 3);

  while(1)
  {

  }
}

The code used for driving the RFID board has been commented out and I am left with only the memset which by the way throws the warning.
Searching through all the headers reveal nothing out of the ordinary to me. Also I've searched through the .depend, .epb, and .elay files for clues. Again, everything looks copacetic.

For grins, I made a simple test project simply calling memset in the main and compiling worked without a hitch.

Mostly looking for guidance. Thanks in advance for all questions and comment.

bri

Print this item

  Print diagnostic messages in any form.
Posted by: AVI-crak - 13-11-2018, 03:27 PM - Forum: EmBitz IDE - No Replies

https://bitbucket.org/AVI-crak/sprint
Size - 1907 bytes with aggressive optimization - much easier and simpler printf ().
Print without parameter type, 1-4 arguments in arbitrary order.
No dependencies on external libraries.
Recognizes: "text", double, float, uint (8-16-32-64) _t, int (8-16-32-64) _t.
The text is printed without abbreviations.
Variables are limited by the number of characters OUT_TXT_SIZE_FLOATING (8-16).

Function to use in user code (macro)
printo ("text"); printo ( 0,566f, "text", 123, "/n/t");

The taste and color can change the contents of the function soft_print (char * txt).
This function prints on physics.

Print this item

Question Does Embitz support Emwin?
Posted by: ray911 - 19-10-2018, 07:51 AM - Forum: EmBitz IDE - Replies (2)

MCU:STM32F429IGT6
OS: none
LCD:5" 800x480  RGB888

Hi~
I recently learned to use a touch screen LCD with emWin Library.
But after adding the library file to Embitz, (Project build options---Linker settings---Libraries---Add---libgui.a)
it seems that there are many errors,
Am I made a mistake? or Embitz does not support it?


emWin Library file:
https://github.com/jserv/stm32f429-lcd-d...ry522_4x9i


emWin\Config\GUIConf.c|83|warning: 'at' attribute directive ignored [-Wattributes]|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(WINDOW.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(WINDOW.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(WIDGET.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(WIDGET.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SPINBOX_CreateIndirect.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SPINBOX_CreateIndirect.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SPINBOX.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SPINBOX.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SLIDER_CreateIndirect.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SLIDER_CreateIndirect.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SLIDER.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SLIDER.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SCROLLBAR_CreateIndirect.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SCROLLBAR_CreateIndirect.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SCROLLBAR.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(SCROLLBAR.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO_SetText.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO_SetText.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO_SetFont.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO_SetFont.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO_CreateIndirect.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO_CreateIndirect.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(RADIO.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(LISTBOX_Font.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(LISTBOX_Font.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(LISTBOX_CreateIndirect.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(LISTBOX_CreateIndirect.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(LISTBOX.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(LISTBOX.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(GUI_ARRAY.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(GUI_ARRAY.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(FRAMEWIN_CreateIndirect.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(FRAMEWIN_CreateIndirect.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(FRAMEWIN.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(FRAMEWIN.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT_SetCursorAtChar.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT_SetCursorAtChar.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT_EnableBlink.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT_EnableBlink.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT_Default.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT_Default.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDITDec.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDITDec.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(EDIT.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(DROPDOWN_SetFont.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(DROPDOWN_SetFont.o)|
||bin\Debug\emwinMove.elf uses VFP register arguments, emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(DROPDOWN_CreateIndirect.o) does not|
||failed to merge target specific data of file emWin\Lib\STemWin522_4x9i_CM4_OS_GCC.a(DROPDOWN_CreateIndirect.o)|
||More errors follow but not being shown.|
||Edit the max errors limit in compiler options...|
||=== Build finished: 50 errors, 1 warnings (0 minutes, 39 seconds) ===|

Print this item

  crash sequence identified
Posted by: jheissjr - 17-09-2018, 03:08 PM - Forum: EmBitz IDE - Replies (1)

I identified a sequence of Embitz crashing. It is reproducible on my side. What info is helpful besides the capture?

https://youtu.be/FEVFBXLL4XY



Attached Files Thumbnail(s)
   

.txt   crashrpt.txt (Size: 1.63 KB / Downloads: 46)
Print this item