This ensures that it does not inflict upon other RISCV SOCs and qemu
based machines, which can result in non-booting systems since entry
adddress in FW_JUMP Firmware Configuration is wrong.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Several issues with the current visionfive 2 support:
* JH7110 Support is only in OpenSBI Master branch, (upcoming 1.3 release). So pin OpenSBI Revision to the commit that adds JH7110 Support otherwise reset etc does not work
* There are two variants of VisionFive2 and Star64 - 4Gb and 8Gb. StarFive's u-boot reads the eeprom on board to determine what variant you have, and modifies the loaded FDT it passes to the kernel with the correct Memory. Current U-boot scripts in meta-riscv do not do this, and thus all boards end up with the default 4Gb configuration. I've updated this for Star64, but needs testing on VF2
* Some of the addresses used in uboot for kernel/initramfs or fdt were different from upstream. Aligned the addresses with upstream StarFive.
As both Star64 and VisionFive2 are based on the same SOC, i've changed the machine configuration so we have a JH7110 SOC and VisionFive2 and Star64 inherit from this. Where appropriate in the recipies, I've changed to jh7110 instead of visionfive2
Finally, as the Star64 has different kernel/u-boot configs/dts files, i've pointed those at my repos for now, and will be upstreaming (assuming Starfive accept star64 related PRs). Once upstreamed, I'll submit a new PR here.
This also lays the groundwork for the new PineTab-V from pine64 which is due to be shipped in May.
Signed-Off-By: Justin Hammond <justin@dynam.ac>
Align uEnv.txt with the Starfive SDK to boot from SD card.
uEnv sets required variables to read the fitImage from the
partition 3 on the SD card and rootfs is expected on the
partition 4.
Signed-off-by: Alexey Firago <alexey.firago@gmail.com>
Add recipe for a jh7110 signature tool, which is used to generate
SPL header information and generate u-boot-spl.bin.normal.out.
Signed-off-by: Alexey Firago <alexey.firago@gmail.com>
At this point DTSes differ between d1/wip branch of the kernel
and corresponding branch of u-boot. Mangopi-MQ-Pro dts is missed in
u-boot part which leads to missing devices nodes (bluetooth in
particular). Sync dts and pin patch to mangopi only to not affect Nezha.
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Use SOC name (Allwinner D1) instead of board name for
generic recipes.
Move board specific configuration to corresponding machine conf
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Based on Nezha D1 machine config with addjusterd DTB configuration
and added wifi module driver.
Tested with core-image-(base|weston) on MangoPi MQ Pro rev 1.3:
- HDMI output/weston and wifi are working. USB-C ethernet detected but not
tested due to lack of HW.
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
If start address ($a1) is not 8-byte aligned, the system will hang in
fw_platform_init where OpenSBI starts to parse fdt, thus need this patch
to adjust the address in SPL.
Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
OE-Core is using OpenSBI tag v1.1, this revision is based to v1.1 while
includes fdt driver support for AE350 platform so it can use with the
latest device tree provided by Andes Linux kernel 6.0.
Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
ae350-ax45mp was using U-boot v2022.07 with the applied patches:
- (f4512618caa0) riscv: ae350: Fix XIP config boot failure
- (aa0eda17cf98) spl: opensbi: convert scratch options to config
Since OE-Core U-boot has upgraded to v2022.10 which includes both
patches so we can drop them.
Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
u-boot common files set O=.. option for make which actually
sets KBUILD_SRC, which triggers a step in u-boot system called
prepare3. This step checks if make has been run inside sourcedir
and since we are setting O=${B} and B is set to S, it has run
inside S during do_configure, so do_compile fails to build e.g.
| /mnt/b/yoe/master/build/tmp/work/visionfive-yoe-linux/u-boot-starfive/v2021.04-r0/git is not clean, please run 'make mrproper'
| in the '/mnt/b/yoe/master/build/tmp/work/visionfive-yoe-linux/u-boot-starfive/v2021.04-r0/git' directory.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is a generic bbappend and opensbi is riscv specific, so this causes
problems when this layer is includes and a build is done for non-riscv
machines e.g.
MACHINE=qemumips bitbake -n world
will show the problem
ERROR: Nothing PROVIDES 'opensbi'
opensbi was skipped: incompatible with host mips-yoe-linux-musl (not in COMPATIBLE_HOST)
NOTE: Runtime target 'u-boot-default-env' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['u-boot-default-env', 'opensbi']
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'libubootenv', 'u-boot-default-env', 'opensbi']
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The LIC_FILES_CHKSUM md5sum changed with the latest mainline u-boot
release. So manually specify the original md5sum value.
Signed-off-by: Matheus Castello <matheus@castello.eng.br>
The LIC_FILES_CHKSUM md5sum changed with the latest mainline u-boot
release, but hasn't changed for the older starfive release. So manually
specify the original md5sum value.
Resolves: https://github.com/riscv/meta-riscv/issues/350
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
This is largely based on the beaglev code nbut tweaked to work with current
starfive kernel repositories and tweak to the board.
The kernel and rootfs boot with working network and graphics. The u-boot
binary builds but is as yet untested.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If this value is not increased, the error occurs during loading uncompressed
kernel from fitImage:
"Error: inflate() returned -5
Image too large: increase CONFIG_SYS_BOOTM_LEN"
Signed-off-by: Cezary Sobczak <cezary.sobczak@3mdeb.com>
