NRF52805 with nrf connect 1.8.0

[matangk]

Hi,

I'm developing a miniature application on nrf52805. I got an nrf52-dk and I am trying to understand which SDK i should use. 

So far my problem is that on one hand - VS code and nrf connect are recommended for new applications, ad look like the correct way moving forward.

On the other hand, the only reference for using nrf52805 by porting nrf52810 designs or emulating on nrf52832 exist for nrf5, sdk 1.7.0, with SES ADE.

Any advice? I will be happy to know if there exist newer instructions or examples.

Thanks!

[Sigurd Hellesvik]

Hi

In case you have not seen it yet, check out our nRF Connect SDK and nRF5 SDK statement.

Developing for the nRF52805 using the nRF Connect SDK should work fine.
For starters, check out the nRF52805 emulation on nRF52 DK board definition.

If you are new to the nRF Connect SDK, board definitions work like this:
When you build, you need to define which board you build for, like this: "west build -b nrf52840dk_nrf52840".
Then the build will work for that board. Now the same project could be built for any other board(*), and will work for them as well.

((*) This is given that they support the same features. Pin/peripheral routing and configurations can be specified different for different boards, using overlays.)

As far as I can see, we do not have a board definition included in Zephyr at this time. Have a look at this Getting started with custom development in nRF Connect SDK Webinar and our Application developement documentation to create a custom board for your project when you get to that.

Did this answer your questions?

Regards,
Sigurd Hellesvik

[matangk]

Hi, this helps, thanks. So, as far as I understand developing on 52dk, using the appropriate gpios and peripherals, and compiling for 52dk_52805 should work fine on vs code? I'll give it a try.

Unfortunately your reference to https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.8.0/zephyr/boards/arm/nrf52dk_nrf52805/doc/index.html

Does not provide concrete "how to" details, but I'll start with the dk and we'll see about the port.

Zephyr is an RTOS, right? My application does not require one, just event->task. Would you recommend to start from the nrf/uart service example?

For some reason, in my installation, if I start an application from the welcome page, the only templates available with zephyr are workspace applications. Am I missing some definitions? This might be am issue for a different ticket. 

Cheers,