STM32: H7S3L8 does not boot when networking is enabled

[mariopaja]

Describe the bug

Since the internal flash memory is insufficient to implement a DHCP client, I attempted to do so using sysbuild/with_mcuboot.
The application code itself remains unchanged — only the nucleo_h7s3l8.overlay and prj.conffiles were modified.

As a result the application does not boot.

Regression

• This is a regression.

Steps to reproduce

Application Used:

samples/sysbuild/with_mcuboot

Add in prj.conf:

CONFIG_NETWORKING=y

Add in nucleo_h7s3l8.overlay:

&sram2 {
	status = "okay";
};

&rng {
	status = "okay";
};

&gpdma1 {
	status = "okay";
};

Relevant log output

Expected:

*** Booting MCUboot v2.2.0-192-g96576b341ee1 ***
*** Using Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***
*** Booting Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***
Address of sample 0x70000000
Hello sysbuild with mcuboot! nucleo_h7s3l8


Output:

*** Booting MCUboot v2.2.0-192-g96576b341ee1 ***
*** Using Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***

Impact

Functional Limitation – Some features not working as expected, but system usable.

Environment

No response

Additional Context

No response

[erwango]

@TD-JBL FYI

[TD-JBL]

You need to enable the HSI48 clock source for der RNG:

&clk_hsi48 {
	status = "okay"; //needed for RNG
};

I put this into the prj.conf and then the board responds to ping:

CONFIG_NETWORKING=y
CONFIG_ETH_DRIVER=y
CONFIG_NET_UDP=y
CONFIG_NET_TCP=y
CONFIG_NET_IPV6=n
CONFIG_NET_IPV4=y
CONFIG_NET_CONFIG_SETTINGS=y
CONFIG_NET_CONFIG_NEED_IPV4=y
CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.1"
CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.0.2.2"
#CONFIG_NET_LOG=y
#CONFIG_NET_STATISTICS=y

[mariopaja]

Using a Static IP with the above overlay & configuration the board boots. I can also confirm that the boards boots when the samples/net/dhcpv4_client/prj.conf is copied into samples/sysbuild/with_mcuboot/prj.conf. In both tests the application remains unchanged

*** Booting MCUboot v2.2.0-192-g96576b341ee1 ***
*** Using Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***
[00:00:00.051,000] <inf> phy_mii: PHY (0) ID 7C131
*** Booting Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***
[00:00:00.055,000] <inf> net_config: Initializing network
[00:00:00.055,000] <inf> net_config: Waiting interface 1 (0x24000be8) to be up...
[00:00:02.154,000] <inf> phy_mii: PHY (0) Link speed 100 Mb, full duplex
[00:00:02.155,000] <inf> net_config: Interface 1 (0x24000be8) coming up
[00:00:02.155,000] <inf> net_config: IPv4 address: 192.0.2.1
Address of sample 0x70000000
Hello sysbuild with mcuboot! nucleo_h7s3l8

*** Booting MCUboot v2.2.0-192-g96576b341ee1 ***
*** Using Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***

[00:00:00.051,000] <inf> phy_mii: PHY (0) ID 7C131
*** Booting Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***
Address of sample 0x70000000
Hello sysbuild with mcuboot! nucleo_h7s3l8
[00:00:02.154,000] <inf> phy_mii: PHY (0) Link speed 100 Mb, full duplex

When samples/net/dhcpv4_client/src/main.c is copied into samples/sysbuild/with_mcuboot/src/main.c the board does not boot anymore (maybe I have forgotten something once again? :/)

*** Booting MCUboot v2.2.0-192-g96576b341ee1 ***
*** Using Zephyr OS build v4.3.0-rc2-49-gd054025fa395 ***

[TD-JBL]

I copied src/main.c and prj.conf from samples/net/dhcpv4_client to samples/sysbuild/with_mcuboot with the mentioned changes to the overlay file and it seems to work:

*** Booting MCUboot v2.2.0-167-g48b0f6da9af8 ***
*** Using Zephyr OS build v4.3.0-rc2-64-g90b4d87d2aa6 ***

[00:00:00.053,000] <inf> phy_mii: PHY (0) ID 7C131
*** Booting Zephyr OS build v4.3.0-rc2-64-g90b4d87d2aa6 ***
[00:00:00.065,000] <inf> net_dhcpv4_client_sample: Run dhcpv4 client
[00:00:00.065,000] <inf> net_dhcpv4_client_sample: Start on ethernet: index=1
[00:00:02.157,000] <inf> phy_mii: PHY (0) Link speed 100 Mb, full duplex
[00:00:05.174,000] <inf> net_dhcpv4: Received: 10.137.xx.xx
[00:00:05.175,000] <inf> net_dhcpv4_client_sample:    Address[1]: 10.137.xx.xx
[00:00:05.175,000] <inf> net_dhcpv4_client_sample:     Subnet[1]: 255.255.xx.xx
[00:00:05.176,000] <inf> net_dhcpv4_client_sample:     Router[1]: 10.137.xx.xx
[00:00:05.176,000] <inf> net_dhcpv4_client_sample: Lease time[1]: 604800 seconds

Can you check in a debug session, where your system hangs? That way I found the missing clock for the RNG within minutes...

[mariopaja]

By disabling log CONFIG_LOG=n

I got the following Error

***** USAGE FAULT *****
  Unaligned memory access
r0/a1:  0x240009cc  r1/a2:  0x00000003  r2/a3:  0x700247b7
r3/a4:  0x24004c70 r12/ip:  0x00000000 r14/lr:  0x7001105f
 xpsr:  0x61000000
Faulting instruction address (r15/pc): 0x70010c02

~/zephyr-sdk-0.17.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-addr2line -e \
~/zephyrproject/zephyr/samples/sysbuild/with_mcuboot/build/with_mcuboot/zephyr/zephyr.elf 0x70010c02

/Users/mariopaja/zephyrproject/modules/hal/stm32/stm32cube/stm32h7rsxx/drivers/src/stm32h7rsxx_hal_rcc.c:1358

https://github.com/zephyrproject-rtos/hal_stm32/blob/286dd285b5bb4fddafdfff27b5405264e5a61bfe/stm32cube/stm32h7rsxx/drivers/src/stm32h7rsxx_hal_rcc.c#L1358

~/zephyr-sdk-0.17.4/arm-zephyr-eabi/bin/arm-zephyr-eabi-addr2line -e \
~/zephyrproject/zephyr/samples/sysbuild/with_mcuboot/build/with_mcuboot/zephyr/zephyr.elf 0x7001105f

/Users/mariopaja/zephyrproject/modules/hal/stm32/stm32cube/stm32h7rsxx/drivers/src/stm32h7rsxx_hal_eth.c:2420

https://github.com/zephyrproject-rtos/hal_stm32/blob/286dd285b5bb4fddafdfff27b5405264e5a61bfe/stm32cube/stm32h7rsxx/drivers/src/stm32h7rsxx_hal_eth.c#L2420

Have you changed any other clock parameters?

[TD-JBL]

You need to enable the HSI48 clock source for der RNG:

&clk_hsi48 {
	status = "okay"; //needed for RNG
};

Is it useful to add a check (static assert or LOG_ERR) to the rng driver for activated hsi48 when the selected soc is h7rs?