Post Go back to editing

Base configuration for ADIN6310

Thread Summary

The user inquired about using the ADIN6310 as a regular Ethernet switch during initial testing. The support engineer clarified that the ADIN6310 always requires a host for configuration, including loading firmware and setting up ports. For basic switch functionality, the user must call SES_init(), SES_AddHardwareInterface(), SES_AddDevice(), and SES_InitializePorts(). The switch configuration is volatile and must be reloaded after each power cycle or reset.
AI Generated Content
Category: Hardware

Hello, 

I am nearing the process of getting a board made with the ADIN6310. I understand that it is a managed switch with a lot of configuration ability. I am curious though, if our purpose was to use it as a regular ethernet switch, would that require any interaction from the host? I ask because we plan on using the TSN features at some point in the future, but for our testing and software development, I would like to know what needs to be done in order for the device to function as a regular switch. 

Thanks,

BW

  • Hello,

    Thanks for message.

    The switch always needs a host to configure it, it's intended for an embedded application and wasn't designed to just boot and start switching. 

    Additionally, the switch is shipped without firmware loaded, this is the first thing that host will need to do during manufacturing. The firmware is about 500k, so the host must be able to store this and then load. The TSN driver package includes the firmware as a character array, it is signed firmware, the switch supports secure boot/firmware update. Once firmware is loaded, that will execute, but switch still needs the host to tell it how user wants the switch configured - e.g. what type of PHY connected, what type of MAC interface etc. On power up, the switch will only enable the host port (can be SPI or MAC interface), all other ports will remain disabled until host configures. The switch configuration is volatile, and must be reloaded after power cycle or reset. 

    For a basic switch use case, user would need to call the following 4 APIs as a minimum: SES_init(), SES_AddHardwareInterface(), SES_AddDevice() and SES_InitializePorts(). After that all ports are enabled and the switch will learn and forward on all ports for untagged and VLAN ID 0. To get any other VLAN traffic to cross the switch requires configuration of the VLAN table. 

    There are examples in the Driver User Guide and project

    Hope that helps, let us know if further questions as you work towards developing. 

    Best regards,

    Catherine. 

  • Thank you for your speedy response! I will take a look at this and will post other questions as I have them. 

    Thanks,

    BW