Industrial stack support

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Industrial stack support

268 Views
Shahbaz_Alam
Contributor I

We are planning to start a project that will have multiple Industrial protocol.

Below are my queries.

Does NXP provide industrial communication protocol stacks for its MCU and MPU platforms? Is these limited to i.MX94 & i.MX-RT1180?

Which industrial communication protocols are currently supported by NXP?

  • PROFINET

  • EtherNet/IP

  • EtherCAT

  • Modbus TCP/RTU

  • OPC UA

  • TSN

  • PROFIsafe

  • CIP Safety

  • IO-Link

  • HART-IP

  • Others

Which NXP hardware platforms support these protocol stacks?

  • i.MX series

  • S32 series

  • MCX series

  • LPC series

  • Other platforms

Is there a platform-versus-protocol support matrix available?

Are sample applications, reference designs, and demonstration projects provided with the protocol stacks?

Are Linux and RTOS integration examples available?

What is the licensing model for the industrial protocol stacks?

Are the protocol stacks available free of charge? If yes, what are the eligibility criteria and usage conditions?

Are there any restrictions on evaluation, development, or commercial deployment?

In what form are the protocol stacks provided?

  • Binary library

  • Object code

  • Source code

  • SDK package

Is source code access available for the protocol stacks?

If source code is available, what are the commercial, licensing, or NDA requirements to obtain it?

Can the protocol stacks be customized and modified by customers?

What is the process for commercializing a product using the NXP protocol stacks?

Are there any one-time licensing fees associated with commercial product deployment?

Are there any per-device royalties, recurring charges, or annual maintenance fees?

Are there any additional costs associated with production deployment versus evaluation use?

0 Kudos
Reply
1 Reply

224 Views
JorgeCas
NXP TechSupport
NXP TechSupport

Hello,

1.

PROFINET - Supported.

EtherNet/IP - Supported.

EtherCAT - Supported.

Modbus TCP/RTU - Supported.

OPC UA - Supported.

TSN - Supported.

PROFIsafe - Not supported.

CIP Safety - Supported

IO-Link - Supported.

HART-IP - Not supported.

2.

All of these families support some of previous mentioned protocols but not all at the same time. As you mention i.MX94 and i.MX-RT1180 are focused to support these protocols. You can also take a look in Layerscape processors.

3. No, we do not have a resource like this.

4. Yes, there are examples in our BSPs/SDKs.

5. Yes, there are examples available.

6. 7. 8. This depends on the way that is provided to the customer and each resource needs to be checked to confirm licensing model.

9. Source code and SDK packages are available.

10. Source code is available.

11. This depends on the way that is provided to the customer and each resource needs to be checked to confirm licensing model.

12. Can be modified by customer.

13. This depends on the way that is provided to the customer and each resource needs to be checked to confirm licensing model.

14. 15. 16. NXP is legally unable to provide guidance on when, where and how to obtain licenses as these are done by 3rd parties with varying and (sometimes) changing terms.

I would suggest you contact the owner of the specific protocol you wish to use for information regarding royalties.

