Problem Description
Customers upgrading with analog packages OSN2500 Network element to V2R11C00SPC200 version, found that N4EFS0 reported
SWDL_PKG_NOBDSOFT, and the alarm does not go away after redoing the loading package.
查询升级后的单板信息为:
:cfg-get-bdverinfo:17
BOARD-VER-INFO
PCB Version : SSN1EFS0 VER.C
BIOS Version . 2.14
ExtBIOS Version : 2.34
Software Version : 7.53
Logic Version : (U10)300(U42)211
Ucode Version : 6.03
Checking the version matching table, I found that the matching table lists the logic as (U42)210, and the note states that it is normal to query the version to show 210 or 211.
SWDL_PKG_NOBDSOFT, and the alarm does not go away after redoing the loading package.
查询升级后的单板信息为:
:cfg-get-bdverinfo:17
BOARD-VER-INFO
PCB Version : SSN1EFS0 VER.C
BIOS Version . 2.14
ExtBIOS Version : 2.34
Software Version : 7.53
Logic Version : (U10)300(U42)211
Ucode Version : 6.03
Checking the version matching table, I found that the matching table lists the logic as (U42)210, and the note states that it is normal to query the version to show 210 or 211.
SWDL _PKG_NOBDSOFT
1. The alert does not disappear after reloading the package.
2. There are two types of logic that have been used on the N4EFS0 veneer (these two types of logic have exactly the same functionality and implementation), one is the standalone FPGA, and the other is the logic that is cured onto the veneer (this logic cannot be upgraded).
The product shows the FPGA version as 210 and the version of the cured logic as 211 for the sake of differentiation, but since the companion table and the software package can only be written in one version, it is written as 210.
The product is shown in a different version for the sake of differentiation, and the version of the FPGA is shown in a different version. br/> Because the N4EFS0 used in the field is the logic cured to the single board, so the SWDL_PKG_NOBDSOFT alarm is reported. In fact, the version is matching, belonging to the software misreporting.
3. In the V200R011C00SPC300 version, the problem will be completely solved by modifying the compatibility field of N4EFS0 FPGA in sccpkg.ini.
2. There are two types of logic that have been used on the N4EFS0 veneer (these two types of logic have exactly the same functionality and implementation), one is the standalone FPGA, and the other is the logic that is cured onto the veneer (this logic cannot be upgraded).
The product shows the FPGA version as 210 and the version of the cured logic as 211 for the sake of differentiation, but since the companion table and the software package can only be written in one version, it is written as 210.
The product is shown in a different version for the sake of differentiation, and the version of the FPGA is shown in a different version. br/> Because the N4EFS0 used in the field is the logic cured to the single board, so the SWDL_PKG_NOBDSOFT alarm is reported. In fact, the version is matching, belonging to the software misreporting.
3. In the V200R011C00SPC300 version, the problem will be completely solved by modifying the compatibility field of N4EFS0 FPGA in sccpkg.ini.
2. There is a problem with the software package
None
END


Chinese
English





