Embedded Connectivity
Intel network controllers, Firmware, and drivers support systems
879 Discussions

Unable to update CAM firmware on an Intel E810 NIC via the devlink interface

PhaniNarasimham
378 Views

Sir,

Need to updated CAM firmware via software tool. Attached the error and details encountered with devlink and nvmupdate tool. Please advice on the documents to check and tool to use for updation.

===================================================================

NVM Update Tool : 

To avoid damage to your device do not stop the update or reboot or power off the system during update

Intel Ethernet controller E810-C for SRP, DevID, 1593, 00:067, Update not available.

====================================================================

Subject: Devlink Flash Not Working on Kernel 5.10.0 for CAM Firmware

 

Description:

While attempting to flash CAM firmware on an Intel E810 NIC using the devlink interface on a system running 

Linux kernel version 5.10.0, the firmware update process does not complete as expected.

 The devlink tool fails

 to initiate the flashing of the firmware file CAM1_Whitestone2_v_4_20.bin. 

 According to Intel document #630155_CVL_EXTERNAL_E810 Feature Summary, kernel versions 5.10

 and later 

 should fully support NVM (Non-Volatile Memory) updates through the devlink interface, but this issue

 is still observed.

 

===========================================================================

 

Thank you for sharing the information. Since the Intel® Ethernet Controller E810-CAM1 is

 integrated into the system, we recommend posting your query in the Embedded Connectivity forum 

for further information regarding the query.

 

Please follow the link below for Embedded Connectivity.

 

https://community.intel.com/t5/Embedded-Connectivity/bd-p/embedded-networking-connectivity

 

 

2 days ago 14:52

 ===========================================================================

 

Thank you for contacting Intel Support. We appreciate you sharing the detailed information. We kindly request you to check the link below for complete information regarding the Devlink user guidelines to update a device's NVM.

https://edc.intel.com/content/www/de/de/design/products/ethernet/adapters-and-devices-user-guide/using-devlink-to-update-a-device%E2%80%99s-nvm/

We recommend that you use the NVM Update tool.

 See Intel® Ethernet NVM Update Tool for more information on this tool.

If you have any questions or doubts, Please reach out to us, We are happy to help you!

We appreciate your understanding!

 

===========================

Card details:

43:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)

DeviceName: E810 CAM1 Port1

Subsystem: Mitac Device 0014

Physical Slot: 2

Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+

Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

Latency: 0, Cache Line Size: 32 bytes

Interrupt: pin A routed to IRQ 16

NUMA node: 0

IOMMU group: 22

Region 0: Memory at 202ffa000000 (64-bit, prefetchable) [size=32M]

Region 3: Memory at 202ffe030000 (64-bit, prefetchable) [size=64K]

Expansion ROM at be200000 [disabled] [size=1M]

Capabilities: <access denied>

Kernel driver in use: ice

Kernel modules: ice

 

43:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)

DeviceName: E810 CAM1 Port2

Subsystem: Mitac Device 0014

Physical Slot: 2

Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+

Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

Latency: 0, Cache Line Size: 32 bytes

Interrupt: pin A routed to IRQ 16

NUMA node: 0

IOMMU group: 23

Region 0: Memory at 202ff8000000 (64-bit, prefetchable) [size=32M]

Region 3: Memory at 202ffe020000 (64-bit, prefetchable) [size=64K]

Expansion ROM at be100000 [disabled] [size=1M]

Capabilities: <access denied>

Kernel driver in use: ice

Kernel modules: ice

 

43:00.2 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)

DeviceName: E810 CAM1 Port3

Subsystem: Mitac Device 0014

Physical Slot: 2

Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+

Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

Latency: 0, Cache Line Size: 32 bytes

Interrupt: pin A routed to IRQ 16

NUMA node: 0

IOMMU group: 24

Region 0: Memory at 202ff6000000 (64-bit, prefetchable) [size=32M]

Region 3: Memory at 202ffe010000 (64-bit, prefetchable) [size=64K]

Expansion ROM at be000000 [disabled] [size=1M]

Capabilities: <access denied>

Kernel driver in use: ice

Kernel modules: ice

 

===========================================================

[ognb@WS03-A3370001 ~]$ lscpu

Architecture: x86_64

CPU op-mode(s): 32-bit, 64-bit

Byte Order: Little Endian

CPU(s): 64

On-line CPU(s) list: 0-63

Thread(s) per core: 2

Core(s) per socket: 32

Socket(s): 1

NUMA node(s): 1

Vendor ID: GenuineIntel

CPU family: 6

Model: 143

Model name: Intel(R) Xeon(R) Gold 6433N

Stepping: 8

CPU MHz: 1400.000

CPU max MHz: 3600.0000

CPU min MHz: 800.0000

BogoMIPS: 2800.00

Virtualization: VT-x

L1d cache: 48K

L1i cache: 32K

L2 cache: 2048K

L3 cache: 61440K

NUMA node0 CPU(s): 0-63

Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 invpcid_single cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_pkg_req hfi avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr avx512_fp16 flush_l1d arch_capabilities

===========================================================================

 

Translate

Add tags

NVM-Update (1).png

307 KB

0 Kudos

Reply

2 Replies

Sort by 

Oldest to Newest

Diego_INTEL

Moderator

‎09-27-2024 07:18 AM

 85 Views

Hello @PhaniNarasimham,

 

Thank you for contacting Intel Embedded Community.

 

You can check document #602853 - Intel® Ethernet Network Controller - Handbook:

Section "13.1.4 - How do I update the E810 NIC NVM?"

 

If the problems persist, please use the IPS service:

https://www.intel.com/content/www/us/en/support/articles/000057045/ethernet-products.html

 

Or try submitting a new forum in Ethernet Products indicating that it is related to the ethernet controller E810:

https://community.intel.com/t5/Ethernet-Products/bd-p/ethernet-products

 

Best regards,

 

@Diego_INTEL 

Translate

Add tags

0 Kudos

 

Novice

‎09-27-2024 08:06 AM

 77 Views

sir,

 #602853 - Intel® Ethernet Network Controller - Handbook:

Section "13.1.4 - How do I update the E810 NIC NVM?"

Can you please provide me the link for the document.

Translate

Add tags

 

0 Kudos
1 Reply
CarlosAM_INTEL
Moderator
358 Views

Hello, @PhaniNarasimham:


Thank you for contacting Intel Embedded Community.

 

We found that you created a previous thread, which is similar to this forum. It can be found on the following website:

https://community.intel.com/t5/Embedded-Connectivity/unable-to-update-cam-firmware-using-devlink-or-nvm-update-tool/m-p/1633588#M5542

 

Please stay tuned to the previous forum to receive the proper answer, and avoid duplicate efforts.

 

Best regards,

@CarlosAM_INTEL.

 

 

0 Kudos
Reply