VCK190: dtsi does not expose EEPROM for factory MAC

Open Beginner friendly
#1,621 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, linux
Domain
embedded-iot, operating-systems

Research direction

Start with boards/VCK190/edf_bsp/board.dtsi and compare its EEPROM wiring with the ZCU111 and ZCU208 device trees. Verify the change with the pynq-selftest bash/mac check, confirming eth0 receives the factory MAC from the board EEPROM rather than a locally administered address.

Written by the indexing model from the issue text.

Description

On VCK190, pynq-selftest bash/mac fails because eth0 has a locally administered MAC (e.g. da:89:99:f7:59:cd) instead of the factory address from board EEPROM.

Likely cause: boards/VCK190/edf_bsp/board.dtsi never wires the EEPROM. U-Boot expects chosen { xlnx,eeprom = &eeprom; } (as on ZCU111/ZCU208) so FRU can set ethaddr and pass local-mac-address into Linux.

Fix: update the VCK190 dtsi to provide the EEPROM node/phandle so the MAC can be read.

Dominant language
Jupyter Notebook
Stars
2.4k
Forks
866
Avg merge
11h 58m
Merged PRs (30d)
32

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Xilinx/PYNQ

All issues in Xilinx/PYNQ

Similar issues

More Embedded & IoT issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.