Search Results

Thank you for the info. I would love for Ozone to support GDB server. Please consider this topic answered.

Thanks.

What are the long term plans between Ozone and the Embedded Studio Debugger? Are they going to merge, stay separate or? This will help me figure out my development environment plans.

I couldn't find it in the description. If not, can you share if there are plans to do so and if so, by when? Thanks!

Was messing with a NUCLEO-F411RE board and decided to convert the onboard STLink to JLink. Downloaded the file from: segger.com/downloads/jlink/STLinkReflash When I ran it, observed the following: 1. The included JLinkArm.DLL is really old - version 5.12 (IIRC) 2. The copyright is old: (c) 2016 SEGGER Microcontroller GmbH & Co. KG segger.com STLinkReflash compiled Aug 12 2019 10:30:05 3. The Firmware Version History at: segger.com/products/debug-prob…j-links/st-link-on-board/ doesn't have an ent…

Sorry my question wasn't clear. How can I define a symbol to be the end of a region or block. The use case is, define a block in RAM for the stack. Then, take the end address of the stack and use that to initialize the stack pointer. Thank you.

In the linker .icf file, I want to define a symbol to be the end of a block. For example: define region CCMRAM = [0x10000000 size 0x10000]; define block stack with size = __STACKSIZE__, alignment = 8, readwrite access { }; place at end of CCMRAM { block heap, block stack }; define symbol _estack = end of stack; <- this doesn't work. What is the proper syntax for determining the start or end of a region / block? Also, where is _estack referenced? I looked and in the .map file it says "Linker crea…

When I use -L to tell the linker where to look and then -lc to use libc.a, the linker finds libc.a. When we use something from libc.a - example, malloc() and free(), they are not found / resolved with libc.a If I don't point the linker to libc.a using -L and then -lc but include libc.a as a file in the project, then the linker is able to resolve malloc() and free() to libc.a

Looks like to use NewLib, I need to use SEGGER_RTT_printf.c because SEGGER_RTT_SES.c relies on SES library/header files. Please consider this not an issue. Thank you for the support.

I needed some new features of the C++ library and so I tried to get NewLib to work. After much effort, I was able to get it to work but I ran into some issues I don't understand. I turned off the ES standard library by selecting No for Project Options->Libraries->Include Standard Libraries. I also set Project Options->Libraries->Standard Libraries Directory to None. I put the NewLib library files on my machine at: C:/Depot/Source/Library/arm-none-eabi/lib/thumb/v7e-m/fpv4-sp/hard So, I set Proje…

There is a thread on the ST forum about this issue with other tool chains. Looks like ST got rid of the guard? waclawek.jan (Community Member) 10 hours ago__FPU_PRESENT has always been defined in the CMSIS-mandated device headers, except that it used to be guarded. For example, this is from stm32f4xx.h from the SPL era #if !defined (__FPU_PRESENT) #define __FPU_PRESENT 1 /*!< FPU present */ #endif /* __FPU_PRESENT */

Sorry but I'm confused. When I used printf() in SEGGER_RTT_SES.c, I saw output in the Debug Terminal pane of Embedded Studio. It looks like SEGGER_RTT_printf.c in the Samples\RTT does the same thing. When should I use which one? What is wrong with using printf() in SEGGER_RTT_SES.c? Thanks.

Hi. Can you share the current state of the C++ STL that is included in the latest version of Embedded Studio? These threads suggest a new version is forthcoming but I cannot tell if that has already happened or still planned. Thanks! forum.segger.com/index.php/Thr…4&highlight=STL#post14264 forum.segger.com/index.php/Thr…0&highlight=STL#post16210 forum.segger.com/index.php/Thr…4&highlight=STL#post17404

Printf over RTT has an improperly declared prototype and/or the function name is incorrect and/or comment is incorrect. This is with Release 4.10a Build 201810203.37618 Windows x64 SEGGER_RTT.h has the following prototype: Source Code (7 lines) I looked and there is no SEGGER_RTT_printf.c However, there is a SEGGER_RTT_SES.c and it has a printf() that looks about right. Source Code (9 lines) I tested this printf, without a prototype, and it works just fine.

This applies to the ST processors. It may/may not apply to other vendors. When you set Project Options->Libraries->CMSIS 5 CMSIS-[CORE|DSP] Library to Yes, the build environment adds a -D__FPU_PRESENT to the c compiler command which ends up being a redefinition of __FPU_PRESENT which is in STM32F411xE.h and similar ST header files. To fix this, I looked at the <ProjectName>.ind file in the output directory which contains the list of files the linker is supposed to use. Found the CMSIS library fi…

Holy moly! That was it. Compilation and linking fly now. Thank you.

$(PackagesDir)/STM32F4xx/Source/STM32F411xx_Vectors.s" has many incorrect IRQ handler entries. For example, all the DMA IRQ handlers, SPI5, etc. are stubbed out as Dummy_Handler. I have "STMicroelectronics STM32F4xx CPU Support Package" Version 1.02 installed. This is apparently the latest package.

Looks like the dialog boxes where you would use a Macro have a drop down that shows the macros. The discoverability is meh...

Release 4.10a Build 2018110203.37618 Windows x64 Minor issue - during compilation, in the output pane, it used to show the core number being used for that command i.e. in the list below, at the start of the line instead of "1>" I would see "1>" or "2>" or "3>" or "4>" depending on which core was being used for the compilation/assembly. I no longer see that. Instead, I only see the "1>". Sample output is copied below. I deleted portions that had my path or extraneous stuff that didn't add value. …

How can I determine the value of a macro? Example: ProjectName or Configuration or ProjectDir or GCCTarget or LibExt or Lib Thank you, Harjit