nrf52832 resurgence

RE: nrf52832 resurgence

SwRa — Wed, 20 Aug 2025 13:58:52 GMT

Hi Micheal,

I just checked this with the expert and heard back the following: "Assuming you have configured the correct configuration(There is Common, Debug, and Release).
You might need to restart SES to ensure it re-parses the .emProject file"

Regards,

Swathy

RE: nrf52832 resurgence

mjscottinnc — Tue, 29 Jul 2025 17:31:43 GMT

SES v5.42a installed and it does now compile and link SDK 17, however (dot)emProject file still does not update the Preprocessor Defines in the Project->Option common window?

RE: nrf52832 resurgence

SwRa — Tue, 29 Jul 2025 12:35:41 GMT

Hi Michael,

Could you try downgrading to SES v5.42a.? We used SES 5.42a for testing and verification of nRF5-SDK 17.1.0.

Regards,

Swathy

RE: nrf52832 resurgence

mjscottinnc — Thu, 24 Jul 2025 15:30:54 GMT

No I started development 5 years ago. Using the nRF connect app on Andriod (as a server) and the nRF Uart example loaded into the MDBT42Q I was able to verify hardware functionality between the microcontroller which connects to the MDBT42Q on my customers board. The hardware design was locked in and the PCB and has been in production since then with the BLE option not populated. Now the customer wants to start populating the boards and wants the some additional functionality. So I have a proven hardware system and all I need is to write the embedded app.

In another question, since I had not received a reply I start down the path of using the SES, I updated the SES from version 4.12 (which was used in the original development) to 8.24. I also downloaded the nRF5 SDK version 17.1.0 (the original testing was using 16.0.0). I soon learned that the memory map was defective in 17 as the original nRF Uart example would not compile and link. The question is, are you aware that the (dot)emProject file does not update the Preprocessor Defines in the Project->Option common window? It is obvious that the compiler and linker see the defines, but the window shows nothing. Is there any fix for this? Since I started down the SES path I'll finish my work there for now.

Thank you and I'm awaiting you reply

RE: nrf52832 resurgence

SwRa — Thu, 24 Jul 2025 12:34:53 GMT

Hi Michael,

You are correct that the MDBT42Q is not listed as a default board in either the nRF5 SDK (for use with Segger Embedded Studio, SES) or in the nRF Connect SDK (for use with VS Code). However, the MDBT42Q module is based on the nRF52832 SoC, which is fully supported by both SDKs. This means you can use the reference board definitions for the nRF52832 (such as PCA10040) as a starting point for your development. I understand that you have not started development and is looking to choose which among the two SDK's needs to be used.. Is that right.?

Regards,

Swathy