fail to generate a TXDRDY Interrupt

RE: fail to generate a TXDRDY Interrupt

Torsten Robitzki — Wed, 28 Jan 2015 15:01:30 GMT

Hi Stefan, thanks for the explanation. With my question, there comes a more general question: where was I supposed to get that information? I spend hours to figure out how this UART is working and read every single letter in that chapter at least twice. In 10.1.4 of the reference, I read: „Events can be generated by the peripheral even when the event register is set to ‚1‘.“ and in 10.1.6 „An interrupt is an exception that is generated by an event …“; so to me it sounds like it’s not necessary to reset the event register. There should be at least some explanation in the UART documentation, that one have to reset the event.

Anyway: Thank your for taking the time for your answer :-)

Cheers Torsten

RE: fail to generate a TXDRDY Interrupt

Torsten Robitzki — Wed, 28 Jan 2015 12:37:31 GMT

Hi Stefan, thank you for replying. No, my plattform is a bare metal nrf51422 with s210 or s310 (depends on the device in a system with multiple nrf51422).

RE: fail to generate a TXDRDY Interrupt

Stefan Birnir Sverrisson — Wed, 28 Jan 2015 12:31:10 GMT

Hi Torsten

Thank you for your question. Is you platform the nRF51822 mBed kit? For those questions, the mbed forum is perhaps better suited for your question.

Update 28.1.2015 When the TXDRDY flag is set, an interrupt is generated. So it is needed to clear the TXDRDY flag in order to get a second interrupt.

I guess disabling the interrupts is required in order for the interrupt_service() and update() functions not conflicting with each other, since they are accessing the same memory addresses. That could be the case if the two processes have different priorities, then one process could interrupt the other.