I am currently trying to debug a "black screen" on a Raspberry Pi. The Pi is plugged to an in-house PCB using connector of the Pi and the LCD screen is connected on this in-house board.

The Linux distro was built with Yocto.

Now, sometimes though not often, the boot process is stopped after a reboot command scheduled by the embedded application running on the platform.

It seems that the boot process is stucked somewhere before loading the kernel into the RAM or at least before the logs are printed.

Now as far as I know there are 3 steps in the early boot phase of the Pi:

  1. videocore
  2. bootcode.bin
  3. start.elf

My questions are :

  • How to have debug log during those 3 steps?
  • As there is no screen directly connected to the Pi,would it be possible to have these logs store in a regular file on the SD Card?

on raspbian, you can access logs by typing dmesg, or dmesg>file to save the logs to a file, you can also look in /var/log, especially /var/log/syslog.

not sure if this will work on your os, hopefuly it does!

also, I think to get more logs on at startup you can install bootlogd with

apt-get install bootlogd

then look in /var/log

  • 1
    The question is more about debug logs before the kernel is actually loaded into the RAM. – user81908 Mar 7 '18 at 8:37
  • I was wondering about that... – scitronboy Mar 7 '18 at 23:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy