Using UART3 in non_secure area causes constant reboots

[gonzalezjl]

Hello,

I have updated secure_boot to allow UART3 to be used in the non_secure area. However, as soon as I try to initialize it in the non_secure area a hard failure occurs as if was still protected. The system then resets and secure_boot runs endlessly.

snippet from secure_boot:

/* Configure UARTE1 as Non-Secure */
secure_boot_config_peripheral(
	NRFX_PERIPHERAL_ID_GET(NRF_UARTE1), 0);
/* Configure UARTE2 as Non-Secure */
secure_boot_config_peripheral(
	NRFX_PERIPHERAL_ID_GET(NRF_UARTE2), 0);
/* Configure UARTE3 as Non-Secure */
secure_boot_config_peripheral(
	NRFX_PERIPHERAL_ID_GET(NRF_UARTE3), 0);

I can bind to UART 1 and 2 without any issue.

Please advise.

[Håkon Alseth]

Hi,

 

UARTE3 is a shared peripheral. Are you using any of the other instances (SPIM/S 3, TWIM/S 3) ?

Could you post the failure log?

 

Kind regards,

Håkon

[gonzalezjl]

Hi,

I am not using SPI or TWI.  Since it is rebooting constantly and stream secure_boot output, I do not have an indication of failure.  

[Håkon Alseth]

Hi,

I see similar behavior when trying to use UARTE3. However; It works if I flash the application as a secure application. I'll report this back to the developers.

To verify your implementation as well: Does it work at your end if you flash it in the secure region (ie: from addr 0)?

Kind regards,

Håkon