DUAL CORE

[konsang]

Hi,

Just to share my though here.

I think it is better way to decouple the BLE and application with dual core design.

It help to get rid of application latency due to BLE processing.

Having BLE and application sharing same core may cause inconsistent behavior to the application.

Thanks

[ovrebekk]

Hi

It is true that you will see some interrupts in the application because of BLE stack processing, but there are several features in the nRF52 series of devices to minimize this the issue. 

For one you have DMA on most peripherals, allowing them to operate seamlessly during radio interrupts, and you also have the PPI controller that allow you to send status signals between peripherals in the background.

For input on future products you should talk to one of our sales representatives. If you don't know who this is just send me a private message, and I will put you in touch with one. 

Best regards
Torbjørn

[konsang]

Hi, 

I have application to decode the IR signal. 

The IR data is encoded using pulse distance method. 

In my previous microchip controller project, I am using rising edge external interrupt, to check when there is a start of IR pulse. 

Then, I get the current  timer1 value when there is a start of IR pulse.

So, I will have start time and end time between pulse. Then, I will able to calculate the distance between pulse.

The micro-controller is in sleep mode and wake up by the external interrupt.

If using nRF52840, the BLE processing will delay the interrupt trigger . Thus, the timer value obtained will have latency. 

The pulse distance calculated will be wrong. 

I need to make application very low power as well.

Please advise what is correct method to do if using nRF52840, so that the pulse distance can calculated accurately. 

Thanks

 

 

[ovrebekk]

Hi

This sounds like a perfect application for the task and event subsystem in the nRF52 device. 

Basically you can setup the GPIOTE module to create different events on the falling and rising edge of your input, and connect these events to a TIMER module through the PPI to have the timer measure the length of the pulse automatically. 

This question has been asked before, and for more information I would suggest you have a look at the following case:
https://devzone.nordicsemi.com/f/nordic-q-a/33318/how-to-decode-pwm

Best regards
Torbjørn