How do I port the BLE Mesh example project (light switch) to my keil IDE?

[Mitch996]

Hello, I couldn't help but notice that unlike previous example projects released by Nordic, this BLE Mesh one doesn't really come in pre-configured uV5 or uV4 format. Furthermore, the makefiles that could be found in the example project directories suggest that Nordic deliberately want to be IDE-neutral.

So here is my question: is there any guide or howto written somewhere which helps me port the project to Keil? Knowing which file to add to the compile chain or to include alone can be painstaking.

I have done many port and migration before, and I did them under the philosophy "if it reports an error, fix it".

But frankly it's getting tiring on this one. I don't want another wild goose chase, there got be another way.

Please help?

[bjorn-spockeli]

Hi Mitch,

the BLE Mesh examples can be built with the armcc v5 toolchain, but we do not have a uVision v5 project for each of the examples.

I am afraid that we do not have any guide for creating Keil uVision projects for the BLE Mesh examples at this point.

However, the lack of support for the uVision IDE has been reported internally,see this question, so we're considering adding it to a future release.

Bjørn

[Mitch996]

So... in other words... I have to add files one by one manually? OK, I'll just take it as a chance to further familiarize the project and keep in mind what those modules are for. Thank you. It'll take more time but not insurmountable.

[bjorn-spockeli]

Yes, you'll have to do it manually. AFIK there is no way of importing a SES project or a Makefile based project in Keil uVision.

[Mahendra Tailor]

I managed to port all the files from the light switch to my v5 keil. But running it, I just end up in sleep_forever() Because it looks like nrf_mesh_node_config() is returning an error. I have even set the optimisation to none. (That is another story because with full optimisation, setting FLASH_MANAGER_RECOVERY_PAGE to a location means that the code thinks it is set to 0 insteaf the 0x6C000 value I am setting

Did you get very far?