I discovered there was a later version (6) of the U-boot patch for the Odroid C2, and also – after more research – found the reason for the compile error… It turns out that the GIT version (May 5, 2016) of U-boot currently needs two patches.. The first one is to provide psci_system_reset for armv8, and details … Continue reading →
I decided to check the latest linux-next tree for signs of Odroid C2 code, and there is some there – apparently for basic functionality.. Compiled OK, but when I tried to boot it, the Hardkernel-supplied version of U-Boot crashed: odroidc2#ext4load mmc 0:1 ${loadaddr} /boot/uboot/Image 7748608 bytes read in 187 ms (39.5 MiB/s) odroidc2#ext4load mmc 0:1 ${dtb_loadaddr} /boot/uboot/meson-gxbb-odroidc2.dtb … Continue reading →
If you need a particular rootfs for an ARM7 or ARM64 device, there is a source of these at http://libguestfs.org/download/builder/ As an example, for Fedora 23 aarch64, then download the http://libguestfs.org/download/builder/fedora-23-aarch64.xz file, and then expand it (I use ark..) This will give you a file fedora-23-aarch64, and simply rename this to fedora-23-aarch64.img. As the Fedora aarch64 images … Continue reading →
I had ordered a Raspberry Pi 3 back in March in the hope that it would be a useful exercise in 64-bit on a different chipset.. I was (somewhat) disappointed to find that there was no initial 64-bit support, and indeed that I had been a bit of a pioneer in even running armv7 code on my … Continue reading →
I recently acquired on of the rather quirky Geekbox ARM64 devices, together with the oddly-named ‘Landingstrip’ expansion board.. http://www.cnx-software.com/2015/11/19/geekbox-is-a-hackable-android-and-linux-tv-box-powered-by-rockchip-rk3368-soc/ http://forum.geekbox.tv/ The similarity in overall design to the ARMv7 Radxa Rock2 will be seen from the photo: If you are ordering one, it is worth getting the USB/UART connector as well, as the 3-pin micro flat-pin connection is … Continue reading →
Just acquired a 64-bit Odroid C2: As usual, I installed Fedora 23 aarch64 on it: Fedora 23 (Twenty Three) Kernel 3.14.29 on an aarch64 (ttyS0) ………………… # uname -a Linux rgc2 3.14.29 #1 SMP PREEMPT Wed Mar 9 11:14:41 PST 2016 aarch64 aarch64 aarch64 GNU/Linux The only kernel source available – so far – is a heavily-patched … Continue reading →
Updated the DragonBoard 410c to Kernel 4.2.4: # git clone https://git.linaro.org/landing-teams/working/qualcomm/kernel.git -b release/qcomlt-4.2 and this version boot/runs OK.. I am running these systems ‘headless’, so have not been able to test monitor/display capabilities.. Fedora 23 (Twenty Three) Kernel 4.2.4 on an aarch64 (ttyMSM0) ……………… # uname -a Linux rg410c 4.2.4 #1 SMP PREEMPT Wed Nov 11 04:12:36 … Continue reading →
Just updated the Qualcomm DragonBoard 410c to Linaro/Qcom patched Kernel 4.2, from here: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/tree/refs/heads/integration-linux-qcomlt Using the saved kernel config from 4.2-rc5, the system booted OK (headless)..: Fedora release 23 (Twenty Three) Kernel 4.2.0 on an aarch64 (ttyMSM0) ……………. # uname -a Linux rg410c 4.2.0 #1 SMP PREEMPT Sun Sep 13 20:13:35 PDT 2015 aarch64 aarch64 aarch64 GNU/Linux … Continue reading →
After some more testing, including trying (unsuccessfully) the HiKey version of Kernel 4.1-rc4 # git clone -b hikey-mainline-rebase –single-branch https://github.com/96boards/linux/ I was frustrated by the complete lack of kernel boot info on screen, after the proprietary bootloader had finished.. More research found that this bootloader was described as somewhat deficient in the ‘fit for purpose’ department, and … Continue reading →
Updated the DragonBoard 410c to patched Kernel 4.2-rc1 from https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/tree/refs/heads/integration-linux-qcomlt , and the system booted OK: Fedora release 22 (Twenty Two) Kernel 4.2.0-rc1+ on an aarch64 (ttyMSM0) ……….. # uname -a Linux rg410c 4.2.0-rc1+ #2 SMP PREEMPT Thu Jul 16 15:14:27 PDT 2015 aarch64 aarch64 aarch64 GNU/Linux – But, on further testing, the SD Card (mmc1) had … Continue reading →