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

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Port ANT-BLE HRM Relay to NRF52840-Dongle

Hello,
I want to port the "ANT and BLE Heart Rate Monitor Relay Application" to the pca10059, but it doesn't seem to work. (The led flashes fast so i guess it indicates BSP_INDICATE_ADVERTISING_DIRECTED as supposed to BSP_INDICATE_ADVERTISING )

I copied the 10056 project and did the following:

Preprocessor includes

APP_TIMER_V2
APP_TIMER_V2_RTC1_ENABLED
BOARD_PCA10059
CONFIG_GPIO_AS_PINRESET
FLOAT_ABI_HARD
INITIALIZE_USER_SECTIONS
NO_VTOR_CONFIG
NRF52840_XXAA
NRF_SD_BLE_API_VERSION=6
NRF52_PAN_74
S340
SOFTDEVICE_PRESENT
ANT_LICENSE_KEY="3831-521d-7df9-24d8-eff3-467b-225f-a00e"

Linker

FLASH_PH_START=0x0 
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0x31000
FLASH_SIZE=0xAF000
RAM_START=0x20002000
RAM_SIZE=0x3E000

I'm on 17.0.2 SDK, with the s340 on version 6.1.1

Top Replies

purpl3F0x over 5 years ago in reply to Kenneth +1 verified

Ok, for some reason now it works, lol . Thank you

Parents

0 Kenneth over 5 years ago

In general you may find this useful:
https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial

I suggest to debug over SWD to find where and what the code is executing here.
Cancel
Vote Up 0 Vote Down

Cancel
0 purpl3F0x over 5 years ago in reply to Kenneth

Hi, Kenneth I read that for configuring the linker. I think, there should be a problem with the BLE configuration. I tried a ant_hrm example and it worked. But I couldn't get the BLE blinky to work.
Cancel
Vote Up 0 Vote Down

Cancel
0 Kenneth over 5 years ago in reply to purpl3F0x

I do not think the BLE blinky example is setup to use S340.

In short you need to use the correct header files for the SoftDevice you are using, so if you are using S340 you need to use the header files found in \components\softdevice\s340\headers. You need to modify the flash and ram settings. You need to make sure that S340 is defined, so that the softdevice_handler support library knows what SoftDevice it is enabling, if you are using this library that is. You also need to change the project to load the s340 softdevice when programming. If you are using SES, you can open the -emproject in notepad and change these settings directly.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Kenneth over 5 years ago in reply to purpl3F0x

I do not think the BLE blinky example is setup to use S340.

In short you need to use the correct header files for the SoftDevice you are using, so if you are using S340 you need to use the header files found in \components\softdevice\s340\headers. You need to modify the flash and ram settings. You need to make sure that S340 is defined, so that the softdevice_handler support library knows what SoftDevice it is enabling, if you are using this library that is. You also need to change the project to load the s340 softdevice when programming. If you are using SES, you can open the -emproject in notepad and change these settings directly.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 purpl3F0x over 5 years ago in reply to Kenneth

I did all of this, for BLE Blinky for example. Change the linker flash, ram. Change s140 headers path to downloaded s340's . And on preprocessor defines the according define.
Cancel
Vote Up 0 Vote Down

Cancel
0 Kenneth over 5 years ago in reply to purpl3F0x

Did you also to the last thing I wrote:

You also need to change the project to load the s340 softdevice when programming (Project Options->common drop down->Debug->Additional load file).

If you are using SES, you can open the .emproject in notepad and change these settings directly.
Cancel
Vote Up 0 Vote Down

Cancel

0 purpl3F0x over 5 years ago in reply to Kenneth

Sorry for late reply, I tried that and doesn't seem to work. Here is the configuration when trying on the blinky app(forked from s140). With the s340 headers instead of the s140, and additional load file poiting to "ANT_s340_nrf52_7.0.1.hex"

APP_TIMER_V2
APP_TIMER_V2_RTC1_ENABLED
BOARD_PCA10059
CONFIG_GPIO_AS_PINRESET
FLOAT_ABI_HARD
INITIALIZE_USER_SECTIONS
NO_VTOR_CONFIG
NRF52840_XXAA
NRF_SD_BLE_API_VERSION=7
S340
SOFTDEVICE_PRESENT

FLASH_PH_START=0x0 
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0x31000
FLASH_SIZE=0xAF000
RAM_START=0x20002000
RAM_SIZE=0x3E000

0 Kenneth over 5 years ago in reply to purpl3F0x

I suggest to take a project you can find is already setup for the S340, copy it to a custom folder, then open the .emproject file in notepad. Then compare with the .emproject file for the pca10059 that you want to use. It will be somewhat similar to the work I did here:
https://devzone.nordicsemi.com/f/nordic-q-a/68654/connecting-via-ant-to-garmin-gsc10/281726#281726
Cancel
Vote Up 0 Vote Down

Cancel
+1 purpl3F0x over 5 years ago in reply to Kenneth

Ok, for some reason now it works, lol .
Thank you
Cancel
Vote Up +1 Vote Down

Cancel