'SDO write failed' errors observed during firmware upgrade

[powerlink-team-kalycito]

Bug Description:

Stack version : V2.6.0-rc1
SHA : b3f8283
Test case : Firmware upgrade test
Managing Node : Linux edrv
Controlled Node: Bus Controllers
Cycle time : 50ms

Bug Summary:

During firmware upgrade test, 'SDO write failed' errors are observed.

Steps to generate CDC using openCONFIGURATOR V2.2:

1. Import Demo_3CN_ openCONFIGURATOR project
2. Add 3 CNs to the network
3. Add Bus controller firmware files to added CNs
   • Add 3 different versions of firmware file to the same CN
4. Build the openCONFIGURATOR project

Steps to reproduce:

1. Compile the hardware, stack, driver and application
   • From openCONFIGURATOR output location, copy the fw.info file, mnobd.cdc and fw folder in the demo_mn_console.exe path.
2. Run the demo_mn_console application

Expected Behavior:

Firmware upgrade should be successful without any error.

Observed Behavior:

Firmware upgrade happens, with the below error messages:

FWM: Updating node 0xXX
FWM: Updating node 0xXX
FWM-ERROR: SDO write failed for node 0xX with state: 0x5 and abort code 0x5040000
FWM-ERROR: SDO written number of bytes does not match for node 0xX:1016 - 299504
FWM-ERROR: SDO event with abort code: 0x5040000 for node 0xX
FWM: Updating node 0xXX
FWM: Updating node 0xXX

[zelenkaj]

Hello,

can you please share the complete console log (stdout and stderr) in a text file!

Thanks + regards,
Joerg

[powerlink-team-kalycito]

Hello Joerg,

Please find below the console log and screenshot of error message displayed.

Firmware-test-SDO-err.txt

[powerlink-team-kalycito]

Hello Joerg,

Please find attached wireshark trace for the corresponding error. We see (from wireshark trace) that SDO close (Packet no. 53) is happening during initial stages of SDO transfer, but the firmware upgrade is successful. Kindly consider the priority of bug and assign the milestone.

Firmware-test-trace.zip

[powerlink-team-kalycito]

The 'SDO write failed' error observed during firmware upgrade was not reproducible in the latest stack version(develop-2.7.0) with commit SHA 8d2357a.

Hence this bug can be closed.