Search Results
Search results 1-13 of 13.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Fabian, This works great! Thank you for the help. One quick question is this documented somewhere and I just missed it? Thanks, Darren
-
Hello Nino, For example I have defined a APP_VER=$(EXT_VER) as a preprocessor macro. Running emBuild on the command line with -D EXT_VER="0.7.0" works fine and sets the static const char* VERSION_STR = APP_VER; t . What I want to do is also build from the GUI and when building from the GUI have APP_VER default to "0.0.0". I can't build from the GUI because when I compile the file that has static const char* VERSION_STR = APP_VER; t in it I get the following warnings and errors Source Code (3 lin…
-
I am trying to get this forum.segger.com/index.php/Thr…Build-Option-D-Questions/ working and have found a working solution yet. What I'm trying to do is be able to build via the GUI and have a default version string 0.0.0 be used in the build. Then when I run my CI/CD scripts with embuild I want to have a version defined via my build scripts injected into embuild. I can successfully get the version into my application when building from the embuild but I'm having trouble getting the default vers…
-
I am trying to do something similar to this post forum.segger.com/index.php/Thr…-SOLVED-EMBuild-D-option/ but I'm not having much luck. What I would like is to have a default version string defined so that a developer can build from the GUI or command line for development. When a release is going to be built then we will use the command line to build but I want to inject a specific version number during the command line build. How can I go about satisfying both requirements? Thanks, Darren
-
Hi, I just downloaded Segger Embedded Studio 4.16 and received a free Nordic License. I can install the license and everything looks fine but it still says Non-Commerical License at the top of the window and every time I build I get the "No commerical-use license detected" window. I'm running macOS Mojave. Thanks.
-
I recently upgraded to the J-Link tools to 6.40 which were bundled with an update from Nordic Semiconductor. When I now start RTT Viewer it always opens to the "Log" window. Previous versions of RTT Viewer have opened directly to the Terminal window. Is there a way to get back the previous functionality? Thanks, Darren
-
I recently updated to SystemView 2.38 from 2.36a and I am now getting a hard fault after about an hour of running. The hard fault seems to be occurring in SEGGER_SYSVIEW_OnUserStart_SYS when the RECORD_END macro is called. I can't find an large difference between the two versions. The other interesting detail is while I am running from my IAR debugger I haven't started a SystemView session and I am not recording. Any thoughts? Cheers, Darren