CoreELEC Troubleshooting

This section provides some basic troublshooting assistance.


Before posting an error

CoreELEC can be installed & booted from USB Flash Drive or SD Card for troubleshooting purposes.

  1. Make a full backup
  2. Power the device off, and leave the power unplugged for at least 30 seconds
  3. Ensure the correct device tree was applied to CoreELEC
    1. Ensure the correct update file was applied to CoreELEC
  4. Try a clean install (using the correct img.gz / dtb.img file for the device) and restore addons and settings from backup
    1. Try a clean install (using the correct img.gz / dtb.img file for the device) and then manually re-install the offending addon
  5. Try a different (class 10) SD card / USB Flash Drive
    1. Try a new (class 10) SD / USB Flash Drive

If the issue is not resolved by one or all of the steps above, proceed with this guide to retrieve a debug log of the system


Enable debug logging

  • select Settings

  • select System

  • ensure user mode is set to Standard
  • enable debug logging

  • reboot device
  • reproduce issue

Upload log

After debug logging is enabled:

  • select Settings

  • select CoreELEC

  • select System
  • select Upload latest …

This will generate a URL with debug information from the device.

CAUTION: the URL is cAsE sEnSiTiVe


Alternate methods for obtaining logs

Sometimes debug information has to be obtained in different ways.

dmesg

  • SSH into device
  • enter:

dmesg | paste

This will generate a URL that can be used in the support forums.

Ramoops Panic Logger

CoreELEC has the ramoops driver enabled by default, allowing the kernel to store kernel oopses, kernel console output, and user messages in a reserved memory region inside the devices RAM.

In normal hardware designs RAM will remain powered on during a reboot, making the data retrievable from RAM.

Prior to using ramoops a folder has to be created.

  • enter:
mkdir /media/ramoops

Ramoops is ready for use now.

  • To create a ramoops log after a reboot enter:
cat /sys/fs/pstore/console-ramoops-0 | paste

This will generate a URL that can be used in the support forums.


Extracting a Device Tree

A device tree can be extracted in 2 different ways:

1. CoreELEC booted from external media

  • SSH into CoreELEC and type:
dd if=/dev/dtb | gzip > /storage/backup/dtb.img.gz

The dtb should reside in the CoreELEC backup folder.

NOTE: This also works for dual boot CoreELEC/Android installations.

2. Android booted from eMMc

  • open a Terminal to acces Android's built-in Linux command line shell and enter:
dd if=/dev/dtb | gzip > /storage/emulated/0/Download/dtb.img.gz

The dtb should reside in the Android download folder.

  • use a USB Flash Drive tranfer transfer the file

SDIO Debug Board

Team CoreELEC has developed a universal Amlogic SDIO debug board.

The SDIO debug board will give easy access to the UART interface without needing to open or modify anything on the device.

Information on how to obtain a board can be found here.