2025-07-15 10:00 PM
Hi Team,
I made a custom board using STM32F769BIT microcontroller using with the DP83867 PHY in MII mode, but I am not able to ping it. What could be the possible reasons?
I did Memory configurations for TxDecrip, RxDecrip, LwipHeap like this.
.lwip_sec (NOLOAD) :
. = ABSOLUTE(0x2007C000);
*(.RxDecripSection)
. = ABSOLUTE(0x2007C0A0);
*(.TxDecripSection)
. = ABSOLUTE(0x2007C140);
*(.LwIPHeap)
also my SRAM configuration is like this_
MEMORY
RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 496K
SRAM2 (xrw) : ORIGIN = 0x2007C000, LENGTH = 16K
FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 2048K
I am using the 10pin STM32 debugger, but I am not able to see the stack usage there, when I press the debug button.
Is it due to code or due to the debugger? For this should I need the 20pin debugger?
Thanks,
Sayan Das
2025-07-16 12:02 AM
Does you code work on a validated board, like a Nucleo one (obvious, with legacy PY interface)?
This should tell if is a PHY problem or a coding problem.
2025-07-16 1:44 AM
I don't have nucleo board. Is there any way to debug?
2025-07-16 1:52 AM - edited 2025-07-16 1:53 AM
A) your board is defective
B) your code is wrong
which one is your case?
Get one board 100% tested and test your code - later you can test your hw !!
2025-07-16 1:58 AM
Hello @Sayan, and Welcome to the community!
To maximize your chances of finding a solution, please refer to How to write your question to maximize your chances to find a solution for best practices.
In particular, please include the following details in your post:
Providing this information helps the community assist you more effectively.
Best regards,
2025-07-16 2:07 AM - edited 2025-07-16 2:14 AM
As @STackPointer64 said, more info is needed.
You haven't said what IP stack you're using - they usually have options for diagnostic output to help debug...
@Sayan wrote:I am using the 10pin STM32 debugger
But have you correctly wired it?
That's why showing your schematic is essential!
How have you validated your DP83867 design? Previous discussions relating to DP83867:
PS:
Have you checked-out TI's Product Page for the DP83867 - I can see a couple of debugging/troubleshooting guides there:
https://www.ti.com/product/DP83867E#tech-docs
https://www.ti.com/product/DP83867E#software-development