594280 D01 Software Configuration Control v01r03

Federal Communications CommissionOffice of Engineering and TechnologyLaboratory DivisionJuly 10, 2014SOFTWARE SECURITY REQUIREMENTS FOR U-NII DEVICESI. INTRODUCTIONOn March 31, 2014, the Commission revised the rules in Part 15 that permits U-NII devices in the 5 GHz Band.1 As part of that revision, the Commission required that all U-NII device software be secured to prevent its modification to ensure that the device operates as authorized thus reducing the potential for harmful interference to authorized users.2 Although, the Commission refused to set specific security protocols, the methods used by manufacturers to implement the security requirements must be well documented in the application for equipment authorization. In this document, we provide generalguidance on the type of information that should be submitted in the equipment authorization application. The security description provided in the application must cover software security, configuration, and authentication protocols descriptions, as appropriate. This guidance applies to master and client devices. Special circumstances that apply only to client devices are also addressed.II. SOFTWARE SECURITY DESCRIPTION GUIDEAn applicant must describe the overall security measures and systems that ensure that only:1. Authenticated software is loaded and operating the device; and2. The device is not easily modified to operate with RF parameters outside of the authorization. The description of the software must address the following questions in the operational description for the device and clearly demonstrate how the device meets the security requirements.3 While the Commission did not adopt any specific standards, it is suggested that the manufacturers may consider applying existing industry standards. 4 Also, this guide is not intended to be exhaustive and may be modified in the future. There may be follow-up questions based on the responses provide by the applicant for authorization.SOFTWARE SECURITY DESCRIPTION General Description 1. Describe how any software/firmware update will be obtained,downloaded, and installed.1 See Revision of Part 15 of the Commission’s Rules to Permit Unlicensed National Information Infrastructure (U-NII) Devices in the 5 GHz Band, First Report and Order, ET Docket No. 13-49 (2014) (1st R&O).2For U-NII devices certified as SDR, see KDB Publication 442812 D01. 3 An exhibit that is part of the Operational Description can be subject to confidentiality. Applicants may request that the software description, as part of the operational description exhibit type, be held confidential. If the software description is submitted as the software information exhibit, it is automatically held confidential.4It is suggested that manufacturers follow existing security standards and definitions: X.800, RFC 2828, and IEEE 802.11i.594280 D02 U-NII Device Security v01r012.Describe all the radio frequency parameters that are modified by anysoftware/firmware without any hardware changes. Are these parametersin some way limited, such that, it will not exceed the authorizedparameters?3.Are there any authentication protocols in place to ensure that the sourceof the software/firmware is legitimate? If so, describe in details; if not,explain how the software is secured from modification.4.Are there any verification protocols in place to ensure that thesoftware/firmware is legitimate? If so, describe in details.5.Describe, if any, encryption methods used.6.For a device that can be configured as a master and client (with active orpassive scanning), explain how the device ensures compliance for eachmode? In particular if the device acts as master in some band ofoperation and client in another; how is compliance ensured in each bandof operation?Third-Party Access Control 1.How are unauthorized software/firmware changes prevented?2.Is it possible for third parties to load device drivers that could modify theRF parameters, country of operation or other parameters which impactdevice compliance? If so, describe procedures to ensure that onlyapproved drivers are loaded.3.Explain if any third parties have the capability to operate a US sold deviceon any other regulatory domain, frequencies, or in any manner that is inviolation of the certification.4.What prevents third parties from loading non-US versions of thesoftware/firmware on the device?5.For modular devices, describe how authentication is achieved when usedwith different hosts.III. SOFTWARE CONFIGURATION DESCRIPTION GUIDEIn addition to the general security consideration, for devices which have “User Interfaces” (UI) toconfigure the device in a manner that may impact the operational parameter, the following questions shall be answered by the applicant and the information included in the operational description. The description must address if the device supports any of the country code configurations or peer-peer modecommunications discussed in KDB 594280 Publication D01.5SOFTWARE CONFIGURATION DESCRIPTION USER CONFIGURATION GUIDE 1. To whom is the UI accessible? (Professional installer, end user, other.) a) What parameters are viewable to the professional installer/end-user?6 b) What parameters are accessible or modifiable to the professional installer? i) Are the parameters in some way limited, so that the installers will not enter parameters that exceed those authorized? ii) What controls exist that the user cannot operate the device outside its authorization in the U.S.? c) What configuration options are available to the end-user? i) Are the parameters in some way limited, so that the installers will not enter parameters that exceed those authorized? ii) What controls exist that the user cannot operate the device outside its authorization in the U.S.? d) Is the country code factory set? Can it be changed in the UI? i) If so, what controls exist to ensure that the device can only operate within its authorization in the U.S.? e) What are the default parameters when the device is restarted? 2. Can the radio be configured in bridge or mesh mode? If yes, an attestation may be required. Further information is available in KDB Publication 905462 D02. 3. For a device that can be configured as a master and client (with active or passive scanning),if this is user configurable, describe what controls exist, within the UI, to ensure compliance for each mode. If the device acts as a master in some bands and client in others, how is this configured to ensure compliance?4. For a device that can be configured as different types of access points, such as point-to-point or point-to-multipoint, and use different types of antennas, describe what controls exist to ensure compliance with applicable limits and the proper antenna is used for each mode of operation. (See Section 15.407(a))5 See KDB Publication 594280 D01Software Configuration Control for Devices. The document provides guidance for devices permitting device configurations and limitations on configuration parameters accessible to the third parties.6The specific parameters of interest for this purpose are those that may impact the compliance of the device. These typically include frequency of operation, power settings, antenna types, DFS settings, receiver thresholds, or country code settings which indirectly programs the operational parameters.Change Notice07/10/2014: 594280 D02 UNII Device Security v01 has been changed to 594280 D02 UNII Device Security v01r01. Changes to items 3 and 4 in the Software Configuration Description table.。

研华工控机BIOS设置译本对照BIOS SETUP UTILITY /BIOS设置实用程序Main主要AMIBIOS电脑故障声音提示全解Version :00.00.00版本Build Date:00/00/00创建日期ID :1210X019信息编号Processor处理器Intel(R)Atom(TM)***************英特尔（R）的原子（TM System Memory系统存储器Size大小:2039MBSystem Time系统时间[00:00:00] System Date系统日期[Thu 00/00/0000/]Use [ENTER],[TAB] or [SHIFT-TAB] to select a field.使用[进入]，[标签]或[ shift-tab ]选择一个字段。

Use [+] or [-] to configure system time.使用[ + ]或[ - ]配置系统时间← Select Screen 选择屏幕↑↓ Select Item 选择项目+ - Change Field 更改字段Tab Select Field 选项卡中选择字段F1 General Help F1帮助F10 Save and Exit F10保存并退出ESC Exit ESC退出V02.61 (C)Copyright 1985-2006,American Megatrends,Inc. v02.61（C）版权1985-2006年，美国大趋势，公司--------------------------------------------------------------------------------------------------------------------------------- Advanced高级设置设定Advanced Settings高级设置WARNING: Setting wrong values in below sections may cause system malfunction.警告：在下面设置错误的值可能导致系统故障。

win10蓝屏错误代码0xc0000428解决办法win10系统蓝屏错误提⽰0xc0000428⽆法验证此⽂件的数字签名解决⽅法下⾯⼩编就给⼤家详细的介绍“此⽂件的数字签名⽆法验证”导致蓝屏的图⽂教程吧！在提供“此⽂件的数字签名⽆法验证”错误修复之前，⼩编先解释什么是“数字签名”以及这个错误的罪魁祸⾸可能是什么。

正如“信息安全杂志”在线版中所解释的那样，“数字签名”是⽤于验证消息，软件或数字⽂档真实性和完整性的数学技术。

换句话说，如果软件，⽂档，消息，⾦融交易是数字签名的，其⽤户或接收者确信该软件，⽂档等是安全的并由该特定组织或个⼈拥有。

因此，数字签名有助于防⽌伪造，篡改和摆脱责任。

考虑到这⼀点，“该⽂件的数字签名⽆法验证”的含义和罪魁祸⾸是明确的- 已经安装在您的操作系统上的⽂件或软件不是由Microsoft进⾏数字签名，这就是为什么它⽆法在Windows 10操作系统上运⾏。

如果您最近安装了第三⽅软件，例如⽆法向Microsoft⽀付数字签名，或者最近已经发布并正在等待数字签名，则可能会发⽣这种现象。

⽆论如何，“这个⽂件的数字签名⽆法验证”错误，防⽌您启动到您的操作系统。

特别提醒win10蓝屏多数原因都是驱动问题，在安装更新系统后，⼤家要第⼀时间下载360安全卫⼠和驱动之家进⾏系统修复和驱动安装升级，这样就会减少90%以上的蓝屏问题。

