Part Number: AM2634
Other Parts Discussed in Thread: DP83869, SYSCONFIG, DP83869HM
AM263x MCU+ SDK 10.02 – UART Garbage Output and CPSW lwIP Not Responding to Ping (Custom Board with DP83869)
Hi TI Team,
I am working on a custom board based on AM263x using MCU+ SDK 10.02.00.
I am testing the following example:
controller : AM2634COLFHAZCZ The board uses:
-
RGMII interface
-
External PHY: DP83869
-
25 MHz crystal for PHY
-
PHY address = 0x03
Observations:
-
UART functional clock configured as 48 MHz
-
Initially SysConfig input clock was incorrectly set to 25 MHz (fixed to 48 MHz)
-
Terminal settings:
-
115200
-
8N1
-
No flow control
-
Even after correcting the UART clock in SysConfig to 48 MHz, the UART output still shows garbage characters.
Questions:
-
What is the correct UART clock source for AM263x in MCU+ SDK 10.02?
-
Is there any additional clock configuration required outside SysConfig?
-
Is there a known issue with UART clock configuration in this SDK version?
Issue 2: Ethernet Link Up but No Ping Response
Hardware Status:
-
Link LED (DL6) stable ON
-
Activity LED (DL7) blinks during ping
-
PHY auto-negotiation enabled (10/100/1000 advertised)
-
Connected directly to PC for testing
Behavior:
When pinging:
ping 192.168.1.200
Result:
Reply from 192.168.1.10: Destination host unreachable.
-
-
it would be greatful if we got support for ping test and uart printfs and need example for ethernet perfect bringup