STM32H735 with Ethernet & ln8710A PHY

[dacha.1]

Hello 

I am triyng to use STM32H735 with ethernet (ln8710A is the PHY) 
We have hardware fault when we connect the cable (se the itm print below)
We use CubeMx version Version: 1.18.0
ETH is in RMII conection is OK

[Andrew Neil]

Welcome to the forum.

Presumably, this is custom hardware?

Therefore, please post your schematic. Also what tools, middleware, versions, etc

See: How to write your question to maximize your chances to find a solution

---

@dacha.1 wrote:

We have hardware fault when we connect the cable (se the itm print below)

---

How to debug Hard Faults:

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

PS:

---

@dacha.1 wrote:

ln8710A is the PHY

---

Did you mean LAN8710A ?

https://www.microchip.com/en-us/product/lan8710a 

[dacha.1]

the hardware is good 
we have test many configurations for memory position for Rx Tx and LwiRamHeap

In certain conditions hi dont remember its , I succeeded to ping my board , but 
after several try of ping we have hardware fault

We think that it was bad configuration for Rx Tx and the heap description .

Can you help me to fit the good comfiguration 

[Andrew Neil]

Note that it's a "Hard Fault" - which is not necessarily a hardware issue.

https://developer.arm.com/documentation/dui0552/a/the-cortex-m3-processor/fault-handling

Again, see how to debug Hard Faults:

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

And did you mean LAN8710A ?

https://www.microchip.com/en-us/product/lan8710a 

[dacha.1]

Now the stack is running

When we try to ping the board the response is OK

C:\Users>ping 192.0.1.218 -t

Envoi d’une requête 'Ping' 192.0.1.218 avec 32 octets de données :
Réponse de 192.0.1.218 : octets=32 temps<1ms TTL=255
Réponse de 192.0.1.218 : octets=32 temps<1ms TTL=255
......................................

but we have DMAErrorCode=0x4080 ? why ?