Has anyone tried updating buildroot?

Duo
1

Hey all,

I have been running into some issues with the buildroot sdk.
I think most of these are a result of using a modern toolchain against the 2021 buildroot version.

For instance this is an issue I have run into. And judging by the thread a lot of people seem to be running into buildroot related issues.

This particular issue I think can be fixed by using a slightly newer version of util-linux or just omitting parts of it from the build.

But as far as I understand buildroot doesn’t allow you to partially update packages. You’d just need to use a new release of buildroot.

So has anyone tried porting the current config to a newer version of buildroot? Is there any particular reason for keeping it on 2021.05?

1 Like
2

I verified that patching util-linux does fix that particular issue, but I still run into other issues.

I am going to try to make a global patch directory to fix these minor patches. And I might also still experiment with updating buildroot in its entirety.

1 Like
3

Weirdly the buildroot was only added last year at which point many newer releases did already exist

1 Like
4

I got the buildroot to compile on ArchLinux!

I had to update 2 packages, the PR is here: buildroot: update util-linux and fakeroot by LevitatingBusinessMan · Pull Request #110 · milkv-duo/duo-buildroot-sdk · GitHub

Know that I am somewhat more familiar with the build system, I generally think that the whole buildroot could be replaced with a newer release without much trouble.

2 Likes
5

Apparently there is a new revision of the sdk in progress:

This includes a newer buildroot.

1 Like
6

Moreover:

$ ./build.sh lunch
Select a target to build:
1. milkv-duo256m-glibc-arm64-sd
2. milkv-duo256m-musl-riscv64-sd
3. milkv-duos-glibc-arm64-sd
4. milkv-duos-musl-riscv64-sd

You see the first and third options? Looks very much as if we’re on the verge of having ARM-core images. :slight_smile:

1 Like
7

I haven’t tested them personally but I think they are working.

I am confused by the lack of emmc, I will try setting it up myself.

1 Like
8

I have a Duo S board with an eMMC module, but for now I’d rather prefer testing these images on TF cards, which are expendables, to some extent.

Currently building them four to see how long it will take (and how much space it’s gonna eat; I’m already thinking of using some filesystem with compression and deduplication), will flash it, and try on my bards, and get back here.

9

I’m happy to say it actually works:

[root@milkv-duo]~# uname -mr
5.10.4-tag- aarch64

I tested the Duo S image, but I’m pretty sure the Duo 256M image will certainly work as well.

So now we actually can have working images with ARM-core as the main one!

2 Likes
10

Could you run some benchmark on both to compare the CPU performance?

1 Like
11

I can try them if you point me to a good benchmark you like.

I am not very smart, but I like testing, and I have the hardware. Therefore, I will need some assistance with this, okay?

1 Like
12

@hannahKobain

Does WiringX work on ARM?

1 Like
13

I was trying to find a convenient excuse for building these images again with some fresh commits.

Oh, and who can point me into Milk-V Duo SDK for ARM?