Open Xu-feng-feng opened 1 day ago
I also tried running this command:
make BOARD=u250 CONFIG=rocket64b2 ROOTFS_URL=192.168.1.100:/sda2/nfsroot HW_SERVER_ADDR=localhost:3121 ROOTFS=NFS JTAG_BOOT=1 jtag-boot
And the output was as follows:
RISC-V 64, Boot ROM V3.8
OpenSBI v1.4
____ _____ ____ _____
/ __ \ / ____| _ \_ _|
| | | |_ __ ___ _ __ | (___ | |_) || |
| | | | '_ \ / _ \ '_ \ \___ \| _ < | |
| |__| | |_) | __/ | | |____) | |_) || |_
\____/| .__/ \___|_| |_|_____/|____/_____|
| |
|_|
Platform Name : freechips,rocketchip-vivado
Platform Features : medeleg
Platform HART Count : 2
Platform IPI Device : aclint-mswi
Platform Timer Device : aclint-mtimer @ 1250000Hz
Platform Console Device : axi-uart
Platform HSM Device : ---
Platform PMU Device : ---
Platform Reboot Device : ---
Platform Shutdown Device : ---
Platform Suspend Device : ---
Platform CPPC Device : ---
Firmware Base : 0x80000000
Firmware Size : 192 KB
Firmware RW Offset : 0x20000
Firmware RW Size : 64 KB
Firmware Heap Offset : 0x27000
Firmware Heap Size : 36 KB (total), 2 KB (reserved), 9 KB (used), 24 KB (free)
Firmware Scratch Size : 4096 B (total), 320 B (used), 3776 B (free)
Runtime SBI Version : 2.0
Domain0 Name : root
Domain0 Boot HART : 0
Domain0 HARTs : 0*,1*
Domain0 Region00 : 0x0000000002000000-0x000000000200ffff M: (I,R,W) S/U: ()
Domain0 Region01 : 0x0000000080020000-0x000000008002ffff M: (R,W) S/U: ()
Domain0 Region02 : 0x0000000080000000-0x000000008001ffff M: (R,X) S/U: ()
Domain0 Region03 : 0x000000000c000000-0x000000000fffffff M: (I,R,W) S/U: (R,W)
Domain0 Region04 : 0x0000000000000000-0xffffffffffffffff M: () S/U: (R,W,X)
Domain0 Next Address : 0x0000000080200000
Domain0 Next Arg1 : 0x0000000000010080
Domain0 Next Mode : S-mode
Domain0 SysReset : yes
Domain0 SysSuspend : yes
Boot HART ID : 0
Boot HART Domain : root
Boot HART Priv Version : v1.12
Boot HART Base ISA : rv64imafdcx
Boot HART ISA Extensions : none
Boot HART PMP Count : 8
Boot HART PMP Granularity : 2 bits
Boot HART PMP Address Bits: 32
Boot HART MHPM Info : 0 (0x00000000)
Boot HART MIDELEG : 0x0000000000000222
Boot HART MEDELEG : 0x000000000000b109
U-Boot 2022.01-dirty (Nov 29 2024 - 13:53:36 +0800)
CPU: rv64imafdczicsr_zifencei_zihpm_xrocket
Model: freechips,rocketchip-vivado
DRAM: 14 GiB
MMC:
Loading Environment from nowhere... OK
In: uart@60010000
Out: uart@60010000
Err: uart@60010000
Net: No ethernet found.
Hit any key to stop autoboot: 0
No MMC device available
No ethernet found.
No ethernet found.
=>
It seems that the system still has trouble detecting the ethernet interface. Could you provide any advice on how to proceed?
The first command is the right one. The problem appears to be either wrong router or wrong Ethernet cable. You need to use 10G SFP+ router and connect it to the first lane of QSFP0 connector using 40G QSFP+ to 4 x 10G SFP+ Breakout Cable.
The message "No ethernet found" is coming from U-Boot, not from the OS. Ethernet in U-Boot is not needed, not supported and not used in this workflow.
Thank you for your reply and suggestion. I followed your advice and used a 10G SFP+ router, connecting it to the first lane of the QSFP0 connector with a 40G QSFP+ to 4 x 10G SFP+ Breakout Cable.
However, after generating the bitstream for rocket64b2
and downloading it to the XCU250, I noticed that the SFP port light does not turn on. When using a different bitstream (from this source), the SFP port light does turn on, and the router interface shows that the SFP port is connected. But with the rocket64b2
bitstream, the SFP port still shows as not connected.
I’m unsure what might be causing this discrepancy. Could there be something specific to the rocket64b2
configuration that affects the SFP port's behavior?
In this repo, ethernet uses GT channel X1Y44, see board/u250/ethernet-u250.tcl, which matches docs for U250. However, that other example looks like it uses channel X1Y48 for the first lane of the QSFP0 connector. I'm not sure which one is correct, I don't have U250 board, I run tests on a different Alveo board.
Hi Eugene,
Thank you for your guidance. I understand that the "No ethernet found" message is coming from U-Boot, not the OS. However, I am currently facing this issue where U-Boot is unable to detect Ethernet. Could you provide any insights on how to resolve this?
I have already ensured that I am using the correct 10G SFP+ router and connecting it properly via the 40G QSFP+ to 4 x 10G SFP+ Breakout Cable as per your recommendation.
Is there any additional configuration I need to check or set in U-Boot to enable Ethernet functionality, or could this be related to the specific hardware configuration for the rocket64b2 bitstream?
Any advice would be greatly appreciated!
This ethernet controller is not supported by U-Boot.
Hi, Eugene Thank you for the open-source project. Could anyone provide insight into the possible causes of this issue or suggest a solution? I have encountered an issue while attempting to boot a system on a Xilinx Alveo U250 using NFS. After generating the bitstream and downloading it to the XCU250, I noticed that the SFP port connected to the router does not light up.
I followed the instructions in [this issue thread](https://github.com/eugene-tarassov/vivado-risc-v/issues/62), and ran the following command:
I’m using Vivado version 2023.2 for this project. However, the process stops at:
The full boot log looks as follows:
After debugging, I found that the issue is related to a DHCP problem. The system seems unable to obtain an IP via DHCP, resulting in a timeout and the failure to mount the root filesystem via NFS. The issue logs show the following: It seems like the system is unable to obtain an IP via DHCP, resulting in a timeout and the failure to mount the root filesystem via NFS.