img_rcvry app doesn't work with Yocto 2024.2 flow or standalone compile
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
The image recovery (img_rcvry) app fails to set up DHCP connection, defaults to static IP. After setting up static IP on computer, the board provides no response to the browser when pointed to the board IP address.
On the other hand, u-boot can ping the computer and set up DHCP connection. Also. the pre-programmed img_rcvry app on KV260 dev board works with static IP, so the computer is set up correctly.
My setup is Kria K26 production SOM installed on KV260 board. I tried "MACHINE=sm-k26 bitbake kria-qspi" with Yocto 2024.2 Xilinx branch. I also tried standalone compile (with make) and then created qspi .bin file with custom .bif file.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the img_rcvry failure on the K26 SOM in the KV260 board using the Yocto 2024.2 MACHINE=sm-k26 bitbake kria-qspi flow and the standalone make flow. Compare DHCP and static-IP behavior with the working u-boot and pre-programmed app; done means the board responds in a browser at its IP address. No source file or test is named.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100