360安全卫⼠领航版 v12.1.0.1113 Beta 官⽅免费安装版类型：⽹络安全⼤⼩：91.1MB语⾔：简体中⽂时间：2020-06-17查看详情360驱动⼤师集成万能⽹卡驱动版 v2.0.0.1690 官⽅安装版类型：驱动下载⼤⼩：189MB语⾔：简体中⽂时间：2021-07-01查看详情360驱动⼤师万能⽹卡版去诱导⼴告 v2.0.0.1590 绿⾊单⽂件版类型：驱动下载⼤⼩：180.5MB语⾔：简体中⽂时间：2020-07-28查看详情360驱动⼤师万能⽹卡版 v2.0.0.1670 中⽂官⽅安装版类型：⽹卡驱动⼤⼩：189MB语⾔：简体中⽂时间：2021-05-11查看详情处理⽅法如下：⽅法⼀.1、连续重启然后强制关机三次，让win10系统⾃动进⼊⾼级启动选项。

Win8.1中常见错误代码店铺带给大家的是win8.1常见错误代码及解决方法汇总，下文将会例举一些win8/win8.1常见问题代码，我们可以根据不同的代码采取不同的解决方法，大家可以来参考一下。

Win8.1中常见错误代码1.找不到详细错误说明。

(错误代码：0xC004C4AA)无法激活具有Media Center 的Windows 8.1 专业版或具有Media Center 的 Windows 8 专业版含义及解决办法：在使用“将功能添加到Windows 8.1”或“将功能添加到Windows 8”来将当前版本的Windows 升级为具有Media Center 的Windows 8.1 专业版或具有Media Center 的Windows 8 专业版之后，可能会看到该错误。

仅可以在以下情况下激活不同版本的 Windows：在预安装 Windows 的电脑上激活，或者Windows 是通过 Windows 网站或零售商店购买的。

要解决此问题，你需要使用通过购买确认电子邮件或DVD 提供的产品密钥来安装Windows。

2.找不到详细错误说明。

(错误代码 0xC004C400)无法激活具有Media Center 的Windows 8.1 专业版或具有Media Center 的 Windows 8 专业版含义及解决办法：在添加 Windows Media Center 包并尝试输入新产品密钥之后，可能会看到该错误。

若要解决此问题，你可以通过手机激活 Windows。

- 从屏幕右边缘向中间轻扫，然后点击“搜索”。

(如果使用鼠标，则指向屏幕右上角，然后将鼠标指针向下移动，再单击“搜索”。

) - 在搜索框中输入 SLUI 04，然后点击或单击“SLUI 04”。

- 按照屏幕上的说明进行操作。

3.正版验证检测到Windows 二进制文件被篡改。

(错误代码0xC004C4AE)含义及解决办法：如果你使用第三方应用添加Windows 当前不支持的显示语言，可能会看到此错误。

如何解决【打开Word等其他软件时自动出现“Windows正在配置AutoC如何解决“窗口正在配置AutoCAD，请稍候”“]问题几天前重新加载了系统。

安装软件后，当打开Word文档时，发现“Windows正在配置AutoCAD......“总是会突然出现。

在打开Word文档之前，有必要“取消”几次或等到它被配置好。

软件环境有:视窗XP SP3、Office2003、AutoCAD2007、思维导图7.1等已尝试:移除Office2003或AutoCAD2007并重新安装。

问题依然存在后来，Word2003被简单地卸载了。

默认情况下，“WPS文本”用于打开Word文档。

暂时不必担心打开Word文档。

如果你今天有空，请试着解决这个问题。

Mindjet MindManager Pro7.1以前已卸载。

因此，在今天安装了Word之后，打开Word文档就很正常了。

放心，也修复了AutoCAD:方法是依次打开”控制面板，添加和删除程序”,选择一个AutoCAD项目，点击右边的”更改”按钮，在弹出的窗口中选择修复-修复注册表项如果您再次尝试打开Word文档，仍然没有问题，并且“Windows正在配置AutoCAD”不会弹出。

分析:网上很多地方说可能是dfst.dll文件引起的，但是这个问题在我使用的版本中不存在(以前的系统也使用这个版本的AutoCAD，但是没有类似的问题)，所以这个问题的原因可能是软件冲突。

需要Microsoft .NET2.0来安装软件，如AutoCAD2007和Mindjet MindManager Pro7.1。

由于安装顺序不同，安装AutoCAD2007时，某些组件可能无法正确配置，这些组件仅与Word相关。

因此，当打开Word文档时，将自动调用AutoCAD2007配置过程。

以下是互联网上的参考资料列表:1。

弹出窗口正在配置AUTOCD 2007。

在弹出的对话框中，建议丢失的文件dfst.dll是由于安装了盗版的AutoCAD，而正版没有这个文件。

英特尔以太网万兆位服务器适配器高级驱动程序设置高级选项卡中的设置让您自定义适配器对QoS 数据包标签、巨帧、分载及其他功能的处理方法。

本页面不适用在其名称中带PRO/10GbE 的适配器。

用于这些适配器，可参阅英特尔® PRO/10GbE 服务器适配器的高级设置。

注意∙某些功能可能不一定可使用，这取决于操作系统和安装的特定适配器。

∙如果安装了英特尔® PROSet Windows 设备管理器版，“高级” 选项卡的布局和功能可用性会有所不同。

∙如果安装了英特尔® PROSet Windows 设备管理器版，便可使用屏幕帮助。

可用设置:流量控制标题数据分割中断节流中断节流率IPv4 校验和卸载巨帧数据包大量接收分载大型发送分载(IPv4)大型发送分载(IPv6)本地管理的地址记录链接状态事件低延迟中断分载TCP 分段优先级和VLAN接收缓冲区接收方调整接收方调整队列TCP 校验和分载(IPv4)TCP 校验和分载(IPv6)传输缓冲区UDP 校验和分载(IPv4)UDP 校验和分载(IPv6)流量控制使适配器能生成流量控制帧或对其作出响应，以帮助调节网络通信量。

流量控制在安装了Windows* 设备管理器英特尔® PROSet 的情况下在性能选项属性下配置。

如果传入帧到达速度超过设备对其处理的速度时，链接伙伴便会超载。

将会丢弃帧，直至超载情况结束。

流量控制机制能解决这种问题，防止丢失帧的情况发生。

如果发生过载的情况，设备会生成流量控制帧。

这会强制传输链接伙伴停止传输，然后尝试再次传输。

注意为使适配器能从此功能获益，链接伙伴必须支持流量控制帧。

Default已启用Rx 和Tx范围禁用: 无流量控制。

启用RX 和TX: 适配器生成流量控制帧并对其作出响应。

启用Rx : 适配器在从链接伙伴接收到流量控制帧时暂停传输。

启用Tx : 适配器在其接收队列达到预定义的限制时生成流量控制帧。

显卡驱动错误代码解析常见错误及解决方法显卡驱动在计算机中扮演着至关重要的角色，它负责控制显卡与操作系统之间的通信，保证图形渲染和图像显示的正常运行。

然而，有时我们可能会遇到显卡驱动错误的情况。

本文将针对常见的显卡驱动错误代码进行解析，并提供相应的解决方法。

错误代码一：代码43错误信息：Windows 已停止此设备，因为它报告了问题。

（代码43）常见原因及解决方法：1. 驱动不兼容：尝试升级显卡驱动至最新版本，或者降级到稳定的旧版本。

2. 显卡设备故障：将显卡从计算机上拆下来重新安装，或更换新的显卡。

3. 电源供应不足：检查电源是否能够提供足够的功率，如果电源不足，则需要更换更高功率的电源。

错误代码二：代码10错误信息：该设备无法启动。

常见原因及解决方法：1. 驱动损坏或丢失：重新安装最新的显卡驱动程序，或者从官方网站下载和安装适合您显卡型号的驱动程序。

2. 系统冲突：检查系统中是否存在其他冲突的设备或软件，并禁用或卸载这些设备或软件。

3. 受损的硬件：将显卡插槽彻底清洁，并确保显卡和主板的连接牢固。

错误代码三：代码28错误信息：该设备没有正常启动，因为部分或全部注册表中的驱动映像无法加载。

常见原因及解决方法：1. 注册表错误：运行系统的“sfc /scannow”命令检查和修复系统文件，或者使用第三方的注册表修复工具进行修复。

2. 硬件冲突：禁用其他设备或打开的程序，确保与显卡驱动程序之间没有冲突。

3. 驱动文件损坏：重新安装或更新显卡驱动程序，确保使用的驱动文件是完整和正确的。

总结：显卡驱动错误是使用计算机过程中常见的问题之一，但我们可以通过以上的解析和解决方法来应对这些错误。

最重要的是，及时升级或降级显卡驱动，确保驱动与操作系统兼容，并始终保持驱动程序的更新。

此外，保持计算机的硬件和软件环境稳定也是非常重要的，时刻注意显卡和其他设备之间的冲突，以确保计算机正常运行。

有时候，如果以上方法都无法解决问题，不妨咨询专业的技术人员，以获得更为准确和有效的解决方案。

