chewitt if I use that test image you provided, will I be able to upgrade to the next release? Will the next release (12.0.2?) contain this patch?
It is also very strange that not everyone has this problem. I wonder if there is a board revision that has the issue?
Yeah, it is pretty strange. So I have the UART wiring harness connected to GND, RXD, and TXD, and then the wiring harness plugged into the USB dongle. And the dongle is just sitting on top of my C2, not plugged into a computer. In this state it will boot. But if I disconnect the wiring harness from the UART port on the C2, it sits there with a red light and does not boot.
It is almost like it needs to see some kind of connection on one of those terminals to boot. I hope chewitt is able to take a look at this and have an idea as to what might be going on.
chewitt I am coming back to this now. Can I get one of those test images to try?
I am currently writing a 12.0.1 image to my microSD card to test. Will report here if it works.
So actually the 12.0.1 image seems to be working for me. I do get some screen flicker, but will see how it goes over the next couple of days.
I spoke too soon. I think the only reason it was working was because I still had the UART adapter connected (but not plugged into my PC). Very odd. I am going to connect it again and see what happens...
I might try a slower micro-SD card as was suggested. I will also ask in the Odroid forums.
Ok, so I finally got my UART-to-USB adapter working and got output:
GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
TE: 233144
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: 0x0000c200, des: 0x01400000, size: 0x000000b0
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x00009ef0
Sending bl30........................................OK.
Run bl30...
Load bl301 from SD, src: 0x0001c200, des: 0x01000000, size: 0x000018c0
Wait bl30...Done
Sending bl301.......OK.
Run bl301...
0x00020200, des: 0x10100000, 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 be Load bl33 from SD, src: 0x00034200, des: 0x01000000, size: 0x0009cd60
ad de not ES chip
[0.349068 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 = 0x1000000
INFO: BL3-1: Next image spsr = 0x3c9
<debug_uart>
U-Boot 2024.04 (May 19 2024 - 05:24:21 +0000) odroid-c2
Model: Hardkernel ODROID-C2
SoC: Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM: 2 GiB
Core: 170 devices, 29 uclasses, devicetree: separate
MMC: mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In: usbkbd,serial
Out: serial
Err: serial
Net: eth0: ethernet@c9410000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1: LibreELEC
Retrieving file: /KERNEL
append: boot=LABEL=LIBREELEC disk=LABEL=STORAGE ssh quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0
Retrieving file: /amlogic/meson-gxbb-odroidc2.dtb
## Booting kernel from Legacy Image at 08080000 ...
Image Name:
Image Type: AArch64 Linux Kernel Image (lzo compressed)
Data Size: 12741308 Bytes = 12.2 MiB
Load Address: 01d80000
Entry Point: 01d80000
Verifying Checksum ... OK
## Flattened Device Tree blob at 08008000
Booting using the fdt blob at 0x8008000
Working FDT set to 8008000
Uncompressing Kernel Image to 1d80000
Moving Image from 0x1d80000 to 0x1e00000, end=3e00000
Loading Device Tree to 000000007bf48000, end 000000007bf5488d ... OK
Working FDT set to 7bf48000
Starting kernel ...
LibreELEC:/ #Here is the strange thing, it looks like it booted... Argh. I am going to connect a keyboard and mouse and see if it still works.
So, if I do not have the UART cable plugged in, it doesn't boot. If I plug the cable in after a while, I don't get any new output.
If I plug in the UART, then plug in power, it boots fine and I get UART output. Any ideas?
smf007 any suggestions on which SD card to get?
Thanks twerty, I removed the jumper and put LE12 back on the micro-SD card. Same behavior as before.
Thanks chewitt. Looks like you saw my other post. The really strange thing is that LibreELEC-Odroid_C2.arm-9.0.2.img.gz from the download page, and CoreELEC-Amlogic.arm-9.2.8-Odroid_C2.img.gz both write and boot fine.
I just tried un-plugging ethernet, HDMI, and my USB keyboard and mouse, then powered on. Same behavior as before. Red light is on, but nothing else seems to be happening. I also plugged the ethernet cable in, and doesn't seem to be connecting to network.
I am going to investigate getting the UART output. Let me know if there are any helpful resources.
Is it possibly related to using a micro-SD card instead of emmc? I have seen some threads indicating that was a problem, but I am not sure. I don't have emmc on my unit, and had previously used the micro-SD card to boot and run before. Would I need to add an emmc module, write the image there, and try again? At that point, I might just upgrade to a newer unit...
Also wanted to note, I have the dedicated power adapter, the one with the small pin looking connector. I am NOT using a micro-USB cable to power the unit.
The file I copied over was gxbb_p200_2G_1Gbit.dtb.
What if I install 9.0.2 on the SD card (which I know works), can I put the 9.2.8.14.img file in the update directory and let it auto-upgrade?
I am trying to get latest image (LibreELEC-Generic_S905.arm-9.2.8.14.img.gz) to work on my ODroid C2. I write the image, copy the 2gb/gigabit DTB file over /dtb.img, plug in the micro-SD and power on. The red light comes on and the network lights start to blink, but the screen doesn't come on and the machine is not reachable via network (I added a static host for the MAC).
Anything I can try? Should I try the DTB file from the 9.0.2 image?
So my /extlinux/extlinux.conf file looks like this:
LABEL LibreELEC
LINUX /KERNEL
FDT /amlogic/meson-gxbb-odroidc2.dtb
APPEND boot=LABEL=LIBREELEC disk=LABEL=STORAGE ssh quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0 video=HDMI-A-1:1920x1080M@60I plugged it in. Blue light never comes on. Network lights come on after a few seconds. Mainly orange one, but orange and green will come on periodically. No output to display.
I think I am going to have to put 9.0.2 back on it so I can get the MAC and then look for the MAC in my DHCP leases because I don't see the device show up in my DHCP leases.
I will also try plugging it into a TV instead of a monitor to see what happens.
I feel like I have to be missing a step. Do I simply use the LibreELEV SD creator, select the img.gz file, write to the micro-SD, then put into the device and boot? Or do I need to make changes after I have written the image?
Ok. So, I used the 8gb micro-sd card that I was running on before, and flashed it with the link you provided above. I used balenaEtcher to write it this time instead of the LibreELEC creator app.
I have an SD to micro-SD interface and then a USB to SD device. I have used this in the past, including this morning to write a pfSense image to another micro-SD card that booted fine on my router/firewall (upgrading to 2.7.2, but that's another story).
When I put the card in the reader, I can see 2 partitions:
I am also able to view the LIBREELEC partition and can open files:
Same behavior as before. I plug power in, the red light turns on, no blue light, and after a few seconds the network jack lights start to blink.
To make sure I wasn't crazy, I also wrote the 9.0.2 image from libreelec.tv to the same micro-SD card. This is the version that was on the card before and was running.
I put the card in my ODroid C2, red light comes on, blue light blinks, monitor wakes up.
I would really like to get a newer version of Kodi running as some of my apps had stopped working. Any ideas of what next steps I can take?
It might be 9.0.2 on the other SD card, I don't recall exactly.
Is there a link to a guide for obtaining UART logs?
How can I tell the difference? I went here: https://libreelec.tv/downloads/amlogic/
And downloaded LibreELEC-AMLGX.aarch64-12.0.0-odroid-c2.img.gz and LibreELEC-AMLGX.arm-11.0.6-odroid-c2.img.gz. Both showed the same problem. I suspect I am missing the "upstream u-boot". How do I get the image that includes that?
Let me ask this, if I have a working SD card with a 9.2 image on it, can I just put one of those img files in the update directory and reboot? Or is there a better way?
I have written the 12.0.0 image and 11.0.6 image to a micro-SD card and put into my box. When I plug in the power cord, the red light comes on, but blue light never comes on and screen never comes on. It seems like this has been reported a few other times. Any suggestions here other than getting UART logs?