Skip to content

Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support

Thomas Petazzoni buildroot 4 versions – New

Get series with b4
b4 am 20190418110025.6e34ff9e@windsurf

Versions newest first · linked by author and title

  1. v5 Latest posting 2/20 of 4 patches 0 repliesNew
  2. v5 posting 1/24 patches 0 repliesSuperseded
  3. v42 patches 0 repliesSuperseded
Earlier versions · 1
VersionPostedPatchesRepliesStatus
v23 patches0 repliesSuperseded

Patches in v5 posting 2/2 No applies recorded yet

None of the 4 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.

Read the v5 thread

Cover letter [Buildroot] [PATCH v5 0/4] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support

Hello Nylon,

Quoted 17 lines · On Thu, 18 Apr 2019 16:39:10 +0800 Nylon Chen <[email protected]> wrote:
Quoted 3 lines

Build failure: http://autobuild.buildroot.net/results/1b1/1b18acb11db4d6c4198deb7385aff3d4d524c37e/build-end.log
Commit to disable binutils on nds32: https://git.buildroot.org/buildroot/commit/?id=b45a703078e6f3be096f24ac63848490d32d0d29

I got two methods can resolve this problem

1.package/binutils/binutils.mk

(quoted diff) +4 -0
+ifeq ($(BR2_nds32),y)
+GNU_TARGET_NAME=nds32le-linux
+endif
+

2.package/Makefile.in

(quoted diff) +3 -0
+ifeq ($(BR2_nds32),y)
+GNU_TARGET_NAME=$(ARCH)le-$(TARGET_OS)
+else
Quoted 2 lines

GNU_TARGET_NAME = $(ARCH)-$(TARGET_VENDOR)-$(TARGET_OS)-$(LIBC)$(ABI) +endif

Ah, so the correct tuple for your architecture is nds32le, not nds32 ?

If that's correct, then the right change is:

arch/Config.in.nds32 +1 -1
index 9c5db20e6f..f268883662 100644
@@ -1,5 +1,5 @@
 config BR2_ARCH
-       default "nds32"
+       default "nds32le"
 
 config BR2_GCC_TARGET_ARCH
        default "v3"

So that ARCH is directly equal to nds32le. Since the architecture at the kernel level is known as nds32, you will also want the following change:

Makefile +1 -0
index 522c0b0606..86e444da98 100644
@@ -439,6 +439,7 @@ KERNEL_ARCH := $(shell echo "$(ARCH)" | sed -e "s/-.*//" \
        -e s/arceb/arc/ \
        -e s/arm.*/arm/ -e s/sa110/arm/ \
        -e s/aarch64.*/arm64/ \
+       -e s/nds32.*/nds32/ \
        -e s/or1k/openrisc/ \
        -e s/parisc64/parisc/ \
        -e s/powerpc64.*/powerpc/ \
Quoted 6 lines
Quoted 5 lines

- The libffi library does not have support for nds32 as well, so I made sure that we don't try to build configurations that include libffi on nds32. Are you planning on adding nds32 support to libffi upstream ?

We have no plans at the moment.

OK. I think you should plan to have libffi support. Without libffi, you can't build libglib, which means a huge set of Linux libraries/applications can't be built for your platform. Another thing that requires libffi is Python, so without libffi support for nds32, you can't build Python.

See https://github.com/libffi/libffi for the upstream source code. And see https://github.com/libffi/libffi/tree/master/src for all the folders containing architecture specific code. There is not that much architecture specific code.

Of course, there is no urgency: Buildroot autobuilders will not try to build any configuration that include libffi. But it means that a lot of packages are not tested, and also that a lot of the Linux software ecosystem is not usable on nds32.

Best regards,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com