mediacreationtool 命令行参数
MediaCreationTool是一款微软开发的软件，用于从Microsoft服务器下载Windows ISO映像。

它支持命令行参数，允许用户通过命令行来启动和配置该工具。

以下是MediaCreationTool支持的一些命令行参数：
/acceptEula：接受软件使用条款。

/install：执行安装程序。

/?, /h, /help：显示帮助信息。

/u：指定用户名。

/p：指定密码。

/target：指定目标文件夹路径，用于保存下载的ISO 映像。

/lang：指定语言。

/sku：指定要下载的Windows版本（例如，Home、Professional等）。

/arch：指定系统架构（例如，x86、x64等）。

/version：指定要下载的Windows版本号（例如，10、
11等）。

/bitsclipper：禁用位剪裁器（bitsclipper）。

/nocopy Protection：禁用复制保护。

这些命令行参数可以帮助用户定制MediaCreationTool 的行为，以满足特定的需求。

请注意，命令行参数的具体使用方法和效果可能因MediaCreationTool的不同版本而有所差异。

在使用命令行参数时，建议查阅官方文档或参考相关资源以获取准确的信息和指导。

修改显卡驱动ID教程转至百度外星人吧（幕后黑手）英伟达的驱动下载好后是个压缩包，解压会在相应目录里找到以337.88驱动版本为例，找到相应图片的目录会发现很多inf文件每个厂商用的文件都是不同的宏碁是nvac.inf华硕是nvam.inf联想是nvlt.inf戴尔是nvdm.inf当然，外星人就是nvdm.inf接下来我们还要查找自己显卡的硬件ID，在设备管理器内，找到自己的显卡，右键属性，点详细信息接下来我们就需要修改inf文件了首先先注意一点，打开inf文件，我们可以看到硬件ID列表中有的在[NVIDIA_SetA_Devices.NTamd64.6.0] 的下面有的在[NVIDIA_SetA_Devices.NTamd64.6.1] 的下面NT6.0也就是vista的代号，说面下面那串ID是对于Vista的NT6.1也就是win7的代号，说明下面那串ID是对于win7的NT6.2也就是win8的代号，说明下面那串ID是对于win8的对于win7用户，我们要确保修改的ID在[NVIDIA_SetA_Devices.NTamd64.6.1] 的下面PCI\VEN_10DE&DEV_119F&SUBSYS_05511028&REV_A1这就是在前面说到的所找到的显卡硬件id号其中119F指的是GTX780m显卡型号我们要在[NVIDIA_SetA_Devices.NT amd64.6.1] 的下面找到相对应开头的。

如图那串字符与我们显卡的硬件ID完全吻合。

说明这个驱动完全适合你的机器你的显卡可以安装。

而对于不能成功安装显卡驱动的用户来说，你们是找不到下图那样与你们硬件ID相吻合的字符的。

这时候我们就要找相近的字符自己进行修改添加。

只需要修改SUBSYS后面的数字和你的硬件ID后面的数字一样就可以了上图为修改后的图，修改之后保存然后将inf文件下拉到底部，会发现然后将对应的显卡，改成相应的id号即可至此，大功告成，保存，然后双击驱动程序进行安装编辑于2015年10月13日星期二。

非常不安全的CDEFAdmin全部共享解决法操作系统C、D、E、F等盘符的共享如何关闭？本人装的是windows系统最近碰到这个问题，首先是对方把我的qq电脑管家本地病毒库在更新时干掉了，接着浏览器自动生成一个快捷图标找不到位置，我知道不对劲，原来是全部盘都共享着。

我上网搜到这篇：2006-02-19 10:01willim72 | 分类：网站使用 | 浏览4458次我安装的winXP sp2操作系统，系统的C、D、E、F等盘符的共享都是打开状态，用瑞星防火墙关闭共享，重启机器后，各盘的共享自动打开，致使上网存在安全隐患，如何解决？我用卡巴的5.0391的最新版本杀过毒了，没有发现病毒。

分享到：2006-02-19 10:08 提问者采纳新建一个记事本,复制以下内容到里面,保存为“关闭默认共享.reg”即可。

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\parameters]"autodisconnect"=dword:0000000f"enableforcedlogoff"=dword:00000001"enablesecuritysignature"=dword:00000000"requiresecuritysignature"=dword:00000000"NullSessionPipes"=hex(7):43,00,4f,00,4d,00,4e,00,41,00,50,0 0,00,00,43,00,4f,\00,4d,00,4e,00,4f,00,44,00,45,00,00,00,53,00,51,00,4c,00,5c,0 0,51,00,55,00,\,00,00,00,4c,\00,4c,00,53,00,52,00,50,00,43,00,00,00,45,00,50,00,4d,00,41, 00,50,00,50,00,\45,00,52,00,00,00,4c,00,4f,00,43,00,41,00,54,00,4f,00,52,00,00 ,00,54,00,72,\00,6b,00,57,00,6b,00,73,00,00,00,54,00,72,00,6b,00,53,00,76, 00,72,00,00,00,\48,00,79,00,64,00,72,00,61,00,4c,00,73,00,50,00,69,00,70,00, 65,00,00,00,54,\00,65,00,72,00,6d,00,53,00,65,00,72,00,76,00,4c,00,69,00,63, 00,65,00,6e,00,\73,00,69,00,6e,00,67,00,00,00,00,00"NullSessionShares"=hex(7):43,00,4f,00,4d,00,43,00,46,00,47 ,00,00,00,44,00,46,\00,53,00,24,00,00,00,00,00"Lmannounce"=dword:00000000"Size"=dword:00000001"Guid"=hex:64,9d,26,92,6e,17,9b,4c,aa,30,a0,dd,35,fc,b8,4e "CachedOpenLimit"=dword:00000000"AutoShareWks"=dword:00000000"AutoShareServer"=dword:00000000提问者评价：你的这个方法最好，我试过了，关闭了共享，省事省力，非常方便，谢谢。

