Failure to flash Kintext Ultrascale+ xcku5p-ffvb676
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- embedded-iot
Research direction
The failure is in the SPI-over-JTAG flash write path: the log shows the helper bitstream spiOverJtag_xcku5p-ffvb676.bit.gz loading, then 'wait: Error' and 'write en: Error' before 'SPI flash write failed'. Start by tracing the flash write and wait logic in the Xilinx SPI flash code, and compare the working Kintex-7 dirtyJtag path. Done means a flash write and verify succeed on the xcku5p with --unprotect-flash, which needs hardware to confirm.
Written by the indexing model from the issue text.
Description
Able to load, verify & detect, but not flash. Also tried with options unprotect-flash & invert-read-edge and slowing freq. I am able to flash using Vivado 2026.1, so no problems with hardware. I am able to flash a Kintext7 using dirtyJtag so no problem with dirtyJtag (maybe...).
- openFPGALoader v1.1.1
- Kintext Ultrascale+
- xcku5p-ffvb676
- dirtyJtag
Flash
openFPGALoader --cable dirtyJtag --fpga-part xcku5p-ffvb676 --freq 1000000 --bitstream build/pack.bit -f --unprotect-flash --verify -r
write to flash
Jtag frequency : requested 1000000 Hz -> real 1000000 Hz
Open file build/pack.bit DONE
Parse file Unknown key SW_HDR_SHA256
DONE
Use: /FPGA/oss-cad-suite/share/openFPGALoader/spiOverJtag_xcku5p-ffvb676.bit.gz
load program
Load SRAM: [== ] 4.00%
Load SRAM: [===== ] 9.00%
Load SRAM: [======= ] 14.00%
Load SRAM: [========== ] 19.00%
Load SRAM: [============ ] 24.00%
Load SRAM: [=============== ] 29.00%
Load SRAM: [================= ] 34.00%
Load SRAM: [==================== ] 39.00%
Load SRAM: [====================== ] 44.00%
Load SRAM: [========================= ] 49.00%
Load SRAM: [=========================== ] 54.00%
Load SRAM: [============================== ] 59.00%
Load SRAM: [================================ ] 63.00%
Load SRAM: [================================== ] 68.00%
Load SRAM: [===================================== ] 73.00%
Load SRAM: [======================================= ] 78.00%
Load SRAM: [========================================== ] 83.00%
Load SRAM: [============================================ ] 88.00%
Load SRAM: [=============================================== ] 93.00%
Load SRAM: [================================================= ] 98.00%
Load SRAM: [===================================================] 100.00%
Done
Shift IR 11
ir: 1 isc_done 0 isc_ena 0 init 1 done 0
Register raw value: 0x1080190c
CRC Error No CRC error
Part Secured 0x0
MMCM lock 0x1
DCI match 0x1
EOS 0x0
GTS CFG B 0x0
GWE 0x0
GHIGH B 0x0
MODE 0x1
INIT Complete 0x1
INIT B 0x1
Release Done 0x0
Done 0x0
ID Error No ID error
DEC Error 0x0
XADC Over temp 0x0
STARTUP State 0x0
Reserved 0x4
BUS Width x1
Reserved 0x2
jtag_chain_len: 1
SOJ version: 1.000000
Detail:
Jedec ID : f7
memory type : fb
memory capacity : 8e
flash chip unknown: use basic protection detection
unlock blocks
timeout: 5 40 1
5
wait: Error
write en: Error
Error: Failed to program FPGA: SPI flash write failed
Detect
openFPGALoader --cable dirtyJtag --fpga-part xcku5p-ffvb676 --freq 1000000 --invert-read-edge -f --unprotect-flash --detect --verbose-level 2
write to flash
Jtag frequency : requested 1000000 Hz -> real 1000000 Hz
Raw IDCODE:
- 0 -> 0x04a62093
- 1 -> 0xffffffff
Fetched TDI, end-of-chain
found 1 devices
index 0:
idcode 0x4a62093
manufacturer xilinx
family kintexusp
model xcku5p
irlength 6
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 396
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from trabucayre/openFPGALoader
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
trabucayre/openFPGALoader#767 ·
Maintainers usually reply within 1 day
-
Done Wait for feedback
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
trabucayre/openFPGALoader#735 · 2 comments ·
Maintainers usually reply within 1 day
-
spiFlash: sectors_erase() erases outside the requested rangePossibly taken @Milo0x1 claimed this today. Open
Difficulty 3/5 1-2 days Newbie friendliness 20/100
trabucayre/openFPGALoader#765 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
trabucayre/openFPGALoader#752 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
trabucayre/openFPGALoader#741 ·
Maintainers usually reply within 1 day
All issues in trabucayre/openFPGALoader
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/DirectXShaderCompiler#9155 ·
Maintainers usually reply within 2 days
-
Errors in 1.20 proseOpenCampaign DiD Campaign EI Campaign HttT Campaign TDG Campaign TSG Campaign WoF Enhancement Help Prose Stable 1.20
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wesnoth/wesnoth#11749 · 2 comments ·
Maintainers usually reply within 1 day
-
agent:Windows bug in progress pri:medium sev:low testing windows
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
protocolbuffers/protobuf#31768 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
godotengine/godot#125651 ·
Maintainers usually reply within 1 day