Part Number: AM6422 Other Parts Discussed in Thread: DP83869 , Tool/software: Hey everyone,
I am an electronics engineer working on fine-tuning the CPU board of our design, where we are integrating a SoC AM6422 and two TI DP83869 Ethernet PHYs, following…
Part Number: AM6422 Tool/software: Hi TI Support Team,
For your information, I am using SDKv09.02.01.10
Please provide the steps to create a custom root file system for the AM6422 controller.
Regards, Kalyan
Part Number: AM6422 Tool/software: Hello,
The hardware we have developed ourselves now uses mcu_uart0 and mcu_uart1 in Linux. We have defined it in the device tree and the corresponding pins have been compared. After testing, it was found that neither…
Hi,
I think there already exists an e2e on this, I would let another engineer continue discussion here if that is okay with you: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1432141/am6422-sdk-8-6-timer-compare-and-capture…
Part Number: AM6422 Other Parts Discussed in Thread: WL1837 Tool/software: Hello,
I use the wl1837 wifi module and want to reset the wifi module on the SK development board, but I didn’t see the reset pin. What is the specific operation process?…
Part Number: AM6422 Tool/software: After tiboot3.bin is downloaded, tispl.bin can not download, and the uart0 prints uncorrect message.
The detail message is below:
am64x/bootloaders-latest# am64x/bootloaders-latest# sudo dfu-util -l dfu-util 0.8
Copyright…
Part Number: AM6422 Tool/software: Hi,
What is the dc characteristics for serdes of AM6422? Such the transmitter differential voltage, common voltage. the receiver differential voltage, common voltage.
I wish to know how to verify my design meet the…
Part Number: AM6422 Tool/software: Hi,
i'm currently working on a project running Yocto Linux on the A53 Cores with some offloaded tasks running on the r5f0_0.
Communication is handled via IPC.
I just wanted to confirm the startup process - our software…
I found that the udelay function is inaccurate. The parameter I gave in the device tree is 2us, but the actual oscilloscope measured it to be 10ms, and it is not equal every time, and it is at ms level. Is this correct?