Following on from this post, I’m looking at ways of sending data to/from an MCU which will be installed on my custom carrier board. The MCU has a 10/100 ethernet interface, as well as SPI, UART, I2C, etc. I would like to use ethernet, as I’d prefer to keep the other interfaces free, and I wouldn’t make use of the ethernet interfaces on either the MCU or the Apalis otherwise.
- Would serialising data on the MCU (e.g. an array of longs), sending it to the Apalis module via TCP/IP, then deserialising the array on the Apalis be a good approach?
- If the answer to 1 above is yes, are there any special considerations when it comes to connecting the two ethernet interfaces together? The example schematics in the Apalis evaluation board and carrier board design documents only feature ethernet interfaces with an external ethernet socket (excerpt from the Apalis carrier board design attached as reference). Given I’m not using a Gigabit connection, the 4 Gigabit-only lines will be left unused (per the diagram below). What about the ETH1_ACT, ETH1_LINK and ETH1_CTREF lines? Can all of them be left unused as well?
If the answer to 1 above is ‘no’, and there’s a better method for sending ~2Mbit/s worth of data between the MCU and the Apalis module I’ll happily consider it!