Disclaimer
This manual represents the current state of the product. Please check with port.de for the latest version as the document may have a newer version since errors may be corrected or changes for a newer version of the product may be incorporated. Port.de assumes no responsibility for errors in this document. Qualified feedback is appreciated at service@port.de.
This document is the Intellectual Property of port.de and is intended to be used with the described product only. It may be forwarded and/or copied in the original and unmodified format. All rights reserved.
The product enables to use technologies such as PROFINET, EtherNet/IP and/or EtherCAT and others. These technologies are promoted by trade organizations, such as PNO (profibus.org), ODVA (odva.org) or ETG (ethercat.org). These trade organizations as well maintain the specification and care about legal issues.
We strongly recommend to become a member of these organisations. Most technologies are making use of patented or otherwise copyrighted technologies, approaches or other intellectual property. The membership usually automatically entitles the member for use of most of the technology-inherent copyrighted or otherwise protected Intellectual Property of the corresponding trade organization and most 3rd parties. Otherwise the user will need to obtain licenses for many patented technologies separately.
Further we suggest to you to subscribe to the corresponding Conformance Test Tool of these trade organizations. For instance the ODVA only accepts conformance test applications from companies who have a valid membership and have a valid subscription to the recent Conformance Test Tool. We as port are members in all corresponding organizations and are holding a subscription to these tools - however you as a customer need to have an own membership and an own subscription to the tool.
All rights reserved
The programs, boards and documentations supplied by port GmbH are created with due diligence, checked carefully and tested on several applications.
Nevertheless, port GmbH cannot guarantee and nor assume liability that the program, the hardware board or the documentation are error-free or appropriate to serve a specific customer purpose. In particular performance characteristics and technical data given in this document may not be interpreted to be guaranteed product features in any legal sense.
For consequential damages, every legal responsibility or liability is excluded.
port has the right to modify the products described or their documentation at any time without prior warning, as long as these changes are made for reasons of reliability or technical improvement.
All rights of this documentation are with port. Unless expressively granted - the transfer of rights to third parties or duplication of this document in any form, whole or in part, is subject to written approval by port. Copies of this document may however be made exclusively for the use of the user and his engineers. The user is thereby responsible that third parties do not obtain access to these copies.
The soft- and hardware designations used are mostly registered and are subject to copyright.
Copyright
© 2019 port GmbH
Regensburger Straße 7
D-06132 Halle
Tel. +49 345 - 777 55 0
Fax. +49 345 - 777 55 20
E-Mail service@port.de
Changelog
Version | Changes |
1.0
|
Initial release |
...
This document describes integration delivered example projects for SoM using the STM32F4xx target with development environment STM32 Cube IDE.
Within the document, special recommendations are given marked by two signs:
...
Special information giving hints to avoid common pitfalls when using the software.
...
Special information to prevent malfunction of the software or that require special attention of the user.
Preparations
Hardware Requirements
...
JP6: Remove this Jumper on the front side of the board
...
| Note |
|---|
Due to a double assignment of pins the simultaneous use of SPI and Ethernet is not possible with STM32 Nucleo-144. The JP6 jumper activates Ethernet. |
Target System
...
Connect both boards (see Figure 3 Target system). Voltage supply is done through the shown USB connector (USB Pwr) on the development board, which also supports flashing and debugging of the CPU.
...
File | Content |
“2015013_20190611_2_20_0_port_STM32F429_Nucleo144_CCM_ci125.zip" | Goal GOAL Library and Headers |
“iRJ45 Management Tool“iCommExplorer-201808221413-win32.win32.x86_64_ci117-v1.3.1.zip"Management Tool | Industrial Communication Explorer |
Management Tool
To use the PROFINET master functionality, WinPCap[1] needs to be installed.
Please unpack the delivery " iRJ45 Management TooliCommExplorer-*-win32.win32.x86_64.zip" to a local folder. The resulting folder contains the executable “mantool”, which can be started.
Prepare GOAL and project
...
After importing the projects can be built. Use the project context menu, menu item “Build Project” to do so. As a result, a binary should be generated and the “Console” log should show the following text:
| Code Block |
|---|
… |
...
Finished building target: 2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.elf |
...
arm-none-eabi-size 2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.elf |
...
arm-none-eabi-objdump -h -S 2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.elf > "2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.list" |
...
arm-none-eabi-objcopy -O binary 2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.elf "2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.bin" |
...
text data bss dec hex filename |
...
190440 888 136000 327328 4fea0 2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.elf |
...
Finished building: default.size.stdout |
...
Finished building: 2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.bin |
...
Finished building: 2015013_irj45__ac__01_pnio_io_mirror__stm32f429_nucleo.list |
...
13:00:37 Build Finished. 0 errors, 358 warnings. (took 16s.925ms) |
If so, compilation was successful. The resulting binary now can be started:
...
| Note |
|---|
Debug configuration must be edited regarding debug probe for proper function. |
Please configure the debug probe as shown (Figure 7 Configure debug session) below to ST-LINK (OpenOCD). When prompted allow firewall exception to be configured.
...
After initiating the debug session, the “Debug perspective” will be shown, where the application can be started by “Resuming” execution.
...
| Note |
|---|
If the communication module was previously started up using another application, a manual reboot will be required of the module (reset button on the Arduino shield). |
...
Industrial Communication Explorer
The Management Tool Industrial Communication Explorer allows development related configuration and management of the SoM application. This management is based on a UDP broadcast communication. Thus, it works independently from IP settings of the management PC and the SoM.
...
This tool is organized in panels. The “Network Navigator” shows a list of available networks. The panel “Messages” shows information regarding actions. The panel “Outline” shows additional information depending on the selected function panel.
Following function panels are available:
Panel | Function |
EtherCAT Master | Provides simple EtherCAT master functionality. |
EtherNet/IP Master | Provides simple EtherNet/IP master functionality |
Exception Log | Shows error messages, which are saved in the non volatile storage of the communication controller. |
Device Log | shows Shows log messages of the running application from both communication controller (CC) and application controller (AC). |
Network state | Shows link state of the available network interfaces of the SoM. |
PNIO Master | Provides simple PNIO master functionality. |
Config ManagerConfigManager | Provides access to the config manager variables of the SoM. |
Firmware Update | Allows update of the firmware in of the SoM. |
Device Detection
At first a communication needs to establish be established with the SoM. Thus, connect the SoM to the network. Between the management PC and the SoM a network connection must be possible.
...
To communicate with the SoM, at first open the “Networks” list in the “Network Navigator”. Choose the network interface where the SoM is reachable. The Then select the “Scan Network” button in the toolbar.
...
With the selected SoM and within the “Device Log” function panel, it is now is possible to read the logging buffer using “Start reading log”. For the demo application, it shows both the log messages from the communication controller (SoM) and the application controller (STM32F4xxRaspberry Pi). Those can be distinguished by the “Source” column, which either shows “CC” ore “AC”. A successful started application reports a successful initialization of PROFINET:
| Code Block |
|---|
[I| goal_miMctcLoop:499] running appl_setup |
...
[I| goal_pnioNewAc:369] PROFINET Application Core successfully started |
...
[I| appl_setup:226] Initializing device structure |
...
[I| appl_setup:275] PROFINET ready |
...
[I| appl_setup:281] Configuring DD |
...
[I| appl_setup:309] DD ready |
To stop logging push the button again.
Config Manager / IP Configuration
This The function panel “ConfigManager” provides access to the config manager variables of the SoM (volatile and nonvolatile stored configuration variables).
To read a list of all variables, select the “Read configuration” button in the toolbar.
...
As a result, all variables with value are shown.
...
To communicate with the SoM, the IP address of the SoM it must be within the same IP network as the IP address of the Management PC IP address. Thus, chose choose a valid IP address and configure the SoM accordingly.
To configure an IP address, navigate to the variables of the “Module” GOAL_ID_NET. There Make sure, that the variable DHCP_ENABLED is set to 0x00, as this option is prioritized. Now it is possible to configure IP, NETMASK and GW. Modify required values. Make sure Set the variable “VALID” is set to 10x01.
The Management Tool will show locally modified variables with a yellow highlight.
...
Those locally modified variables are downloaded to the SoM using the “Write configuration” button in the toolbar. When prompted if changed values shall be written, answer “Yes”. Afterwards the locally modified values are transferred to the SoM, where there are only modified in RAM. To make changes permanently, answer the following prompt with “Yes”. Modified IP settings are applicated after restart of the system (power cycle the STM32F4xx/SoM).
...
To establish a cyclic PROFINET communication use the I/O panel of the PNIO Master.
...
...
Please start the example “01_pnio_simple_io” according to the previous descriptions.
To establish a PROFINET communication, at first the SoM must be selected in the “Network Navigator”. Then select the function panel PNIO Master. At first use “Scan device” to detect the PROFINET device.
...
Use the “Wink” command to identify the connected SoM, which will be shown with a flashing “LED1” on the Arduino shield.
To establish a cyclic PROFINET communication use the I/O panel of the PNIO Master.
...
To continue, load the GSDML file provided with the distribution, located in “goal\appl\2015013_irj45\ac\gsdml\GSDML-V2.32-portGmbH-irj45-20180810.xml".
In the selector “Device Access Point” select “2-port Device”.
Afterwards press the “Connect” button. This button initiated a cyclic PROFINET communication.
| Info |
|---|
If the cyclic connection failes, try to decrease the “Device Interval”. Take also a look at our Support Knowledge Base and FAQ. |
The example application on the application controller will mirror the output data to the input data. I/O data can be manipulated and monitored in the I/O Data table. Beside that if a connection is established, the “LED1” Led on the Arduino shield will be enabled.
...
Default settings are compatible with the example. Press the “Connect” button. This button initiated a cyclic EtherNet/IP communication.
The example application on the application controller will mirror the output data to the input data.
...