• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 30 subscribers
  • Views 271 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM2434: Feature codes required to use RX L2 Status

Takashi Kato
Prodigy 80 points
Part Number: AM2434
Other Parts Discussed in Thread: TMDS243EVM, LP-AM243

Dear Support team,

I use the RX L2 status of mode 0 of ICSSG in my custom firmware.
Does this status work for function code "D" product ?
(Table 10-1. Nomenclature Description in the datasheet)

To use this mode, ICSS_G_CFG[2] RX_L2_G_EN = 0h.
This is the default setting, but in TRM this setting is "for EtherCAT Target protocols".
I would like to know what feature codes are needed to create a custom board.

Best regards,

Takashi Kato

  • 0
    TI__Mastermind 36293 points

    Hi Takashi,

    Could you please add more details on what is the intent of firmware is it a custom Ethernet based Protocol

  • 0
    TI__Mastermind 36293 points
    Takashi Kato said:
    Does this status work for function code "D" product ?
    (Table 10-1. Nomenclature Description in the datasheet)

    You will need product code D for this feature where Industrial comms feature is enabled.So answer is yes

  • +1
    TI__Mastermind 36293 points
    Takashi Kato said:
    To use this mode, ICSS_G_CFG[2] RX_L2_G_EN = 0h.
    This is the default setting, but in TRM this setting is "for EtherCAT Target protocols".
    I would like to know what feature codes are needed to create a custom board.

    This feature was introduced for EtherCAT and other hard real time protocols but can be used with D part devices.

  • 0
    TI__Mastermind 36293 points
    Takashi Kato said:
    I would like to know what feature codes are needed to create a custom board.

    For this can you provide more details on your implementation.

  • 0 in reply to Nilabh Anand
    Prodigy 80 points

    Dear Nilabh Anand,

    Thank you for the quick reply.
    My firmware seems to work at the TMDS243EVM and LP-AM243, but both are "F", so I asked.

    Regarding the protocol, the packet format is preamble and CRC are the same, but other fields are not compliant.

    The firmware is created for ICSS (AM335x) and ported, so it mainly uses the same functions.
    The only additions are RTU, TX cores and the SpinLock.

    The MAC interfece is MII mode, 100Mbps.
    The modules used are INTC, MII_G_RT, MDIO, and IEP(with sync0).
    Five out of six pru cores are used.

    Are there any items that affect the product code?

    Regards,

    Takashi Kato

  • 0 in reply to Takashi Kato
    TI__Mastermind 36293 points
    Takashi Kato said:

    Regarding the protocol, the packet format is preamble and CRC are the same, but other fields are not compliant.

    The firmware is created for ICSS (AM335x) and ported, so it mainly uses the same functions.
    The only additions are RTU, TX cores and the SpinLock.

    Ideally the firmware developed for AM335x PRU is compatible with AM243x PRU also. AM243x PRU had additional capability which is mentioned here: www.ti.com/.../sprac90

  • +1 in reply to Nilabh Anand
    TI__Mastermind 36293 points
    Takashi Kato said:
    The MAC interfece is MII mode, 100Mbps.
    The modules used are INTC, MII_G_RT, MDIO, and IEP(with sync0).
    Five out of six pru cores are used.

    Are there any items that affect the product code?

    All of these look fine. They should work as expected. Feel free to create a new thread in case you need help with anything else.

  • 0 in reply to Nilabh Anand
    Prodigy 80 points

    Thank you for your response.