nrf52832 resurgence

I have a 5 year old design using a nrf52832 on a MDBT42Q module. The BLE option was placed on the PCB in 2020 and has been unoccupied since going into production. My customer wants to add it now and I need to make improvements to the firmware. In looking at the VSCode vs SES option for renewing the BLE. I can't find a MDBT42Q listed in the boards. The SES option seems like it a basket of problems trying to match up the correct version of the nrf5 SDK with the SES version. I see a lot of compile failures due to SES version changes. Any advise?

Parents
  • 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

Reply
  • 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

Children
No Data
Related