Re: [opensuse-arm] Odroid-C2
On 30/04/17 13:03, Andreas Färber wrote: Hi Sid, Am 27.04.2017 um 17:20 schrieb Sid Boyce: Looks like my SD card interface is broken as it does not boot with any distro. I normally run Ubuntu from a eMMC. Did you detach the eMMC for SD testing? I don't have an eMMC module. If you're feeling like experimenting, you could back up your Ubuntu and try dd'ing the JeOS to eMMC. I'm not aware of any special blobs being needed for eMMC, so it might work... Regards, Andreas Hi Andreas, Yes I did. I always remove the eMMC when testing SD cards. When you said you had no problems and no one else reported problems I thought I would try to boot other OS's from SD cards, all failed the same way. It can only be the SD card slot at fault. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Hi Sid, Am 27.04.2017 um 17:20 schrieb Sid Boyce: > Looks like my SD card interface is broken as it does not boot with any > distro. > > I normally run Ubuntu from a eMMC. Did you detach the eMMC for SD testing? I don't have an eMMC module. If you're feeling like experimenting, you could back up your Ubuntu and try dd'ing the JeOS to eMMC. I'm not aware of any special blobs being needed for eMMC, so it might work... Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Hi Daniel, Am 22.04.2017 um 13:32 schrieb Daniel Bischof: > On Fri, 21 Apr 2017, Sid Boyce wrote: >> On 21/04/17 09:13, Andreas Färber wrote: >>> JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, >>> instructions at https://en.opensuse.org/HCL:OdroidC2. >> >> Burned >> openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz >> per instructions, does not boot. Only the red LED lights. fsck'd both >> partitions to make sure they are clean. Results the same. > > I had to wait several minutes before I could log in via ssh. Glad it works for you. > No LED > flashing, just the red one constantly on. [...] You can run `modprobe ledtrig-heartbeat` to get the LED flashing. leds_gpio is not part of the initrd but gets loaded just fine; adding ledtrig-heartbeat to dracut's add_drivers did not help, nor did adding it to force_drivers load it (I did verify with lsinitrd that it's there after local config changes and subsequent `mkinitrd`). Nothing in dmesg. If you find any clues, let us know - the LED is no priority to me. ;) > Nice work, btw. Thank you, Andreas. You're welcome. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
On 22/04/17 00:08, Sid Boyce wrote: On 21/04/17 16:57, Andreas Färber wrote: Hi, Am 21.04.2017 um 17:00 schrieb Sid Boyce: On 21/04/17 15:40, Andreas Färber wrote: Am 21.04.2017 um 16:13 schrieb Sid Boyce: On 21/04/17 09:13, Andreas Färber wrote: JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT patches yet. Booting does not mean full-featured! Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. [...] I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. Having HDMI connected didn't hurt here. The blue LED never flashes on For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting. and no message appears on the serial connection. Baudrate 115200? Working for your Ubuntu image? I am using one of the recommended Toshiba SD cards - 64 GB. 32 GB SanDisk Ultra microSHDC Class 10 UHS-I here. Where did you read about recommended cards? http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2 "The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon." What they're selling is SanDisk 8 GB and 16 GB: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743 Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling... Regards, Andreas http://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf - Page 24 Fully compatible microSD cards. I have left it powered up for around 2 hours, it still doesn't show any messages on the serial console -- 115200-8-N1. microSD card compatibility can be a real problem, I have 3 dead ones that is not sensed. I have a Sandisk Ultra XC-1 I shall try. Regards Sid. Hi Andreas, Looks like my SD card interface is broken as it does not boot with any distro. I normally run Ubuntu from a eMMC. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
On 22/04/17 12:32, Daniel Bischof wrote: Sid, On Fri, 21 Apr 2017, Sid Boyce wrote: On 21/04/17 09:13, Andreas Färber wrote: Am 20.04.2017 um 20:57 schrieb Andreas Färber: Am 18.04.2017 um 23:25 schrieb Andreas Färber: Am 18.04.2017 um 21:35 schrieb Sid Boyce: On 15/04/17 09:48, Andreas Färber wrote: Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel. Am 11.04.2017 um 01:42 schrieb Andreas Färber: == aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. fsck'd both partitions to make sure they are clean. Results the same. I had to wait several minutes before I could log in via ssh. No LED flashing, just the red one constantly on. Using a SanDisk Extreme 32GB (considerably faster than my other microSDs, but also more expensive). Nice work, btw. Thank you, Andreas. --Daniel. I have had it powered up ever since I last posted, "nmap -sT 192.168.10.0/24" does not see it. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Sid, On Fri, 21 Apr 2017, Sid Boyce wrote: On 21/04/17 09:13, Andreas Färber wrote: Am 20.04.2017 um 20:57 schrieb Andreas Färber: Am 18.04.2017 um 23:25 schrieb Andreas Färber: Am 18.04.2017 um 21:35 schrieb Sid Boyce: On 15/04/17 09:48, Andreas Färber wrote: Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel. Am 11.04.2017 um 01:42 schrieb Andreas Färber: == aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. fsck'd both partitions to make sure they are clean. Results the same. I had to wait several minutes before I could log in via ssh. No LED flashing, just the red one constantly on. Using a SanDisk Extreme 32GB (considerably faster than my other microSDs, but also more expensive). Nice work, btw. Thank you, Andreas. --Daniel.
Re: [opensuse-arm] Odroid-C2
On 22/04/17 00:08, Sid Boyce wrote: On 21/04/17 16:57, Andreas Färber wrote: Hi, Am 21.04.2017 um 17:00 schrieb Sid Boyce: On 21/04/17 15:40, Andreas Färber wrote: Am 21.04.2017 um 16:13 schrieb Sid Boyce: On 21/04/17 09:13, Andreas Färber wrote: JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT patches yet. Booting does not mean full-featured! Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. [...] I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. Having HDMI connected didn't hurt here. The blue LED never flashes on For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting. and no message appears on the serial connection. Baudrate 115200? Working for your Ubuntu image? I am using one of the recommended Toshiba SD cards - 64 GB. 32 GB SanDisk Ultra microSHDC Class 10 UHS-I here. Where did you read about recommended cards? http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2 "The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon." What they're selling is SanDisk 8 GB and 16 GB: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743 Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling... Regards, Andreas http://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf - Page 24 Fully compatible microSD cards. I have left it powered up for around 2 hours, it still doesn't show any messages on the serial console -- 115200-8-N1. microSD card compatibility can be a real problem, I have 3 dead ones that is not sensed. I have a Sandisk Ultra XC-1 I shall try. Regards Sid. Same result with the Sandisk Ultra. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
On 21/04/17 16:57, Andreas Färber wrote: Hi, Am 21.04.2017 um 17:00 schrieb Sid Boyce: On 21/04/17 15:40, Andreas Färber wrote: Am 21.04.2017 um 16:13 schrieb Sid Boyce: On 21/04/17 09:13, Andreas Färber wrote: JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT patches yet. Booting does not mean full-featured! Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. [...] I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. Having HDMI connected didn't hurt here. The blue LED never flashes on For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting. and no message appears on the serial connection. Baudrate 115200? Working for your Ubuntu image? I am using one of the recommended Toshiba SD cards - 64 GB. 32 GB SanDisk Ultra microSHDC Class 10 UHS-I here. Where did you read about recommended cards? http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2 "The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon." What they're selling is SanDisk 8 GB and 16 GB: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743 Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling... Regards, Andreas http://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf - Page 24 Fully compatible microSD cards. I have left it powered up for around 2 hours, it still doesn't show any messages on the serial console -- 115200-8-N1. microSD card compatibility can be a real problem, I have 3 dead ones that is not sensed. I have a Sandisk Ultra XC-1 I shall try. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Hi, Am 21.04.2017 um 17:00 schrieb Sid Boyce: > On 21/04/17 15:40, Andreas Färber wrote: >> Am 21.04.2017 um 16:13 schrieb Sid Boyce: >>> On 21/04/17 09:13, Andreas Färber wrote: JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. >>> Burned >>> openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz >>> per instructions, does not boot. >>> Only the red LED lights. >> It does here. Are you maybe looking at an HDMI screen instead of serial? >> HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT >> patches yet. Booting does not mean full-featured! >> >> Also as usual it takes some minutes until Kiwi has repartitioned the >> card and network is up. [...] > I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. Having HDMI connected didn't hurt here. > The blue LED never flashes on For some reason the ledtrig-heartbeat module does not get loaded automatically. So the blue LED is unrelated to booting. > and no message appears on the serial > connection. Baudrate 115200? Working for your Ubuntu image? > I am using one of the recommended Toshiba SD cards - 64 GB. 32 GB SanDisk Ultra microSHDC Class 10 UHS-I here. Where did you read about recommended cards? http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438&tab_idx=2 "The ODROID-C2 can utilize the newer UHS-1 SD model, which is about 2 times faster than a normal class 10 card. Note that there are some cards which needs additional booting delay time around 30 seconds. According to our test, most Sandisk Micro-SD cards don't cause the booting delay. We will make a compatibility list soon." What they're selling is SanDisk 8 GB and 16 GB: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145636129743 Note that the initial serial output comes from BL1, so is independent of any mainline U-Boot code specific to us. I doubt that meson-tools are at fault if the same image boots for me. So rather puzzling... Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
On 21/04/17 15:40, Andreas Färber wrote: Hi Sid, Am 21.04.2017 um 16:13 schrieb Sid Boyce: On 21/04/17 09:13, Andreas Färber wrote: JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Hi Andreas, Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT patches yet. Booting does not mean full-featured! Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. On my home branch, before submitting JeOS, I had verified that also second boot works, thanks to the dracut config added. Regards, Andreas GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 312955 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 set vcck to 1100 mv set vddee to 1050 mv CPU clk: 1536MHz DDR channel setting: DDR0 Rank0+1 same DDR0: 2048MB(auto) @ 912MHz(2T)-13 DataBus test pass! AddrBus test pass! Load fip header from SD, src: 0xc200, des: 0x0140, size: 0x00b0 Load bl30 from SD, src: 0x00010200, des: 0x0100, size: 0x9ef0 Sending bl30OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x0100, size: 0x18c0 Wait bl30...Done Sending bl301...OK. Run bl301... 0, des: 0x1010, size: 0x00011130 --- UART initialized after reboot --- [Reset cause: unknown] [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04] bl30: check_permit, count is 1 bl30: check_permit: ok! chipid: ef be ad de d f0 ad ba ef bLoad bl33 from SD, src: 0x00034200, des: 0x0100, size: 0x00055b50 e ad de not ES chip [0.427617 Inits done] secure task start! high task start! low task start! NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO:BL3-1: Initializing runtime services INFO:BL3-1: Preparing for EL3 exit to normal world INFO:BL3-1: Next image address = 0x100 INFO:BL3-1: Next image spsr = 0x3c9 U-Boot 2017.05-rc2 (Apr 21 2017 - 03:45:10 +) odroid-c2 DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 Using default environment In:serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: eth0: ethernet@c941 Hit any key to stop autoboot: 0 => boot switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 19109 bytes read in 28 ms (666 KiB/s) Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi 731648 bytes read in 37 ms (18.9 MiB/s) ## Starting EFI application at 0108 ... Scanning disk m...@72000.blk... Card did not respond to voltage select! mmc_init: -95, time 10 Found 1 disks Welcome to GRUB! error: terminal `gfxterm' isn't found. error: no suitable video mode found. error: can't find command `terminal'. GNU GRUB version 2.02~rc2 ┌────────────────────────────────────────────────────────────────────────────â”� │ openSUSE [ VMX ] │ │*Failsafe -- openSUSE [ VMX ] │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────────┘ Use the â–² and â–¼ keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. Hi Andreas, I have both the serial console on /dev/ttyUSB0 and HDMI screens connected. The blue LED never flashes on and no message appears on the serial connection. I am using one of the recommended Toshiba SD cards - 64 GB. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Hi Sid, Am 21.04.2017 um 16:13 schrieb Sid Boyce: > On 21/04/17 09:13, Andreas Färber wrote: >> JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, >> instructions at https://en.opensuse.org/HCL:OdroidC2. >> > Hi Andreas, > Burned > openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz > per instructions, does not boot. > Only the red LED lights. It does here. Are you maybe looking at an HDMI screen instead of serial? HDMI drivers will come in 4.12, and currently there are no Odroid-C2 DT patches yet. Booting does not mean full-featured! Also as usual it takes some minutes until Kiwi has repartitioned the card and network is up. On my home branch, before submitting JeOS, I had verified that also second boot works, thanks to the dracut config added. Regards, Andreas GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0; TE: 312955 no sdio debug board detected BL2 Built : 11:44:26, Nov 25 2015. gxb gfb13a3b-c2 - jcao@wonton Board ID = 8 set vcck to 1100 mv set vddee to 1050 mv CPU clk: 1536MHz DDR channel setting: DDR0 Rank0+1 same DDR0: 2048MB(auto) @ 912MHz(2T)-13 DataBus test pass! AddrBus test pass! Load fip header from SD, src: 0xc200, des: 0x0140, size: 0x00b0 Load bl30 from SD, src: 0x00010200, des: 0x0100, size: 0x9ef0 Sending bl30OK. Run bl30... Load bl301 from SD, src: 0x0001c200, des: 0x0100, size: 0x18c0 Wait bl30...Done Sending bl301...OK. Run bl301... 0, des: 0x1010, size: 0x00011130 --- UART initialized after reboot --- [Reset cause: unknown] [Image: unknown, amlogic_v1.1.3046-00db630-dirty 2016-08-31 09:24:14 tao.zeng@droid04] bl30: check_permit, count is 1 bl30: check_permit: ok! chipid: ef be ad de d f0 ad ba ef bLoad bl33 from SD, src: 0x00034200, des: 0x0100, size: 0x00055b50 e ad de not ES chip [0.427617 Inits done] secure task start! high task start! low task start! NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO:BL3-1: Initializing runtime services INFO:BL3-1: Preparing for EL3 exit to normal world INFO:BL3-1: Next image address = 0x100 INFO:BL3-1: Next image spsr = 0x3c9 U-Boot 2017.05-rc2 (Apr 21 2017 - 03:45:10 +) odroid-c2 DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 Using default environment In:serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: eth0: ethernet@c941 Hit any key to stop autoboot: 0 => boot switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 19109 bytes read in 28 ms (666 KiB/s) Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi 731648 bytes read in 37 ms (18.9 MiB/s) ## Starting EFI application at 0108 ... Scanning disk m...@72000.blk... Card did not respond to voltage select! mmc_init: -95, time 10 Found 1 disks Welcome to GRUB! error: terminal `gfxterm' isn't found. error: no suitable video mode found. error: can't find command `terminal'. GNU GRUB version 2.02~rc2 ┌┐ │ openSUSE [ VMX ] │ │*Failsafe -- openSUSE [ VMX ] │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └┘ Use the ▲ and ▼ keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
On 21/04/17 09:13, Andreas Färber wrote: Am 20.04.2017 um 20:57 schrieb Andreas Färber: Am 18.04.2017 um 23:25 schrieb Andreas Färber: Hi Sid, Am 18.04.2017 um 21:35 schrieb Sid Boyce: On 15/04/17 09:48, Andreas Färber wrote: Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel. Am 11.04.2017 um 01:42 schrieb Andreas Färber: == aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Enjoy, Andreas Hi Andreas, Burned openSUSE-Tumbleweed-ARM-JeOS-odroidc2.aarch64-2017.04.21-Build3.1.raw.xz per instructions, does not boot. Only the red LED lights. fsck'd both partitions to make sure they are clean. Results the same. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Am 20.04.2017 um 20:57 schrieb Andreas Färber: > Am 18.04.2017 um 23:25 schrieb Andreas Färber: >> Hi Sid, >> >> Am 18.04.2017 um 21:35 schrieb Sid Boyce: >>> On 15/04/17 09:48, Andreas Färber wrote: Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel. Am 11.04.2017 um 01:42 schrieb Andreas Färber: > == aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) >> [...] >>> Which image boots on the ODROID-C2? JeOS-odroidc2 is now bootable - available from Contrib:OdroidC2, instructions at https://en.opensuse.org/HCL:OdroidC2. Enjoy, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Am 18.04.2017 um 23:25 schrieb Andreas Färber: > Hi Sid, > > Am 18.04.2017 um 21:35 schrieb Sid Boyce: >> On 15/04/17 09:48, Andreas Färber wrote: >>> Amlogic S905 MMC support has just landed in U-Boot last night, allowing >>> to finally migrate my two S905 devices over to our openSUSE kernel. >>> >>> Am 11.04.2017 um 01:42 schrieb Andreas Färber: == aarch64 == >>> Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) > [...] >> Which image boots on the ODROID-C2? > > Short answer: None, I have not created a JeOS image yet. > > Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for > it to hit Factory. [...] > Binary-only ARM Trusted Firmware blobs are needed for booting, that are > unlikely to ever reach Factory. So they would need to live in a Contrib. Packaged as odroidc2-firmware in Contrib:OdroidC2. > Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for > packing the ATF and U-Boot binaries into a bootable form. > My solution for OBS/aarch64 was to piece together an Open Source tool: > https://github.com/afaerber/meson-tools > Currently that still requires the fip tool from downstream Hardkernel > U-Boot (with its alignment magic), which didn't build with gcc5+. Found a workaround: fip_create actually builds fine without U-Boot. Packaged as odroidc2-firmware-tools for Leap 42.2 and Tumbleweed. odroidc2-firmware now builds u-boot.odroidc2 - boots OK when written to SD card as documented in the Wiki below. :) Thanks to everyone who supported the development of meson-tools! In particular a hint on "sha2" functions being used, which lead me to discover the right SHA256 check-sum algorithm, was invaluable. > Cf. https://en.opensuse.org/HCL:OdroidC2 > > So... would it help to create a JeOS image without the bootloader? Only this final part is still missing. > You could then dd the bootloader onto the SD card in a second step. > > The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD. > > I've create a Contrib:OdroidC2, but it's still empty: > https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2 > > Regards, > Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
Am 19.04.2017 um 00:43 schrieb Sid Boyce: > On 18/04/17 22:25, Andreas Färber wrote: >> Am 18.04.2017 um 21:35 schrieb Sid Boyce: >>> On 15/04/17 09:48, Andreas Färber wrote: Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel. Am 11.04.2017 um 01:42 schrieb Andreas Färber: > == aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) >> [...] >>> Which image boots on the ODROID-C2? >> Short answer: None, I have not created a JeOS image yet. >> >> Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for >> it to hit Factory. (https://build.opensuse.org/request/show/487710 is >> still pending for the previous v2017.03...) >> -rc2 still does not include all patches for a convenient boot from SD - >> we could queue some in our package of course. >> >> Binary-only ARM Trusted Firmware blobs are needed for booting, that are >> unlikely to ever reach Factory. So they would need to live in a Contrib. >> >> Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for >> packing the ATF and U-Boot binaries into a bootable form. >> My solution for OBS/aarch64 was to piece together an Open Source tool: >> https://github.com/afaerber/meson-tools >> Currently that still requires the fip tool from downstream Hardkernel >> U-Boot (with its alignment magic), which didn't build with gcc5+. >> >> Cf. https://en.opensuse.org/HCL:OdroidC2 >> >> So... would it help to create a JeOS image without the bootloader? >> You could then dd the bootloader onto the SD card in a second step. >> >> The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD. >> >> I've create a Contrib:OdroidC2, but it's still empty: >> https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2 > > Thanks Andreas, > > Looks like much work is left to do. My meson-tools are packaged in Contrib:OdroidC2 now, and I've applied a patch to u-boot-odroid-c2 in Base:System:Staging. The Wiki page above has been updated with how to build the bootloader from the Hardkernel blobs and our U-Boot package with my tool. Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Odroid-C2
On 18/04/17 22:25, Andreas Färber wrote: Hi Sid, Am 18.04.2017 um 21:35 schrieb Sid Boyce: On 15/04/17 09:48, Andreas Färber wrote: Amlogic S905 MMC support has just landed in U-Boot last night, allowing to finally migrate my two S905 devices over to our openSUSE kernel. Am 11.04.2017 um 01:42 schrieb Andreas Färber: == aarch64 == Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] Which image boots on the ODROID-C2? Short answer: None, I have not created a JeOS image yet. Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for it to hit Factory. (https://build.opensuse.org/request/show/487710 is still pending for the previous v2017.03...) -rc2 still does not include all patches for a convenient boot from SD - we could queue some in our package of course. Binary-only ARM Trusted Firmware blobs are needed for booting, that are unlikely to ever reach Factory. So they would need to live in a Contrib. Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for packing the ATF and U-Boot binaries into a bootable form. My solution for OBS/aarch64 was to piece together an Open Source tool: https://github.com/afaerber/meson-tools Currently that still requires the fip tool from downstream Hardkernel U-Boot (with its alignment magic), which didn't build with gcc5+. Cf. https://en.opensuse.org/HCL:OdroidC2 So... would it help to create a JeOS image without the bootloader? You could then dd the bootloader onto the SD card in a second step. The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD. I've create a Contrib:OdroidC2, but it's still empty: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2 Regards, Andreas Thanks Andreas, Looks like much work is left to do. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Odroid-C2 (was: Kernel 4.11-rc6 testing status)
Hi Sid, Am 18.04.2017 um 21:35 schrieb Sid Boyce: > On 15/04/17 09:48, Andreas Färber wrote: >> Amlogic S905 MMC support has just landed in U-Boot last night, allowing >> to finally migrate my two S905 devices over to our openSUSE kernel. >> >> Am 11.04.2017 um 01:42 schrieb Andreas Färber: >>> == aarch64 == >> Odroid-C2 - boots OK (add fixed, gpio-regulator modules to dracut) [...] > Which image boots on the ODROID-C2? Short answer: None, I have not created a JeOS image yet. Just today was U-Boot v2017.05-rc2 packaged, and it'll take a while for it to hit Factory. (https://build.opensuse.org/request/show/487710 is still pending for the previous v2017.03...) -rc2 still does not include all patches for a convenient boot from SD - we could queue some in our package of course. Binary-only ARM Trusted Firmware blobs are needed for booting, that are unlikely to ever reach Factory. So they would need to live in a Contrib. Next problem was that Hardkernel uses a binary-only x86 Amlogic tool for packing the ATF and U-Boot binaries into a bootable form. My solution for OBS/aarch64 was to piece together an Open Source tool: https://github.com/afaerber/meson-tools Currently that still requires the fip tool from downstream Hardkernel U-Boot (with its alignment magic), which didn't build with gcc5+. Cf. https://en.opensuse.org/HCL:OdroidC2 So... would it help to create a JeOS image without the bootloader? You could then dd the bootloader onto the SD card in a second step. The Factory 4.10 kernel booted okay, so no dependency on Kernel:HEAD. I've create a Contrib:OdroidC2, but it's still empty: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:OdroidC2 Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
