• State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 74 subscribers
  • Views 3520 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 249377
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Development for nRF52832: nRF5 SDK +SES or NRF Connect SDK and nRF Connect for Desktop?

martinspedro

I am starting the development of a product using the nRF52 DK for the nRF52832 SoC.

The product will use some peripherals (RTC, NVMC, Timers) and communicate using BLE and NFC with a smartphone. It will also feature Firmware updates over BLE. There is no need (at least for this stage of the product), to use any RTOS.

So far, I am unable to understand if the recommend development toolchain is to use Segger Embeded Studio with the NRF5 SDK, as detailed here, or if I should start to use already the nRF Connect SDK with the nRF Connect for Desktop, which features a SEGGER Embedded Studio Nordic Edition.

I am aware of this thread, but I believe my question is broader. What is the recommended toolchain (IDE and other tools) and SDK to use in new nRF52832 products?

Thank you in advance

Parents
  • 0

    We use the nRF5 SDK, GCC, and whatever editor each developer wants - a mix of Emacs, Visual Studio Code, and Clion. We also use the Segger Ozone debugger, and a bit of GDB. The curve ball in this setup is that we have the development environment in a virtual machine, configured with Vagrant ("infrastructure as code") so that every developer has the exact same environment no matter if they're running Windows, some obscure Linux distribution, or MacOS. This way, whenever the build environment is changed it's super quick and easy to propagate that change across the team and build systems, and when something goes wrong it's just as easy to start over from a clean setup. ;)

    The problem you're seeing with the fractured/muddy ecosystem is unfortunately very real. It's quite clear that Nordic doesn't have the software development resources to keep up with their rapidly expanding product offerings, so their efforts are being spent almost exclusively on the new shiny to the detriment of the support of their established products. Fair warning...

    • Add to Phrasebook
      • No word lists for English -> English...
      • Create a new word list...
    • Copy
  • 0 in reply to Richard

    Thank you for sharing your setup, Richard. I really appreciate the insight!

    If I understood correctly, code development is native on the developer machine and the build and debug are carried on the virtual machine configured with vagrant, right?

    Do you also use Segger build tools or opt to use a custom Makefile?

    Richard said:
    The problem you're seeing with the fractured/muddy ecosystem is unfortunately very real.

    This is my problem exactly. I see concurrent tools, IDEs and toolchains, both supported, updated and recommend and cannot understand what is really the "best choice" for development with the nRF52832 and nRF52 DK.

Reply
  • 0 in reply to Richard

    Thank you for sharing your setup, Richard. I really appreciate the insight!

    If I understood correctly, code development is native on the developer machine and the build and debug are carried on the virtual machine configured with vagrant, right?

    Do you also use Segger build tools or opt to use a custom Makefile?

    Richard said:
    The problem you're seeing with the fractured/muddy ecosystem is unfortunately very real.

    This is my problem exactly. I see concurrent tools, IDEs and toolchains, both supported, updated and recommend and cannot understand what is really the "best choice" for development with the nRF52832 and nRF52 DK.

Children
No Data
Related
Terms of service