After having succefully tested some EMAC0 examples on the sc589_ezkit board (inetd,dnsClient,Multicast Sender) under uos3 or freertos, I tried the same examples on the SC573_EZKIT.
All examples fail in different ways depending on the tasks structure.
Mainly fails the adi_twi_Write() in softswitch_cfg.c , line 143. : result = adi_twi_Write(hDevice, twiBuffer, (uint32_t)2, false);
This function never returns blocking the task or even the main init procedure depending where the ConfigSoftSwitches() function is placed.
The same code on the SC589_EZKIT works perfectly.
Checking the code and the hardware i found some incoerences in the documentation and peraphs inside the code itself.
All EZ_SC573 documentation and code report the EMAC0 PHY chip as DP83865 instead the mounted chip is a DP83867.
The EZ_SC589 requires the softswitch configuration to reset and manage the reset of two EMACS instead for resetting only the PA_05 GPO should be required.
The adi_twi_Write() fails just trying to configure this softswitch.
Does my SC_573EZKIT card have hardware problems or the EMAC port isn't correctly configured for the sc573 case?
THE SC_573KIT BOM REV 1.8
Sorry for the late response. It should be the problem that your CrossCore Embedded Studio(CCES) does not support the new PHY DP83867 on the SC573-EZKIT board. Currently the CCES version 2.8.2 support the NEW PHY. Download the CCES version 2.8.2 here: https://www.analog.com/en/design-center/processors-and-dsp/evaluation-and-development-software/adswt-cces.html#dsp-documentation
I downloaded the CCES 2.8.2 before i was using the 2.8.0. But nothing is changed.
Exactly the same behavior (locks inside the i2c write) and at first sight the init code in exactly the same.
I was able to run the inetd example using CCES 2.83 with LWIP 2.6.0 on a BOM 1.8 of the 573 board. I did have to set it to boot mode 0 when I powered up otherwise I get an unregistered interrupt ID from the interrupt handler.
If you haven't tried yet, can you try with boot mode 0?