[opensuse-arm] Odroid XU4
I have an Odroid XU4 that I tried installing openSUSE on with the XU3 image from here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odro... But there must be enough differences in the device tree and/or u-boot between the XU3/XU4 that it will not boot. I dd'ed the image to an SD card and it gets this far: U-Boot 2019.10 (Oct 26 2019 - 16:24:56 +0000) for ODROID- XU3/XU4/HC1/HC2 CPU: Exynos5422 @ 800 MHz DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 Loading Environment from MMC... *** Warning - No block device, using default environment In: serial Out: serial Err: serial Model: Odroid XU3 based on EXYNOS5422 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc2 is current device ** Unrecognized filesystem type ** Scanning mmc 2:3... Found U-Boot script /boot/boot.scr 2654 bytes read in 19 ms (135.7 KiB/s) ## Executing script at 50000000 SCRIPT FAILED: continuing... Scanning mmc 2:1... Found EFI removable media binary efi/boot/bootarm.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@12200000.blk... Disk mmc@12200000.blk not ready Scanning disk mmc@12220000.blk... Found 4 disks BootOrder not defined EFI boot manager: Cannot load any image 905216 bytes read in 111 ms (7.8 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Welcome to GRUB! ... It then loads the ram disk, kernel, and stalls after loading memory map. - Not suprising after seeing that boot.scr script failed. The XU3 has not been produced since 2015, and Hardkernel has pledged support of the XU4/HC1/HC2 for some years yet. What are the chances that we could get a working image for the XU4? Thanks. Mark -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 12/07/2020 19:26, Mark Petersen wrote:
I have an Odroid XU4 that I tried installing openSUSE on with the XU3 image from here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odro...
But there must be enough differences in the device tree and/or u-boot between the XU3/XU4 that it will not boot. I dd'ed the image to an SD card and it gets this far:
U-Boot 2019.10 (Oct 26 2019 - 16:24:56 +0000) for ODROID- XU3/XU4/HC1/HC2
CPU: Exynos5422 @ 800 MHz DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 Loading Environment from MMC... *** Warning - No block device, using default environment
In: serial Out: serial Err: serial Model: Odroid XU3 based on EXYNOS5422 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc2 is current device ** Unrecognized filesystem type ** Scanning mmc 2:3... Found U-Boot script /boot/boot.scr 2654 bytes read in 19 ms (135.7 KiB/s) ## Executing script at 50000000 SCRIPT FAILED: continuing... Scanning mmc 2:1... Found EFI removable media binary efi/boot/bootarm.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@12200000.blk... Disk mmc@12200000.blk not ready Scanning disk mmc@12220000.blk... Found 4 disks BootOrder not defined EFI boot manager: Cannot load any image 905216 bytes read in 111 ms (7.8 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Welcome to GRUB! ... It then loads the ram disk, kernel, and stalls after loading memory map. - Not suprising after seeing that boot.scr script failed.
The XU3 has not been produced since 2015, and Hardkernel has pledged support of the XU4/HC1/HC2 for some years yet. What are the chances that we could get a working image for the XU4?
We are always happy to have new active members of the community. So if you are interested to add the support yourself we can guide you what to do. Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, 2020-07-12 at 20:19 +0200, Matthias Brugger wrote:
On 12/07/2020 19:26, Mark Petersen wrote:
I have an Odroid XU4 that I tried installing openSUSE on with the XU3 image from here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odro...
But there must be enough differences in the device tree and/or u- boot between the XU3/XU4 that it will not boot. I dd'ed the image to an SD card and it gets this far:
U-Boot 2019.10 (Oct 26 2019 - 16:24:56 +0000) for ODROID- XU3/XU4/HC1/HC2
CPU: Exynos5422 @ 800 MHz DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 Loading Environment from MMC... *** Warning - No block device, using default environment
In: serial Out: serial Err: serial Model: Odroid XU3 based on EXYNOS5422 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc2 is current device ** Unrecognized filesystem type ** Scanning mmc 2:3... Found U-Boot script /boot/boot.scr 2654 bytes read in 19 ms (135.7 KiB/s) ## Executing script at 50000000 SCRIPT FAILED: continuing... Scanning mmc 2:1... Found EFI removable media binary efi/boot/bootarm.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@12200000.blk... Disk mmc@12200000.blk not ready Scanning disk mmc@12220000.blk... Found 4 disks BootOrder not defined EFI boot manager: Cannot load any image 905216 bytes read in 111 ms (7.8 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Welcome to GRUB! ... It then loads the ram disk, kernel, and stalls after loading memory map. - Not suprising after seeing that boot.scr script failed.
The XU3 has not been produced since 2015, and Hardkernel has pledged support of the XU4/HC1/HC2 for some years yet. What are the chances that we could get a working image for the XU4?
We are always happy to have new active members of the community. So if you are interested to add the support yourself we can guide you what to do.
Regards, Matthias
Matthias, I would be willing to try, but I would need quite a bit of guidance/hand-holding as I am not any kind of a programmer. Mark -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Mark, On 12/07/2020 20:34, Mark Petersen wrote:
On Sun, 2020-07-12 at 20:19 +0200, Matthias Brugger wrote:
On 12/07/2020 19:26, Mark Petersen wrote:
I have an Odroid XU4 that I tried installing openSUSE on with the XU3 image from here: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odro...
But there must be enough differences in the device tree and/or u- boot between the XU3/XU4 that it will not boot. I dd'ed the image to an SD card and it gets this far:
U-Boot 2019.10 (Oct 26 2019 - 16:24:56 +0000) for ODROID- XU3/XU4/HC1/HC2
CPU: Exynos5422 @ 800 MHz DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 Loading Environment from MMC... *** Warning - No block device, using default environment
In: serial Out: serial Err: serial Model: Odroid XU3 based on EXYNOS5422 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc2 is current device ** Unrecognized filesystem type ** Scanning mmc 2:3... Found U-Boot script /boot/boot.scr 2654 bytes read in 19 ms (135.7 KiB/s) ## Executing script at 50000000 SCRIPT FAILED: continuing... Scanning mmc 2:1... Found EFI removable media binary efi/boot/bootarm.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc@12200000.blk... Disk mmc@12200000.blk not ready Scanning disk mmc@12220000.blk... Found 4 disks BootOrder not defined EFI boot manager: Cannot load any image 905216 bytes read in 111 ms (7.8 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Welcome to GRUB! ... It then loads the ram disk, kernel, and stalls after loading memory map. - Not suprising after seeing that boot.scr script failed.
The XU3 has not been produced since 2015, and Hardkernel has pledged support of the XU4/HC1/HC2 for some years yet. What are the chances that we could get a working image for the XU4?
We are always happy to have new active members of the community. So if you are interested to add the support yourself we can guide you what to do.
Regards, Matthias
Matthias,
I would be willing to try, but I would need quite a bit of guidance/hand-holding as I am not any kind of a programmer.
Please have a look on the email I wrote a month ago, it will describe the basic steps. Then feel free to ask more questions here or on IRC (#opensuse-arm): https://lists.opensuse.org/opensuse-arm/2020-06/msg00019.html Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
We are always happy to have new active members of the community. So if you are interested to add the support yourself we can guide you what to do.
Regards, Matthias
Matthias,
I would be willing to try, but I would need quite a bit of guidance/hand-holding as I am not any kind of a programmer.
Please have a look on the email I wrote a month ago, it will describe the basic steps. Then feel free to ask more questions here or on IRC (#opensuse-arm): https://lists.opensuse.org/opensuse-arm/2020-06/msg00019.html
Regards, Matthias
Per your mailing list post from 05 June 2020, I checked if openSUSE U- Boot builds a package for the Odroid XU4 There is no defconfig for the XU4 There is no odroid-xu4 entry in the _multibuild file So to enable building u-boot for the odroid XU4 I think this is what I need to do: In OBS I branched the hardware:boot/u-boot package into my home: home:chiefpete:odroid-xu4/u-boot - Is this the correct package to branch? In my branched package I'll need to: Create odroid-xu4_defconfig file. Can I just copy this from https://github.com/hardkernel/u-boot/tree/odroidn2-v2015.01/configs ? Create odroid-xu4_defconfig.patch file to add defconfig for XU4 to u- boot-2020.04.tar.bz2 - I've never written a patch file so I will need help with this. Edit the _mulitbuild file to add <flavor>odroid-xu3</flavor> Edit the u-boot.spec file to add odroid-xu4-defconfig.patch Please let me know if these items are correct and if there are other things that I would have to do. Thanks Mark -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Mark, On 16/07/2020 02:06, Mark Petersen wrote:
We are always happy to have new active members of the community. So if you are interested to add the support yourself we can guide you what to do.
Regards, Matthias
Matthias,
I would be willing to try, but I would need quite a bit of guidance/hand-holding as I am not any kind of a programmer.
Please have a look on the email I wrote a month ago, it will describe the basic steps. Then feel free to ask more questions here or on IRC (#opensuse-arm): https://lists.opensuse.org/opensuse-arm/2020-06/msg00019.html
Regards, Matthias
Per your mailing list post from 05 June 2020, I checked if openSUSE U- Boot builds a package for the Odroid XU4 There is no defconfig for the XU4 There is no odroid-xu4 entry in the _multibuild file So to enable building u-boot for the odroid XU4 I think this is what I need to do:
In OBS I branched the hardware:boot/u-boot package into my home: home:chiefpete:odroid-xu4/u-boot - Is this the correct package to branch?
In my branched package I'll need to: Create odroid-xu4_defconfig file. Can I just copy this from https://github.com/hardkernel/u-boot/tree/odroidn2-v2015.01/configs ? Create odroid-xu4_defconfig.patch file to add defconfig for XU4 to u- boot-2020.04.tar.bz2 - I've never written a patch file so I will need help with this. Edit the _mulitbuild file to add <flavor>odroid-xu3</flavor> Edit the u-boot.spec file to add odroid-xu4-defconfig.patch
Well I think odroid-xu3_config also works for XU4 boards: https://github.com/u-boot/u-boot/blob/master/doc/README.odroid Sorry I didn't checked that beforehand. If I remember correctly from your last mail, odroid-xu3_config is already build in our U-Boot package, correct?
Please let me know if these items are correct and if there are other things that I would have to do.
If you use the downstream config with the upstream project, that won't work in 99% of the cases. From your last email I can see that you reached grub, which is half way through it already. But it somehow hangs, correct? Are you sure you are providing the correct console parameter via the grub boot menu? You could try to add earlycon to the kernel boot parameters (by editing it in the grub menu). That would help to see, where it actually fails. Regards, Matthias Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 16/07/2020 02:17, Matthias Brugger wrote:
Hi Mark,
On 16/07/2020 02:06, Mark Petersen wrote:
We are always happy to have new active members of the community. So if you are interested to add the support yourself we can guide you what to do.
Regards, Matthias
Matthias,
I would be willing to try, but I would need quite a bit of guidance/hand-holding as I am not any kind of a programmer.
Please have a look on the email I wrote a month ago, it will describe the basic steps. Then feel free to ask more questions here or on IRC (#opensuse-arm): https://lists.opensuse.org/opensuse-arm/2020-06/msg00019.html
Regards, Matthias
Per your mailing list post from 05 June 2020, I checked if openSUSE U- Boot builds a package for the Odroid XU4 There is no defconfig for the XU4 There is no odroid-xu4 entry in the _multibuild file So to enable building u-boot for the odroid XU4 I think this is what I need to do: In OBS I branched the hardware:boot/u-boot package into my home: home:chiefpete:odroid-xu4/u-boot - Is this the correct package to branch?
In my branched package I'll need to: Create odroid-xu4_defconfig file. Can I just copy this from https://github.com/hardkernel/u-boot/tree/odroidn2-v2015.01/configs ? Create odroid-xu4_defconfig.patch file to add defconfig for XU4 to u- boot-2020.04.tar.bz2 - I've never written a patch file so I will need help with this. Edit the _mulitbuild file to add <flavor>odroid-xu3</flavor> Edit the u-boot.spec file to add odroid-xu4-defconfig.patch
Well I think odroid-xu3_config also works for XU4 boards: https://github.com/u-boot/u-boot/blob/master/doc/README.odroid
Sorry I didn't checked that beforehand. If I remember correctly from your last mail, odroid-xu3_config is already build in our U-Boot package, correct?
Please let me know if these items are correct and if there are other things that I would have to do.
If you use the downstream config with the upstream project, that won't work in 99% of the cases.
From your last email I can see that you reached grub, which is half way through it already. But it somehow hangs, correct? Are you sure you are providing the correct console parameter via the grub boot menu? You could try to add earlycon to the kernel boot parameters (by editing it in the grub menu). That would help to see, where it actually fails.
Another thing you can do is to check if the device tree blob *.dtb is different from ux3 (I suppose so). As a first step, just build the upstream DTB and copy it on your SD card (in the EFI partition). Then in grub type 'e' to edit the grub menu entry and add 'devicetree /path/to/the/dtb' This will pass the ux4 DTB to the kernel. Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Mark Petersen -
Matthias Brugger