DediProg SF Software User ManualV6.4I. Introduction (3)II. Software Installation Guide (3)2.1 Operating System Requirement (3)2.2 USB Installation (3)III. DediProg SF Software Engineering GUI (9)3.1 Prepare the Environment (9)3.2 Identify the Target SPI Flash (10)3.3 Tool Bar Description (11)3.4 Edit Window Description (12)3.5 Configuration Window Description (14)3.6 Supported Devices, Software Version, Firmware Version (27)IV. DediProg SF Software Production GUI (28)4.1 Search and Select (30)4.2 Batch Config (32)4.3 Single Site programming (32)V. DediProg Windows Command Line (33)5.1 Introduction (33)5.2 How to Start (36)5.4 Basic Switches (36)5.5 Optional Switches (37)5.6 Exit Code (39)VI. Specific Functions (SF600 and SF600Plus) (40)6.1Dual/Quad IO (40)6.2 Hold Pin Status Setting (40)VII. Stand Alone Mode (SF600Plus only) (41)7.1 Project preparation (41)7.2 Stand Alone programming (44)VIII. Firmware Support for Microsoft Windows (45)IX. Revision History (46)FileSelect image: load the file you intend to program. application SPI Flash size.BlankBlank check: check if the target serial flash is Blank (All Erased)EraseErase SPI Flash: Erase the full content in a Serial Flash. After “Erase” the target serial flash shall be blank.ProgProgram: Program the selected image into the Serial FlashVerifyVerify the checksum value of the selected image and the programmed Serial Flash contentBatchBatch operation: The programmer will perform a pre‐configured set of operations such as (reload file + erase + program + verify) all together in one click. The configuration can be set by clicking on the “Config” button. The configuration will not be changed until it is re‐configured.Press start button can do batch function when user run the SF software.EditWhen click on Edit, the programmer will by default display the selected file content. User can click on “read” to read and display the chip contents. See “Edit window description” for more details.ConfigThis allows users to configure advanced settings. See “advanced settings window description” for more detailsLoad PrjLoad the existed project to execute the programming operation.Save PrjSave all programming settings to a project file for reducing re‐setting action.Download PrjSF600Plus only, please refer to Chapter 7‐ VII. Stand Alone Mode (SF600Plus only).3.4 Edit Window DescriptionSPI Flash content display:In the edit window, file contents and chip contents can be displayed in the same time so that user can make the comparison. By default the selected file contents are displayed once the user enters into the edit window.The user can click on “Open” if another file contents are to be shown. The user can click on “Read” in order to read the chip contents are display them on the edit window as well. Checksum of file contents and chip contents are displayed.C.Update memory only on sector locations with contents difference or Smart updateUser can select the sector locations to have the file programmed.‐ Update start from address (Hex):To program a whole file starting from address 0 of a chip.‐ Update up to address (Hex):To program a whole file, ending at the last address of a chip. The default endingaddress will automatically calculated by the software according to memory size.When the user clicks on Batch button, the following operations will be automaticallyexecuted:1) Read the memory content2) Compare the memory content from the given address with the file at the 64KBsector base3) Erase only the 64KB sectors with some differences4) Program only the erased sectors with the file data of the corresponding address5) Verify the data on the updated 64KB sectorsSmart Update can be used in the following cases:-A small file can be programmed or updated at a given address without any change on the rest of the memory (local update).-A file with only minor change compare to the memory content can be quickly updated. The sectors without difference are kept unchanged.Remark:The file data which are identical with the target memory but with an address shift(after compilation) will be interpreted as different and will not benefit of the Smartupdate advantages.D.Update memory and keep one protected area unchangedWhen the user clicks on Batch button, the following operations will be automaticallyexecuted:1) Read the memory content from the given address for the given length2) Insert the read memory contents into the file buffer3) Erase the whole chip4) Program the whole chip with the updated file in step 25) Verify the programmed dataF.Enable Freescale EzPort MCU & Send the DIV value (Hex)If the box is checked, the programmer will automatically enable EzPort. Details please seeMethods Comparison:Case 1:64Mb Serial flash update with 64Mb file totally different. Memory has been previously programmed and need to be totally erased.Chip Erase: 50secSector Erase (64KB): 0.8secChip: 128 sectorsUpdate with BC Update without BC Smart Update Memory Read 32 sec none 32 secCompare 1 sec none 1 secErase 50 sec 50 sec 100 secProgram 64 sec 64 sec 64 secVerify 32 sec 32 sec 32 secTOTAL 179 seconds 146 seconds 229 secondsComparison ChartConclusion:If the memory needs to be completely Erased for a file update, the “Update without Blank Check” is the optimum choice.Time Saving: 20%64Mb Serial flash programming with a 64Mb file.Memory has never been programmed (from supplier).Update with BC Update without BC Smart UpdateMemory Read 32 sec none 32 secCompare 1 sec none 1 secErase 0 sec 50 sec 0 secProgram 64 sec 64 sec 64 secVerify 32 sec 32 sec 32 secTOTAL 129 seconds 146 seconds 129 secondsComparison ChartConclusion:If the memory is blank (from supplier), the “Update with Blank Check” or “Smart update” is the optimum choice.Time Saving: 12%64Mb Serial flash update with a 64Mb file with only data differences on 2 sectors or a small file of 2 sectors size only at a specified address.Sector Erase: 0.8 secSector Programming: 0.5 secSector Verify: 0.25 secUpdate with BC Update without BC Smart Update Memory Read 32 sec none 32 secCompare 1 sec none 1 secErase 50 sec 50 sec 1.6 secProgram 64 sec 64 sec 1 secVerify 32 sec 32 sec 0.5 secTOTAL 179 seconds 146 seconds 36 secondsComparison ChartConclusion:If the difference between the memory content and file are small or if the file to be programmed is small, the “Smart update” is the optimum choice.Time Saving: 75%Status window Programmer Site Status bar Log Windowthe to‐be‐programmed chip is selected, thethe Programmer SITE Status bar, the status5.2 How to StartDediProg window dos command line software is executed by the file “dpcmd.exe.” There are three different ways to run the dos command line.1.Double click on the “dpcmd” icon on your desktop and type in dpcmd and enter.2.Change your dos directory to the same location where “dpcmd.exe” is located.C:\program files\dediprog\SF1003.Type in the following command to auto directs the dpcmd command to the“dpcmd.exe” location.Set path=%path%;”c:\program files\dediprog\SF1005.3 Basic Usages1. dpcmd ‐r"f:\file.bin",reads the chip and save it into a file "file.bin"2. dpcmd ‐rSTDOUT ‐a0x100 ‐l0x23,reads 0x23 bytes starting from 0x100 and display it on the screen3. dpcmd ‐ufile.bin,erases and then program file.bin into the serial flash4. dpcmd ‐pfile.bin ‐a0x100,writes file.bin into the serial flash starting from address 0x1005. dpcmd ‐pfile.bin ‐x0xaa,programs file.bin into the serial flash and fill the rest area with 0xaaRemarks: ‐a, ‐l only works with ‐p, ‐r, ‐sRemarks: ‐x only works with ‐pRemarks: space is not needed between the switches parameters. E.g. dpcmd ‐ubio.bin5.4 Basic Switches‐? [ ‐‐help ]‐‐list‐d [ ‐‐detect ]‐b [ ‐‐blank ]‐e [ ‐‐erase ]‐r [ ‐‐read ] arg‐p [ ‐‐prog ] arg‐u [ ‐‐auto ] arg‐ Erase only the sectors ‐z [ ‐‐batch ] argShow this help messagePrint supproted chip listdetect chipblank checkerase entire chipread chip contents and save to a bin/hex/s19 fileuse STDOUT for the console.program chip without eraseutomatically run the following sequence:‐ Read the memory c‐ Compare the memory content references‐ Program only the erased sectors with the file data from address 0automatically run the following sequence:‐s [ ‐‐sum ]‐f [ ‐‐fsum ] arg‐‐raw‐instruction arg‐‐raw‐require‐return arg (=0)‐ check if the chip is blank or not;‐ erase the entire chip(if not blank);‐ program a whole file starting from address 0 display chip content checksumdisplay the file checksum‐ needs to work with a fileissue raw serial flash instructions.‐ use spaces(" ") to delimit bytes.‐ instructions must be enclosed in double quotationmarks("")Example:dpcmd ‐‐raw‐instruction "03 FF 00 12"decimal bytes of result to return in decimal after issuing raw instructions.‐ used along with ‐‐raw‐instruction only. Example:dpcmd ‐‐raw‐instruction "03 FF 00 12"raw‐require‐return 15.5 Optional Switches(Specify the following switches to change default values):‐a [ ‐‐addr ] arg‐l [ ‐‐length ] arg‐v [ ‐‐verify ]‐x [ ‐‐fill ] arg (=FF)‐‐type arghexadecimal starting address hexadecimal (e.g. 0x1000),‐ works with ‐‐prog/read/sum/auto only ‐ defaults to 0, if omitted. hexadecimal length to read/program in bytes, ‐ works with ‐‐prog/read/sum/auto only ‐ works with ‐‐prog, ‐‐auto onlySpecify a type to override auto detection‐ use ‐‐list arguement to look up supported type.‐‐lock‐start arg‐‐lock‐length arg‐‐blink arg‐‐device arg‐‐fix‐device arg‐ defaults to whole file if omittedverify checksum file and chip‐ works with ‐‐prog/auto onlyfill spare space with an hex value(e.g. FF),hexadecimal starting address(e.g. 0x1000),‐ works with ‐‐prog/read/sum/auto only ‐ defaults to 0, if omitted. hexadecimal length of area that will be kept unchanged while updating ‐ used along with ‐‐auto only.‐ 0 : Blink green LED 3 times from USB1 to USBn (Default)note: the sequence is assigned by OS during USB plug‐in‐ 1: Blink the programmer connected to USB1 3 times.‐‐list‐device‐id arg‐ n: Blink the programmer connected to USBn 3 times. (work with all Basic Switches)‐ 1 : activate only the programmer connected to USB1‐ n : activate only the programmer connected to USBnnote: if "‐‐device" is not used, the command will be executed with the same chip type and file on all connected programmer. Fix programmer serial number with programmer sequence.‐ instructions must be enclosed in double quotation marks("") Example:dpcmd ‐‐fix‐device "1 DP000001"‐ 0 : List all ID of programmers from USB1 to USBn (Default)note: the sequence is assigned by OS during USB plug‐in‐ 1 : Prompt the device ID of programmer connected to USB1. ‐ n : Prompt the device ID of programmer connected to USBn.Miscellaneous options:Note: The programming operation always uses the default value for command. If users want to use other setting, must add the wanted option to every command.‐t [ ‐‐timeout ] arg (=300) ‐g [ ‐‐target ] arg (=1) Timeout value in seconds Target Options Available values:1, Chip 1(Default)2, Chip 23, Socket0, reference card‐‐vcc arg (=0) specify vcc0, 3.5V(Default)1, 2.5V2, 1.8V1800 ~ 3800, 1.8 ~ 3.8V (minimum step 100mV)(For SF600/SF600Plus only)‐‐vpp ‐ work with ‐‐prog and ‐‐erase.apply vpp when the memory chip supports it‐‐log write operation result into file"%appdata%\dediprog\SF100\log.txt"‐i [ ‐‐silent ] suppress the display of real‐time timer counting‐ used when integrating with 3rd‐party tools (e.g. IDE) ‐‐spi‐clk arg (=2) specify SPI clock:2, 12 MHz(Default)0, 24 MHz1, 8 MHz3, 3 MHz4, 2.18 MHz5, 1.5 MHz6, 750 KHz7, 375 KHz5.6 Exit Codeenum ErrorCode{EXCODE_PASS,EXCODE_FAIL_ERASE,EXCODE_FAIL_PROG,EXCODE_FAIL_VERIFY,EXCODE_FAIL_READ,EXCODE_FAIL_BLANK, // 5EXCODE_FAIL_BATCH,EXCODE_FAIL_CHKSUM,EXCODE_FAIL_IDENTIFY,EXCODE_FAIL_OTHERS=99,};VIII.Firmware Support for Microsoft WindowsConsider the programming stability with the software and firmware on Windows 8.1. DediProg modify the way of communication between Windows and SF serial products. Please note the software and firmware compatibility. Before you update the firmware, please make sure your software is the latest version.User can download the latest version on DediProg website./downloadSF100 5.x.x 5.5.0SF600 6.x.x 6.9.0SF600 7.x.x 7.1.0 and above versionIX. Revision HistoryDate Version Changes2010/03/195.5Added: Enable EzPort Function on Configuration; log.txt file available on Commend line; Blink/Device/Fix ‐Device on Dpcmd. 2010/04/14 5.6 Added: Update up to address option on Batch and Program Configuration operation options. 2010/05/10 5.7 Minor improvement 2011/05/18 5.8 1. Added specific function.2.Added region configuration programming function.2011/08/26 5.9 Added SF600 Hold pin status setting method. 2012/01/09 6.0 Added SF600 stand alone programming. 2012/12/20 6.1 Revise the CLI detail and add exit codes. 2013/08/236.21. Added status register ‐2 function2. Added the multiple ‐Dpcmd function. 2013/12/18 6.3 1. Remove part of SF200 and SF3002.Remove “isolation free” from software2014/02/256.41. New feature for SF600PlusInformation furnished is believed to be accurate and reliable. However, DediProg assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties which may result from its use. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. All rights reserved Printed in Taiwan.DediProg Technology Co., Ltd (Taiwan)4F., No.7, Ln. 143, Xinming Rd., Neihu Dist., Taipei City 114, Taiwan TEL: 886-2-2790-7932 FAX: 886-2-2790-7916DediProg Technology (ShangHai) Room 503, Block E, No.1618, Yishan Road, Shanghai, China TEL: 86-21-5160-0157 FAX: 86-21-6126-3530 Technical Support：******************** Sales Support：****************** 。

Win10提⽰错误0xc0000428⽆法验证此⽂件的数字签名怎么办？电脑安装的是Windows 10系统，因为安装某些软件或驱动程序后，⽆法开机，提⽰：Windows 未能启动。

原因可能是最近更改了硬件或软件。

⽂件：windows\system32\drivers\amd_xata.sys。

状态：0xc0000428信息：Windows⽆法验证此⽂件的数字签名。

如何解决Windows ⽆法验证此⽂件数字签名的问题呢？⼀、问题描述Win10系统电脑，因为安装某些软件或驱动程序后，⽆法开机，提⽰：Windows 未能启动。

原因可能是最近更改了硬件或软件。

⽂件：windows\system32\drivers\amd_xata.sys状态：0xc0000428信息：Windows⽆法验证此⽂件的数字签名。

⼆、解决办法1、按下主机上电源键（笔记本按下键盘上电源键） - 关机，关机后再按下电源键重新开机，开机后按下键盘上的 Ctrl 键，进⼊【选择操作系统】界⾯，点击：更改默认值或选择其他选项；2、然后进⼊【选项】界⾯，我们点击：选择其他选项，进⼊【选择⼀个选项】界⾯；3、在【选择⼀个选项】窗⼝中，点击：4、在【疑难解答】窗⼝中，我们再点击：5、在⾼级选项窗⼝中，点击：⽅法⼀：禁⽤驱动程序强制签名在启动设置窗⼝中，重启以更改 Windows 选项，例如：……禁⽤驱动程序强制签名。

我们点击：重启；电脑重新启动，启动后进⼊【启动设置】窗⼝，我们按下键盘上的数字键【7】；按下键盘上的数字键【7】后，电脑再次重新启动，进⼊系统桌⾯，问题解决。

⽅法⼆：进⼊带命令提⽰符的安全模式，执⾏bcdedit.exe /set nointegritychecks on命令。

在在启动设置窗⼝中，重启以更改 Windows 选项，例如：……启⽤带命令提⽰符的安全模式。

我们点击：重启；电脑重启后，⾃动进⼊命令提⽰符窗⼝，我们将bcdedit.exe /set nointegritychecks on命令复制到命令提⽰符窗⼝中，按下键盘上的回车键，显⽰：操作成功完成。

mediacreationtool错误代码Media Creation Tool 错误代码有 0x000013A、0xC1900102、0xC1900101、0x80070003、0x80042405、0x8007002C、0xC1900208、0x80240020、0x80070070、0xC1900107、0xC1900200、0x800F0923、0x80070002、0x80070652、0x80070020、0x8007000E 。

0X000013A：此错误代表组件更新时出现问题，可能是下载文件已损坏或丢失，也可能是 Windows 更新过程出现了问题。

0XC1900102：此错误代表系统中存在系统错误，通常伴随着“更新的系统检测不到”的消息而出现。

0XC1900101：此错误代表在安装过程中检测到一个严重的错误，表明系统正在安装新的更新，但无法安装这个更新。

0X80070003：此错误代表未能安装新的更新，因为系统上存在一些文件缺失或已损坏。

此错误代码可能会随着“Windows 更新中出现错误”的消息一起出现。

0X80042405：此错误代表由于磁盘上的某些文件已损坏或丢失，因此无法安装更新。

0X8007002C：此错误代表未能安装新的更新，因为 windows_root \ temp 文件夹中的文件已损坏或丢失。

0XC1900208：此错误代表 Media Creation Tool 在处理文件时出现错误，很可能是由于文件夹权限问题导致的。

此错误代码会随着“找不到要安装的文件”的消息一起出现。

0X80240020：此错误代表未能安装新的更新，由于 Windows Update 已暂停，可能是由于系统中存在一些活动进程。

0X80070070：此错误代表磁盘上没有足够的可用空间，无法安装新的更新，可能是由于内部缓存或用户文件中包含大量尚未删除的文件。

0XC1900107：此错误代表由于未能正确检测系统，无法继续安装新的更新。

Intel® Dynamic Load Balancer(Intel® DLB) SoftwareUser GuideRev. v7.8.0Sept 2022Rev.: v7.8.0Intel ® DLB Software User Guide Sept 2022 2Rev.: v7.8.0Intel technologies may require enabled hardware, software or service activation. No product or component can be absolutely secure. Your costs and results may vary.No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. All product plans and roadmaps are subject to change without notice.The products described may contain design defects or errors known as errata, which may cause the product to deviate from published specifications. Current characterized errata are available on request.Intel does not control or audit third-party data. You should consult other sources to evaluate accuracy.Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.Customer is responsible for safety of the overall system, including compliance with applicable safety-related requirements or standards.© Intel Corporation. Intel, Xeon, and the Intel logo, and other Intel marks are trademarks of Intel Corporation or itssubsidiaries. Other names and brands may be claimed as the property of others. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.Table of ContentsIntel ® DLB SoftwareSept 2022 User GuideRev.: v7.8.03Table of Contents1 Introduction .............................................................................................................. 5 2Build Instructions ...................................................................................................... 6 2.1 Package Contents .............................................................................................. 6 2.2 Intel ® DLB Linux Driver Build .............................................................................. 6 2.3 Intel ® DPDK DLB PMD Build ................................................................................. 7 2.4 Libdlb build ....................................................................................................... 7 3Sample Applications (8)3.1 Libdlb Sample Apps ............................................................................................ 8 3.2 DPDK Sample Apps ............................................................................................ 8 3.3 DLB Monitor .................................................................................................... 10 3.4DLB Debug Utility (11)TablesTable 1.Terminology (5)Intel ® DLB Software User Guide Sept 2022 4Rev.: v7.8.0Revision HistoryIntel ® DLB SoftwareSept 2022 User GuideRev.: v7.8.0 5®1 IntroductionThe Intel ® Dynamic Load Balancer (Intel ® DLB) is a PCIe device that provides load-balanced, prioritized scheduling of events (that is, packets) across CPU cores enabling efficient core-to-core communication as discussed in this White Paper . It is a hardware accelerator located inside the latest Intel ® Xeon ® devices offered by Intel. It supports the event-driven programming model of DPDK's Event Device Library. This library is used in packet processing pipelines for multi-core scalability, dynamic load-balancing, and variety of packet distribution and synchronization schemes. The DLB can also be used without DPDK as discussed later in this document.This document describes the steps involved in building The DLB Kernel Driver, DPDK DLB Poll Mode Driver and running the sample applications. It also introduces libdlb, the client library for building DLB applications without using DPDK framework. This release package supports Intel Dynamic Load Balancer 2.0 only. Disclaimer:This code is being provided to potential customers of DLB to enable the use of DLB well ahead of the and upstreaming process. Based on the open source community feedback, the design of the code module can change in future, including API interface definitions. If the open source implementation differs from what is presented in this release, Intel reserves the right to update the implementation to align with the open source version at a later time and stop supporting this early enablement version.Table 1. TerminologyBuild InstructionsIntel ® DLB Software User Guide Sept 2022 6Rev.: v7.8.0®2Build Instructions2.1Package ContentsThis software release is provided as a gzip archive that can be unzipped to install the provided files and documentation. The archive is designed to provide three major components:1. DLB Kernel Driver Source Code2. Files needed to patch DPDK to enable both PF (Physical Function) andbifurcated modes. 3. The libdlb files that can be leveraged to use DLB without using DPDK.For supported kernels, refer to README. When unzipped, the included files/directories will be structured as follows: dlb ||-driver ||-dlb2 ||-dpdk ||-dpdk_dlb_xxx.patch ||-libdlb ||-docs2.2 Intel ® DLB Linux Driver BuildDLB2 driver uses the kbuild build system. To build out-of-tree, simply run 'make'. You can optionally provide the KSRC environment variable to specify the kernel source tree to build against. (If unspecified, build uses the host OS's kernel headers.)$ cd $DLB_SRC_TOP(top-level directory of the extracted DLB source package tarball)$ cd dlb/driver/dlb2 $ makeIntel ® DLB SoftwareSept 2022 User GuideRev.: v7.8.0 7®2.3 Intel ® DPDK DLB PMD BuildMore details on DLB PMD can be found athttps:///guides/eventdevs/dlb2.htmlTo apply the addon patch and build DPDK, follow these steps:$ cd $DLB_SRC_TOP$ wget <URL for DPDK base package> $ tar xfJ dpdk-<DPDK version>.tar.xz$ cd dpdk-<DPDK version> (This is the $DPDK_DIR path used in steps ahead)$ patch -Np1 < $DLB_SRC_TOP/dlb/dpdk/<DPDK patch name>.patchFor meson-ninja build :$ export DPDK_DIR=path to dpdk-<DPDK version> $ export RTE_SDK=$DPDK_DIR $ export RTE_TARGET=installdir$ meson setup --prefix $RTE_SDK/$RTE_TARGET builddir $ ninja -C builddir installAdditional meson configuration and build options can be found on .2.4 Libdlb buildTo build libdlb:$ cd $DLB_SRC_TOP/dlb/libdlb $ makeSample ApplicationsIntel ® DLB Software User Guide Sept 2022 8Rev.: v7.8.0®3Sample Applications3.1Libdlb Sample AppsThe Libdlb library provides directed and load-balanced traffic tests to demonstrate features supported by DLB. The sample codes are located at libdlb/examples and are built together with libdlb in section 2.4. Details of supported APIs can be found in the software release under docs/libdlb_html, documentation is accessible from index.html that can be opened using any browser. To load the dlb kernel driver and run the sample applications, follow these steps :$ modprobe mdev $ modprobe vfio_mdev $ cd $DLB_SRC_TOP/dlb$ insmod driver/dlb2/dlb2.ko $ cd libdlbFor Directed Traffic test:$ LD_LIBRARY_PATH=$PWD ./examples/dir_traffic -n 128 For Load Balanced Traffic test:$ LD_LIBRARY_PATH=$PWD ./examples/ldb_traffic -n 128(n: number of events to be sent)The default wait mode supported is the interrupt mode. “-w ” option can be used to change to poll or epoll mode. Use “-h” to display other command line options for the sample applications.3.2 DPDK Sample AppsDPDK contains dpdk-test-eventdev, a small standalone application to demonstrate eventdev capabilities. Following are the steps to run its order_queue test with DLB. DLB eventdev supports two modes of operation, Bifurcated and the PF PMD modes. Either of the two can be used to run the sample app : 1) Load the drivers needed for DPDK applications:•For Bifurcated mode, load the DLB Kernel Driver:$ insmod $DLB_SRC_TOP/dlb/driver/dlb2/dlb2.ko•For PF PMD mode, bind DLB to either vfio-pci or uio_pci_generic driver. For vfio-pci driver :Intel ® DLB SoftwareSept 2022 User GuideRev.: v7.8.0 9®$ modprobe vfio$ modprobe vfio-pci$ lspci -d :2710 #Check the DLB2.0 device id (For ex: eb:00.0)$ $DPDK_DIR/usertools/dpdk-devbind.py --bind vfio-pci \eb:00.0For uio_pci_generic driver :$ modprobe uio_pci_generic$ $DPDK_DIR/usertools/dpdk-devbind.py \ --bind uio_pci_generic eb:00.02) Setup Hugepages: Check if the hugepage requirements are met using the following command:$ cat /proc/meminfo | grep HugeIf no hugepages are available, setup 2048 count of 2048kB sized hugepages as below (sudo required) :$ mkdir -p /mnt/hugepages$ mount -t hugetlbfs nodev /mnt/hugepages$ echo 2048 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages3) Run the application$ cd $DPDK_DIR (DPDK base directory) $ cd builddir/app• To run the application in PF PMD Mode$ ./dpdk-test-eventdev -c 0xf -- --test=order_queue \--plcores=1 --wlcore=2,3 --nb_flows=64•To run the application in Bifurcated mode, --vdev=dlb2_event needs to be passed$ ./dpdk-test-eventdev -c 0xf --vdev=dlb2_event \-- --test=order_queue --plcores=1 --wlcore=2,3 \ --nb_flows=64Sample ApplicationsIntel ® DLB Software User Guide Sept 2022 10Rev.: v7.8.0®dpdk-test-eventdev’s perf-queue test can be used to explore the different queue types supported by DLB. The –-stlist command-line option allows configuring the number of stages and scheduling types . ‘p’ for parallel, ‘a’ for atomic and ‘o’ forordered queue types. --prod_enq_burst_sz option can be used for producer core to enqueue burst of events.This test can also be run in both PF and Bifurcated PMD modes. Follow Steps 1 and 2 from above to load required drivers and setup hugepages, if not already done. To run the application in PF PMD mode :./dpdk-test-eventdev -c 0xf -- --test=perf_queue --plcores=1 \ --wlcore=2,3 --nb_flows=64 --stlist=p --prod_enq_burst_sz=64For Bifurcated PMD mode :./dpdk-test-eventdev -c 0xf --vdev=dlb2_event -- \--test=perf_queue --plcores=1 --wlcore=2,3 --nb_flows=64 \ --stlist=p --prod_enq_burst_sz=64More details of different testcases supported by dpdk-test-eventdev app and command-line options can be found inhttps:///guides-21.11/tools/testeventdev.html3.3 DLB MonitorThe DPDK patch provides dlb_monitor application, a telemetry tool that collects and displays DLB hardware and software configuration and statistics. The tool also identifies and reports common misconfiguration issues and potential applicationperformance issues. When any dpdk application is run, dlb_monitor can be triggered as a secondary process to monitor eventdev port, queue, device status. This toolcannot be started independently without a primary process running. The stats can be printed once, or the application can run in ‘watch mode’ (-w option) and the data is repeatedly collected and displayed at a user-specified frequency.$ cd builddir/app•To run dlb_monitor in PF PMD Mode :$ ./dpdk-dlb_monitor -- -w•To run in Bifurcated PMD Mode :$ ./dpdk-dlb_monitor --vdev dlb2_event -- -wIntel ® DLB Software Sept 2022 User Guide Rev.: v7.8.0 11 ®3.4 DLB Debug Utility The DLB tar file provides dlb_monitor_sec application, a tool that collects and displays DLB hardware register configuration and statistics for the libdlb applications. When any DLB application is run, dlb_monitor_sec can be triggered as another process to monitor port, queue, device status. The stats can be printed once, or the application can run in ‘watch mode’ (-w option) and the data is repeatedly collected and displayed at a user-specified frequency. • To run dlb_monitor_sec : $ cd dlb/libdlb/cli $ ./dlb_monitor_sec -w ‘-i’ option can be used to specify the DLB Device ID. Device 0 is used by default. More supported options can be found using ‘-h’ (help).。

