Problem bringing up custom board with custom board file

RE: Problem bringing up custom board with custom board file

Thomas — Fri, 25 Apr 2025 07:13:13 GMT

The project where it is working is in git and devops. But copying all CONFIG from that (working) project does not fix the problem in the new project.

RE: Problem bringing up custom board with custom board file

Sigurd Hellesvik — Thu, 24 Apr 2025 16:06:56 GMT

[quote user="tmaltesen"]forgot how. Now I have a new taget with nRF9151 and I get the same problem again...[/quote]

I can highly recommend git! (or other version control) If you start using git from now, you can go back and check the fix next time you change the target.

If you want me to help this time, you can answer the previous questions I asked, and we can take it from there I guess.

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 23 Apr 2025 17:10:06 GMT

I did fix it in my old target, really stupid forgot how. Now I have a new taget with nRF9151 and I get the same problem again...

Application asserts in stdio_uart() on second call comming from a SPU_IRQHandler().

I am so mad at myself for not knowing the fix... I have used a whole day without figuring it out. I can remove the error by removing uart2 from the device tree, and I get the error if I insert it again. Note my uart2 has modbus part in it.

RE: Problem bringing up custom board with custom board file

i21-mehdi — Wed, 12 Mar 2025 15:41:39 GMT

Did you have any progress on this error? I'm having the same problem that does not happen everytime...

RE: Problem bringing up custom board with custom board file

Sigurd Hellesvik — Fri, 14 Jun 2024 13:43:26 GMT

[quote user="tmaltesen"]The problem that I am stuck at, seems to be that the function stdio_uart() are called more than one time as soon as I declare more that one uart.[/quote]

How do you declare your uarts?

What do you intend to use the uarts for?

Could you share your uart code?

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 15:25:52 GMT

The problem that I am stuck at, seems to be that the function stdio_uart() are called more than one time as soon as I declare more that one uart. It does not matter if it is uart1 or uart2 that are added.

Both call are initializeing uart0

I have just tried to swap the usage of uart0 and uart2, same result still an assertion.

This ASSERT in line 94 of uart_stdout.c is causing the problem, the error is NRFX_ERROR_INVALID_STATE returned internally by nrtx_uarte_init().

Both calls to stdio_uart() are initializing uart0.... through the Driver_USART.c module.

Looking on the call stack.

The first call is comming from main().
But the second call is originating from SPU_IRQHandler() through dump_error....

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 15:23:00 GMT

Both call are initializeing uart0

I have just tried to swap the usage of uart0 and uart2, same result still an assertion.

This ASSERT in line 94 of uart_stdout.c is causing the problem, the error is NRFX_ERROR_INVALID_STATE returned internally by nrtx_uarte_init().

Both calls to stdio_uart() are initializing uart0.... through the Driver_USART.c module.

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 14:55:37 GMT

Could it be related to the use of Segger RTT. In the project I really do not want to use any uart for console or logging. But since uarts kept on causing problems, I have kept uart0.

I have the following in prj.conf that shoud stop console on uart and use RTT instread.

# Logging

CONFIG_LOG=y

CONFIG_LOG_MODE_DEFERRED=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

CONFIG_UART_CONSOLE=n

CONFIG_LOG_BACKEND_RTT=y

CONFIG_NRF_MODEM_LIB_TRACE=n

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 14:52:59 GMT

If i set the uart2 to status disabled, the application will run and connect.

&uart2 {

status = "disabled";

};

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 14:47:56 GMT

If I remove everything except status I am unable to compile. The pinctrl-0 is required.

devicetree error: 'pinctrl-0' is marked as required in 'properties:' in C:/ncs/v2.6.1/zephyr/dts/bindings\serial\nordic,nrf-uarte.yaml, but does not appear in <Node /soc/peripheral@40000000/uart@a000 in 'C:/ncs/v2.6.1/zephyr/misc/empty_file.c'>

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 14:37:34 GMT

