nrf_serial UART on nRF52840 sdk 15

RE: nrf_serial UART on nRF52840 sdk 15

mtfurlan_t — Fri, 29 Jun 2018 14:57:01 GMT

Many thanks.

RE: nrf_serial UART on nRF52840 sdk 15

Vidar Berg — Fri, 29 Jun 2018 14:50:38 GMT

You can find the ARM documentation of the interrupt status register here, and the ISR numbers used on nrf52840 can be found in the nrf52840.h header (\modules\nrfx\mdk).

Notice that processor exceptions starts from -15 so POWER_CLOCK_IRQn corresponds to 16 in the interrupt status register.

RE: nrf_serial UART on nRF52840 sdk 15

mtfurlan_t — Fri, 29 Jun 2018 14:26:50 GMT

Fair enough, I was noticing that it wouldn't crash if I disabled the app timer, so I thought it was something there.

Where is the documentation on the ISR numbers?

RE: nrf_serial UART on nRF52840 sdk 15

Vidar Berg — Fri, 29 Jun 2018 10:09:50 GMT

Thanks for the update. '10' is the POWER_CLOCK_IRQn so it seems that the problem was related to the clock configuration, not UARTE.

RE: nrf_serial UART on nRF52840 sdk 15

mtfurlan_t — Thu, 28 Jun 2018 19:42:09 GMT

So I tried again from scratch, and it works. I clearly touched something I shouldn't have and didn't notice.
Sorry about the confusion.

Once again, the issue is user error.

RE: nrf_serial UART on nRF52840 sdk 15

mtfurlan_t — Thu, 28 Jun 2018 17:20:51 GMT

That's `10` for me, not `12`.
Could we get a new example of using both UARTs in SDK 15?

RE: nrf_serial UART on nRF52840 sdk 15

Vidar Berg — Tue, 19 Jun 2018 08:33:40 GMT

I'd suggest to check the interrupt status register to confirm if the default IRQ handler is triggered by one of the UART instances.

Eg., run nrfjprog --readregs after the program has entered the default handler.

RE: nrf_serial UART on nRF52840 sdk 15

mtfurlan_t — Mon, 18 Jun 2018 13:38:27 GMT

I do not have -flto enabled.

I tried switching to 6.3 2017-q2-update but did not see any difference.

RE: nrf_serial UART on nRF52840 sdk 15

Vidar Berg — Mon, 18 Jun 2018 07:47:42 GMT

Hi,

It's possible that you're seeing this bug if you have enabled link time optimization (-flto) : https://bugs.launchpad.net/gcc-arm-embedded/+bug/1747966 . Please try the GCC ARM Embedded 6.3 2017-q2-update release and see if you get the same result. This is the release we used for testing and validation of SDK 15.0.0 (stated in release notes).