Hard fault after activating network interfaces

[unkn0wn]

I'm trying to establish a TCP connection between my Nucleo-H753ZI and my PC.

I'm using ThreadX and NetxDuo.

First of all, i'm triggering a hard fault when activating Network Interfaces and then using the debug mode.

I don't seem to have hard fault if i flash the program directly into the board (I have a thread that blinks an LED that still works)

This is my cubeMX configuration :

I installed the following, using the Software Packs Component Selector:

STMicroelectronics-X-CUBE-AZRTOS-H7:

  ThreadX => Core

  NetXDuo => NX Core

  Network Interfaces => Ethernet Interface, Ethernet Phy Interface : LAN8742_Phy_Interface

  Board Part STM32Cube_BSP_Components : ETHPhy / LAN8742

I tried to ping the board using CMD in windows, but i'm guessting that wouldn't work because i haven't added any code in nx_app_thread_entry.

Thank you

[unkn0wn]

Duplicate post - merged

---

I'm trying to establish a TCP connection between my Nucleo-H753ZI and my PC.

I'm using ThreadX and NetxDuo.

First of all, i'm triggering a hard fault when activating Network Interfaces and then using the debug mode.

I don't seem to have hard fault if i flash the program directly into the board (I have a thread that blinks an LED that still works)

This is my cubeMX configuration :

I installed the following, using the Software Packs Component Selector:

STMicroelectronics-X-CUBE-AZRTOS-H7:

  ThreadX => Core

  NetXDuo => NX Core

  Network Interfaces => Ethernet Interface, Ethernet Phy Interface : LAN8742_Phy_Interface

  Board Part STM32Cube_BSP_Components : ETHPhy / LAN8742

I tried to ping the board using CMD in windows, but i'm guessting that wouldn't work because i haven't added any code in nx_app_thread_entry.

Thank you

[Andrew Neil]

On debugging Hard Faults - both Cortex-M in general, and STM32 specifically:

https://community.st.com/t5/community-guidelines/how-to-write-your-question-to-maximize-your-chances-to-find-a/tac-p/708193/highlight/true#M51

---

@unkn0wn wrote:

I'm using ThreadX and NetxDuo.

---

Presumably they can provide some diagnostic tracing to (help) see what's going on ?

You can, of course, add your own ...

PS:

NetXDuo Knowledge Base articles:

https://community.st.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&filter=includeTkbs&include_tkbs=true&q=NetXDuo

[DmitryR]

Hi @unkn0wn ,

First of all please make sure that your Ethernet buffers are not in AXI SRAM as Ethernet MAC has no access to it.

Regards,

Dmitry

[Haithem Rahmani]

Hi @DmitryR 

Actually, the Ethernet MAC has access to AXI SRAM as shown below in the bus matrix.

the only unaccessible memory is the DTCM.

regards
haithem.

[DmitryR]

@Haitem,

First of all you show the picture for the H723 but @unkn0wn  uses H753. For H753, this link from Ethernet MAC to AXI bridge was added in documentation revision 10 only. I do not know the reason but I know that for silicon revisions Y and V this does not work, I have had this problem myself. Putting Ethernet buffers to AHB SRAM makes it work without any problems.

Regards,

Dmitry

[Haithem Rahmani]

Sorry @DmitryR 

Indeed I used the wrong reference manual, here is the correct one to keep the tracking.