We do not currently have any plans on adding support for Keil in nRF5 SDK for Mesh. This is
due to fact that the evaluation version of Keil ARM MDK-Lite has a code size limit of 32kB. The code size of the examples in the nRF5 SDK for Mesh exceeds this limit and we have therefore chosen not to add support for Keil, but selected GCC and Segger Embedded Studio, which does not have any code size limitations.
We do not currently have any plans on adding support for Keil in nRF5 SDK for Mesh. This is
due to fact that the evaluation version of Keil ARM MDK-Lite has a code size limit of 32kB. The code size of the examples in the nRF5 SDK for Mesh exceeds this limit and we have therefore chosen not to add support for Keil, but selected GCC and Segger Embedded Studio, which does not have any code size limitations.
Thank you for the update. Is there a dedicated reason for the missing support of Keil? We have chosen Keil as our compiler for BLE projects because it seemed to be the compiler with best support from you. So it's a bit a disappointment that the new features are coming for our compilers only.
@myjtag: As previously mentioned we do not currently have any plans on adding support for Keil. However, if a lot of customers ask for/need Keil support then this is obviously something that we need to take in to consideration. I suggest that you contact your Nordic Sales representative and inform him about your requirements and then he will pass this on to Product Management.
Is there any news in this topic? In the current release of the Mesh SDK 3.1.0 there is still no support for uVision.
I've tried to integrate the mesh in our current uVision project, but it always ends in a Softdevice Assert after enabling the mesh stack. Has anybody success with using the Mesh SDK with uVision projects? What problems did you have and how could you resolve them?
