Programming of i210 on ARM aarch64 (raspberrypi) platform

[Arno70]

Hi everybody,

I need to program the i210 device on my custom-board, which is equipped with a raspberrypi CM4 compute module.

I have downloaded:
- 513655_I210_I211_Production_images.zip
- 348742_Quartzville Tools_704968.zip

As no LANCONF binary seems available for my architecture, I found that I might need to use EepromAccessTool instead and downloaded
- 572162-eepromaccesstool-0.8.0.zip

When starting the tool on the device, a Kernel panic is issued and the device is halted:

# EepromAccessTool

Intel(R) EEPROM Access Tool NVM/OTP Programming E[ 2813.858945] SError Interrupt on CPU2, code 0x00000000bf000002 -- SError
[ 2813.858959] CPU: 2 PID: 7789 Comm: EepromAccessToo Tainted: G O 5.15.92-v8 #1
[ 2813.858968] Hardware name: Raspberry Pi Compute Module 4 Rev 1.1 (DT)
[ 2813.858972] pstate: 20000000 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2813.858980] pc : 000000556be265b8
[ 2813.858983] lr : 000000556be26d88
[ 2813.858985] sp : 0000007fd2859b40
[ 2813.858987] x29: 0000007fd2859b40 x28: 0000007fd2859bc8 x27: 0000000000000100
[ 2813.858999] x26: 0000000000001531 x25: 000000556be41038 x24: 0409800600004019
[ 2813.859008] x23: 0000000007bc003d x22: 000000556be41010 x21: 0000000000000001
[ 2813.859016] x20: 000000559595a2b0 x19: 0000007fd2859bc8 x18: 0000000000000000
[ 2813.859023] x17: 0000007f934cb090 x16: 000000556be40ea8 x15: 0000008086000000
[ 2813.859030] x14: 0000000000000000 x13: 2e2e2e64726f7720 x12: 646e616d6d6f6320
[ 2813.859038] x11: 00000000ffffffd0 x10: 00000000ffffff80 x9 : 0000007f9358c628
[ 2813.859046] x8 : 0000000000000001 x7 : be5b1656a3515c0d x6 : 0000000000000000
[ 2813.859053] x5 : 0000000600800000 x4 : 0000000000000004 x3 : 0000000000000001
[ 2813.859060] x2 : 0000000000001565 x1 : 0000000000001531 x0 : 00000000deaddead
[ 2813.859069] Kernel panic - not syncing: Asynchronous SError Interrupt
[ 2813.859073] CPU: 2 PID: 7789 Comm: EepromAccessToo Tainted: G O 5.15.92-v8 #1
[ 2813.859079] Hardware name: Raspberry Pi Compute Module 4 Rev 1.1 (DT)
[ 2813.859082] Call trace:
[ 2813.859083] dump_backtrace+0x0/0x1c0
[ 2813.859102] show_stack+0x18/0x40
[ 2813.859109] dump_stack_lvl+0x68/0x84
[ 2813.859118] dump_stack+0x18/0x34
[ 2813.859124] panic+0x18c/0x338
[ 2813.859130] add_taint+0x0/0xc0
[ 2813.859138] arm64_serror_panic+0x6c/0x7c
[ 2813.859146] do_serror+0x58/0x5c
[ 2813.859153] __el0_error_handler_common+0x30/0x80
[ 2813.859159] el0t_64_error_handler+0x10/0x20
[ 2813.859165] el0t_64_error+0x1a0/0x1a4
[ 2813.859170] SMP: stopping secondary CPUs
[ 2813.859176] Kernel Offset: 0x1ede600000 from 0xffffffc008000000
[ 2813.859179] PHYS_OFFSET: 0x0
[ 2813.859181] CPU features: 0x800804f1,00000842
[ 2813.859186] Memory Limit: none
[ 2814.054208] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

Any advice how to proceed - should I use a different tool instead or is EepromAccessTool correct?

Best regards

[Fikri_Intel]

Hi Arno70,

Thank you for contacting Intel Ethernet Communities.

Regarding your inquiry about the Programming of i210 on ARM aarch64.

We have a dedicated team that is expertise in this topic.

Therefore, we will move this forum thread to the Embedded team. Please give them some time and they will assist you regarding this.

Regards,

Fikri O.

[CarlosAM_INTEL]

Hello,  @Fikri_Intel:

Thank you for contacting Intel Embedded Community.

We need to clarify that this forum is not related to an Intel Embedded Platform.

Due to this, the customer request is out of our scope of support.

Please consider this information when you provide the previous suggestion, or transfer any forums to the channel that you mentioned in your previous communication.

Best regards,
@CarlosAM_INTEL.

[Arno70]

Thank you for moving the request.

Just for reference, in case it helps. We are using yocto on kirkstone branch, kernel is:

# uname -a
Linux xxx-raspberrypi 5.15.92-v8 #1 SMP PREEMPT Wed Feb 8 16:47:50 UTC 2023 aarch64 GNU/Linux

[Arno70]

Just a short update: I tried with the current image from https://www.raspberrypi.com/software/ - result was ok (no kernel panic).
Then I tried to use their 6.6.20 kernel configuration with my current 5.15.92 kernel -> no kernel panic any more!

Seems to be a kernel configuration issue - I will try to boil it down and post the result.

Best regards
Arno

[Arno70 · Accepted solution]

Just for reference, in case anybody else has the same problem:

The EepromAccessTool expects that the Linux Kernel option CONFIG_PCIEPORTBUS is activated.

This solved my kernel panic problem.

Best regards
Arno