nrf52832 resurgence

[mjscottinnc]

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?

[mjscottinnc]

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