This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
My project is based on `examples\networking\lwip\enet_cpsw_tcpserver` ... I then added the FSI sysconfig sections in from the `drivers\fsi\fsi_loopback_interrupt` project.
The FSI comms on the 2 launchpads I have connected together works totally fine.
I start the tcp server (calling appMain() from the example... yes I have moved the Drivers_open/Board_driversOpen out) on board #1 only. Board #1 obtains an IP through DHCP and the TCP comms work fine with a PC.
Board #1 can successfully send an fsi frame to board #2. However after the TCP server is started, board #1 can no longer receive frames from board #2.
I've breakpointed inside the FSI RX INT1 ISR on board #1 and confirmed the interrupt is not firing.
I am using the PROC109A(001) revision of the board.
Please advise.
The A revision of the board has the CONFIG_ENET_RGMII_PHY_RST pin set to GPMC0_AD11 in sysconfig GPIO section, but in revision E3 this was changed to GPMC0_AD13.
Changing the sysconfig GPIO for CONFIG_ENET_RGMII_PHY_RST to GPMC0_AD13 resolved my issue.
Note: The sysconfig in the examples should probably be updated in the next revision of the MCU plus SDK.