Softdevice S310 and interrupt

RE: Softdevice S310 and interrupt

bubune — Mon, 04 Jan 2016 23:11:58 GMT

Hi I've found the problem. The issue happen on the chibios rtos port that I'm working on. Briefly, the problem comes from the task switch context. Chibios is configured to use the PendSV interrupt.

During the switch context, in the normal port, PendSV bit is set and then interrupt are enable. PendSV Interrupt occurs immedialtly.
With softdevice, interrupt are never disable. Instead, a specific functions are called (sd_nvic_critical_region_exit/enter, with counter to avoid reentrance). soon PendSV bit is set, interrupt occur, and then never sd_nvic_critical_region_exit is called. that' why some interrupts are disable

RE: Softdevice S310 and interrupt

bubune — Thu, 02 Jul 2015 12:01:36 GMT

Any news?

RE: Softdevice S310 and interrupt

bubune — Wed, 17 Jun 2015 21:57:09 GMT

HI Stephan, I'm nearly sure that I'm doing things correctly. I've sent to Vidar my code in may (he was interrested to see the port) but I've no news from him. Have you got a chance to look at the code and let me know what's wrong?

Regrads, Bruno

RE: Softdevice S310 and interrupt

Stefan Birnir Sverrisson — Wed, 29 Apr 2015 12:31:14 GMT

Make sure you use sd_* calls when you set the interrupt priorities with the softdevice enabled, like done in e.g. this example where the ADC interrupt priority is set in line 825.

RE: Softdevice S310 and interrupt

bubune — Thu, 23 Apr 2015 22:22:37 GMT

Hi Stefan, I've tested with S310 v1.0, S210 v4.0.1 and S210 v3.0.0 and still the same behavior. I'm sure my inetrrupt priory are all set to '3'. Any idea

RE: Softdevice S310 and interrupt

Stefan Birnir Sverrisson — Fri, 27 Feb 2015 13:14:32 GMT

ok, I see. For changes between nRF51422 v2 and nRF51422 v3, look at the PCN-093 document.

RE: Softdevice S310 and interrupt

bubune — Fri, 27 Feb 2015 10:30:08 GMT

Hi Stefan,

Thanks for your answer. I don't use a specific SDK. I've ported a RTOS named Chibios on the NRF51422 with GCC. It's not enought stable yet with softdevice enabled, but I'm working on it. With some work around, I'able to enable S310 v2.0 and get HRM data sent it to the UART.

I'm going to try S310 v1.0, see it makes difference. Is there any more difference between NRF51422v2 and v3. I believed it was just RAM size?

Bruno

RE: Softdevice S310 and interrupt

Stefan Birnir Sverrisson — Thu, 26 Feb 2015 14:21:28 GMT

What SDK are you using? See the nRF51 compatibility matrix for SDK's compatible with S310 v2.0.

According to the nRF51 compatibility matrix, S310 v2.0 has not been tested with second revision nRF51 hardware that you have, i.e. nRF51422 QFAAE0, so I would recommend for you to purchase a third revision chip. The nRF51 DK has a third revision nRF51422 chip which is directly compatible with S310 v2.0 and and compatible SDK's v7.x.

The examples in SDK 7.1.0/7.2.0, which are compatible with S310 v2.0, are directly compatible with QFAC 32kB RAM chip. If you have 16kB RAM, like the QFAA chip, then you will have to modify the RAM settings in Keil -> Options for Target -> Target tab to match the 16kB RAM.

RE: Softdevice S310 and interrupt

bubune — Wed, 25 Feb 2015 09:26:30 GMT

So, I've continued to investigate and I found something very strange. If I try to enable for exeample UART Interrupt by using CMSIS function after to eanbled the softdevice, interrupt is working well. But it's not the recommanded way. We have to use the SD_nvic functions. So I've replaced the CMSIS functions by the sd_nvic function and the interrupt are not set (uart IT is never reached and the corresponding bit in the the Interrupt Enable control register @0xE000E100 is not set).

Of course, I've always checked the result the sd_ functions and they all return "NRF_SUCCESS (0)"

Any idea?

Regards, Bruno