PN-Driver V2.1, PNConfigLib V1.0: CD content including patches
For download section please scroll down.
Patches for PN-Driver:
Patch 03: The following bugs have been fixed
- PRM-Write with CM_ERR_PRM_ACCESS_DENIED leads to fatal error
This fix handles CM_ERR_PRM_ACCESS_DENIED error during PRM-Write operation and prevents the fatal error.
- Wrong handling of jumbo frames in packet32 receive mechanism
When Jumbo frames (size > 1518) are received, packet32 EDDS lower layer will drop the frame by returning EDD_STS_OK_NO_DATA . With this fix, jumbo frames are handled in the LL_RECV function call.
- PNIO_ALARM_PROCESS doesn't occur during a hardware interrupt
Maximum data length of a submodule has been increased to 1024 bytes as described in Quick Start document.
Patch 02: The following bugs have been fixed
- PNDevDrv compilation problems with kernel 4.9.0-8-rt-amd64 (RT Debian 4.9.144-3.1 x86_64)
Kernel version of PnDevDriver for Linux is upgraded to 4.9.144 including RT patch. With this update the PN Driver is now updated to be used with the following Linux version: 4.9.0-8-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux
- AR breakdown after moderate TCP netload
Lower Layer Packet32 returned EDD_STS_OK_NO_DATA if they received a frame with invalid unicast MAC. This behavior is incorrect, since EDD_STS_OK_NO_DATA means, no more Data received, which makes the scheduler end the current receiving cycle. The problem has been fixed by jumping back to the start of the function instead of returning EDD_STS_NO_DATA. This fix ensures that additional packets can be received if available.
- Wrong error in ART-testcase MRP_CHK1
The fix solves the wrong error hierarchy for PDEV records.
- PNDevDriver Linux 32 Bit Error
The fix solves the memory allocation issue for Linux 32 Bit kernel.
- Fix issue introduced with RQ 3938736: AR breakdown after moderate TCP netload
The fix solves the issue which has been introduced with RQ "AR breakdown after moderate TCP netload".
Patch 01: The following bugs have been fixed
- ModuleDiffBlock information is transported to the user application:
PNIO_CTRL_ALARM_DATA structure has been enhanced as it includes a new object which is of type PNIO_ALARM_MOD_DIFF_BLOCK . The new object consists of ModuleDiffBlock as a byte array and the length information as the number of bytes.
The user application can read ModuleDiffBlock information within the callback function which is registered for alarm indications via PNIO_controller_open() IO-Base function. This information is valid for only the following alarm types:
- ModuleDiffBlock is parsed by the example application "test_app":
The example application "test_app" parses ModuleDiffBlock information if it is available within the alarm indication and prints the result on the display.
- Zero is supported as the minimum value of MaxRecordSize:
PN Driver version 2.1 accepts the value range of 1 - 65535 for the MaxRecordSize attribute of an IO device. However, because of historical reasons, the attribute value in the hardware configuration might be zero too.
PN Driver supports zero as the minimum value for the MaxRecordSize attribute and assigns the default value 4068 to the attribute internally, with this fix.
- The crash due to accumulated DCP hello frames has been fixed:
PN Driver version 2.1 crashes sporadically in case of prioritized startup and high system load. This is because DCP Hello frames which belong to the prioritized startup sequence are not processed at the expected time if the controller is under load.
This problem has been fixed and late processing of the DCP frames does not cause a crash anymore.
- Wrong next-hop value has been fixed:
The fix solves a potential problem about the reporting of the next-hop entry in the ipRouteTable of MIB-II. Typical error case is that the next-hop value is shown as 22.214.171.124.
- Make a backup of your source files
- Extract the archive file which includes this fix
- Replace all of the PN Driver source files with the files which you have extracted from the archive file
How to upgrade Linux Kernel version (Patch 03):
- for 32-bit systems:
The packages linux-image-4.9.0-8-rt-686 and linux-image-4.9.0-8-rt-amd64 are outdated and replaced with the more recent packages linux-image-4.9.0-11-rt-686 and linux-image-4.9.0-11-rt-amd64. Therefore, we recommend you to install the real-time kernel from the repository with the following command:
sudo apt install 4.9.0-11-rt-686
- for 64-bit systems:
sudo apt install 4.9.0-11-rt-amd64
In section 4.2.3 of Quick Start document, the procedure of building a Yocto image is explained. Because of the location change of one of the external resources, you must run the following command
sed -i 's/wagi\/linux-cip-rt/cip\/linux-cip/g' meta-iot2000-bsp/recipes-kernel/linux/linux-ciprt_4.4.bb
kas build meta-iot2000-example/kas-rt.yml
Please refer to readme documentation for further information and known problems section.
Patches for PNConfigLib:
Patch 02: The following bugs have been fixed
The patch affects the behaviour of PNConfigLib for invalid GSDML files.
Interpreter project inside PNConfigLib solution is responsible for checking the validity of GSDML file which is given as input to PNConfigLib. Since Interpreter methods are not called correctly by PNConfigLib, GSDML validations are not executed, so that PNConfigLib generates output with an invalid GSDML file instead of an error message. This problem is fixed with patch 02.
Patch 01: There is no such patch; Release Version is V1.0.1.
A password is required to unzip all files. Registered customers will receive the password from the ComDeC.firstname.lastname@example.org
Patch 03 - update recommended
Size: 14449181 Bytes (13 MiB)
only for backup:
Size: 14318122 Bytes (13 MiB)
Size: 14151462 bytes (13 MiB)
Patch 02 - update recommended
Size: 3164623 Bytes (3090 KiB)
Checksum information: (How do you determine the SHA-256 checksum of a file?:109483101