Development Resources

[Slaminger]

What would the easiest way to backport the kernel and uboot stuff from 20 to 19?

There are no dependencies that I am aware of. The kernel and uboot should be capable of running any modern Linux distribution (Ubuntu, Fedora, Arch, etc).
See also:
https://wiki.odroid.com/odroid_go_advance/build_uboot
https://wiki.odroid.com/odroid_go_advance/build_kernel

(Note that I do not package uboot/kernel/bootini. They are provided by HardKernel.)

Thanks. Remind me what the option to disable save States from command again? It was long ago and I cant recall. For retro run I mean

[Slaminger]

uboot and kernel should not have any dependencies.. you should be able to install the 20.04 uboot and kernel on 19.xx image without issues.

The question is can I do it in a way that's not on the hard kernel wiki. Meaning can I build and install the kernel on the device, or do I have to use my linux VM and cross compile then put it onto the SD? The wiki only shows cross compiling steps, and my VM hates my SD reader

[meveric]

I always compile directly on the ODROIDs.
In fact it's much easier than cross compiling, but might be a little bit more time consuming, aside from that compiling natively should always be better.
But didn't you say, you just want to use the existing Kernel instead of compiling again?

[crashoverride]

Remind me what the option to disable save States from command again?

The options are here:
https://github.com/OtherCrashOverride/r ... pp#L71-L80

Use "--restart" or "-r" on the command line.

[crashoverride]

The question is can I do it in a way that's not on the hard kernel wiki.

In the past, I have encountered issues building uboot and needed to use the same version of GCC that is used in the wiki. The GCC version will also affect kernel compilation as newer versions may detect errors that prior versions did not.

[Slaminger]

Well I got the kernel and uboot from the links above into Ubuntu 19 but it didn't get the on board WiFi working

[crashoverride]

it didn't get the on board WiFi working

Check the dmesg log for errors related to WIFI.

[Slaminger]

are we sure that those links are to the new kernel? because it didn't seem to enable l2 r2 or the on board wifi, I feel like it might have been the ubuntu 19 one

[crashoverride]

because it didn't seem to enable l2 r2 or the on board wifi,

This likely indicates you are using the device tree for rev1.0 instead of the one for rev1.1.
https://github.com/hardkernel/linux/blo ... ux-v11.dts

The boot.ini file in the reference image automatically selects the device tree based on hardware revision.

[Slaminger]

because it didn't seem to enable l2 r2 or the on board wifi,

This likely indicates you are using the device tree for rev1.0 instead of the one for rev1.1.
https://github.com/hardkernel/linux/blo ... ux-v11.dts

The boot.ini file in the reference image automatically selects the device tree based on hardware revision.

I confirmed that by looking at the boot.ini, it seems the instructions HK provided are for model 1 ubuntu 19 kernel and have not been updated for oga v11 yet, I do see the dts you referenced in the git clone tho, im just going to try swapping the boot.ini and see what I get

[Slaminger]

I got it working, the button layout is messed up but I can fix that, l2 r2 and wifi now work in my ubuntu 19 image

[pmprog]

RetroRun
https://github.com/OtherCrashOverride/retrorun-go2

Hi CrashOverride,

I've just cloned your retrorun-go2, and changed it to use four function keys to control brightness and volume instead of F4 then the dpad; but when I looked to copy it into /usr/bin, there was "retrorun" and "retrorun32". The make file built me "retrorun", so what's "retrorun32" and how do I build it?

Thanks

[crashoverride]

The make file built me "retrorun", so what's "retrorun32" and how do I build it?

"retrorun32" is a 32bit (armhf) version of "retrorun". This is required since 64bit applications can not load 32bit shared libraries (libretro cores) and vice versa. It is build exactly the same as "retrorun" except in a 32bit environment instead of a 64bit one. The resulting binary is then renamed from "retrorun" to "retrorun32".

[pmprog]

Thanks for the reply. I'm building directly on the OGA, and I think I read in one of your other posts that there was a chroot to 32bit. Sorry if this is a dumb question, I know some basic linux stuff (and I've heard of a chroot), but could you (or anyone else) walk me through building the 32bit version over SSH?

[crashoverride]

could you (or anyone else) walk me through building the 32bit version over SSH?

It is not a trivial task. It requires using debootstrap to generate the 32bit environment (its another copy of the OS compiled for 32bit). Then, required dependencies and headers (libgo2, librga, build-essential, git, libopenal, libevdev, libdrm) need to be installed or copied into the environment. Optionally, mount point remapping is established to provide access to hardware devices like GPU.

I really would like to get the process documented, but I currently do not have the time. As previously stated, it is non-trivial.

