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.

AM6442: How to Switch Industrial Protocols

Part Number: AM6442

Tool/software:

Hi experts,

My customer of mine is considering the AM64x.

Is it possible to implement multiple protocols such as EtherCAT, EtherNet/IP, Profinet, etc. in an industrial network and enable only one of them?
The hardware and firmware themselves are the same, and the following switching is assumed.

They are considering the following product lineup:
- Products that do not support industrial Ethernet
- Products that support EtherCAT slaves
- Products that support EtherNet/IP
- Products that support Profinet
...

As another way to achieve this, we are considering the Anybus module from HMS.
A connector for the module would be prepared on the microcontroller board, and the function would be switched based on the module type.
- For those that do not support industrial Ethernet ⇒ No module
- For those that support EtherCAT slave ⇒ Install AB6607-E
 -For those that support EtherNet/IP ⇒ Install AB6604-E
 -For those that support Profinet ⇒ Install AB6605-E
 ...

It seems possible to achieve something similar by preparing separate firmware.
However, as this would require complicated management and operation, we were wondering if there might be some way to enable one of the industrial Ethernet interfaces using common firmware, and have it operate with that setting from the next time it is started.

Best regards,
O.H

  • Hello O.H,

    As part of Electronica 2024, we showcased a multiprotocol demo on the AM64x EVM which switches between EtherCAT, Ethernet/IP and Profinet protocols based on the connected PLC device.
    Perhaps something similar can be used for your application.

    The firmware for the protocols would be booted from a SD card in this example. For each protocol, a corresponding image file is copied onto the SD card.
    The selection of protocol is done at the Secondary Boot loader (SBL) based on a flag in a non-volatile memory (EEPROM). This flag can be set by a common protocol selection application.
    Since the protocol selection is done at SBL, switching between protocols would require a warm reset of the device.


    The demo also showcased protocol detection, but I assume you won't be needing that.
    Perhaps the selection of the protocol can be done through GPIO inputs/ a rotary switch or even UART console for your application.

    Regards,
    Bharath

  • Hi Bharath,

    I think this is probably exactly what the customer is looking for!

    However, they don't need it right away.
    Will the demo be published on TI.com? If not, would it be possible to provide it offline?

    Best regards,
    O.H

  • Hi Bharath,

    Sorry for rush you. Is there any update?

    Best regards,
    O.H

  • Hi O.H,

    The demo is not published on TI.com, but we can provide the example to you.
    Please understand that this is a demo example and you'd have to modify it for your customer application. 

    Shall contact you offline to discuss this.

    Regards,
    Bharath

  • Hi Bharath,

    Thank you for your support. I understood!

    Best regards,
    O.H