RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

Ole Bauck — Mon, 07 Mar 2016 12:34:37 GMT

You need to change to

#define GPIOTE_ENABLED 1

in nrf_drv_config.h. You may also miss some files, in that case go into "Select Software Packs.." and add the files that are missing.

RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

bob — Mon, 07 Mar 2016 10:52:00 GMT

alse some project errors.

RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

bob — Mon, 07 Mar 2016 10:43:06 GMT

I found this example is for NRF51422, so I changed project settings. 1, select device 'nRF51822_xxab' 2, set IROM1: start at '0x18000', size '0x28000' 3, set IRAM1: start at '0x20002000', size '4000'

rebuild, there are 18 errors:

Build target 'nrf51422_xxac_s110' compiling nrf_drv_gpiote.c... C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\gpiote\nrf_drv_gpiote.c(43): error: #20: identifier "GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS" is undefined nrf_drv_gpiote_evt_handler_t handlers[NUMBER_OF_GPIO_TE+GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS]; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\gpiote\nrf_drv_gpiote.c(157): error: #20: identifier "GPIOTE_CONFIG_IRQ_PRIORITY" is undefined nrf_drv_common_irq_enable(GPIOTE_IRQn, GPIOTE_CONFIG_IRQ_PRIORITY); C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\gpiote\nrf_drv_gpiote.c: 0 warnings, 2 errors compiling nrf_drv_uart.c... C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_PSEL_TXD" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_PSEL_RXD" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_PSEL_CTS" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_PSEL_RTS" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_HWFC" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_PARITY" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_BAUDRATE" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c(74): error: #20: identifier "UART0_CONFIG_IRQ_PRIORITY" is undefined static const nrf_drv_uart_config_t m_default_config = NRF_DRV_UART_DEFAULT_CONFIG; C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Drivers\3.1.0\uart\nrf_drv_uart.c: 0 warnings, 8 errors compiling app_uart.c... RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_PSEL_TXD" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_PSEL_RXD" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_PSEL_CTS" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_PSEL_RTS" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_HWFC" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_PARITY" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_BAUDRATE" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c(55): error: #20: identifier "UART0_CONFIG_IRQ_PRIORITY" is undefined nrf_drv_uart_config_t config = NRF_DRV_UART_DEFAULT_CONFIG; RTE\nRF_Drivers\nRF51822_xxAB\app_uart.c: 0 warnings, 8 errors "._build\nrf51422_xxac_s110.axf" - 18 Error(s), 0 Warning(s). Target not created.

RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

Ole Bauck — Fri, 04 Mar 2016 13:15:24 GMT

Then you need to change to SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, NULL) or similar.

RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

bob — Fri, 04 Mar 2016 11:33:05 GMT

Hi, Ole Bauck, The proximity example from SDK10 can run on my board. My board is using NRF51822QFABC0 and External XTAL 16MHz, but no XTAL 32.76khz.

RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

Ole Bauck — Wed, 02 Mar 2016 09:15:09 GMT

SDK 10 should also work fine, it has S110 examples.

RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

bob — Wed, 02 Mar 2016 06:16:02 GMT

Ole Bauck, thanks for your answer. however, when i go to newest SDK, all samples are using S130 etc., costing much more space of my NRF51822QFAB, so space not enough. i do not want to change to NRF51822QFAA. do you have any idea ?

RE: pwm can not work with softdevice, when i use s110(v7.1) , sdk 6.1

Ole Bauck — Mon, 22 Feb 2016 15:21:57 GMT

If you are using the code in pwm_example it may be because the example access some registers that are restricted when using SoftDevice, more specific NRF_CLOCK and NRF_POWER, see here. You will need to use sd_clock_hfclk_request and sd_power_mode_set instead, although these are not necessary (pwm will work fine with RC clock and not constant latency mode).

This PWM example has a high possibility of inverting when using it with a SoftDevice. I will recommend to update to our newest SDK to use the newest driver which does not have this bug. You will need to update the SoftDevice also.