lowRISC / lowRISC/lowrisc-chip
the new chip_top.new.bit is same as chip_top.bit
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 601
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
Hi , i use the kc705_update branch to generate xc7k325 bit. the new bit chip_top.new.bit is same as chip_top.bit in beyondcompare.
And the command make bit-update which transfer to (data2mem -bm src/boot.mem -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit ). the -bm and -bd parameter is same.
i look the data2mem instruction -bm filename Linkable Format (ELF) or memory (MEM) root file name with a .bmm extension is assumed. so i tried (data2mem -bm src/boot.bmm -bd src/boot.mem -bt lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.bit -o b lowrisc-chip-imp/lowrisc-chip-imp.runs/impl_1/chip_top.new.bit), but it dose not work either.
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 with the kc705_update branch and the make bit-update target. Reproduce the data2mem command using src/boot.mem and then src/boot.bmm, comparing chip_top.bit with chip_top.new.bit as reported. Done means determining why the generated bitstreams are identical or why the alternate command fails, and documenting the verified result.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100