Same happens if I change the declaration to be &uart1 {...
I have checked the ID, it is spi and twi that uses ID 10, I am not using any of these...

RE: Problem bringing up custom board with custom board file

Sigurd Hellesvik — Wed, 12 Jun 2024 14:03:01 GMT

Here is a guess:

https://infocenter.nordicsemi.com/topic/ps_nrf9160/memory.html?cp=2_1_0_3_1_1#topic

UART2 has ID10. You cannot use peripherals with the same ID at the same time.
Make sure you do not have any of the other ID 10.

[quote user="tmaltesen"]

&uart2 {

status = "okay";

current-speed = <9600>;

pinctrl-0 = <&uart_rs485_default>;

pinctrl-1 = <&uart_rs485_sleep>;

pinctrl-names = "default", "sleep";

};

[/quote]

Try to remove everything but the status, does that still crash stuff?

Try to set this to "disabled", does that crash stuff?

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 13:38:07 GMT

I have made a demonstration of the problem in the attached project. Im on version 2.6.1 of SDK and toolchain.

This only requires a nRF9160_DK board.

The project have two build versions. One is the original nrf9160_dk_nrf9160 board configuration. The other is the one that I have made from a copy. I have removed declaration of I/O I do not need.

In the attached version both builds will run and connect to the network.

devzone.nordicsemi.com/.../pmi8004a2_5F00_nrf9160.zip

devzone.nordicsemi.com/.../PMI8004c.zip

But in the pmi8004a2_nrf9160 board, the file pmi8004a2_nrf9160_common.dtsi contains an outcommented declation of uart2 as described above.

If this declaration is reintroduced, the application will not run.

Any change that you can take a look?

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 12 Jun 2024 13:10:52 GMT

I had to leave the problem for a while.Now I'm back and really needs this device to run.

Since it seems that it is the board configuration, I restarted with a new copy of the nrf9160_dk_nrf9160 board, and slowly adopted to my hardware, removing unused declarations and adding new.

I am testing on the nrf9160_dk hardware.

When I introduce uart2 in the dts file the applications fails.

The difference betwwen an application running or not running is this dts statement: When this is added application wont run.

&uart2 {

status = "okay";

current-speed = <9600>;

pinctrl-0 = <&uart_rs485_default>;

pinctrl-1 = <&uart_rs485_sleep>;

pinctrl-names = "default", "sleep";

};

The application fails to start hanging in an assertion. I will fail in this function on the first ASSERT_HIGH (this is from uarts_stdout.c):

void stdio_init(void)

{

int32_t ret;

ret = STDIO_DRIVER.Initialize(NULL);

ASSERT_HIGH(ret);

ret = STDIO_DRIVER.PowerControl(ARM_POWER_FULL);

ASSERT_HIGH(ret);

The application I am running is without any modifications to the sample, except configuration values for DPS. I am running same application with nrf9160_dk_nrf9160 board and my modified version of the same.

RE: Problem bringing up custom board with custom board file

Sigurd Hellesvik — Fri, 03 May 2024 14:32:30 GMT

I was able to reproduce the issue, and observe the following log from TF-M

FATAL ERROR: Platform external interrupt (IRQn): 0x00000003
Platform Exception: SPU Fault

When I remove everything but the CONFIG_MODBUS and CONFIG_BOOTLOADER_MCUBOOT I also get this error.

The error is specifc for your boards build target, and not for the nRF9160dk.

Here is the modified project:

devzone.nordicsemi.com/.../azure_5F00_iot_5F00_hub_5F00_2_5F00_urd.zip

When I put your board inside the project like that, you can build it from the project by selecting the board in VS Code from "Custom boards".

This is as far as I go now.
Next up, you should compare board files for nRF9160DK and your custom board until you find which difference causes the issue.

RE: Problem bringing up custom board with custom board file

Thomas — Wed, 01 May 2024 11:06:13 GMT

devzone.nordicsemi.com/.../azure_5F00_iot_5F00_hub_5F00_2.zip devzone.nordicsemi.com/.../pmi8004a1_5F00_nrf9160.zipYes - I does not compile directly to DK because the modbus is missing in the device tree for the DK. My my board definition can be loaded into the DK and seems to do same but of course modbus is not available but can be compiled in and activated.
I will attach both my board and my project.

RE: Problem bringing up custom board with custom board file

Sigurd Hellesvik — Mon, 29 Apr 2024 11:41:19 GMT

Are you able to build a project with this error for a Development Kit?
If so, I could test it on my end.

RE: Problem bringing up custom board with custom board file

Thomas — Mon, 29 Apr 2024 09:12:50 GMT

I am currently again at continues reboot:

00> *** Booting nRF Connect SDK v3.5.99-ncs1 ***
00> I: Starting bootloader
00> I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
00> I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
00> I: Boot source: none
00> I: Image index: 0, Swap type: none
00> I: Bootloader chainload address offset: 0x10000
00> I: Jumping to the first image slot
00> *** Booting nRF Connect SDK v3.5.99-ncs1 ***
00> I: Starting bootloader
00> I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
00> I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
00> I: Boot source: none
00> I: Image index: 0, Swap type: none
00> I: Bootloader chainload address offset: 0x10000
00> I: Jumping to the first image slot
00> *** Booting nRF Connect SDK v3.5.99-ncs1 ***
00> I: Starting bootloader
00> I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
00> I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
00> I: Boot source: none
00> I: Image index: 0, Swap type: none
00> I: Bootloader chainload address offset: 0x10000
00> I: Jumping to the first image slot
00> *** Booting nRF Connect SDK v3.5.99-ncs1 ***
00> I: Starting bootloader
00> I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
00> I: Secondary image:

I am experimenting with uart settings but do not find any setting where I can use a serial port for rs485 modbus and optionally another one for console (not in current hardware, but pins are free).

I have the following in the pinmux, and this is not changed during experimenting:

uart_rs485_default: uart_rs485_default {

group1 {

psels = <NRF_PSEL(UART_TX, 0, 9)>;

};

group2 {

psels = <NRF_PSEL(UART_RX, 0, 10)>;

bias-pull-up;

};

uart_rs485_sleep: uart_rs485_sleep {

group1 {

psels = <NRF_PSEL(UART_TX, 0, 9)>,

<NRF_PSEL(UART_RX, 0, 10)>;

low-power-enable;

};

uart_console_default: uart_console_default {

group1 {

psels = <NRF_PSEL(UART_TX, 0, 29)>;

};

group2 {

psels = <NRF_PSEL(UART_RX, 0, 28)>;

bias-pull-up;

};

uart_console_sleep: uart_console_sleep {

group1 {

psels = <NRF_PSEL(UART_TX, 0, 29)>,

<NRF_PSEL(UART_RX, 0, 28)>;

low-power-enable;

};

Then experimeting with dtsi and config settings. Current test that causes continous reboot is caused by:

chosen {

zephyr,console = &uart0;

zephyr,shell-uart = &uart0;

zephyr,uart-mcumgr = &uart0;

ncs,at-host-uart = &uart0;

};

&uart2 {

status = "okay";

current-speed = <9600>;

pinctrl-0 = <&uart_rs485_default>;

pinctrl-1 = <&uart_rs485_sleep>;

pinctrl-names = "default", "sleep";

modbus0 {

compatible = "zephyr,modbus-serial";

status = "okay";

de-gpios = < &gpio0 8 GPIO_ACTIVE_HIGH>;

};

&uart0 {

status = "okay";

current-speed = <115200>;

pinctrl-0 = <&uart_console_default>;

pinctrl-1 = <&uart_console_sleep>;

pinctrl-names = "default", "sleep";

};

Some serial things from config:

# Enable uart driver

CONFIG_SERIAL=y

# enable console

CONFIG_CONSOLE=y

CONFIG_UART_CONSOLE=n

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

CONFIG_LOG=y

CONFIG_LOG_MODE_DEFERRED=y

CONFIG_LOG_DEFAULT_LEVEL=4

# Modem

CONFIG_NRF_MODEM_LIB_TRACE=n

#CONFIG_AT_HOST_LIBRARY=y

CONFIG_MODEM_KEY_MGMT=y

# Modbus and serial

CONFIG_UART_INTERRUPT_DRIVEN=y

CONFIG_UART_LINE_CTRL=n

CONFIG_TFM_LOG_LEVEL_SILENCE=y

CONFIG_MODBUS=y

CONFIG_MODBUS_ROLE_CLIENT=y

CONFIG_PINCTRL=y

CONFIG_UART_USE_RUNTIME_CONFIGURE=y

And in my application I am opening modbus port with the following:

#define MODBUS_NODE DT_COMPAT_GET_ANY_STATUS_OKAY(zephyr_modbus_serial)

#define MODBUS_STACK_SIZE 1024

#define MODBUS_PRIORITY 5

K_THREAD_DEFINE(modbus_tid, MODBUS_STACK_SIZE,

ModbusClientThread, NULL, NULL, NULL,

MODBUS_PRIORITY, 0, 0);

static int init_modbus_client(void)

{

const char iface_name[] = {DEVICE_DT_NAME(MODBUS_NODE)};

client_iface = modbus_iface_get_by_name(iface_name);

return modbus_init_client(client_iface, client_param);

}

RE: Problem bringing up custom board with custom board file

Sigurd Hellesvik — Fri, 26 Apr 2024 13:57:26 GMT

Try to use the VS Code DeviceTree editor, find ncs,at-host-uart under "chosen" and delete it there. Then you can see how that looks in the overlay file

RE: Problem bringing up custom board with custom board file

Thomas — Fri, 26 Apr 2024 13:35:43 GMT

Now I have tried adding

chosen {
ncs,at-host-uart = &uart2;
}

And declared uart2 in the DTS, then I can compile. So that seems to remove last reference to uart0,

So I found out that CONFIG_AT_HOST_LIBRARY removes this dependency.

So I have removed the AT host library and is trying to reintroduce the use of uart0 in my application.

RE: Problem bringing up custom board with custom board file

Thomas — Fri, 26 Apr 2024 13:24:09 GMT

Trying to figure out why I have so many conflicts with the uart, I have remove use of it in my application.

I have removed decaration of uart0 from the DTS.

In DTS I have also removed the use of uart0

chosen {

zephyr,console = &uart0;

zephyr,shell-uart = &uart0;

zephyr,uart-mcumgr = &uart0;

};

And in prj.conf got:

CONFIG_TFM_LOG_LEVEL_SILENCE=y

CONFIG_NRF_MODEM_LIB_TRACE=n

So I am trying to remove all use of uart0...

I now cannot compile because of at_host.c where uart0 is used in

#if DT_HAS_CHOSEN(ncs_at_host_uart)

static const struct device *const uart_dev = DEVICE_DT_GET(DT_CHOSEN(ncs_at_host_uart));

#else

static const struct device *const uart_dev = DEVICE_DT_GET(DT_NODELABEL(uart0));

#endif

How do I prevent this use of uart0

-------------------------

It is not really that I need uart0 to be unused. But my problems seems to come from uart usage conflict.

It would be nice to have uart0 as a console and for all the default and uart2 for my modbus port. But I am unable to figure out a DTS and configuration that can work with that.

RE: Problem bringing up custom board with custom board file

Thomas — Fri, 26 Apr 2024 11:23:38 GMT

It is fine for me not to use uart1. I have kept the following in the device tree:

/* Disable UART1, because it is used by default in TF-M */

&uart1 {

status = "disabled";

};

In my prj.conf file I have

CONFIG_TFM_LOG_LEVEL_SILENCE=y

Now I am trying with CONFIG_NRF_MODEM_LIB_TRACE=n, I found this in the source code following the call stack.

RE: Problem bringing up custom board with custom board file

Sigurd Hellesvik — Fri, 26 Apr 2024 11:18:46 GMT

Ah, looks like modem trace uses UART1.
You could try to disable it if not not needed usingCONFIG_NRF_MODEM_LIB_TRACE.

From Enabling tracing in the application:
"

By default, the nRF Connect SDK’s modem library uses the UART1 peripheral for trace output. This means that you cannot use UART1 for other purposes in your application. If this does not work for your application, you must update the configuration and code of the modem library to use a different UART peripheral for trace output.

RE: Problem bringing up custom board with custom board file

Thomas — Fri, 26 Apr 2024 10:50:15 GMT

Using the CONFIG_TFM_LOG_LEVEL_SILENCE brings me into an assertion. The following line 76 in uart_deprecated_async.c:

err = pinctrl_apply_state(PINCTRL_DT_DEV_CONFIG_GET(UART1_NL), PINCTRL_STATE_DEFAULT);

__ASSERT_NO_MSG(err == 0);

It is being called from nrf_modem_lib_trace_init().

RE: Problem bringing up custom board with custom board file

Thomas — Fri, 26 Apr 2024 09:04:21 GMT

In current testing I am ending up in an assertion in tfm_hal_platform_common_init that is calling stdio_init().

Event though I was just thinking that I would not do anything with uart1 (that was supposed to be used by TFM), it seems to have influence. So I will try the suggested CONFIG_FTM_LOG_LEVE_SILENCE...