Blog

netX 51 is used as a Host Controller in this case. A netX 51 based hardware like NXHX 51-ETM must be connected to any netX based companion chip which runs the PROFINEt or EtherCAT Slave LFW
I.e. in this setup 2 netX chips are used: One as host, the second as companion chip.
In most cases, netX 51 will not be used as a host controller. Anyway this example might be helpful for users to understand the usage of PNS V3 and ECS V4 stacks.

  • cifX Demo Application V2
  • CMSID and netX_Driver V0.0.4.7
  • cifX Toolkit 1.6.0.0
  • HIL_ Hilscher Definitions instead of rcX_ and TLR_ definitions
  • netxSTUDIO project includes FDL, HWC, MFW files

### V0.9.0.8 Pre-release PROFINET example

- updated PNS firmware V4.4.7.0 (beta 6)

- updated component netx_drv V0.0.4.3 (netX90 final)

- updated component CMSIS V0.0.4.3

- updated hardware_config files (hwconfig tool V3.0.4)


### V0.9.0.8 Pre-release EtherCAT example

- updated component netx_drv V0.0.4.3 (netX90 final)

- updated component CMSIS V0.0.4.3

- updated hardware_config files (hwconfig tool V3.0.4)

based on beta LFW EIS V3.4.4.0 for netX 90

Hotfix for STM32CubeExpansion V1.3.0.1 released.

OS_WaitMutex(), OS_EnterLock() in OS_Custom_STM32.c may be called recursively by the cifX Toolkit. Recursive call support for these functions was added in V1.3.0.1. This is necessary to assure correct locking of the SPI interface.

 


PROFINET IO Device and EtherCAT Slave example applications pre-released