Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

firesim debug:using config (Rocket chip+custom Axi4 Peripheral) on fpga, segmentation faullt occurs when accessing Specific peripheral address #2062

Open
3 tasks done
huchensong opened this issue Sep 26, 2024 · 0 comments
Labels

Comments

@huchensong
Copy link

Background Work

Chipyard Version and Hash

Release: 1.8.1

OS Setup

uname -a
Linux ip-192-168-0-135.us-west-2.compute.internal 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.9.2009 (Core)
Release: 7.9.2009
Codename: Core

Other Setup

I follow the GCD example, using GCDRocketConfig in firesim to generate bitstream.
REF:https://chipyard.readthedocs.io/en/1.8.1/Customization/MMIO-Peripherals.html#constructing-the-digitaltop-and-config
I add with chipyard.example.CanHavePeripheryGCDModuleImp to enable GCD Peripheral.
image
I use riscv64-unknown-linux-gnu-gcc -O3 -std=gnu99 -o GCD GCD.c to generate riscv binary file.
I use marshal to generate linux image.

> ./marshal -v build br-base.json
> ./marshal -v install br-base.json

Current Behavior

When I use verilator to compile the code, I can see gcd module in device tree.
image-20240910122604117
I can access the SOC , can run easy binary such as helloworld, but fail to run GCD progam(segmentation fault).
image-20240823000451333

Expected Behavior

Successful access the GCD module .

Other Information

No response

@huchensong huchensong added the bug label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant