board/andes: rearrange andes folder structure
PATCH v4 1/3 board/andes: rearrange andes folder structure
Rename ae3xx to ae300 for nds32 architecture and add ae350 platform.
AE300 (NDS32):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae300/
AE350 (RISC-V):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae350-axi-based-platform-pre-integrated-with-n25f-nx25f-a25-ax25/
---
Changes v1 -> v2:
- move linux source code and its patches to AndesTech Github repo
- rename ae350_andestar45_defconfig to andes_ae350_45_defconfig
- change C library to uClibc
- remove OpenSSL package
- remove rootfs.cpio and rootfs.tar
- update DEVELOPERS
Changes v2 -> v3:
- specifiy branch to download from AndesTech linux repo
- change boot.cmd to extlinux.conf
- add post-build.sh for extlinux.conf to retrieve Image and DTB
- fix format and update genimage_sdcard.cfg
- update readme.txt
- add packages (python3, pylibfdt and openssl) for u-boot binman
- reorder item in DEVELOPERS
Changes v3 -> v4:
- rename ae3xx folder to ae300
- rename andes_ae3xx_defconfig to andes_ae300_defconfig
- update readme.txt and item in DEVELOPERS
---
.../{ae3xx/ae3xx.fragment => ae300/ae300.fragment} | 0
.../linux/0001-nds32-Fix-boot-messages-garbled.patch | 0
...-dtc-Remove-redundant-YYLOC-global-declaratio.patch | 0
board/andes/{ => ae300}/readme.txt | 10 +++++-----
.../{andes_ae3xx_defconfig => andes_ae300_defconfig} | 4 ++--
.../toolchain-external-andes-nds32/Config.in | 2 +-
6 files changed, 8 insertions(+), 8 deletions(-)
rename board/andes/{ae3xx/ae3xx.fragment => ae300/ae300.fragment} (100%)
rename board/andes/{ => ae300}/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch (100%)
rename board/andes/{ => ae300}/patches/linux/0002-scripts-dtc-Remove-redundant-YYLOC-global-declaratio.patch (100%)
rename board/andes/{ => ae300}/readme.txt (71%)
rename configs/{andes_ae3xx_defconfig => andes_ae300_defconfig} (69%)board/andes/ae300/ae300.fragment renamed from board/andes/ae3xx/ae3xx.fragment +0 -0
board/andes/ae300/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch renamed from board/andes/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch +0 -0
board/andes/ae300/patches/linux/0002-scripts-dtc-Remove-redundant-YYLOC-global-declaratio.patch renamed from board/andes/patches/linux/0002-scripts-dtc-Remove-redundant-YYLOC-global-declaratio.patch +0 -0
board/andes/ae300/readme.txt renamed from board/andes/readme.txt +5 -5
@@ -1,10 +1,10 @@ Intro ===== -Andestech(nds32) AE3XX Platform +Andestech(nds32) AE300 Platform -The AE3XX prototype demonstrates the AE3XX example platform on the FPGA. -It is composed of one Andestech(nds32) processor and AE3XX. +The AE300 prototype demonstrates the AE300 example platform on the FPGA. +It is composed of one Andestech(nds32) processor and AE300. How to build it ===============
@@ -12,10 +12,10 @@ How to build it Configure Buildroot ------------------- -The andes_ae3xx_defconfig configuration is a sample configuration with +The andes_ae300_defconfig configuration is a sample configuration with all that is required to bring the FPGA Development Board: - $ make andes_ae3xx_defconfig + $ make andes_ae300_defconfig Build everything ----------------
configs/andes_ae300_defconfig renamed from configs/andes_ae3xx_defconfig +2 -2
@@ -1,10 +1,10 @@ BR2_nds32=y -BR2_GLOBAL_PATCH_DIR="board/andes/patches/" +BR2_GLOBAL_PATCH_DIR="board/andes/ae300/patches" BR2_TOOLCHAIN_EXTERNAL=y BR2_TOOLCHAIN_EXTERNAL_ANDES_NDS32=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_VERSION=y BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.17" BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y -BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/andes/ae3xx/ae3xx.fragment" +BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/andes/ae300/ae300.fragment" BR2_TARGET_ROOTFS_INITRAMFS=y
toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in +1 -1
@@ -12,4 +12,4 @@ config BR2_TOOLCHAIN_EXTERNAL_ANDES_NDS32 help nds32 toolchain for the nds32 architecture. It uses GCC 8.2.1, GDB 8.1.1, glibc 2.28, Binutils 2.30. It generates - code that runs on ae3xx platform + code that runs on ae300 platform
Signature · 6 lines
2.17.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
PATCH v4 2/3 board/andes/ae350: add support for Andes AE350
This patch provides defconfig and basic support for Andes 45 series RISC-V architecture on AE350 platform.
--- board/andes/ae350/ae350.dts | 274 ++++++++++++++++++ board/andes/ae350/genimage_sdcard.cfg | 26 ++ ...isable-PIC-explicitly-for-assembling.patch | 29 ++ ...2-Enable-cache-for-opensbi-jump-mode.patch | 25 ++ ...001-Fix-mmc-no-partition-table-error.patch | 27 ++ ...2-Prevent-fw_dynamic-from-relocation.patch | 27 ++ ...0003-Fix-u-boot-proper-booting-issue.patch | 26 ++ ...04-Enable-printing-OpenSBI-boot-logo.patch | 25 ++ board/andes/ae350/post-build.sh | 3 + board/andes/ae350/readme.txt | 65 +++++ .../boot/extlinux/extlinux.conf | 4 + board/andes/ae350/uboot.config.fragment | 5 + configs/andes_ae350_45_defconfig | 43 +++ 13 files changed, 579 insertions(+) create mode 100755 board/andes/ae350/ae350.dts create mode 100644 board/andes/ae350/genimage_sdcard.cfg create mode 100644 board/andes/ae350/patches/opensbi/0001-Disable-PIC-explicitly-for-assembling.patch create mode 100644 board/andes/ae350/patches/opensbi/0002-Enable-cache-for-opensbi-jump-mode.patch create mode 100644 board/andes/ae350/patches/uboot/0001-Fix-mmc-no-partition-table-error.patch create mode 100644 board/andes/ae350/patches/uboot/0002-Prevent-fw_dynamic-from-relocation.patch create mode 100644 board/andes/ae350/patches/uboot/0003-Fix-u-boot-proper-booting-issue.patch create mode 100644 board/andes/ae350/patches/uboot/0004-Enable-printing-OpenSBI-boot-logo.patch create mode 100755 board/andes/ae350/post-build.sh create mode 100644 board/andes/ae350/readme.txt create mode 100644 board/andes/ae350/rootfs_overlay/boot/extlinux/extlinux.conf create mode 100644 board/andes/ae350/uboot.config.fragment create mode 100644 configs/andes_ae350_45_defconfig
board/andes/ae350/ae350.dts new file +274 -0
@@ -0,0 +1,274 @@ +/dts-v1/; + +/ { + #address-cells = <2>; + #size-cells = <2>; + compatible = "andestech,ae350"; + model = "andestech,ax45"; + aliases { + uart0 = &serial0; + spi0 = &spi; + }; + + chosen { + bootargs = "console=ttyS0,38400n8 earlycon=sbi debug loglevel=7"; + stdout-path = "uart0:38400n8"; + }; + cpus { + #address-cells = <1>; + #size-cells = <0>; + timebase-frequency = <60000000>; + CPU0: cpu@0 { + device_type = "cpu"; + reg = <0>; + status = "okay"; + compatible = "riscv"; + riscv,isa = "rv64i2p0m2p0a2p0f2p0d2p0c2p0xv5-1p1xdsp0p0"; + riscv,priv-major = <1>; + riscv,priv-minor = <10>; + mmu-type = "riscv,sv48"; + clock-frequency = <60000000>; + i-cache-size = <0x8000>; + i-cache-sets = <256>; + i-cache-block-size = <64>; + i-cache-line-size = <64>; + d-cache-size = <0x8000>; + d-cache-sets = <128>; + d-cache-block-size = <64>; + d-cache-line-size = <64>; + next-level-cache = <&L2>; + CPU0_intc: interrupt-controller { + #interrupt-cells = <1>; + interrupt-controller; + compatible = "riscv,cpu-intc"; + }; + }; + CPU1: cpu@1 { + device_type = "cpu"; + reg = <1>; + status = "okay"; + compatible = "riscv"; + riscv,isa = "rv64i2p0m2p0a2p0f2p0d2p0c2p0xv5-1p1xdsp0p0"; + riscv,priv-major = <1>; + riscv,priv-minor = <10>; + mmu-type = "riscv,sv48"; + clock-frequency = <60000000>; + i-cache-size = <0x8000>; + i-cache-sets = <256>; + i-cache-block-size = <64>; + i-cache-line-size = <64>; + d-cache-size = <0x8000>; + d-cache-sets = <128>; + d-cache-block-size = <64>; + d-cache-line-size = <64>; + next-level-cache = <&L2>; + CPU1_intc: interrupt-controller { + #interrupt-cells = <1>; + interrupt-controller; + compatible = "riscv,cpu-intc"; + }; + }; + CPU2: cpu@2 { + device_type = "cpu"; + reg = <2>; + status = "okay"; + compatible = "riscv"; + riscv,isa = "rv64i2p0m2p0a2p0f2p0d2p0c2p0xv5-1p1xdsp0p0"; + riscv,priv-major = <1>; + riscv,priv-minor = <10>; + mmu-type = "riscv,sv48"; + clock-frequency = <60000000>; + i-cache-size = <0x8000>; + i-cache-sets = <256>; + i-cache-block-size = <64>; + i-cache-line-size = <64>; + d-cache-size = <0x8000>; + d-cache-sets = <128>; + d-cache-block-size = <64>; + d-cache-line-size = <64>; + next-level-cache = <&L2>; + CPU2_intc: interrupt-controller { + #interrupt-cells = <1>; + interrupt-controller; + compatible = "riscv,cpu-intc"; + }; + }; + CPU3: cpu@3 { + device_type = "cpu"; + reg = <3>; + status = "okay"; + compatible = "riscv"; + riscv,isa = "rv64i2p0m2p0a2p0f2p0d2p0c2p0xv5-1p1xdsp0p0"; + riscv,priv-major = <1>; + riscv,priv-minor = <10>; + mmu-type = "riscv,sv48"; + clock-frequency = <60000000>; + i-cache-size = <0x8000>; + i-cache-sets = <256>; + i-cache-block-size = <64>; + i-cache-line-size = <64>; + d-cache-size = <0x8000>; + d-cache-sets = <128>; + d-cache-block-size = <64>; + d-cache-line-size = <64>; + next-level-cache = <&L2>; + CPU3_intc: interrupt-controller { + #interrupt-cells = <1>; + interrupt-controller; + compatible = "riscv,cpu-intc"; + }; + }; + }; + L2: l2-cache@e0500000 { + compatible = "cache"; + cache-level = <2>; + cache-size = <0x80000>; + reg = <0x00000000 0xe0500000 0x00000000 0x00001000>; + andes,inst-prefetch = <3>; + andes,data-prefetch = <3>; + // The value format is <XRAMOCTL XRAMICTL> + andes,tag-ram-ctl = <0 0>; + andes,data-ram-ctl = <0 0>; + }; + memory@0 { + reg = <0x00000000 0x00000000 0x00000000 0x80000000>; + device_type = "memory"; + }; + soc { + #address-cells = <2>; + #size-cells = <2>; + compatible = "andestech,riscv-ae350-soc", "simple-bus"; + ranges; + plic0: interrupt-controller@e4000000 { + compatible = "riscv,plic0"; + reg = <0x00000000 0xe4000000 0x00000000 0x02000000>; + interrupts-extended = < &CPU0_intc 11 &CPU0_intc 9 &CPU1_intc 11 &CPU1_intc 9 &CPU2_intc 11 &CPU2_intc 9 &CPU3_intc 11 &CPU3_intc 9>; + interrupt-controller; + #address-cells = <2>; + #interrupt-cells = <2>; + riscv,ndev = <71>; + }; + plic1: interrupt-controller@e6400000 { + compatible = "riscv,plic1"; + reg = <0x00000000 0xe6400000 0x00000000 0x00400000>; + interrupts-extended = < &CPU0_intc 3 &CPU1_intc 3 &CPU2_intc 3 &CPU3_intc 3>; + interrupt-controller; + #address-cells = <2>; + #interrupt-cells = <2>; + riscv,ndev = <4>; + }; + plmt0: plmt0@e6000000 { + compatible = "riscv,plmt0"; + reg = <0x00000000 0xe6000000 0x00000000 0x00100000>; + interrupts-extended = < &CPU0_intc 7 &CPU1_intc 7 &CPU2_intc 7 &CPU3_intc 7>; + }; + spiclk: virt_100mhz { + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <100000000>; + }; + timer0: timer@f0400000 { + compatible = "andestech,atcpit100"; + reg = <0x00000000 0xf0400000 0x00000000 0x00001000>; + interrupts = <3 4>; + interrupt-parent = <&plic0>; + clock-frequency = <60000000>; + }; + pwm: pwm@f0400000 { + compatible = "andestech,atcpit100-pwm"; + reg = <0x00000000 0xf0400000 0x00000000 0x00001000>; + interrupts = <3 4>; + interrupt-parent = <&plic0>; + clock-frequency = <60000000>; + pwm-cells = <2>; + }; + wdt: wdt@f0500000 { + compatible = "andestech,atcwdt200"; + reg = <0x00000000 0xf0500000 0x00000000 0x00001000>; + interrupts = <3 4>; + interrupt-parent = <&plic0>; + clock-frequency = <15000000>; + }; + serial0: serial@f0300000 { + compatible = "andestech,uart16550", "ns16550a"; + reg = <0x00000000 0xf0300000 0x00000000 0x00001000>; + interrupts = <9 4>; + interrupt-parent = <&plic0>; + clock-frequency = <19660800>; + reg-shift = <2>; + reg-offset = <32>; + no-loopback-test = <1>; + }; + rtc0: rtc@f0600000 { + compatible = "andestech,atcrtc100"; + reg = <0x00000000 0xf0600000 0x00000000 0x00001000>; + interrupts = <1 4 2 4>; + interrupt-parent = <&plic0>; + wakeup-source; + }; + gpio: gpio@f0700000 { + compatible = "andestech,atcgpio100"; + reg = <0x00000000 0xf0700000 0x00000000 0x00001000>; + interrupts = <7 4>; + interrupt-parent = <&plic0>; + wakeup-source; + }; + mac0: mac@e0100000 { + compatible = "andestech,atmac100"; + reg = <0x00000000 0xe0100000 0x00000000 0x00001000>; + interrupts = <19 4>; + interrupt-parent = <&plic0>; + dma-coherent; + }; + smu: smu@f0100000 { + compatible = "andestech,atcsmu"; + reg = <0x00000000 0xf0100000 0x00000000 0x00001000>; + }; + mmc0: mmc@f0e00000 { + compatible = "andestech,atfsdc010"; + reg = <0x00000000 0xf0e00000 0x00000000 0x00001000>; + interrupts = <18 4>; + interrupt-parent = <&plic0>; + clock-freq-min-max = <400000 100000000>; + max-frequency = <100000000>; + fifo-depth = <16>; + cap-sd-highspeed; + dma-coherent; + }; + dma0: dma@f0c00000 { + compatible = "andestech,atcdmac300"; + reg = <0x00000000 0xf0c00000 0x00000000 0x00001000>; + interrupts = <10 4 64 4 65 4 66 4 67 4 68 4 69 4 70 4 71 4>; + interrupt-parent = <&plic0>; + dma-channels = <8>; + }; + lcd0: lcd@e0200000 { + compatible = "andestech,atflcdc100"; + reg = <0x00000000 0xe0200000 0x00000000 0x00001000>; + interrupts = <20 4>; + interrupt-parent = <&plic0>; + dma-coherent; + }; + pmu: pmu { + compatible = "riscv,andes-pmu"; + device_type = "pmu"; + }; + spi: spi@f0b00000 { + compatible = "andestech,atcspi200"; + reg = <0x00000000 0xf0b00000 0x00000000 0x00001000>; + interrupts = <4 4>; + interrupt-parent = <&plic0>; + #address-cells = <1>; + #size-cells = <0>; + num-cs = <1>; + clocks = <&spiclk>; + flash@0 { + compatible = "jedec,spi-nor"; + reg = <0x00000000>; + spi-max-frequency = <50000000>; + spi-cpol; + spi-cpha; + }; + }; + }; +};
board/andes/ae350/genimage_sdcard.cfg new file +26 -0
@@ -0,0 +1,26 @@ +image boot.vfat { + vfat { + files = { + "u-boot-spl.bin", + "u-boot.itb", + "ae350.dtb", + } + } + size = 2M +} + +image sdcard.img { + hdimage { + } + + partition boot { + partition-type = 0xC + image = "boot.vfat" + } + + partition rootfs { + partition-type = 0x83 + bootable = true + image = "rootfs.ext4" + } +}
board/andes/ae350/patches/opensbi/0001-Disable-PIC-explicitly-for-assembling.patch new file +29 -0
@@ -0,0 +1,29 @@ +From 3ccb71eeca42dbcd5e4d00ae1877a489ae82598d Mon Sep 17 00:00:00 2001 +From: Yu Chien Peter Lin <[email protected]> +Date: Wed, 29 Dec 2021 16:04:54 +0800 +Subject: [PATCH] Disable PIC explicitly for assembling + +This patch is necessary if the fw_dynamic load address +is not equal to link address. +However, they are equal currently, since we include an u-boot +patch for preventing fw_dynamic relocation. + +Signed-off-by: Yu Chien Peter Lin <[email protected]> +--- + Makefile | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/Makefile b/Makefile +index d6f097d..441518d 100644 +--- a/Makefile ++++ b/Makefile +@@ -225,6 +225,7 @@ ASFLAGS += -mcmodel=$(PLATFORM_RISCV_CODE_MODEL) + ASFLAGS += $(GENFLAGS) + ASFLAGS += $(platform-asflags-y) + ASFLAGS += $(firmware-asflags-y) ++ASFLAGS += -fno-pic + + ARFLAGS = rcs + +-- +2.25.1
board/andes/ae350/patches/opensbi/0002-Enable-cache-for-opensbi-jump-mode.patch new file +25 -0
@@ -0,0 +1,25 @@ +From 325328f4204b40b1fcc8db3b46c7c8805710d21c Mon Sep 17 00:00:00 2001 +From: Yu Chien Peter Lin <[email protected]> +Date: Thu, 30 Dec 2021 08:47:34 +0800 +Subject: [PATCH] Enable cache for opensbi jump mode + +Signed-off-by: Yu Chien Peter Lin <[email protected]> +--- + firmware/fw_base.S | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/firmware/fw_base.S b/firmware/fw_base.S +index ab33e11..155d230 100644 +--- a/firmware/fw_base.S ++++ b/firmware/fw_base.S +@@ -46,6 +46,8 @@ + .globl _start + .globl _start_warm + _start: ++ li t0, 0x80003 ++ csrw 0x7ca, t0 + /* Find preferred boot HART id */ + MOV_3R s0, a0, s1, a1, s2, a2 + call fw_boot_hart +-- +2.25.1
board/andes/ae350/patches/uboot/0001-Fix-mmc-no-partition-table-error.patch new file +27 -0
@@ -0,0 +1,27 @@ +From ea4675215b53d16a72d29b8a6fc6a86cccf59cf0 Mon Sep 17 00:00:00 2001 +From: Yu Chien Peter Lin <[email protected]> +Date: Wed, 5 Jan 2022 11:00:59 +0800 +Subject: [PATCH] Fix mmc no partition table error + +Signed-off-by: Yu Chien Peter Lin <[email protected]> +--- + drivers/mmc/ftsdc010_mci.c | 4 ---- + 1 file changed, 4 deletions(-) + +diff --git a/drivers/mmc/ftsdc010_mci.c b/drivers/mmc/ftsdc010_mci.c +index 570d54cf..3b1e0aa0 100644 +--- a/drivers/mmc/ftsdc010_mci.c ++++ b/drivers/mmc/ftsdc010_mci.c +@@ -438,10 +438,6 @@ static int ftsdc010_mmc_probe(struct udevice *dev) + return ret; + #endif + +- if (dev_read_bool(dev, "cap-mmc-highspeed") || \ +- dev_read_bool(dev, "cap-sd-highspeed")) +- chip->caps |= MMC_MODE_HS | MMC_MODE_HS_52MHz; +- + ftsdc_setup_cfg(&plat->cfg, dev->name, chip->buswidth, chip->caps, + priv->minmax[1] , priv->minmax[0]); + chip->mmc = &plat->mmc; +-- +2.25.1
board/andes/ae350/patches/uboot/0002-Prevent-fw_dynamic-from-relocation.patch new file +27 -0
@@ -0,0 +1,27 @@ +From 4c0c5378d032f2f95577585935624baf7b4decf3 Mon Sep 17 00:00:00 2001 +From: Yu Chien Peter Lin <[email protected]> +Date: Wed, 5 Jan 2022 11:02:26 +0800 +Subject: [PATCH] Prevent fw_dynamic from relocation + +This patch prevents OpenSBI relocation, load fw_dynamic to link address + +Signed-off-by: Yu Chien Peter Lin <[email protected]> +--- + board/AndesTech/ax25-ae350/Kconfig | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/board/AndesTech/ax25-ae350/Kconfig b/board/AndesTech/ax25-ae350/Kconfig +index e50f505a..385c4c11 100644 +--- a/board/AndesTech/ax25-ae350/Kconfig ++++ b/board/AndesTech/ax25-ae350/Kconfig +@@ -25,7 +25,7 @@ config SPL_TEXT_BASE + default 0x800000 + + config SPL_OPENSBI_LOAD_ADDR +- default 0x01000000 ++ default 0x0 + + config BOARD_SPECIFIC_OPTIONS # dummy + def_bool y +-- +2.25.1
board/andes/ae350/patches/uboot/0003-Fix-u-boot-proper-booting-issue.patch new file +26 -0
@@ -0,0 +1,26 @@ +From 3d09501175ae6f5e3f6520b48b1358226a99ff16 Mon Sep 17 00:00:00 2001 +From: Yu Chien Peter Lin <[email protected]> +Date: Wed, 5 Jan 2022 18:17:39 +0800 +Subject: [PATCH] Fix u-boot proper booting issue + +Signed-off-by: Yu Chien Peter Lin <[email protected]> +--- + arch/riscv/cpu/start.S | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/arch/riscv/cpu/start.S b/arch/riscv/cpu/start.S +index 76850ec9..2ccda4f5 100644 +--- a/arch/riscv/cpu/start.S ++++ b/arch/riscv/cpu/start.S +@@ -139,7 +139,9 @@ call_harts_early_init: + * accesses gd). + */ + mv gp, s0 ++#if !CONFIG_IS_ENABLED(RISCV_SMODE) + bnez tp, secondary_hart_loop ++#endif + #endif + + jal board_init_f_init_reserve +-- +2.25.1
board/andes/ae350/patches/uboot/0004-Enable-printing-OpenSBI-boot-logo.patch new file +25 -0
@@ -0,0 +1,25 @@ +From 3847a959ac4c07facbd80104ca5fa6a91fad5f35 Mon Sep 17 00:00:00 2001 +From: Yu Chien Peter Lin <[email protected]> +Date: Thu, 6 Jan 2022 13:50:07 +0800 +Subject: [PATCH] Enable printing OpenSBI boot logo + +Signed-off-by: Yu Chien Peter Lin <[email protected]> +--- + include/opensbi.h | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/include/opensbi.h b/include/opensbi.h +index d812cc8c..91fb8fd9 100644 +--- a/include/opensbi.h ++++ b/include/opensbi.h +@@ -20,7 +20,7 @@ + + enum sbi_scratch_options { + /** Disable prints during boot */ +- SBI_SCRATCH_NO_BOOT_PRINTS = (1 << 0), ++ SBI_SCRATCH_NO_BOOT_PRINTS = 0, + }; + + /** Representation dynamic info passed by previous booting stage */ +-- +2.25.1
board/andes/ae350/post-build.sh new file +3 -0
@@ -0,0 +1,3 @@ +#!/bin/sh +cp $BINARIES_DIR/Image $TARGET_DIR/boot +cp $BINARIES_DIR/ae350.dtb $TARGET_DIR/boot
board/andes/ae350/readme.txt new file +65 -0
65 lines not on this page · raw message
board/andes/ae350/rootfs_overlay/boot/extlinux/extlinux.conf new file +4 -0
@@ -0,0 +1,4 @@ +label linux + kernel /boot/Image + fdt /boot/ae350.dtb + append earlycon=sbi root=/dev/mmcblk0p2 rootwait
board/andes/ae350/uboot.config.fragment new file +5 -0
@@ -0,0 +1,5 @@ +CONFIG_SPL_FS_FAT=y +CONFIG_SPL_MMC=y +# CONFIG_SPL_RAM_SUPPORT is not set +# CONFIG_OF_BOARD is not set +CONFIG_OF_SEPARATE=y
configs/andes_ae350_45_defconfig new file +43 -0
43 lines not on this page · raw message
Signature · 6 lines
2.17.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
PATCH v4 3/3 DEVELOPERS: add Yu-Chien Lin to board/andes
In reply to Yu Chien Peter LinNylon is no longer at Andes.
--- DEVELOPERS | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
DEVELOPERS +3 -2
@@ -2146,10 +2146,11 @@ N: Norbert Lange <[email protected]> F: package/systemd/ F: package/tcf-agent/ -N: Nylon Chen <[email protected]> +N: Yu Chien Peter Lin <[email protected]> F: arch/Config.in.nds32 F: board/andes -F: configs/andes_ae3xx_defconfig +F: configs/andes_ae300_defconfig +F: configs/andes_ae350_45_defconfig F: toolchain/toolchain-external/toolchain-external-andes-nds32/ N: Olaf Rempel <[email protected]>
Signature · 6 lines
2.17.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Peter,
Quoted 21 lines · Yu Chien Peter Lin
Rename ae3xx to ae300 for nds32 architecture and add ae350 platform.
AE300 (NDS32):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae300/
AE350 (RISC-V):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae350-axi-based-platform-pre-integrated-with-n25f-nx25f-a25-ax25/Signed-off-by Yu Chien Peter Lin <[email protected]>Signed-off-by Alan Kao <[email protected]>---
Changes v1 -> v2:
- move linux source code and its patches to AndesTech Github repo
- renameae350_andestar45_defconfigtoandes_ae350_45_defconfig
- change C library to uClibc
- remove OpenSSL package
- remove rootfs.cpio and rootfs.tar
- update DEVELOPERS
Changes v2 -> v3:
- specifiy branch to download from AndesTech linux repo
- change boot.cmd to extlinux.conf
- addpost-build.shfor extlinux.conf to retrieve Image and DTB
Quoted 8 lines
- fix format and update genimage_sdcard.cfg
- update readme.txt
- add packages (python3, pylibfdt and openssl) for u-boot binman
- reorder item in DEVELOPERS
Changes v3 -> v4:
- rename ae3xx folder to ae300
- renameandes_ae3xx_defconfigtoandes_ae300_defconfig
- update readme.txt and item in DEVELOPERS
Some of these change ^^^ must have been moved to the single patch, like DEVELOPERS is updated in patch 3/3. I've also forgotten to point you to add a --cover-letter, so keep in mind both points for next time.
I've built tested both defconfig successfully, so:
And the other patches of this series is all reviewed, so to me it's ready to be committed, but this will happen after Buildroot 2022.02 is released, since between rc1 to the release Maintainers only accept fixes. Another possibility is that they will commit these patches to next branch.
Please remember to tag V3.
Thank you for your effort!
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sas
Quoted 85 lines
--- .../{ae3xx/ae3xx.fragment => ae300/ae300.fragment} | 0 .../linux/0001-nds32-Fix-boot-messages-garbled.patch | 0 ...-dtc-Remove-redundant-YYLOC-global-declaratio.patch | 0 board/andes/{ => ae300}/readme.txt | 10 +++++----- .../{andes_ae3xx_defconfig => andes_ae300_defconfig} | 4 ++-- .../toolchain-external-andes-nds32/Config.in | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-)rename board/andes/{ae3xx/ae3xx.fragment => ae300/ae300.fragment} (100%)
rename board/andes/{ =>ae300}/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch(100%) rename board/andes/{ =>ae300}/patches/linux/0002-scripts-dtc-Remove-redundant-YYLOC-global-declaratio.patch(100%) rename board/andes/{ =>ae300}/readme.txt(71%)
rename configs/{andes_ae3xx_defconfig =>andes_ae300_defconfig} (69%)board/andes/ae300/ae300.fragment renamed from board/andes/ae3xx/ae3xx.fragment +0
-0board/andes/ae300/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch renamed from board/andes/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch +0
-0board/andes/ae300/patches/linux/0002-scripts-dtc-Remove-redundant-YYLOC-global-declaratio.patch renamed from board/andes/patches/linux/0002-scripts-dtc-Remove-redundant-YYLOC-global-declaratio.patch +0
-0board/andes/ae300/readme.txt renamed from board/andes/readme.txt +5
-5@@ -1,10 +1,10 @@ Intro ===== -Andestech(nds32) AE3XX Platform +Andestech(nds32) AE300 Platform -The AE3XX prototype demonstrates the AE3XX example platform on the FPGA. -It is composed of one Andestech(nds32) processor and AE3XX. +The AE300 prototype demonstrates the AE300 example platform on the FPGA. +It is composed of one Andestech(nds32) processor and AE300. How to build it ===============@@ -12,10 +12,10 @@ How to build it Configure Buildroot ------------------- -The andes_ae3xx_defconfig configuration is a sample configuration with +The andes_ae300_defconfig configuration is a sample configuration with all that is required to bring the FPGA Development Board: - $ make andes_ae3xx_defconfig + $ make andes_ae300_defconfig Build everything ----------------configs/andes_ae300_defconfig renamed from configs/andes_ae3xx_defconfig +2
-2@@ -1,10 +1,10 @@ BR2_nds32=y -BR2_GLOBAL_PATCH_DIR="board/andes/patches/" +BR2_GLOBAL_PATCH_DIR="board/andes/ae300/patches" BR2_TOOLCHAIN_EXTERNAL=y BR2_TOOLCHAIN_EXTERNAL_ANDES_NDS32=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_VERSION=y BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.17" BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y -BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/andes/ae3xx/ae3xx.fragment" +BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/andes/ae300/ae300.fragment" BR2_TARGET_ROOTFS_INITRAMFS=ytoolchain/toolchain-external/toolchain-external-andes-nds32/Config.in +0
-0
toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in config BR2_TOOLCHAIN_EXTERNAL_ANDES_NDS32 · line 15
Quoted 5 lines
toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in +1
-1@@ -12,4 +12,4 @@ config BR2_TOOLCHAIN_EXTERNAL_ANDES_NDS32 help nds32 toolchain for the nds32 architecture. It uses GCC 8.2.1, GDB 8.1.1, glibc 2.28, Binutils 2.30. It generates - code that runs on ae3xx platform + code that runs on ae300 platform
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Giulio,
Quoted 48 lines · Giulio Benetti
Quoted 47 lines
Hi Peter,
Quoted 21 lines · Yu Chien Peter Lin
Rename ae3xx to ae300 for nds32 architecture and add ae350 platform.
AE300 (NDS32):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae300/
AE350 (RISC-V):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae350-axi-based-platform-pre-integrated-with-n25f-nx25f-a25-ax25/Signed-off-by Yu Chien Peter Lin <[email protected]>Signed-off-by Alan Kao <[email protected]>---
Changes v1 -> v2:
- move linux source code and its patches to AndesTech Github repo
- renameae350_andestar45_defconfigtoandes_ae350_45_defconfig
- change C library to uClibc
- remove OpenSSL package
- remove rootfs.cpio and rootfs.tar
- update DEVELOPERS
Changes v2 -> v3:
- specifiy branch to download from AndesTech linux repo
- change boot.cmd to extlinux.conf
- addpost-build.shfor extlinux.conf to retrieve Image and DTBQuoted 8 lines
- fix format and update genimage_sdcard.cfg
- update readme.txt
- add packages (python3, pylibfdt and openssl) for u-boot binman
- reorder item in DEVELOPERS
Changes v3 -> v4:
- rename ae3xx folder to ae300
- renameandes_ae3xx_defconfigtoandes_ae300_defconfig
- update readme.txt and item in DEVELOPERSSome of these change ^^^ must have been moved to the single patch, like DEVELOPERS is updated in patch 3/3. I've also forgotten to point you to add a --cover-letter, so keep in mind both points for next time.
I've built tested both defconfig successfully, so:
Reviewed-by Giulio Benetti <[email protected]>Tested-by Giulio Benetti <[email protected]>[Giulio: build tested only]And the other patches of this series is all reviewed, so to me it's ready to be committed, but this will happen after Buildroot 2022.02 is released, since between rc1 to the release Maintainers only accept fixes. Another possibility is that they will commit these patches to next branch.
Quoted 8 lines
Quoted 8 lines
Please remember to tag V3.
Thank you for your effort!
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sas
Thanks for reviewing my patches and the guidance. I will make a new patch for the Config.in,
The last question, is it tag V5 for the next submission?
Regards,
Yu Chien Peter Lin
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Peter,
Quoted 52 lines · Yu Chien Peter Lin
Hi Giulio,
Quoted 50 lines · Giulio Benetti
Quoted 49 lines
Hi Peter,
Quoted 21 lines · Yu Chien Peter Lin
Rename ae3xx to ae300 for nds32 architecture and add ae350 platform.
AE300 (NDS32):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae300/
AE350 (RISC-V):
- http://www.andestech.com/en/products-solutions/andeshape-platforms/ae350-axi-based-platform-pre-integrated-with-n25f-nx25f-a25-ax25/Signed-off-by Yu Chien Peter Lin <[email protected]>Signed-off-by Alan Kao <[email protected]>---
Changes v1 -> v2:
- move linux source code and its patches to AndesTech Github repo
- renameae350_andestar45_defconfigtoandes_ae350_45_defconfig
- change C library to uClibc
- remove OpenSSL package
- remove rootfs.cpio and rootfs.tar
- update DEVELOPERS
Changes v2 -> v3:
- specifiy branch to download from AndesTech linux repo
- change boot.cmd to extlinux.conf
- addpost-build.shfor extlinux.conf to retrieve Image and DTBQuoted 8 lines
- fix format and update genimage_sdcard.cfg
- update readme.txt
- add packages (python3, pylibfdt and openssl) for u-boot binman
- reorder item in DEVELOPERS
Changes v3 -> v4:
- rename ae3xx folder to ae300
- renameandes_ae3xx_defconfigtoandes_ae300_defconfig
- update readme.txt and item in DEVELOPERSSome of these change ^^^ must have been moved to the single patch, like DEVELOPERS is updated in patch 3/3. I've also forgotten to point you to add a --cover-letter, so keep in mind both points for next time.
I've built tested both defconfig successfully, so:
Reviewed-by Giulio Benetti <[email protected]>Tested-by Giulio Benetti <[email protected]>[Giulio: build tested only]And the other patches of this series is all reviewed, so to me it's ready to be committed, but this will happen after Buildroot 2022.02 is released, since between rc1 to the release Maintainers only accept fixes. Another possibility is that they will commit these patches to next branch.
Please remember to tag V3.
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Thank you for your effort!
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sasThanks for reviewing my patches and the guidance.
You're welcome.
Quoted 1 line
I will make a new patch for the Config.in,
Which one? I only see:
toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in
Do you mean you will add an entry in DEVELOPERS for it?
Quoted 1 line
The last question, is it tag V5 for the next submission?
It depends if you need to modify these patches. Or if you add a new patch that depends on these patches, then yes, please send a V5 with all changes moved to the different patches, including adding the patch if this is your goal.
Best regards
Signature · 6 lines
Giulio Benetti Benetti Engineering sas _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Giulio,
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 4 lines
Changes v3 -> v4:
- rename ae3xx folder to ae300
- renameandes_ae3xx_defconfigtoandes_ae300_defconfig
- update readme.txt and item in DEVELOPERSSome of these change ^^^ must have been moved to the single patch, like DEVELOPERS is updated in patch 3/3. I've also forgotten to point you to add a --cover-letter, so keep in mind both points for next time.
I've built tested both defconfig successfully, so:
Reviewed-by Giulio Benetti <[email protected]>Tested-by Giulio Benetti <[email protected]>[Giulio: build tested only]
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
And the other patches of this series is all reviewed, so to me it's ready to be committed, but this will happen after Buildroot 2022.02 is released, since between rc1 to the release Maintainers only accept fixes. Another possibility is that they will commit these patches to next branch.
Please remember to tag V3.
Oh, I thought you were refering to format-patch with v3, sorry. I will mark the patch on patchwork to rejected state except the latest patch version.
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Thank you for your effort!
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sasThanks for reviewing my patches and the guidance.
Quoted 8 lines
Quoted 8 lines
You're welcome.
Quoted 1 line
I will make a new patch for the Config.in,
Which one? I only see:
toolchain/toolchain-external/toolchain-external-andes-nds32/Config.inDo you mean you will add an entry in DEVELOPERS for it?
I found the modifications on these files in Git history, usually have its own patch. So in PATCH v5, I will split [PATCH 1/3] to [PATCH 1/4] and [PATCH 2/4] for toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in other patches remain the same, and attach [PATCH 0/4] cover letter.
Quoted 11 lines
Quoted 11 lines
Quoted 1 line
The last question, is it tag V5 for the next submission?
It depends if you need to modify these patches. Or if you add a new patch that depends on these patches, then yes, please send a V5 with all changes moved to the different patches, including adding the patch if this is your goal.
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sas
Is there any the new comment?
Again, thanks for your help. :)
Best regards,
Yu Chien Peter Lin
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Peter,
Quoted 21 lines · Yu Chien Peter Lin
Hi Giulio,
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Quoted 4 lines
Changes v3 -> v4:
- rename ae3xx folder to ae300
- renameandes_ae3xx_defconfigtoandes_ae300_defconfig
- update readme.txt and item in DEVELOPERSSome of these change ^^^ must have been moved to the single patch, like DEVELOPERS is updated in patch 3/3. I've also forgotten to point you to add a --cover-letter, so keep in mind both points for next time.
I've built tested both defconfig successfully, so:
Reviewed-by Giulio Benetti <[email protected]>Tested-by Giulio Benetti <[email protected]>[Giulio: build tested only]And the other patches of this series is all reviewed, so to me it's ready to be committed, but this will happen after Buildroot 2022.02 is released, since between rc1 to the release Maintainers only accept fixes. Another possibility is that they will commit these patches to next branch.
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Please remember to tag V3.
Oh, I thought you were refering to format-patch with v3, sorry. I will mark the patch on patchwork to rejected state except the latest patch version.
Ok, V3 it's still tagged as new in patchwork for the moment.
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Thank you for your effort!
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sasThanks for reviewing my patches and the guidance.
You're welcome.
Quoted 1 line
I will make a new patch for the Config.in,
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Which one? I only see:
toolchain/toolchain-external/toolchain-external-andes-nds32/Config.inDo you mean you will add an entry in DEVELOPERS for it?
I found the modifications on these files in Git history, usually have its own patch.
No, maybe you mean there is a cover-letter that summarize the changes of all patches in patchset and then in every patch you list the changes of on that patch.
Quoted 4 lines
So in PATCH v5, I will split [PATCH 1/3] to [PATCH 1/4] and [PATCH 2/4] for toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in other patches remain the same,
No, wait. I've meant you only need to split:
---
Changes v1->v2:
*
*
[..]
---
for every patch. So, don't summarize all the changes on patch [1/3], because those changes are related to different patches. For example in V1->V2 you state:
- update DEVELOPERS
but you do it in patch [3/3], so you only have to move the changes into the right patch, that's all.
Quoted 1 line
and attach [PATCH 0/4] cover letter.
And yes please, add a cover letter that briefly explain what patchset does and that's it.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
The last question, is it tag V5 for the next submission?
It depends if you need to modify these patches. Or if you add a new patch that depends on these patches, then yes, please send a V5 with all changes moved to the different patches, including adding the patch if this is your goal.
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sasIs there any the new comment?
Again, thanks for your help. :)
For the moment I don't see anything wrong except the changelog.
Thank you!
Best regards
Signature · 6 lines
Giulio Benetti Benetti Engineering sas _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Giulio,
Quoted 24 lines · Giulio Benetti
Hi Peter,
Quoted 21 lines · Yu Chien Peter Lin
Hi Giulio,
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Quoted 19 lines
Quoted 4 lines
Changes v3 -> v4:
- rename ae3xx folder to ae300
- renameandes_ae3xx_defconfigtoandes_ae300_defconfig
- update readme.txt and item in DEVELOPERSSome of these change ^^^ must have been moved to the single patch, like DEVELOPERS is updated in patch 3/3. I've also forgotten to point you to add a --cover-letter, so keep in mind both points for next time.
I've built tested both defconfig successfully, so:
Reviewed-by Giulio Benetti <[email protected]>Tested-by Giulio Benetti <[email protected]>[Giulio: build tested only]And the other patches of this series is all reviewed, so to me it's ready to be committed, but this will happen after Buildroot 2022.02 is released, since between rc1 to the release Maintainers only accept fixes. Another possibility is that they will commit these patches to next branch.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Please remember to tag V3.
Oh, I thought you were refering to format-patch with v3, sorry. I will mark the patch on patchwork to rejected state except the latest patch version.
Ok, V3 it's still tagged as new in patchwork for the moment.
Updated to rejected state.
Quoted 61 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Thank you for your effort!
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sasThanks for reviewing my patches and the guidance.
You're welcome.
Quoted 1 line
I will make a new patch for the Config.in,
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Which one? I only see:
toolchain/toolchain-external/toolchain-external-andes-nds32/Config.inDo you mean you will add an entry in DEVELOPERS for it?
I found the modifications on these files in Git history, usually have its own patch.
No, maybe you mean there is a cover-letter that summarize the changes of all patches in patchset and then in every patch you list the changes of on that patch.
Quoted 4 lines
So in PATCH v5, I will split [PATCH 1/3] to [PATCH 1/4] and [PATCH 2/4] for toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in other patches remain the same,
No, wait. I've meant you only need to split:
---
Changesv1->v2:
*
*
[..]
---
for every patch. So, don't summarize all the changes on patch [1/3], because those changes are related to different patches. For example inV1->V2you state:
- update DEVELOPERS
but you do it in patch [3/3], so you only have to move the changes into the right patch, that's all.Quoted 1 line
and attach [PATCH 0/4] cover letter.
And yes please, add a cover letter that briefly explain what patchset does and that's it.
Quoted 12 lines
Quoted 11 lines
Quoted 11 lines
Quoted 1 line
The last question, is it tag V5 for the next submission?
It depends if you need to modify these patches. Or if you add a new patch that depends on these patches, then yes, please send a V5 with all changes moved to the different patches, including adding the patch if this is your goal.
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sas
Quoted 11 lines
Quoted 2 lines
Is there any the new comment?
Again, thanks for your help. :)For the moment I don't see anything wrong except the changelog.
Thank you!
Best regards
Signature · 2 lines
Giulio Benetti Benetti Engineering sas
Thanks for clarification.
Best regards,
Yu Chien Peter Lin
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot