Problem with setting up SEGGER on MAC

RE: Problem with setting up SEGGER on MAC

pemar13 — Thu, 04 Jun 2020 14:53:06 GMT

Your more than welcome Edgar!

Please note Case 250739 I just submitted: using the above scheme, I cannot get ncs v1.3.0 rc1 to work.

Best regards,
Per

RE: Problem with setting up SEGGER on MAC

edgars.dev — Tue, 02 Jun 2020 10:27:55 GMT

Please, don't be sorry and huge thanks for your help! Finally, with your help, got through setup process and build was succesful.

RE: Problem with setting up SEGGER on MAC

pemar13 — Thu, 28 May 2020 11:17:57 GMT

Hi Edgar!

Sorry to jump in, but I have struggled a lot before finally getting SES to work reliably in macOS (especially Catalina) before finally trying python virtual environments. The only(?) caveat is that you have to start SES from a terminal.

Since I had made a lot of failed attempts at getting things to work, I started with a complete uninstall of HomeBrew. Then, I basically followed the instructions in the nrFConnect Getting Started Assistant with the following additions (not sure how important each step is, but the end result is good):

1. After extracting the GNU ARM Embedded tar to /opt/gnuarmemb, install the nRF Command-Line Tools (nRF Tools and J_LINK).

2. After installing west and cloning the repos to the ncs folder of my choice, in the terminal:
a. Create a Python virtual environment: python3 -m venv Path/To/ncs120 (or whatever folder name you choose)
b. Activate the Python virtual environment: source path/to/ncs120/bin/activate

3. Then, still in the terminal, install the required Python modules:
a. pip3 install -r zephyr/scripts/requirements.txt
b. pip3 install -r nrf/scripts/requirements.txt
c. pip3 install -r bootloader/mcuboot/scripts/requirements.txt

After extracting the SES to /Applications/Path/To/SES (or whatever folder name you choose) start SES as follows:
A. Open a terminal
B. Activate the Python virtual environment: 'source path/to/ncs120/bin/activate'
C. Start SES: "/Applications/PathTo/SES/Segger Embedded Studio for ARM 4.52.app/Contents/MacOS/emStudio"

Ensure the correct paths in your .bashrc/.zshrc file:
export PATH="$HOME/Library/Python/3.7/bin:$PATH"
export PATH="/Applications/Nordic Semiconductor/nrfjprog:$PATH"
export PATH="/Applications/Nordic Semiconductor/mergehex:$PATH"
export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
export GNUARMEMB_TOOLCHAIN_PATH=/opt/gnuarmemb
export ZEPHYR_BASE=/Volumes/MacData/Users/pemar/Develop/Nordic/ncs/zephyr
source /Volumes/MacData/Users/pemar/Develop/Nordic/ncs/zephyr/zephyr-env.sh

Ensure that the SES Options for RF Connect CMake and Executable are set to None; the Directories for ARM Embedded Toolchainand Zephyr Base must be set correctly

One "bonus" is that you can start multiple instances of SES by repeating the steps A-C from a new terminal window.

I hope I didn't miss anything. Good luck!
/Per

RE: Problem with setting up SEGGER on MAC

edgars.dev — Wed, 27 May 2020 11:30:31 GMT

I know that, I tried both. But it doesn't change anything regarding to my problem.

RE: Problem with setting up SEGGER on MAC

Simon — Wed, 27 May 2020 10:59:32 GMT

Check the comment in NCS tutorial part 1 - nRF9160 DK:

"The modem always operates in a non-secure domain (read more about this in External domain access control on the infocenter), and the application must do the same in order to communicate with it. Therefore, all the samples in <..>/nrf/samples/nrf9160 as well as the asset_tracker, have to be built as nonsecure in order to work."

Therefore, you have to choose the nonsecure version of the board in the nRF Connect Options. Set Board name equal to thingy91_nrf9160ns instead of thingy91_nrf9160.

Best regards,

Simon