Application Note nForce 220/420 Platform Installing nForce Core Drivers Under Windows 98Installing Core DriversUnder Windows 98 This application note provides instructions to install the NVIDIA nForce coredrivers (GART, Ethernet, Audio, Audio Utilities, SMBUS and Memory Controller)under Windows 98. Currently, the NVIDIA installer supports Windows XP,Windows 2000 and Windows ME. Use the following procedure to install allNVIDIA devices under Windows 98 until the release of Windows 98 installersupport.To install the nForce integrated video driver, use the standard Windows installationsteps for ‘Updating a Video Driver.’Driver Package ContentsIt is recommended to have the following nForce drivers before proceeding:q GART Driverq Audio Drivers with Audio Utilitiesq Ethernet Driverq SMBUS Driver (System Management Bus)q Memory Controller DriverInstalling GART DriversWhen a Windows 98 operating system is installed, there are a series of unknowndevices in Windows 98 Device Manager. To install the nForce GART drivers, usethe following procedure:1. Extract the GART driver package to a temporary location.GART Manager is present in Device Manager under: PCI Standard Host CPUBridge. Microsoft Generic Drivers are used until you upgrade with the properGART drivers.2. Go to the Device Manager (STARTØCONTROL PANELØSYSTEMØDEVICE MANAGER).3. Look for the following devices:- NVIDIA nForce GART Manager- PCI Standard Host CPU Bridge- PCI standard PCI-to-PCI bridge device4. Update the drivers using the ones saved into the temporary location instep 1.5. Restart your system.Installing the Audio DriversUse the following procedure to install nForce Audio drivers:1. Extract the Audio driver package to a temporary location.Use the drivers from Audio Driver package to enumerate all unknown mediaclass devices.2. Go to the Device Manager (STARTØCONTROL PANELØSYSTEMØDEVICE MANAGER).3. Look for the following devices:Unknown Drivers- NVIDIA Audio Codec Interface- NVIDIA Media Controller ProcessorSound, Video, and Game Controllers- NVIDIA nForce Audio Codec Interface- NVIDIA nForce MCP Audio Processing UnitNote: Various nForce Audio items Under Sound, Video and GameControllers will be replaced when the System Devices are updated.4. Update the drivers using the ones saved into the temporary location instep 1.5. Restart your system.Installing Ethernet DriversUse the following procedure to install Ethernet drivers:1. Extract the Ethernet driver package to a temporary location.Use the drivers from the Ethernet Driver package to enumerate the unknownEthernet Device.2. Go to the Device Manager (STARTØCONTROL PANELØSYSTEMØDEVICE MANAGER).3. Look for the following devices:Unknown Drivers- NVIDIA Ethernet DeviceNetwork Adapters- NVIDIA nForce MCP Networking Adapter4. Update the drivers using the ones saved into the temporary location instep 1.5. Restart your system.Installing SMBus DriversUse the following procedure to install Ethernet drivers:1. Extract the SMBus driver package to a temporary location.SMBus needs to be enabled for DDC to function correctly and systemmanagement functions to be enabled.2. Go to the Device Manager (STARTØCONTROL PANELØSYSTEMØDEVICE MANAGER).3. Go to Unknown Devices / PCI System Management Bus4. Update the drivers using the ones saved into the temporary location instep 1.5. Restart your system.Updating MemoryController Drivers1. Extract the files from the (os)\memory directory of the driver package to atemporary location.Microsoft Generic Drivers will be used. To replace the Microsoft drivers withNVIDIA drivers, continue with Step 2.Note: Several instances of Memory Controller may be present in DeviceManager under:- Windows 9x/ME or Windows 2000/XP- PCI Standard RAM Controller2. Go to the Device Manager (STARTØCONTROL PANELØSYSTEMØDEVICE MANAGER).3. Look for the following devices:System Devices- PCI Standard RAM Controller- NVIDIA nForce 420 Memory Controller- NVIDIA nForce 220/420 Memory Controller4. Update all instances of these drivers using the ones saved into the temporarylocation in step 1.5. Restart your system.Note: It is important to restart your computer after all drivers are installed.Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication or otherwise under any patent or patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. NVIDIA Corporation products are not authorized for use as critical components in life support devices or systems without express written approval of NVIDIA Corporation.TrademarksNVIDIA, the NVIDIA logo, and nForce are trademarks of NVIDIA Corporation.Microsoft, Windows and the Windows logo are registered trademarks of Microsoft Corporation Other company and product names may be trademarks of the respective c ompanies with which they are associated.CopyrightCopyright NVIDIA Corporation 2001NVIDIA Corporation2701 San Tomas ExpresswaySanta Clara, CA 95050。

