lowRISC / lowRISC/ibex

Changing Memory Width of Ibex

Open
#1,707 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type:Question
Dominant language
SystemVerilog
Stars
2.1k
Forks
810
Avg merge
5d 23h
Merged PRs (30d)
9

Description

Hi guys... I am probably asking an irrelevant question so sorry:
In this makefile you utilized these lines of code related to SRecord:

%.vmem: %.bin
	srec_cat $^ -binary -offset 0x0000 -byte-swap 4 -o $@ -vmem

if I want to extend the memory width to 64 how can I do that here?
I tried this:

%.vmem: %.bin
	srec_cat $^ -binary -offset 0x0000 -byte-swap 4 -memory-width 64 -o $@ -vmem 

It gives error (unknown option)
Note: Suppose I have a vector coprocessor attached to ibex that utilizes a same bus with ibex to the memory and I want to extend this memory bandwidth to 64 bit
Should I even do that in the makefile?
So the Ibex is 32bit and the coprocessor is 32bit but just the bus will be 64 to get more data for vector each time I load or store.. This is what I want to do

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.

Research direction

Start with examples/sw/led/Makefile and the %.vmem rule, then check the srec_cat documentation for supported binary-to-vmem options. Trace whether the requested 64-bit width belongs only to image conversion or also to the Ibex–coprocessor memory bus. Done means documenting the required scope and a validated conversion or hardware design path.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.