Best regards.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2386758%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EIndustrial%20stack%20support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2386758%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EWe%20are%20planning%20to%20start%20a%20project%20that%20will%20have%20multiple%20Industrial%20protocol.%3C%2FP%3E%3CP%3EBelow%20are%20my%20queries.%3C%2FP%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EDoes%20NXP%20provide%20industrial%20communication%20protocol%20stacks%20for%20its%20MCU%20and%20MPU%20platforms%3F%20Is%20these%20limited%20to%20i.MX94%20%26amp%3B%20i.MX-RT1180%3F%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EWhich%20industrial%20communication%20protocols%20are%20currently%20supported%20by%20NXP%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EPROFINET%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EEtherNet%2FIP%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EEtherCAT%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EModbus%20TCP%2FRTU%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EOPC%20UA%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3ETSN%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EPROFIsafe%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3ECIP%20Safety%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EIO-Link%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EHART-IP%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EOthers%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EWhich%20NXP%20hardware%20platforms%20support%20these%20protocol%20stacks%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3Ei.MX%20series%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3ES32%20series%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EMCX%20series%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3ELPC%20series%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EOther%20platforms%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EIs%20there%20a%20platform-versus-protocol%20support%20matrix%20available%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EAre%20sample%20applications%2C%20reference%20designs%2C%20and%20demonstration%20projects%20provided%20with%20the%20protocol%20stacks%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EAre%20Linux%20and%20RTOS%20integration%20examples%20available%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EWhat%20is%20the%20licensing%20model%20for%20the%20industrial%20protocol%20stacks%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EAre%20the%20protocol%20stacks%20available%20free%20of%20charge%3F%20If%20yes%2C%20what%20are%20the%20eligibility%20criteria%20and%20usage%20conditions%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EAre%20there%20any%20restrictions%20on%20evaluation%2C%20development%2C%20or%20commercial%20deployment%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EIn%20what%20form%20are%20the%20protocol%20stacks%20provided%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EBinary%20library%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EObject%20code%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3ESource%20code%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3ESDK%20package%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EIs%20source%20code%20access%20available%20for%20the%20protocol%20stacks%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EIf%20source%20code%20is%20available%2C%20what%20are%20the%20commercial%2C%20licensing%2C%20or%20NDA%20requirements%20to%20obtain%20it%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3ECan%20the%20protocol%20stacks%20be%20customized%20and%20modified%20by%20customers%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EWhat%20is%20the%20process%20for%20commercializing%20a%20product%20using%20the%20NXP%20protocol%20stacks%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EAre%20there%20any%20one-time%20licensing%20fees%20associated%20with%20commercial%20product%20deployment%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EAre%20there%20any%20per-device%20royalties%2C%20recurring%20charges%2C%20or%20annual%20maintenance%20fees%3F%20%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%EF%82%B7%20%3CFONT%20face%3D%22Times%20New%20Roman%2C%20serif%22%3EAre%20there%20any%20additional%20costs%20associated%20with%20production%20deployment%20versus%20evaluation%20use%3F%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2387145%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Industrial%20stack%20support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2387145%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3E1.%3C%2FP%3E%0A%3CP%3EPROFINET%20-%20Supported.%3C%2FP%3E%0A%3CP%3EEtherNet%2FIP%20-%20Supported.%3C%2FP%3E%0A%3CP%3EEtherCAT%20-%20Supported.%3C%2FP%3E%0A%3CP%3EModbus%20TCP%2FRTU%20-%20Supported.%3C%2FP%3E%0A%3CP%3EOPC%20UA%20-%20Supported.%3C%2FP%3E%0A%3CP%3ETSN%20-%20Supported.%3C%2FP%3E%0A%3CP%3EPROFIsafe%20-%20Not%20supported.%3C%2FP%3E%0A%3CP%3ECIP%20Safety%20-%20Supported%3C%2FP%3E%0A%3CP%3EIO-Link%20-%20Supported.%3C%2FP%3E%0A%3CP%3EHART-IP%20-%20Not%20supported.%3C%2FP%3E%0A%3CP%3E2.%3C%2FP%3E%0A%3CP%3EAll%20of%20these%20families%20support%20some%20of%20previous%20mentioned%20protocols%20but%20not%20all%20at%20the%20same%20time.%20As%20you%20mention%20i.MX94%20and%20i.MX-RT1180%20are%20focused%20to%20support%20these%20protocols.%20You%20can%20also%20take%20a%20look%20in%20Layerscape%20processors.%3C%2FP%3E%0A%3CP%3E3.%20No%2C%20we%20do%20not%20have%20a%20resource%20like%20this.%3C%2FP%3E%0A%3CP%3E4.%20Yes%2C%20there%20are%20examples%20in%20our%20BSPs%2FSDKs.%3C%2FP%3E%0A%3CP%3E5.%20Yes%2C%20there%20are%20examples%20available.%3C%2FP%3E%0A%3CP%3E6.%207.%208.%20This%20depends%20on%20the%20way%20that%20is%20provided%20to%20the%20customer%20and%20each%20resource%20needs%20to%20be%20checked%20to%20confirm%20licensing%20model.%3C%2FP%3E%0A%3CP%3E9.%20Source%20code%20and%20SDK%20packages%20are%20available.%3C%2FP%3E%0A%3CP%3E10.%20Source%20code%20is%20available.%3C%2FP%3E%0A%3CP%3E11.%20This%20depends%20on%20the%20way%20that%20is%20provided%20to%20the%20customer%20and%20each%20resource%20needs%20to%20be%20checked%20to%20confirm%20licensing%20model.%3C%2FP%3E%0A%3CP%3E12.%20Can%20be%20modified%20by%20customer.%3C%2FP%3E%0A%3CP%3E13.%20This%20depends%20on%20the%20way%20that%20is%20provided%20to%20the%20customer%20and%20each%20resource%20needs%20to%20be%20checked%20to%20confirm%20licensing%20model.%3C%2FP%3E%0A%3CP%3E14.%2015.%2016.%20NXP%20is%20legally%20unable%20to%20provide%20guidance%20on%20when%2C%20where%20and%20how%20to%20obtain%20licenses%20as%20these%20are%20done%20by%203rd%20parties%20with%20varying%20and%20(sometimes)%20changing%20terms.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20suggest%20you%20contact%20the%20owner%20of%20the%20specific%20protocol%20you%20wish%20to%20use%20for%20information%20regarding%20royalties.%3C%2FP%3E%0A%3CP%3EBest%20regards.%3C%2FP%3E%3C%2FLINGO-BODY%3E