[pmprog]

Yeah, it sounds it... Okay, I'll leave it for now, and see which cores i use don't use my new retrorun. If all the ones i use do, then i guess it's not really a problem
Thanks again

[apd]

To create a quick chroot for odroid go adv, and enable qemu user emulation I am using this:

https://github.com/aplanas/chrootctl

You can now install the compiler and the headers commented by @crashoverride, still missing the part about remapping the hardware, does any one have a pointer about how to do this? I would like to complete this chrootctl script.

[crashoverride]

still missing the part about remapping the hardware, does any one have a pointer about how to do this?

Code: Select all

mount --rbind /dev YOUR_ROOT/dev

Where "YOUR_ROOT" is the top level of the chroot folder.

Note that the chroot needs the same user/group IDs that match those set in /dev. Normally the "root" user is sufficient.

[apd]

Ah cool! That was already in place then (https://github.com/aplanas/chrootctl/bl ... ootctl#L68). At least I am able to see the same devices inside the chroot and outside.

Thanks!

[escalade]

I always compile directly on the ODROIDs.
In fact it's much easier than cross compiling, but might be a little bit more time consuming, aside from that compiling natively should always be better.

Actually, there's no difference at all. The same compiler version will output the same binaries if you are running it natively or using a cross compiler. I build the entire OS in about 3 hours on my NUC8, how long does it take you to compile the kernel?

[Christian_Haitian]

To create a quick chroot for odroid go adv, and enable qemu user emulation I am using this:

https://github.com/aplanas/chrootctl

You can now install the compiler and the headers commented by @crashoverride, still missing the part about remapping the hardware, does any one have a pointer about how to do this? I would like to complete this chrootctl script.

I tried this script but I'm not sure what base environment it's based to run from. I tried a Lubuntu 16.04 X64 and it didn't work. I tried a ubuntu armv71 install on an Raspberry pi and I got a little further but it still failed to create the chroot. Any advice on this? My goal is to create a 32bit dev environment so I can build a 32 bit version of retroarch 1.8.9.

Thanks

[apd]

I tried this script but I'm not sure what base environment it's based to run from. I tried a Lubuntu 16.04 X64 and it didn't work. I tried a ubuntu armv71 install on an Raspberry pi and I got a little further but it still failed to create the chroot. Any advice on this? My goal is to create a 32bit dev environment so I can build a 32 bit version of retroarch 1.8.9.

My env is openSUSE Tumbleweed, but I do not see anything that depends on it. Should work on any Linux distribution. Try again with the Lubuntu and show me the error. Be sure that you installed this:

> apt-get install curl kpartx rsync qemu binfmt-support qemu-user-static

The process is very simple, download the official odroid go advance ubuntu image, extract the content via rsync, and register the qemu-static in a way that if an ARM (32 or 64) is detected, it will execute the command through qemu.

[Christian_Haitian]

I tried this script but I'm not sure what base environment it's based to run from. I tried a Lubuntu 16.04 X64 and it didn't work. I tried a ubuntu armv71 install on an Raspberry pi and I got a little further but it still failed to create the chroot. Any advice on this? My goal is to create a 32bit dev environment so I can build a 32 bit version of retroarch 1.8.9.

My env is openSUSE Tumbleweed, but I do not see anything that depends on it. Should work on any Linux distribution. Try again with the Lubuntu and show me the error. Be sure that you installed this:

> apt-get install curl kpartx rsync qemu binfmt-support qemu-user-static

The process is very simple, download the official odroid go advance ubuntu image, extract the content via rsync, and register the qemu-static in a way that if an ARM (32 or 64) is detected, it will execute the command through qemu.

I will try this thank you for sharing the required dependencies as well. How do I set it up so that this chroot is a 32bit only environment?

[apd]

How do I set it up so that this chroot is a 32bit only environment?

The official Ubuntu image for OGA mix 32 and 64 versions of libraries. Use apt-get to install the libraries of 32 bits that you require.

Enable the chroot env (see the chrootctl doc for more help)

> sudo chrootctl shell

You can see that already the official image is multiarch, nothing to do here.

# dpkg --print-architecture
arm64

# dpkg --print-foreign-architectures.
armhf

To learn more about multiarch in debian:
https://wiki.debian.org/Multiarch/HOWTO

Install the compiler;

# apt install build-essential

Now you need to pass to GCC the appropriate flags to generate 32 bits executable, for example:

https://github.com/OtherCrashOverride/m ... ild.sh#L36

[Christian_Haitian]

This is the error I get once I've verified I have installed all of the dependencies on Lubuntu 16.04.03 X64. This is when I attempt to do sudo ./chrootctl create

[apd]

IMAGE="ubuntu-20.04-4.4-es-odroid-goA-20200514.img"
# De-register the partitions, ignore the error
kpartx -vd "${IMAGE}"
# Register again the partitions
kpartx -va "${IMAGE}"

What is the output of the last command? Please, ignore the errors of the first one, is there to make sure that you start from scratch.

[Christian_Haitian]

IMAGE="ubuntu-20.04-4.4-es-odroid-goA-20200514.img"
# De-register the partitions, ignore the error
kpartx -vd "${IMAGE}"
# Register again the partitions
kpartx -va "${IMAGE}"

What is the output of the last command? Please, ignore the errors of the first one, is there to make sure that you start from scratch.

I get the following.

Capture.PNG (5.49 KiB) Viewed 3063 times

[apd]

I get the following.Capture.PNG

This seems to be OK. Christian, I am not able to reproduce your issue. The post with the first error suggested that kpartx was to able to detect the partitions, but this output from this last post shows that is not the case.

I suggest to retry, or use set -x to have some insight of what is happening. I any case I recommend you to move the debugging session outside the forum. Maybe create an issue in the github project?

[pmprog]

To use the hardware acceleration from libgo2, do you need to use the EGL context? At the minute I'm just using memory bitmaps and go2_presenter_post.

Would any kind soul be willing to do a small 3D rotating cube GLES example using libgo2 please?

[crashoverride]

To use the hardware acceleration from libgo2, do you need to use the EGL context? At the minute I'm just using memory bitmaps and go2_presenter_post.

The "go2_presenter_post" function uses RGA2 (instead of GLES) for hardware acceleration of rotation and scaling.

Would any kind soul be willing to do a small 3D rotating cube GLES example using libgo2 please?

To use GLES, a 3D "context" is created that provides surfaces to "go2_presenter_post".

1) Create a 3D context. Note the "major" and "minor" fields denote the version of GLES to use.
https://github.com/OtherCrashOverride/e ... p#L87-L100

