Trouble getting started on OS X

[Christopher Hunt]

Version: Mac OS X 10.15.5 (19F101)

I'm using the nRF Connect app Getting Started Assistant and manage to get through most of it. However, when I use Segger to open up a sample project I'm faced with permissions issues trying to run executables of the embedded toolchain.

My work-around for that was to use Homebrew to install the GNU ARM Embedded toolchain as per https://github.com/osx-cross/homebrew-arm. 

With that behind me, I then moved to the next problem when attempting to open a file within Segger.

When opening "/opt/nordic/ncs/nrf/applications/serial_lte_modem/CMakeLists.txt", selecting "/opt/nordic/ncs/nrf/boards/arm/nrf52840gmouse_nrf52840" as my board directory, I'm presented with a dialog box of warnings and errors:

Including boilerplate (Zephyr base): /opt/nordic/ncs/zephyr/cmake/app/boilerplate.cmake
nrf52840gmouse_nrf52840.dts.pre.tmp:161.22-169.5: Warning (unique_unit_address_if_enabled): /soc/i2c@40004000: duplicate unit-address (also used in node /soc/spi@40004000)
  also defined at nrf52840gmouse_nrf52840.dts.pre.tmp:423.7-427.3

warning: RTT_CONSOLE (defined at drivers/console/Kconfig:119) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: CONSOLE (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_RTT_CONSOLE.html and/or look up
RTT_CONSOLE in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


/opt/nordic/ncs/nrf/applications/serial_lte_modem/prj.conf:26: warning: attempt to assign the value 'y' to the undefined symbol BSD_LIBRARY

/opt/nordic/ncs/nrf/applications/serial_lte_modem/prj.conf:41: warning: attempt to assign the value 'y' to the undefined symbol LTE_LINK_CONTROL

/opt/nordic/ncs/nrf/applications/serial_lte_modem/prj.conf:42: warning: attempt to assign the value 'n' to the undefined symbol LTE_AUTO_INIT_AND_CONNECT

warning: UART_0_NRF_HW_ASYNC (defined at drivers/serial/Kconfig.nrfx:74) has direct dependencies UART_0_NRF_UARTE && UART_ASYNC_API && (UART_0_NRF_UART || UART_0_NRF_UARTE) && UART_NRFX && SERIAL with value n, but is currently being y-selected by the following symbols:
 - SLM_CONNECT_UART_0 (defined at /opt/nordic/ncs/nrf/applications/serial_lte_modem/Kconfig:36), with value y, direct dependencies <choice> (value: y), and select condition <choice> (value: y)

error: Aborting due to Kconfig warnings

CMake Error at /opt/nordic/ncs/zephyr/cmake/kconfig.cmake:217 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /opt/nordic/ncs/zephyr/cmake/app/boilerplate.cmake:506 (include)
  /opt/nordic/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /opt/nordic/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:20 (find_package)

...continuing beyond that yields, the following error:

Any pointers? I've gone over the install steps a number of times now. I'm looking forward to doing some development with my newly purchased boards. Thanks for any help.

Cheers,

-C

[Simon]

The application serial_lte_modem is meant to run on a board with the nRF9160 (which has a modem), and that is the reason it fails. The board nrf52840gmouse_nrf52840 is not compatible with that example.

Try building the sample \zephyr\samples\hello_world and see if that works for you.

Best regards,

Simon

[Christopher Hunt]

Even if I pick the 9160 board then I still get a similar error.

However, if I build the Hello World then I get further, but fail at (what looks like) the last step:

[Simon]

Ooh.. I just saw that you used the Getting Started Assistant app, could you use the Toolchain Manager instead? It is much simpler to use and requires just a button click. Then everything will get installed in a local environment and it should all work out-of-the-box.

Follow the steps in the NCS tutorial to achieve this (The tutorial is written for NCS v1.2.0, and you may encounter some issues if using NCS v1.3.0. I will update the tutorial soon).

In this case, I also explain how to use the Toolchain Manager, check that out as well.

Best regards,

Simon

[Christopher Hunt]

Thanks again for the replies. The responsiveness to these forums is impressive.

What's the future looking like in terms of tooling. The getting started experience has been somewhat difficult to navigate. In the future, will the "getting started assistant" be the route for newcomers, or will it be the toolchain manager?

Personally, I'd like to be able to just use my Rust toolchain. :-)

[Simon]

The Getting Started Assistant App is deprecated and the Toolchain Manager App is the recommended option to follow.

Best regards,

Simon