NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Karl Ylvisaker — Wed, 02 Nov 2022 11:38:14 GMT

Hello,

I can not see anything that should cause this behavior from the prj.conf alone.
Would it be possible for you to send me a minimal version of this project that replicates this behavior, so that I may take a look at this myself?

Best regards,
Karl

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Hugo.Dev — Tue, 01 Nov 2022 13:13:21 GMT

Hi,

Attached my proj.conf

# Enabling assert
CONFIG_ASSERT=y

# Logger configuration
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n

# Enable temperature sensor
CONFIG_NRFX_TEMP=y

# Enable DC/DC Support
CONFIG_NRFX_POWER=y

# Enable RNG
CONFIG_NRFX_RNG=y
# Use XOROSHIRO PRNG
CONFIG_XOROSHIRO_RANDOM_GENERATOR=y

# Enable Timer
CONFIG_NRFX_TIMER2=y

# Enabling radio driver
CONFIG_NRF_802154_RADIO_DRIVER=y

# Allow sharing the RTC between IEEE 802.15.4 and Zephyr
CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT=2

# Workaround for a bug in the MPSL Glue Layer (not required for nRF52840)
CONFIG_BT=y

# Enable ring buffers
CONFIG_RING_BUFFER=y

# Set temperature sensor update period in ms
CONFIG_NRF_802154_TEMPERATURE_UPDATE_PERIOD=10000

CONFIG_NRF_802154_ENCRYPTION=n

# Shell configuration
CONFIG_SHELL=y
CONFIG_SHELL_PROMPT_UART=">"
CONFIG_SHELL_VT100_COLORS=n

#enable qspi
CONFIG_NRFX_QSPI=y

#enable spi
CONFIG_NRFX_SPI0=y

#enable uart
CONFIG_NRFX_UARTE1=y

# Debug configuration
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_DEBUG_THREAD_INFO=y

Then, I dont have any custom overlay file.

My project is using the default nrf52840dk_nrf52840.dts located at ncs\v2.1.0\zephyr\boards\arm\nrf52840dk_nrf52840

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Karl Ylvisaker — Tue, 01 Nov 2022 12:44:18 GMT

[quote user="Hugo.Dev"]Providing handler, it halts everything when trying to TX. Shell thread got unresponsive.[/quote]

Halts, without any returned error codes?
Do you have a minimal example that demonstrates this behavior, that you could share with me, in its entirety, so that I may take a look?

[quote user="Hugo.Dev"]I am not sure about the power management, the only I can see enabled in proj.conf is CONFIG_NRFX_POWER=y[/quote]

Could you share with me your entire prj.conf, and any other overlays that are active in the build configuration here?
The Power management I referenced in my previous comment is governed by the CONFIG_PM Kconfig.

Best regards,
Karl

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Hugo.Dev — Mon, 31 Oct 2022 14:19:13 GMT

Providing handler, it halts everything when trying to TX. Shell thread got unresponsive.

I am not sure about the power management, the only I can see enabled in proj.conf is CONFIG_NRFX_POWER=y

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Karl Ylvisaker — Mon, 31 Oct 2022 14:08:39 GMT

[quote user="Hugo.Dev"]I am trying to use it in blocking mode. But tried providing handler too and it is failing in a different way.[/quote]

Could you elaborate on how it fails in this case?

[quote user="Hugo.Dev"]Talking about blocking mode, I am not triggering TXSTOP. And yes, it happens every time, the call to nrf_uarte_event_check(p_instance->p_reg, NRF_UARTE_EVENT_TXSTOPPED) returns always true[/quote]

Are you using the power manager in your application?

Best regards,
Karl

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Hugo.Dev — Mon, 31 Oct 2022 14:03:58 GMT

Hi.

I am trying to use it in blocking mode. But tried providing handler too and it is failing in a different way.

Talking about blocking mode, I am not triggering TXSTOP. And yes, it happens every time, the call to nrf_uarte_event_check(p_instance->p_reg, NRF_UARTE_EVENT_TXSTOPPED) returns always true.

I am using SPI0 and QSPI (afaik there is only one, just enabling it with CONFIG_NRFX_QSPI=y)

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Karl Ylvisaker — Mon, 31 Oct 2022 13:21:35 GMT

Hello again,

[quote user="Hugo.Dev"]thanks for your answer[/quote]

No problem, I am happy to help! :)

[quote user="Hugo.Dev"]

This is the log where I get the error code:

Function: nrfx_uarte_tx, error code: NRFX_ERROR_FORBIDDEN.failed!

I am checking the error code returned by nrfx_uarte_tx, that´s where I get the error.

I am using QSPI, SPI and a couple of GPIOs. Then zephyr shell uart is enabled, using UART0.

[/quote]

Thank you for elaborating.
Which instances are you using for the QSPI/SPI?
The call to nrfx_uarte_tx fails with NRFX_ERROR_FORBIDDEN when you have not provided a handler to your UARTE peripheral during initialization, which means you are using it in blocking mode, and then triggering a TXSTOP task before the call to TX has completed.
Are you triggering this manually elsewhere in the code, perhaps to reduce power consumption?
If not, does this happen every time you attempt to call nrfx_uarte_tx? Does the call to nrf_uarte_event_check always return true when you debug this issue?

Best regards,
Karl

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Hugo.Dev — Fri, 28 Oct 2022 12:23:02 GMT

Hi, thanks for your answer

This is the log where I get the error code:

Function: nrfx_uarte_tx, error code: NRFX_ERROR_FORBIDDEN.failed!

I am checking the error code returned by nrfx_uarte_tx, that´s where I get the error.

I am using QSPI, SPI and a couple of GPIOs. Then zephyr shell uart is enabled, using UART0.

RE: NRFX UARTE TX failure (using nRF connect SDK v2.1.0)

Karl Ylvisaker — Fri, 28 Oct 2022 12:12:51 GMT

Hello,

Could you please show the entire log where you receive the error code?
I notice that the nrfx_uarte_tx call does not check its return value. Is this the exact section of the code that returns the error, or could it be returned elsewhere?
What other peripherals are you using concurrently in your project, are there any other serial interfaces enabled when this happens? If so, which, and which instances are they running on?

Best regards,
Karl