• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 325 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AM64x: Understanding interrupts

Device IDs and IO-Link

Philip Schröder
Prodigy 230 points


Hello,
when I tried to understand the use of interrupt router and interrupt aggregator there was the use of certain device IDs (I guess host ID is a device ID as well?) for source and destination devices as used here

downloads.ti.com/.../rm_irq.html

and described here:

http://downloads.ti.com/tisci/esd/18_08_00/5_soc_doc/am6x/devices.html


My question here is are those the same device IDs as in IO-Links IODD?

Thank you for your time and trouble


Best regards

Philip.

  • +1
    Prodigy 230 points

    Ok, it seems the question originated from my lack of understanding of both the TI MCU+ SDK and IO-Link.
    The device IDs of the SDK are identifying the subsystems described in the AM64x datasheet, while IO-Link device IDs describe IO-Link slaves attached to a master.

    My hope was that there was a stadndard identification of SMDs and their pins on a circuit board, which could be used in a vendor-independant interface.
    Apart from for instance the JEDEC ID at least for the American sector I cannot think of anything in this regard at the moment.

    At least the question is solved by this.