© Copyright 2017-2019 Hewlett Packard Enterprise Development LP通知本文档中包含的信息如有更改，恕不另行通知。

随 Hewlett Packard Enterprise 产品和服务提供的明确保修声明中阐明了此类产品和服务的全部保修服务。

此处的任何内容都不应视作额外的担保信息。

对于本文档中包含的技术或编辑方面的错误或疏漏，Hewlett Packard Enterprise 不承担任何责任。

保密的计算机软件。

必须具有 Hewlett Packard Enterprise 颁发的有效许可证，方可拥有、使用或复制本软件。

按照 FAR 12.211 和 12.212 的规定，可以根据供应商的标准商业许可证授权美国政府使用商用计算机软件、计算机软件文档以及商业编号的技术数据。

单击指向第三方网站的链接将会离开 Hewlett Packard Enterprise 网站。

Hewlett Packard Enterprise 无法控制 Hewlett Packard Enterprise 网站之外的信息，也不对这些信息承担任何责任。

商标声明Microsoft®、Windows®和 Windows Server®是 Microsoft Corporation 在美国和（或）其他国家（或地区）的注册商标或商标。

Linux®是 Linus Torvalds 在美国和其他国家（地区）的注册商标。

Red Hat®是 Red Hat, Inc. 在美国及其他国家（地区）的注册商标。

