In the docs under buildroot-sdk it says “The current SDK does not support the ARM core of Duo256M and DuoS. If you need to use the ARM core, you can temporarily refer to this repositories:” and has a link to the “duo-buildroot-sdk-v2” repo. This repo has no documentation, I am wondering about a few things
Is “v2” going to become the repo that hosts the official images at some point?
Docs say you “temporarily” refer to the repository, does milkv have any kind of timeline for when they will release an image with ARM support? (Duo advertises ARM core and I purchased thinking it was supported)
The process is very much the same as for the v1 SDK project.
You’re saying you’re building it on Ubuntu 24.04 LTS, which is not what’s recommended (for any reason) by the developers.
I’ve built firmwares for all three boards, both RV64 and ARM64 with this repo after starting with the v1 repo. There must’ve been something missing, but I’m afraid it would not let you build it from the v1 repo either.
I tried setting up a Ubuntu 22.04 docker container and following the instructions in the v1 repo to run the build script (installing the needed dependencies inside the container, then running ./build.sh 'milkv-duo256m-glibc-arm64-sd'. After fixing an issue with python command not being available by installing python-is-python3. Now I am getting an error,
Which I think is caused by /~/duo-buildroot-sdk-v2/osdrv/interdrv/v2/sys/Makefile:1: /~/duo-buildroot-sdk-v2/linux_5.10/build/sg2002_milkv_duo256m_glibc_arm64_sd/../Makefile.interdrv.param: No such file or directory
Does anyone know how to fix this error? Regardless, if there is an experimental image for the ARM core, why doesn’t milkv host that for users who don’t want to compile it themselves?
Yes, our goal is to replace the V1 code repository with V2.
According to the plan, the current status of V2 has completed 90% of the functions. We can compile various versions of firmware normally on Ubuntu 20.04 internally, and the compilation method is basically the same as V1.
Next, we will continue to improve the functions of V2 and solve compilation problems like the one you encountered. After that, we will use V2 to release the firmware and update related documents.
@lama milkv support told me a few weeks ago it would be about a month. Being an engineer myself I know it’s hard to give accurate time estimates but I would expect something in mid October. According to commit messages in the v2 repo from August 19th there should be bluetooth support
What machines (architectures) are you running builds on? I started buildroot on RPI5 bookwork, then RPI5 LTS xx,xx. The toolchain doesn’t support that. I have Macbook Pro, M1,RPI AND Duo S. I have a Windows x64 but I think they are nightmares.
I hooked up a camera and the camera test didn’t initialize the camera. So I wanted to go backwards and make buildroot.
This has been a lot of fun and I hope to get my projects running on these small units.