nRF Connect SDK v1.1.0 not having pca20035 board

RE: nRF Connect SDK v1.1.0 not having pca20035 board

Akash Patel — Mon, 23 Dec 2019 17:44:27 GMT

Hi Luis,

To change CONFIG_ENVIRONMENT_DATA_SEND_INTERVAL in Segger Embedded Studio (SES), you can go to Project -> Configure nRF Connect SDK Project... -> menuconfig. Then in the top right filter, you can search for environment and you will find the relevant parameter that you can change. Then be sure to press configure once you are done. This will change the .config in ncs\nrf\applications\asset_tracker\build_nrf9160_pca20035ns\zephyr and place your previous configuration in .config.old.

If you open the autoconf.h file in ncs\nrf\applications\asset_tracker\build_nrf9160_pca20035ns\zephyr\include\generated, you will see that the CONFIG_ENVIRONMENT_DATA_SEND_INTERVAL has now changed to your given parameter.

Documentation for this example can be found here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker/README.html

RE: nRF Connect SDK v1.1.0 not having pca20035 board

Luis Alberto — Fri, 20 Dec 2019 20:41:52 GMT

Hi Akash,

My bad, I overlooked the path, I can download the binary now, thanks!

I want to decrease the period with which the data is send to nrfcloud...

I see that there is a delay in sending the events to send_env_data_work, to be CONFIG_ENVIRONMENT_DATA_SEND_INTERVAL, but it is defined in 3 configs.c, which is the one used by the application? where can I start looking into how this sample app works?

k_delayed_work_submit(&send_env_data_work,K_SECONDS(CONFIG_ENVIRONMENT_DATA_SEND_INTERVAL));

RE: nRF Connect SDK v1.1.0 not having pca20035 board

Akash Patel — Wed, 18 Dec 2019 22:25:33 GMT

Hi Luis,

The board for the Thingy:91 is in the NRF folder as Heidi mentioned and not the zephyr folder like the nRF9160 DK is. You should navigate to ncs\nrf\boards\arm\nrf9160_pca20035

You can also find the nrf52840_pca20035 in the same path (\ncs\nrf\boards\arm) which is used for developing for the nRF52840 on the Thingy:91 board.

RE: nRF Connect SDK v1.1.0 not having pca20035 board

Luis Alberto — Wed, 18 Dec 2019 19:42:32 GMT

[quote userid="82276" url="~/f/nordic-q-a/55763/nrf-connect-sdk-v1-1-0-not-having-pca20035-board/226157"]Are you using a terminal or SES?[/quote]

I am using powershell to configure the repos and west as nRF Connect 3.3.0 - getting started assistant suggested. Is this what you wanted to know?

[quote userid="82276" url="~/f/nordic-q-a/55763/nrf-connect-sdk-v1-1-0-not-having-pca20035-board/226157"]The board folder for the Thingy:91 can be found in ncs/nrf/boards/arm (either nRF9160_pca20035 or nRF52840_pca20035).[/quote]

As I'm programming the nrf9160 which is the one that interfaces with the sensors and report that data over the LTE-M (which is what I want to modify) I was assuming that I needed to select nRF9160_pca20035 board... can I use the nRF52840_pca20035 if I want to flash the nrf9160? anyway that isn't available in my setup...

[quote userid="82276" url="~/f/nordic-q-a/55763/nrf-connect-sdk-v1-1-0-not-having-pca20035-board/226157"]Where are you trying to select this board? [/quote]

When loading the board in the open nRF connect SDK project menu in SES:

This is the tag I am using for the nrf repo

I did checkout to that tag then proceed to use "west update" as per nRF Connect 3.3.0 - getting started assistant instructed...

I do not know what else I can tell to provide more insight on what might be happening...

Thanks for the help!

RE: nRF Connect SDK v1.1.0 not having pca20035 board

Heidi — Wed, 18 Dec 2019 13:30:10 GMT

Hi!

[quote user=""]notice there is no pca20035 board to select.[/quote]

Where are you trying to select this board?

The board folder for the Thingy:91 can be found in ncs/nrf/boards/arm (either nRF9160_pca20035 or nRF52840_pca20035).

Are you using a terminal or SES?

[quote user=""]My ultimate goal is to flash the 9160 in the thingy91 using an nrf9160 dk (I have both devices and the cable) and want to do small changes to the code to start getting into it and do my own stuff.[/quote]

This should absolutely not be a problem! We just need to figure out why you can't select pca20035.

Best regards,

Heidi