Put Linux files, ko and demo_mn on SD.
Start system. Mount card and install ko as described in Readme.
Start demo_mn. On the other side I have X20BC0083.
First run - no problem. Devices connect. Lights on X20BC0083 running.
Press Ctrl-C for stopping demo_mn.
I start it again and recieve an error:
Initializing openPOWERLINK stack...
2016/03/05-06:56:57 INFO CONTROL Initializing openPOWERLINK stack
oplk_initialize() failed with "Resource could not be created (Windows, PxROS, ...)" (0x0008)
2016/03/05-06:56:57 FATAL CONTROL oplk_init() failed with "Resource could not be created (Windows, PxROS, ...)" (0x0008)
oplk_freeProcessImage() failed with "API called but stack is not initialized/running" (0x014e)
oplk_execNmtCommand() failed with "API called but stack is not initialized/running" (0x014e)
Stack is in state off ... Shutdown
I remove ko module and insert it again.
Start demo_mn. Previous error disappeared, but mn can't connect to cn, always cyclically restart. Cycle output:
Thanks you for trying out the prebuilt Zynq Linux demo binaries and getting back with the problem.
With regards to the first issue, i.e. after the MN demo is stopped the kernel driver module has to be unloaded and loaded again for the demo to work, is a known issue. It is due to the reason that the POWERLINK device node (in Linux kernel used for Zynq) is deleted automatically when the demo MN is stopped even when the kernel module is not unloaded. This creates an error when restarting the demo application since it needs the POWERLINK device to start demo operation.
The second issue observed, i.e. the CN device not connecting to MN after successfully restarting the demo MN, from the console log it is unclear as to what is the exact problem. Can you please post the complete console log and if possible a network trace for the same?
Best regards,
Powerlink team,
Kalycito
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the detailed logs and sorry for the late reply.
We are able to reproduce the behavior you observed with the demo binaries and it seems that the MN has problems in receiving the PRes frames from the CN when the demo is started a second time without powercycling the board.
We have added this to the bug list of the openPOWERLINK stack development. Since we are already moving the Zynq based designs to the latest Vivado tool chain (now it is on ISE) for openPOWERLINK version 2.5 and the behavior may have been due to a tool chain bug, the bug fix is planned for the version 2.5 of the stack with the latest toolchain. Meanwhile the board has to be powercycled for running the demo after stopping it once.
Regards,
Powerlink team,
Kalycito
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello!
Took Linux prebuild files for Zynq ZC702 here - https://sourceforge.net/projects/openpowerlink/files/QuickStartGuides/Xilinx_Zynq_ZC702/
Put Linux files, ko and demo_mn on SD.
Start system. Mount card and install ko as described in Readme.
Start demo_mn. On the other side I have X20BC0083.
First run - no problem. Devices connect. Lights on X20BC0083 running.
Press Ctrl-C for stopping demo_mn.
I start it again and recieve an error:
I remove ko module and insert it again.
Start demo_mn. Previous error disappeared, but mn can't connect to cn, always cyclically restart. Cycle output:
And one time I've got a Kernel Panic.
Where could I make mistake? Or it's a problem with prebuild files?
Last edit: Maksim 2016-04-22
Hi Maksim,
Thanks you for trying out the prebuilt Zynq Linux demo binaries and getting back with the problem.
With regards to the first issue, i.e. after the MN demo is stopped the kernel driver module has to be unloaded and loaded again for the demo to work, is a known issue. It is due to the reason that the POWERLINK device node (in Linux kernel used for Zynq) is deleted automatically when the demo MN is stopped even when the kernel module is not unloaded. This creates an error when restarting the demo application since it needs the POWERLINK device to start demo operation.
The second issue observed, i.e. the CN device not connecting to MN after successfully restarting the demo MN, from the console log it is unclear as to what is the exact problem. Can you please post the complete console log and if possible a network trace for the same?
Best regards,
Powerlink team,
Kalycito
First run (after unload-load ko) - recive Kernel panic:
Second try - same result. On the third I recieved situation described earlier (full log from first start demo_mn):
Network trace in attachment.
Hello Maksim,
Thank you for the detailed logs and sorry for the late reply.
We are able to reproduce the behavior you observed with the demo binaries and it seems that the MN has problems in receiving the PRes frames from the CN when the demo is started a second time without powercycling the board.
We have added this to the bug list of the openPOWERLINK stack development. Since we are already moving the Zynq based designs to the latest Vivado tool chain (now it is on ISE) for openPOWERLINK version 2.5 and the behavior may have been due to a tool chain bug, the bug fix is planned for the version 2.5 of the stack with the latest toolchain. Meanwhile the board has to be powercycled for running the demo after stopping it once.
Regards,
Powerlink team,
Kalycito