This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Load firmware mesh examples into PCA10056 using Segger Embedded

Hi,

I was trying some examples of the SDK 13 and 14 for keil but now I need to undestand how works the ble mesh.

I did the download of the SDK mesh, and there are only segger's project.

I am trying to do the load of the firmware (light switch client/server) to nordic board (NRF52840) and this examples works when I use the Debug >> Go options... The problem is that when I turn off the board and remove the usb cable, the firmware is not save in the board.

I wanna know how I can load the firmware (SDK mesh examples) using SEGGER, looks like the load button in the keil. Do I need a JLink programmer to do it?

I tried also to load the firmware by command line: nrfjprog --program <dir>/light_switch_client_nrf52840_xxAA_s140_5_0_0-3_alpha.hex (Using the SDK 14/13 examples it works) but using the hex files generated from SEGGER, doenst works.

Thanks

Parents
  • Hello Renato,

    If you are simply trying to learn/familiarize yourself with Bluetooth Mesh then I would suggest that you don't use any Mesh SDKs prior to v1.0.1. Many of the issues that you may 'discover' when using a prior Mesh SDK would have possibly been reported by other developers and fixed in the 1.0.1 version. Additionally, some of the functionality in the examples has been enhanced in the Mesh SDK v1.0.1 code drop.

    If you are looking to build for both the PCA10040 and PCA10056 boards, then simply download the Nordic Mesh SDK v1.0.1 from this link. I would then recommend that you follow the instructions in this post to get the Segger Embedded Studio (SES) project files for the PCA10056/NRF52840 board (look for the attached examples.zip file in Hung Bui's response). My understanding is that inclusion of the PCA10056 project files was simply an oversight when the v1.0.1 Mesh SDK was packaged so this step should not be required in future Mesh SDK code drops.

    Once you have both Mesh SDK v1.0.1 and the examples.zip file in place, then I would recommend that you erase all the boards you will be using via either the nrfjprog -s xxxxxxxxx --family nRF52 -e command or whatever your preference may be (the caveat here is that you erase all remnants of any previous mesh configuration data).

    From there, build and flash your boards with the relevant softdevice and example firmware (This step should be done automatically by SES when you select the Debug->Go or Target->Download... menu optons). Alternatively, you can also use nrfjprog to manually flash the softdevice and .hex files to your relevant boards (if nrfjprog is used, don't forget to issue the nrfjprog -s xxxxxxxxx --family nRF52 -r command after flashing the softdevice & hex files)

    If you still run into issues after following the above, then post back and we can try to help you further (at least knowing that you are running the latest Mesh SDK and examples)

    Regards,

Reply
  • Hello Renato,

    If you are simply trying to learn/familiarize yourself with Bluetooth Mesh then I would suggest that you don't use any Mesh SDKs prior to v1.0.1. Many of the issues that you may 'discover' when using a prior Mesh SDK would have possibly been reported by other developers and fixed in the 1.0.1 version. Additionally, some of the functionality in the examples has been enhanced in the Mesh SDK v1.0.1 code drop.

    If you are looking to build for both the PCA10040 and PCA10056 boards, then simply download the Nordic Mesh SDK v1.0.1 from this link. I would then recommend that you follow the instructions in this post to get the Segger Embedded Studio (SES) project files for the PCA10056/NRF52840 board (look for the attached examples.zip file in Hung Bui's response). My understanding is that inclusion of the PCA10056 project files was simply an oversight when the v1.0.1 Mesh SDK was packaged so this step should not be required in future Mesh SDK code drops.

    Once you have both Mesh SDK v1.0.1 and the examples.zip file in place, then I would recommend that you erase all the boards you will be using via either the nrfjprog -s xxxxxxxxx --family nRF52 -e command or whatever your preference may be (the caveat here is that you erase all remnants of any previous mesh configuration data).

    From there, build and flash your boards with the relevant softdevice and example firmware (This step should be done automatically by SES when you select the Debug->Go or Target->Download... menu optons). Alternatively, you can also use nrfjprog to manually flash the softdevice and .hex files to your relevant boards (if nrfjprog is used, don't forget to issue the nrfjprog -s xxxxxxxxx --family nRF52 -r command after flashing the softdevice & hex files)

    If you still run into issues after following the above, then post back and we can try to help you further (at least knowing that you are running the latest Mesh SDK and examples)

    Regards,

Children
No Data
Related