build
build copied to clipboard
Add wetek-play board based on odroidc1
Description
I want to make something useful of my old Wetek Play TV-Box. "Some" years ago, it was meant to be used with OpenElec (now Libreelec), but support had been dropped...
As long as Debian supports "armhf", I assume, it should be possible to make it work somehow. I have some coding experience, but no big experience with armbian itself or kernel/u-boot integration, etc. If somebody sees this PR, and could help me e.g. by pointing me into the right direction, I would be very happy 😃 This PR is "work-in-progress", so it should not be merged, yet. For now, It is just for "transparency". 😉
Basic information
AMLogic AML-8726 MX (meson6, 32bit) GPU: Mali MP400 1GB RAM 4GB local NAND flash storage
How Has This Been Tested?
Here I might need some input, what else I have to test!
- [ ] Image for SD card had been created successfull
- [ ] Wetek Play boots from SD card successfull
Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] Any dependent changes have been merged and published in downstream modules
u-boot integration
Yes, low level support, "bios", is problematic. Perhaps with your HW odroid c1 boot loader might work better - sd card interface is broken to some degree.
As long as Debian supports "armhf", I assume, it should be possible to make it work somehow.
A very basic condition but not really relevant in this problem.
my 2c
@igorpecovnik are there any plans to add support for TV boxes ?
are there any plans to add support for TV boxes ?
No plans.
No plans.
No one forbids the user to work in this direction, but what is the point of this PR for the master version?
Here I might need some input, what else I have to test!
Is this tested / finished?
Is this tested / finished?
There was no progress in the last weeks. It seems, that I have to take a step back, because it seems, that the build of odroidc1 is broken... Can somebody confirm that?
We had a general build issues for past few days. Since we don't deal with C1 for a while I don't know if it builds or not.
Is this still WIP?
Yes, I'm still working on that. I still have an issue with broken build of odroidc1 on untouched src. Can somebody confirm, that running
./compile.sh docker \
BOARD=odroidc1 \
BRANCH=current \
RELEASE=bullseye \
BUILD_MINIMAL=yes \
BUILD_DESKTOP=no \
KERNEL_ONLY=no \
KERNEL_CONFIGURE=yes \
KERNEL_KEEP_CONFIG=yes
results int this:
== u-boot make odroidc_config ==
== u-boot make ==
/root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/../libexec/gcc/arm-linux-gnueabihf/4.8.3/cc1: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
/root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/../libexec/gcc/arm-linux-gnueabihf/4.8.3/cc1: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
/root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/arm-linux-gnueabihf-ld: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
/root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/../libexec/gcc/arm-linux-gnueabihf/4.8.3/cc1: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
make: *** [Makefile:669: /root/armbian/cache/sources/u-boot-odroidc1/odroidc-v2011.03/build/lib/asm-offsets.s] Error 1
Or what else, am I doing wrong? I was assuming, that using docker images for build is the cleanest (and most reproduceable) way to build armbian...
Can somebody confirm, that running
Can't confirm since I won't run this, but its most likely related to this: https://stackoverflow.com/questions/21256866/libz-so-1-cannot-open-shared-object-file
Odroid C1 is EOL and it is highly possible that it doesn't build.
I was able to build image for C1 some weeks ago with u-boot compiler arm-none-eabi-gcc https://wiki.odroid.com/odroid-c1/software/building_u-boot https://forum.armbian.com/topic/13888-odroid-c1-s805/?do=findComment&comment=137707
Yes, I'm still working on that. I still have an issue with broken build of odroidc1 on untouched src. Can somebody confirm, that running
./compile.sh docker \ BOARD=odroidc1 \ BRANCH=current \ RELEASE=bullseye \ BUILD_MINIMAL=yes \ BUILD_DESKTOP=no \ KERNEL_ONLY=no \ KERNEL_CONFIGURE=yes \ KERNEL_KEEP_CONFIG=yes
results int this:
== u-boot make odroidc_config == == u-boot make == /root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/../libexec/gcc/arm-linux-gnueabihf/4.8.3/cc1: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory /root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/../libexec/gcc/arm-linux-gnueabihf/4.8.3/cc1: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory /root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/arm-linux-gnueabihf-ld: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory /root/armbian/cache/toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/../libexec/gcc/arm-linux-gnueabihf/4.8.3/cc1: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory make: *** [Makefile:669: /root/armbian/cache/sources/u-boot-odroidc1/odroidc-v2011.03/build/lib/asm-offsets.s] Error 1
Or what else, am I doing wrong? I was assuming, that using docker images for build is the cleanest (and most reproduceable) way to build armbian...
sudo apt-get install zlib1g:i386
you use https://github.com/150balbes/build branch master version in this fork source code ,you may be compile odroidc1 .
I have AML 8726-MX devices too.
I think after OneCloud is well maintained https://github.com/armbian/build/commit/965ce372de88a9330769a41a7f169e64e5c263df https://github.com/armbian/build/pull/3794 ... this should be easier to implement @jiangxianfu @2markus @DJAlPee
Closing. It needs rework / new PR anyway.