On Mon, Jan 21, 2019 at 7:26 PM Andreas Schwab schwab@suse.de wrote:
On Jan 18 2019, Anup Patel Anup.Patel@wdc.com wrote:
This patch adds SiFive FU540 board support. For now, only SiFive serial, SiFive PRCI, and Cadance MACB drivers are only enabled. The SiFive FU540 defconfig by default builds U-Boot for S-Mode because U-Boot on SiFive FU540 will run in S-Mode as payload of BBL or OpenSBI.
What am I expected to see when started with BBL? All I see is the logo, then nothing.
Here's the log of BBL+U-Boot on QEMU sifive_u machine:
anup@anup-ubuntu64:~/Work/riscv-test$ qemu-system-riscv64 -M sifive_u -m 256M -display none -serial stdio -kernel build-riscv-pk-uboot/bbl bbl loader
U-Boot 2019.01-00018-gc3a9211ebc (Jan 21 2019 - 21:36:12 +0530)
CPU: rv64imafdcsu Model: ucbbar,spike-bare,qemu DRAM: 256 MiB In: uart@10013000 Out: uart@10013000 Err: uart@10013000 Net: Warning: ethernet@100900fc (eth0) using random MAC address - 02:4a:de:c3:c8:80 eth0: ethernet@100900fc Hit any key to stop autoboot: 0 ethernet@100900fc: PHY present at 0 ethernet@100900fc: link up, 1000Mbps full-duplex (lpa: 0x7c00) BOOTP broadcast 1 DHCP client bound to address 10.0.2.15 (2 ms) Using ethernet@100900fc device TFTP from server 10.0.2.2; our IP address is 10.0.2.15 Filename 'boot.scr.uimg'. Load address: 0x82300000 Loading: * TFTP error: 'Access violation' (2) Not retrying... ethernet@100900fc: PHY present at 0 ethernet@100900fc: link up, 1000Mbps full-duplex (lpa: 0x7c00) BOOTP broadcast 1 DHCP client bound to address 10.0.2.15 (0 ms) Using ethernet@100900fc device TFTP from server 10.0.2.2; our IP address is 10.0.2.15 Filename 'boot.scr.uimg'. Load address: 0x80600000 Loading: * TFTP error: 'Access violation' (2) Not retrying... => ping 10.0.2.2 ethernet@100900fc: PHY present at 0 ethernet@100900fc: link up, 1000Mbps full-duplex (lpa: 0x7c00) Using ethernet@100900fc device host 10.0.2.2 is alive => ethernet@100900fc: PHY present at 0 ethernet@100900fc: link up, 1000Mbps full-duplex (lpa: 0x7c00) Using ethernet@100900fc device host 10.0.2.2 is alive => qemu-system-riscv64: terminating on signal 2
On real board, we generally boot OpenSBI+U-Boot. We will try and share log of BBL+U-Boot on real board but the log will look exactly like above.
Regards, Anup