Search Results

Hi NINO - that doesn't solve my problem exactly. I'm trying to inject the pre-proc define in at build time, from the command line script. I think what you describe is a change to the emProject file from the command line or the GUI. If I can add a preprocessor definition into the call to EMBuild, that would work. In the meantime, I'm working around it by modifying a project source file. There are those who object to the idea of pulling the code from source control, then modifying it before build.…

Does the -D option to EMBuild make the macro visible to the precompiler while my project is being built?I'm trying to automate a build of my SES project for a Nordic nRF52 processor on a custom board. I can build the project from the command line using EMBuild. I'm adding a -D APP_VER="b92662f" option to the command. But this doesn't appear to take effect in my code. Here's my call: embuild -config "Release" -D APP_VER="b92662f" E:\corp\Code\buildDir\app\app.emProject Here's the code in my proje…

Nino - clicking the X closes the displayed window, but Debug Terminal is still working in the background. I can tell because the behavior is the same whether open or closed, but more conclusively - when you re-open the Debug Terminal it has captured some of the input made to Putty while it (the Debug Terminal) was closed. Jakub - I did set echo off using the sdk_config.h file, but it had no effect. The guys at Nordic did send me some updated code that fixed my double-char problem; they said it w…

Hi, I'm trying to run a version of the command-line-interface (CLI) example from Nordic Semiconductor. The only interface is RTT. The problem seems to be that the "Debug Terminal" window opens automatically and can't be truly shut down. This interferes with access to the CLI with a terminal program like PuTTY. When PuTTY is open, it gets part of the CLI feedback, and the Debug Terminal gets the remaining parts. Same with J-Link viewer and the debug terminal. The problems with simply using the de…