SD 和 microSD 是 SD-3C 在美国和/或其他国家（地区）的商标或注册商标。

VMware®是 VMware, Inc. 在美国和/或其他司法辖区的注册商标或商标。

目录使用本指南 (10)入门 (10)支持的服务器 (10)其它故障排除资源 (11)故障排除的准备工作 (12)服务器故障排除的前提条件 (12)重要安全信息 (12)设备上的符号 (13)警告和小心 (13)静电释放 (14)防止静电释放 (14)防止静电释放的接地方法 (15)收集症状信息 (15)诊断服务器前的准备工作 (15)处理器故障排除准则 (16)将服务器降级到最低硬件配置 (17)常见问题的解决方法 (18)解决连接松动问题 (18)搜索服务通知 (18)固件更新 (18)在启用了 HPE 可信平台模块和 BitLocker 的情况下更新服务器 (19)DIMM 处理准则 (19)DIMM 和 NVDIMM 安装信息 (19)在 HPE ProLiant Gen10 服务器上支持的 Intel Xeon 可扩展处理器 (20)DIMM-处理器兼容性 (20)NVDIMM-处理器兼容性 (20)组件 LED 指示灯定义 (20)存储 (20)SAS、SATA 和 SSD 驱动器准则 (20)热插拔驱动器 LED 定义 (21)半高 LFF 驱动器 LED 指示灯定义 (22)NVMe SSD LED 指示灯定义 (22)SFF 闪存适配器组件和 LED 指示灯定义 (24)系统电源 LED 指示灯定义 (24)运行状态条形 LED 指示灯定义（仅限 c 系列服务器刀片） (25)前面板 LED 指示灯和按钮 (25)前面板 LED 指示灯注释 (26)使用服务器运行状况摘要 (26)前面板 LED 指示灯电源故障代码 (28)控制器和能源包电缆 (29)远程故障排除 (30)远程故障排除工具 (30)远程访问 Virtual Connect Manager (31)3使用 iLO 远程排除服务器和服务器刀片的故障 (31)使用 Onboard Administrator 对服务器刀片进行远程故障排除 (32)使用 OA CLI (32)诊断流程图 (34)诊断步骤 (34)在开始之前收集重要信息 (34)故障排除流程图 (34)使用诊断流程图 (34)初始诊断 (34)远程诊断流程图 (35)开机故障流程图 (36)ML 和 DL 系列服务器的服务器开机故障流程图 (36)XL 系列服务器的服务器开机故障流程图 (38)BL 系列服务器刀片的服务器刀片开机故障流程图 (40)POST 故障流程图 (43)POST 问题 - 服务器在 POST 期间挂起或重新引导流程图 (44)POST 问题 - 无法引导，没有视频流程图 (46)POST 问题 - 可以引导，没有视频流程图 (47)操作系统引导故障流程图 (48)Intelligent Provisioning 故障流程图 (49)控制器故障流程图 (51)HPE Smart Array 控制器的能源包问题 (53)物理驱动器故障流程图 (56)逻辑驱动器故障流程图 (58)故障指示流程图 (59)非刀片服务器的服务器故障指示流程图 (60)BL c 系列服务器刀片的服务器刀片故障指示流程图 (62)网卡故障流程图 (64)常规诊断流程图 (67)硬件问题 (70)用于所有 ProLiant 服务器的步骤 (70)电源问题 (70)服务器无法开机 (70)供电来源问题 (70)电源问题 (71)没有足够的电源配置 (72)UPS 问题 (73)UPS 无法正常供电 (73)显示电池电量不足警告 (74)UPS 上的一个或多个 LED 指示灯呈红色 (74)常规硬件问题 (74)新硬件问题 (74)未知问题 (76)第三方设备问题 (76)测试设备 (77)驱动器问题（硬盘驱动器和固态驱动器） (78)驱动器发生故障 (78)无法识别驱动器 (78)无法访问数据 (79)服务器响应时间比平时长 (80)HPE SmartDrive 图标或 LED 指示灯指示驱动器错误，或者在 POST、HPE SSA 或HPE SSADUCLI 中显示错误消息 (81)4SSD Smart Wear 错误 (81)诊断阵列问题 (81)HPE Smart Array SR 和 MR Gen10 控制器的诊断工具 (81)存储控制器问题 (82)常规控制器问题 (82)控制器不再是冗余的 (83)在 RAID 模式下访问的驱动器上的数据与在非 RAID 模式下访问的数据不兼容 (84)在将驱动器移到新的服务器或 JBOD 后，Smart Array 控制器不显示这些驱动器 (84)驱动器漫游 (84)具有 10 SFF 驱动器背板或 12 LFF 驱动器背板的服务器上的数据故障或磁盘错误 (84)禁用 RAID 模式后找不到 HPE Smart Array S100i SR Gen10 驱动器 (85)无法识别 HPE Smart Array S100i SR Gen10 驱动器 (85)风扇和散热问题 (86)常规风扇问题 (86)风扇的运行速度比预期速度高 (87)风扇噪音太大（高速） (87)风扇噪音太大（低速） (88)热插拔风扇问题 (88)HPE BladeSystem c 系列机箱风扇高速运行 (89)内存问题 (89)常规内存问题 (89)隔离并最小化内存配置 (90)服务器内存不足 (90)DIMM 配置错误 (90)服务器无法识别现有的内存 (91)服务器无法识别新的内存 (92)无法修复的内存错误 (93)超过可纠正的内存错误阈值 (94)NVDIMM 问题 (94)NVDIMM 安装错误 (94)已禁用 NVDIMM (95)在操作系统中不显示持久性内存驱动器 (96)持久性内存驱动器是只读的 (96)持久性内存驱动器不再具有持久性 (97)HPE 可扩展持久性内存问题 (98)在操作系统中不显示持久性内存驱动器 (98)持久性内存驱动器是只读的 (100)持久性内存驱动器不再具有持久性 (101)HPE 可扩展持久性内存备份和恢复失败 (102)无法配置可扩展持久性内存 (103)处理器问题 (104)排除处理器故障 (104)无法纠正的计算机检查异常 (105)可信平台模块问题 (105)TPM 发生故障或检测不到它 (105)系统电池电量不足或耗尽 (106)主板和电源背板问题 (106)microSD 卡问题 (107)系统无法从 microSD 卡引导 (107)U 盘问题 (107)系统无法从 U 盘引导 (107)图形和视频适配器问题 (108)排除常规图形和视频适配器故障 (108)视频问题 (108)打开服务器电源后屏幕黑屏超过 60 秒 (108)如果使用节能功能，显示器无法正常工作 (109)显示颜色不对 (110)5显示慢慢移动的水平线 (110)鼠标和键盘问题 (110)扩展卡问题 (111)系统在更换扩展卡期间要求使用恢复方法 (111)网络控制器或 FlexibleLOM 问题 (111)安装了网络控制器或 FlexibleLOM，但无法正常工作 (111)网络控制器或 FlexibleLOM 已停止工作 (112)在添加扩展卡后，网络控制器或 FlexibleLOM 停止工作 (112)网络互连模块刀片问题 (113)具有 AMD 处理器的 HPE ProLiant Gen10 服务器的网络性能或虚拟机性能问题 (113)能源包问题 (114)Gen10 服务器中的能源包支持 (114)能源包在长期搁置后可能会耗尽电量 (114)能源包配置错误 (115)能源包故障 (115)电缆问题 (116)在使用较旧的小型 SAS 电缆时，发生驱动器错误、重试、超时和无根据的驱动器故障 (116)无法识别 USB 设备，显示错误消息，或者设备在连接到 SUV 电缆时无法开机 (116)软件问题 (117)操作系统问题和解决方法 (117)操作系统问题 (117)操作系统锁定 (117)错误日志中显示错误 (117)在安装 Service Pack 后出现问题 (117)更新操作系统 (118)更新操作系统的前提条件 (118)更新操作系统 (118)重新配置或重新加载软件 (118)重新配置或重新加载软件的前提条件 (118)还原备份版本 (119)Linux 资源 (119)应用程序软件问题 (119)软件锁定 (119)更改软件设置后出错 (119)更改系统软件后出错 (120)安装了应用程序后出错 (120)ROM 问题 (120)远程 ROM 刷新问题 (120)命令行语法错误 (120)目标计算机上拒绝访问 (121)无效或不正确的命令行参数 (121)网络连接在进行远程通信时失败 (121)ROM 刷新期间发生故障 (121)不支持目标系统 (122)系统在固件更新期间要求使用恢复方法 (122)引导问题 (123)服务器无法引导 (123)UEFI 服务器的 PXE 引导准则 (125)软件和配置实用程序 (126)服务器模式 (126)产品规格说明简介 (126)6Active Health System Viewer (126)Active Health System (127)Active Health System 数据收集 (127)Active Health System 日志 (127)HPE iLO 5 iLO (127)iLO 联合 (128)iLO服务端口 (128)iLO RESTful API (129)RESTful Interface Tool (129)iLO Amplifier Pack (129)Integrated Management Log (129)Intelligent Provisioning (129)Intelligent Provisioning 操作 (130)管理安全性 (131)适用于 Windows 和 Linux 的 Scripting Toolkit (131)UEFI System Utilities (131)选择引导模式 (131)安全引导 (132)启动嵌入式 UEFI Shell (133)HPE Smart Storage Administrator (133)HPE MR Storage Administrator (134)StorCLI (134)USB 支持 (134)外置 USB 功能 (134)支持冗余 ROM (134)安全性和安全优势 (135)使系统保持最新状态 (135)更新固件或系统 ROM (135)Service Pack for ProLiant (135)更新 System Utilities 中的固件 (136)从 UEFI 嵌入式 Shell 中更新固件 (137)联机刷新组件 (137)驱动程序 (137)软件和固件 (137)支持的操作系统版本 (138)HPE Pointnext 产品 (138)主动通知 (138)报告和日志 (139)报告和日志概述 (139)Active Health System 日志 (139)Active Health System 日志下载方法 (139)下载某个日期范围的 Active Health System 日志 (139)下载整个 Active Health System 日志 (140)使用 cURL 下载 Active Health System 日志 (141)清除 Active Health System 日志 (143)通过 IP 下载 AHS 日志 (143)下载 Active Health System 日志 (iLOREST) (144)使用 AHSV 排除故障或打开支持案例 (145)Intelligent Provisioning 诊断工具 (145)Integrated Management Log (145)查看 IML (145)使用 HPE SSA 执行诊断任务 (146)HPE Smart Storage Administrator Diagnostics Utility CLI (146)安装实用程序 (146)7在 CLI 模式下启动该实用程序 (146)诊断报告过程 (147)查看诊断报告 (147)识别和查看诊断报告文件 (147)SmartSSD Wear Gauge 报告过程 (148)查看 SmartSSD Wear Gauge 报告 (148)识别和查看 SmartSSD Wear Gauge 报告文件 (148)HPS 报告 (148)Linux 报告 (148)故障排除资源 (149)在线资源 (149)Hewlett Packard Enterprise 支持中心网站 (149)Hewlett Packard Enterprise 信息库 (149)以前的 HPE ProLiant 服务器型号的故障排除资源 (149)服务器刀片机箱故障排除资源 (149)故障排除资源 (149)服务器文档 (150)服务器用户指南 (150)服务器维护和维修指南 (150)设置和安装指南 (151)HPE iLO 软件文档 (151)UEFI System Utilities 文档 (151)Intelligent Provisioning 软件文档 (151)产品规格说明简介 (151)白皮书 (151)服务通知、咨询和通告 (151)订阅服务 (152)HPE Pointnext 产品 (152)产品信息资源 (152)其他产品信息 (152)HPE SmartMemory 速度信息 (152)注册服务器 (152)服务器功能概述和安装说明 (152)主要功能和选件部件号 (152)服务器和选件的规格、符号、安装警告和通告 (153)HPE Smart Array 控制器文档 (153)备件号 (153)拆卸步骤、部件号和规格 (153)拆卸和更换步骤视频 (153)技术主题 (153)产品安装资源 (153)外部布线信息 (153)电源容量 (154)开关设置、LED 指示灯功能、驱动器、内存、扩展卡和处理器安装说明以及板卡布局.154产品配置资源 (154)Data Center Infrastructure Advisor (154)设备驱动程序信息 (154)DDR4 内存配置 (154)操作系统安装和配置信息（对于出厂时安装的操作系统） (154)服务器配置信息 (154)服务器设置软件的安装和配置信息 (154)服务器的软件安装和配置 (154)HPE iLO 信息 (155)服务器管理 (155)8服务器管理系统的安装和配置信息 (155)容错、安全保护、保养和维护、配置和设置 (155)网站 (156)支持信息和其他资源 (157)获取 Hewlett Packard Enterprise 支持 (157)获取更新 (157)客户自行维修 (158)远程支持 (158)保修信息 (158)法规信息 (158)文档反馈 (159)症状信息检查清单 (160)9使用本指南入门注意：对于常见的故障排除步骤，“服务器”一词用于表示服务器和服务器刀片。