-
Notifications
You must be signed in to change notification settings - Fork 667
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
cann't down load br.xxxx.img.zip from web #1557
Comments
@abejgonzalez cache problem? |
In addition, I found a similar issue with version 1.8.1, with the following error:
And this is the log file: |
The error is not related to caching but with buildroot based on this error message.
In the buildroot submodule I would try running |
Hi @abejgonzalez .I have ran
In addition,here is the log file: |
That is a build-root Linux issue. To work around this you can run the following script: https://github.com/ucb-bar/chipyard/blob/main/scripts/fix-open-files.sh. If that script prints the warning then you need to fix your open files limit, restart your terminal, and run the build again (remember to source the Chipyard |
Hi @abejgonzalez .you are right.I have generated the prototype Linux image successful. |
I met the same issue, firesim/FireMarshal#312, how can you solved this? |
Background Work
Chipyard Version and Hash
Release: 1.10.0
OS Setup
I used the command "build_setup.sh riscv-tools" to complete the installation of the Chipyard runtime environment, and installed the firemarshal conda environment through the README file. The configuration in the marshal-config. yaml file is as follows:
board-dir: 'boards/prototype'
When I run the command:
./Marshal - v - d build boards/prototype/base-workloads/br-base. json
Error in downloading the br.222b.img.zip file. The error is as follows:
Based on the error message, I found that only the corresponding images of the fireship development board exist in the firemarshal-public-br-images repository, and there are no images of prototype and chipboard types. Personally, I suspect that this is a code bug?
And this is the log file:
br-base-build-2023-07-15--02-34-20-3XGQWP4BPRGW9NTJ.log
Other Setup
no
Current Behavior
no
Expected Behavior
no
Other Information
no
The text was updated successfully, but these errors were encountered: