nRF tools, software, hardware development navigation

Hello all,

looking at how to navigate with the nRF tools, hardware amd software.

For example, have designed a bit of applciation with seome peripheral drivers, but I am not sure, if I am on the right path. For example, currently working on the PCA10040, however, the module that is the final target is based on the PCA10100e. Indeed, this is not the only change that I have to consider:

1) how to deal with the fact that the module is based on the nRF52820, but I am so far working on the nRF52DK, SDK5, is there a way to transfer the code that I have done so far to the PCA10100e and start using that code on the module, actually how does someone do that?

2) at the moment the coding is done within the segger em studio and with the sdk5, however, it seems that nordic is moving to the VS Code and nRF Connect SDK, so far I would like to stay on the emStudio due to time constraints of getting used to the new IDE ... and if possible) get the mesh going with the nRF52820 that is on the module.

So, my question is do I have to move to the nRF Connect SDK or can I just complete the etape I am at with the tools I am using at the moment? In short, I do not want to worry about the transition to the new software currently, but rather focus on the app, etc.

2.1) Will the mobile apps, tools, for the nRF ... be useful in this case? For example, what nRF mobile app is best to show the proof of concept with regard to the mash networking, light switch application, blinky, etc. that enables the scenes ?

Current development setup:

- nRF52DK (PCA10040)
- nRF52820 - on pan1781 module (PCA10100e)
- nrf5SDK, emSegger

Parents
  • Dear MuRa,

    I think I can answer a few questions:

    1) PCA10040 is a nrf52840 , PCA10100e is a nRF52820
    Both are from the same nrf52 family and thus the software application is easy to transfer.
    Focus on the changing properties like available memory/ports/pins related to the MCU.

    2) nRF connect  SDK; NCS 1.9.1 is the last version supporting the SES.
    cs 2.0.0 has no support for Segger Embedded Studio.
    note: I am in the same boot as you here. i am also moving from SES to VScode with ncs 2.0.0 

    The zephyr devicetree makes the transfer easy for the mcu 's you are using.
    you can select a different board.
    note: Both board are supported by zephyr (see Boards)

    2.1)  no advice on this.

  • Hey nRF5xFanBoy

    Thanks for your input, it HELPs a lot!


    APROPOS zephyr can you say more about the benefits it brings to such a development? PS totally new to me!

Reply Children
No Data
Related