uVision V5.16a GPIOTE error on compilation

[mc]

Hi,

I am new to Nordic. Will someone help me figure out what is wrong with UVision V5.16a. I get sample codes from pack installer example the "ble_app_hrs_s310_pca10028" for nRF51422xxAC and compile it using Uvison v5.16a.

My problem is that, the uVision always has an error during compilation of sample programs. The problems are:

1. C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.0.1\gpiote\nrf_drv_gpiote.c(43): error: #20: identifier "GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS" is undefined

2. C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.0.1\gpiote\nrf_drv_gpiote.c(157): error: #20: identifier "GPIOTE_CONFIG_IRQ_PRIORITY" is undefined

Do I need some configuration setting in order to eliminate this error? Or the sample code are to be modified to work correctly?

Below are my configuration setting:

*******************************uVision5.16a ****************************************** License Information:

---

---

LIC=----

Tool Version Numbers: Toolchain: MDK-Lite Version: 5.16a Toolchain Path: C:\Keil_v5\ARM\ARMCC\Bin C Compiler: Armcc.exe V5.06 (build 20) Assembler: Armasm.exe V5.06 (build 20) Linker/Locator: ArmLink.exe V5.06 (build 20) Library Manager: ArmAr.exe V5.06 (build 20) Hex Converter: FromElf.exe V5.06 (build 20) CPU DLL:
Dialog DLL:
Target DLL: Segger\JL2CM3.dll V2.99.15.2 Dialog DLL: TARMCM1.DLL V1.9.0.0

PACK INSTALLER************* Version: 1.3.7.0

My nRF51 kit is loaded with "s310_nrf51422_3.0.0_softdevice.hex" using nRFgo Studio with QT version 5.3.2.

Thanks for the help.

[Susheel Nuguru]

Why are you using hrs_s310? are you working with ANT protocol as well? If not then you should use nRF51_SDK_9.0.0_2e23562\examples\ble_peripheral\ble_app_hrs\pca10028\s130 example. You should also program softdevice first from

nRF51_SDK_9.0.0_2e23562\components\softdevice\s130\hex

before you program your application. If you have already done all that then you should try to debug and see at what point your code is resetting the chip.

Normally any error in APP_ERROR_CHECK fail will cause a system reset in app_error_handler. The behaviour you are seeing could be just some function failing and the macro APP_ERROR_CHECK resetting your device. Search this forum about it, there should be a lot of info.