TMDSSK3358: EMAC boot

Nancy,

what hardware is being used? Is this really on the TI AM335x Starter Kit? Or some custom hardware?

Regards, Andreas

Hi,

It's TI AM335x Starter Kit.

Customer 1.Removed R160 resistor 100K, add R35 resistor 10K (SYSBOOT [4]) 2. Remove R37 resistor 10K, add R158 resistor 10K (SYSBOOT [6]) 3. Remove R38 resistor 10K and add R157 resistor 10K (SYSBOOT [7]). Since he don’t have a 100K resistor, R157 and R158 use a 10K resistor instead.

Hi Nancy,

thanks for the inputs. Please allow for a couple of days to look into this a bit closer (we have a holiday weekend coming up here too). Will get back on this early next week.

Regards, Andreas

Hi Andreas.

Thank you for following this question.I will also continue to study the problem.I'll wait for your message. Thank you so much.

Way

Way,

we should check if the device actually tries booting from the network interface. Two suggestions...

1. Use a logic analyzer to check the signals between the AM335x SoC and the Ethernet PHY to see if there is any activity (the MDIO bus would be a good candidate for this, I'd expect it to be accessed during PHY/network intitialization by the ROM bootloader)
2. Use JTAG to check the status of the bootloading process. The AM335x Starter Kit has a bare-bones JTAG emulator on-board, that should be enough for the job. We offer an AM335x-specific "Debug Server Scripting Package" for use with Code Composer Studio that will analyze the traces left behind by the boot ROM in detail, and will tell you what it attempted to boot (if it even tried Ethernet), what the device sees how the boot pins are configured, etc. You can find more info in our U-Boot board port guide here: https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/AM335X/linux/How_to_Guides/Board_Port/U-Boot.html#u-boot-bringup-debugging-tips

Regards, Andreas

Andreas.

OK, thank you for your advice. I will try these methods.

Way.