2) Perform any GLES operations for drawing.

3) Display the surface:
https://github.com/OtherCrashOverride/e ... #L280-L288

[pmprog]

Fantastic, thanks, I'll have a look at that

[pmprog]

Sorry, another probably dumb question, but which GLES versions are supported?

[crashoverride]

which GLES versions are supported?

All of them!
1.0, 2.0, 3.0, 3.1, 3.2

[pmprog]

I did say it was probably a dumb question. Thanks

[Christian_Haitian]

Greetings,

I was able to setup a 64 bit and 32 bit chroot dev environment on a Lubuntu 16.04 Virtualbox VM. I decided to package it and make available for others in case others encounter similar initial struggles like I did.

Helpful tools already preinstalled in both chroot instances:

build-essential git wget libdrm-dev python3 python3-pip python3-setuptools python3-wheel ninja-build libopenal-dev premake4 autoconf libevdev-dev ffmpeg libsnappy-dev libboost-tools-dev magics++ libboost-thread-dev libboost-all-dev

File Manager: PCManFM version 1.2.4 with Open as Root configured

User: osboxes.org
Pass: password

From terminal session like lxterminal:

sudo chroot /mnt/data/armhf/ #for 32 bit Arm environment
sudo chroot /mnt/data/arm64/ #for 64 bit Arm environment

It can be downloaded from the Mega link below

11/1/2020 Update -- I was able to create an updated virtual box vm development environment using a variant of Debian Dog called Buster Dog. It's a much smaller distro, it's based on the newer Debian Buster release, has PCManFM version 1.3.1, boots directly into root and has both 32 bit and 64 bit Arm environments included. This download is only a little over 2.7GBs and expands to a little under 8GBs but is configured to grow up to 50GBs to allow space for various development needs. Virtualbox guest additions have already be preinstalled as well for Virtual Box version 6.1.12. I've also created 2 shortcuts for the chroots on the vm's desktop named Arm32 and Arm64. If you double click into them, they will open a terminal directly into the respective environments so you can begin your various builds. Filezilla is also included.

01/05/2021 Update -- I've received a couple of reports that internet from within the chroots may not work out of the box. What has fixed this is to connect to the internet outside of the chroot (like ping google.com from a regular terminal session in the VM) then move the resolv.conf from /etc to the chroot /etc folders (/mnt/data/arm64/etc) and (/mnt/data/armhf/etc) then internet will work within them.

More info about Buster Dog is available here: https://debiandog.github.io/doglinux/zz03busterdog.html

The actual download link of the vm: https://mega.nz/file/ucw3DQ7C#wO1biH-zn ... 65bNFz63R8

Hopefully this is helpful for others.