lowRISC / lowRISC/lowrisc-chip

loading bitstream file into FPGA but no reaction happened on Tera Term

Open
#188 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SystemVerilog
Stars
601
Forks
147
PR merge metrics
No merged PRs in 30d

Description

Hi, I am working on the hello world test of "lowrisc-chip". The branch that I am working on is kc705_update. The problem is that I can generate the bitstream file and combine it with the "hello world" test hex file, but when I load it into my FPGA, there is no reaction on the terminal.

The board that I am using is Xilinx Atrix-7 AC701 board. I made a lot of modifications based on the "kc705_update" branch including pin mapping, MIG, BRAM controller, etc. The whole synthesis and implementation look normal. Since I don't have Xilinx Kintex KC705 board, I am not sure whether this "kc705_update" is correct or not. My final target is to build a RISC-V CPU on Xilinx AC701 board and port Linux on it, so I choose KC705 board project as a base.

For now, after checking Xilinx official BIST (Build In Self Test), I guess the problem is the test .c file is wrong. But I am not sure. Thanks for your help.

Contributor guide

No contributing guide indexed for this repository

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 the kc705_update board project and the bitstream plus hello world hex loading workflow, comparing the AC701 setup with the KC705 assumptions. Inspect the pin mapping, MIG, BRAM controller, and hello world test .c file, then check the Tera Term output. Done means identifying whether the missing response comes from the board configuration or the test software.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.