Several Issues Getting Started with SES and NCS

RE: Several Issues Getting Started with SES and NCS

rupert.jtyler — Wed, 07 Oct 2020 15:04:27 GMT

That worked! Thank you for your help.

RE: Several Issues Getting Started with SES and NCS

Heidi — Wed, 07 Oct 2020 14:40:19 GMT

The non-secure version of the board does not have its own directory. In SES, you should see a drop-down menu when selecting this board, as you can see in the picture below.

RE: Several Issues Getting Started with SES and NCS

rupert.jtyler — Wed, 07 Oct 2020 13:52:13 GMT

Thanks Heidi, do you know where I can find the "thingy91_nrf9160ns" board directory? Due to the issue I had in #1, I didn't see that directory.

RE: Several Issues Getting Started with SES and NCS

Heidi — Tue, 06 Oct 2020 08:14:46 GMT

Hi!

For number three, try building your board for the nonsecure board, "thingy91_nrf9160ns".

You're seeing those errors because those configurations aren't defined for the secure board.

RE: Several Issues Getting Started with SES and NCS

rupert.jtyler — Mon, 05 Oct 2020 19:09:15 GMT

Understood, thanks for your help!

RE: Several Issues Getting Started with SES and NCS

Marciano-PL — Mon, 05 Oct 2020 19:07:27 GMT

Not necessarily true. Perhaps there is a step you missed, or added something extra to the application? It's hard for me to say with my limited info. I'd dig around a little longer and see where these Kconfig are coming from. Hopefully a Nordic FAE can chime in here.

RE: Several Issues Getting Started with SES and NCS

rupert.jtyler — Mon, 05 Oct 2020 19:04:48 GMT

Thank you, #2 worked.

For #3, it sounds like there isn't a clear direction to go, is that correct?

RE: Several Issues Getting Started with SES and NCS

Marciano-PL — Mon, 05 Oct 2020 18:57:45 GMT

2. You need to activate Segger RTT

CONFIG_PRINTK=y
CONFIG_UART_CONSOLE=n 
CONFIG_RTT_CONSOLE=y
CONFIG_USE_SEGGER_RTT=y

3. The error doesn't really have anything to do with JavaScript, rather it is telling you that you need to fix your Kconfigs. It says that BSD_LIBRARY requires you to have CONFIG_TRUSTED_EXECUTION_NONSECURE=n but it is configured to y by CONFIG_MODEM_INFO. So in short, these Kconfig symbols are incompatible. There may be even more Kconfig issues.