Nordic Is Getting Involved in RISC-V

Re:Nordic Is Getting Involved in RISC-V by fullstop on Friday November 10, 2023 @10:51AM (#38220358)

> nRF5 is indeed inferior SDK of the 2 (thus abandoned). Also I dislike that a big chunk of the stack there is a binary blob. Regarding the code organization, not sure what toolchain you used, but the latest recommendation for nRF5 (Segger studio) could make it fairly easy to do this, but manually opening the project config files and changing them, not through the GUI.

Yes, I ended up editing the .emProject files by hand. It worked, but it felt like I was doing something wrong. I assume that you are referring to the soft device blob? Has that been abandoned in nRF Connect?

[ Parent | on HN ]

Re:Nordic Is Getting Involved in RISC-V by 5ADBEEF on Friday November 10, 2023 @11:44AM (#38221049)

There is a Zephyr BLE stack that can be used as well as a SoftDevice stack but SoftDevice isn't a huge binary anymore, much more modular to save code space.

[ Parent | on HN ]

Re:Nordic Is Getting Involved in RISC-V by wallaBBB on Saturday November 11, 2023 @04:00AM (#38228640)

> I assume that you are referring to the soft device blob? Has that been abandoned in nRF Connect?

Quite, yes. They took the ZephyrOS approach, but it comes with a learning curve penalty, unless you go the easy route of nRF Connect GUI. In that case you do have some limitations of how you organize the code base (so that the GUI works), but even that is miles ahead in configuration compared with to the nRF5 SDK + Segger Studio.

Some skim reading material about it: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/...

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/...

[ Parent | on HN ]