search

raspberrypi / firmware

This repository contains pre-compiled binaries of the current Raspberry Pi kernel and modules, userspace libraries, and bootloader/GPU firmware.
5.18k stars 1.68k forks source link

Unable to Boot RPI 3B from USB #1033

Open blacktek opened 6 years ago

blacktek commented 6 years ago

Hi, I'm trying (with no success) to let my raspberry pi 3 Model B boot from an external usb SSD device (a SanDisk SDSSDA-120G).

Device info:

Raspbian GNU/Linux 8 (jessie) Linux raspi 4.14.67-v7+ #1139 SMP Wed Aug 29 15:17:05 BST 2018 armv7l GNU/Linux

pi@raspi:~ $ vcgencmd version Aug 29 2018 14:52:07

I followed many tutorials, forums and videos, but this easy thing seems to not work for me. I've no other USB devices attached to the raspberry (except the SSD)

First thing I did was to flash the SSD disk with a brand new Raspbian Lite. The SSD disk is seen by the raspberry after I attach it:

pi@raspi:~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sde 8:64 0 111.8G 0 disk ├─sde2 8:66 0 1.7G 0 part └─sde1 8:65 0 43.2M 0 part mmcblk0 179:0 0 14.9G 0 disk ├─mmcblk0p2 179:2 0 1K 0 part ├─mmcblk0p7 179:7 0 13.7G 0 part / ├─mmcblk0p5 179:5 0 32M 0 part ├─mmcblk0p1 179:1 0 1.1G 0 part └─mmcblk0p6 179:6 0 63M 0 part /boot

1) echo program_usb_boot_mode=1 | sudo tee -a /boot/config.txt

2) before reboot I had: pi@raspi:~ $ vcgencmd otp_dump | grep 17: 17:1020000a

3) after reboot I had: pi@raspi:~ $ vcgencmd otp_dump | grep 17: 17:3020000a

After the reboot I removed “program_usb_boot_mode=1“ from /boot/config.txt and than rebooted again, but the raspi didn't reboot from USB device attached

4) I removed the SD card and than I powered up the device, but nothing was happening, just the red led staying red and nothing else.

5) I tried to create an SD card (formatted as FAT32) with just bootcode.img (https://github.com/raspberrypi/firmware/raw/master/boot/bootcode.bin) copied on it, but no success. I tried to both put this file in the root directory and in the /boot/ directory. When booting the raspberry with this sd card inside I was seeing the green led flashing 4 times. And in some cases the rainbow screen (and nothing else) Anyway most of tutorials reported that SD card was not needed to boot from external device.

6) I tried to use my working SD card and add rootdelay=5 in the boot settings (/boot/cmdline.txt), but no luck here too.

7) I tried to add "program_usb_boot_timeout=1” in /boot/config.txt and then rebooted again the raspi with the sd card inside, but still no luck. After I shutted down the pi, removed the sd card and tried to boot again, but still no luck (just red led on, and green led off)

pi@raspi:~ $ vcgencmd otp_dump | grep 66 66:01009daa

(so bit 24 seems to be set properly)

I've no more guns, can you help?

Thank you

blacktek commented 6 years ago

forgetting to say that the SanDisk SSD disk is connected to the RPI with a Sabrent (EC-SSHD) SSD/SATA to USB converter

blacktek commented 6 years ago

If I copy https://github.com/raspberrypi/firmware/raw/next/boot/bootcode.bin in a formatted FAT32 SD card (copied both in / and in /boot/) I see the green led blinking 7 times (should means missing kernel.img)

Ve2mrx commented 5 years ago

To make my Kingston SSD work with it's provided external enclosure, I had to format an SD card in FAT, NOT FAT32 and copy the whole BOOT on it.

Not just the bootcode.bin, but the whole BOOT partition files. Boots nicely now, but the BOOT partition files on your SSD is no longer used. That means that if you edit config.txt, cmdline.txt ot other BOOT files, you would have to edit those on the SD instead of the SSD. They are NOT mounted under /boot.

Also, you should use the files from your current Raspbian installation. Since the Blog post of 2016, they have been updated with the required boot code . The GitHub files may have bugs you don't need now. So, again, take the BOOT files from the latest Raspbian installation.

Martin

ghollingworth commented 5 years ago

It should work fine with just bootcode.bin if not, then it's likely you need the extended timeout (because your SSD takes a long time to initialise). You should be able to enable UART debug output and get log messages which would tell you what the problem was.

blacktek commented 5 years ago

I would avoid using the BOOT in the external SD card because I see it like a dirty solution to just go around the problem without really solving it. Moreover this solution is worse to maintain, manage and backup :/

Could you please provide instructions on how to do UART debug? Sometimes my raspi hangs before the rainbow screen and sometims after. It never hangs after a cold boot, it randomly hangs only after reboots.

I've tried with 2 SSDs (SanDisk SDSSDA-120G and now a crucial MX500) and with 3 sata controllers. I've updated/upgraded the system to latest version of raspbian Stretch. I don't use NOOBS (as some people said it could cause problems with boot)

no more guns to shot :(

tnx

pelwell commented 5 years ago

To enable UART debugging of the boot process, follow this guide: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/

blacktek commented 5 years ago

thank you (I read it); could you please provide a link to an usb serial cable I could buy on amazon?

could this https://www.amazon.it/DSD-TECH-Convertitore-seriale-Compatibile/dp/B072K3Z3TL/ work?

blacktek commented 5 years ago

or better this https://www.amazon.it/Sumind-Raspberry-Programmazione-Seriale-Supported/dp/B01N4X3BJB/ ?

pelwell commented 5 years ago

I can't guarantee anything, but the second link even mentions Raspberry Pi so I'm reasonably certain it will work.

blacktek commented 5 years ago

ok, ordered; I should receive it tomorrow. One question: at every reboot I should restablish the serial connection or I should open it just one time? should I do something on my host computer (windows) after issuing the reboot command on the raspi?

pelwell commented 5 years ago

You can leave the terminal window open on the host computer - it will survive unplugging from and rebooting of the Pi. My terminal app is often open for weeks at a time, during which time it will be connected to many different Pis.

blacktek commented 5 years ago

thank you. I'll update you tomorrow :)

blacktek commented 5 years ago

Hello, UART debug started. First boot worked properly and I read:

Raspberry Pi Bootcode

USB MSD boot Read File: config.txt, 1685 (bytes)

Raspberry Pi Bootcode Read File: config.txt, 1685 Read File: start.elf, 2857060 (bytes) Read File: fixup.dat, 6666 (bytes) MESS:00:00:16.838451:0: brfs: File read: /mfs/sd/config.txt MESS:00:00:16.843203:0: brfs: File read: 1685 bytes MESS:00:00:17.289041:0: HDMI:EDID version 1.3, 1 extensions, screen size 41x26 cm MESS:00:00:17.294869:0: HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF MESS:00:00:17.312683:0: HDMI:EDID found preferred DMT detail timing format: 1440x900p @ 60 Hz (47) MESS:00:00:17.321322:0: HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II [...]

Then I issued a reboot and things stopped here:

Raspberry Pi Bootcode

USB MSD boot Read File: config.txt, 1685 (bytes)

Raspberry Pi Bootcode Read File: config.txt, 1685 Read File: start.elf, 2857060 (bytes)

So never did "Read File: fixup.dat, 6666 (bytes)"

What can we say?

blacktek commented 5 years ago

2-3 other times stopped there. another time stopped here:

MESS:00:00:19.024008:0: *** Restart logging MESS:00:00:19.026498:0: brfs: File read: 1685 bytes MESS:00:00:19.886866:0: brfs: File read: /mfs/sd/cmdline.txt MESS:00:00:19.890864:0: Read command line from file 'cmdline.txt': MESS:00:00:19.896733:0: 'dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=43be32d2-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait rootdelay=5' MESS:00:00:19.912682:0: brfs: File read: 154 bytes MESS:00:00:53.477020:0: No kernel trailer - assuming DT-capable MESS:00:00:54.493675:0: Failed to load Device Tree file '?' MESS:00:00:54.498057:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:59.307475:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:04.116061:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:08.924643:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:13.733240:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:18.541828:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:23.350418:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:28.159004:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:32.967617:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:37.776198:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:42.584790:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:47.393369:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:52.201965:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:01:57.010547:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined

ideas?

pelwell commented 5 years ago

Have you installed the latest rpi-update firmware, including bootcode.bin? It contains a few fixes that might be relevant.

blacktek commented 5 years ago

somebody said to not do "rpi-update" because this way I would install latest beta firmwares (less tested) too. Is it wrong? should I do rpi-update?

pelwell commented 5 years ago

We certainly wouldn't advise everybody to rpi-update - in general, "sudo apt-get upgrade" or "sudo apt-get distupgrade" is safer - but in this case you have been asked to do so by a Raspberry Pi employee. I'm not aware of any new problems in the current firmware, so I believe it is safe to update.

blacktek commented 5 years ago

rpi-update done; after apt-get update and apt-get upgrade. Still no luck.

in one of the reboots the raspi hanged before any output to console too.

At next hard reboot I had this:

Raspberry Pi Bootcode

USB MSD boot Read File: config.txt, 1685 (bytes)

Raspberry Pi Bootcode Read File: config.txt, 1685 Read File: start.elf, 2869092 (bytes) Read File: fixup.dat, 6695 (bytes) MESS:00:00:16.850579:0: brfs: File read: /mfs/sd/config.txt MESS:00:00:16.855347:0: brfs: File read: 1685 bytes MESS:00:00:17.301913:0: HDMI:EDID version 1.3, 1 extensions, screen size 41x26 cm MESS:00:00:17.307741:0: HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF MESS:00:00:17.325553:0: HDMI:EDID found preferred DMT detail timing format: 1440x900p @ 60 Hz (47) MESS:00:00:17.334194:0: HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II MESS:00:00:17.343304:0: HDMI:EDID found DMT format: code 5, 640x480p @ 72 Hz in established timing I/II MESS:00:00:17.352419:0: HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II MESS:00:00:17.361533:0: HDMI:EDID found DMT format: code 8, 800x600p @ 56 Hz in established timing I/II MESS:00:00:17.370648:0: HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II MESS:00:00:17.379763:0: HDMI:EDID found DMT format: code 10, 800x600p @ 72 Hz in established timing I/II MESS:00:00:17.388964:0: HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II MESS:00:00:17.398167:0: HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II MESS:00:00:17.407454:0: HDMI:EDID found DMT format: code 17, 1024x768p @ 70 Hz in established timing I/II MESS:00:00:17.416742:0: HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II MESS:00:00:17.426033:0: HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II MESS:00:00:17.435453:0: HDMI:EDID standard timings block x 8: 0x950F 8180 8140 714F 8100 0101 0101 0101 MESS:00:00:17.444621:0: HDMI:EDID found DMT format: code 48, 1440x900p @ 75 Hz (16:10) in standard timing 0 MESS:00:00:17.454081:0: HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 1 MESS:00:00:17.463455:0: HDMI:EDID found DMT format: code 32, 1280x960p @ 60 Hz (4:3) in standard timing 2 MESS:00:00:17.472743:0: HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 3 MESS:00:00:17.482032:0: HDMI:EDID found DMT format: code 28, 1280x800p @ 60 Hz (16:10) in standard timing 4 MESS:00:00:17.504453:0: HDMI:EDID parsing v1 CEA extension MESS:00:00:17.508257:0: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4) MESS:00:00:17.515986:0: HDMI:EDID found CEA detail timing format: 1280x720p @ 50 Hz (19) MESS:00:00:17.523798:0: HDMI:EDID found CEA detail timing format: 720x576p @ 50 Hz (17) MESS:00:00:17.531521:0: HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2) MESS:00:00:17.539153:0: HDMI:EDID moving support for CEA mode 4 to DMT mode 85 because sink does not support HDMI MESS:00:00:17.549137:0: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023 MESS:00:00:17.558141:0: HDMI:EDID preferred mode remained as DMT (47) 1440x900p @ 60 Hz with pixel clock 106 MHz MESS:00:00:18.448794:0: brfs: File read: /mfs/sd/config.txt MESS:00:00:18.453424:0: HDMI:Setting property pixel encoding to Default MESS:00:00:18.459008:0: HDMI:Setting property pixel clock type to PAL MESS:00:00:18.465171:0: HDMI:Setting property content type flag to No data MESS:00:00:18.471769:0: HDMI:Setting property fuzzy format match to enabled MESS:00:00:18.478548:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:18.680878:0: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined MESS:00:00:18.688319:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:18.694324:0: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<< MESS:00:00:18.713806:0: hdmi: HDMI:EDID version 1.3, 1 extensions, screen size 41x26 cm MESS:00:00:18.720163:0: hdmi: HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF MESS:00:00:18.738500:0: hdmi: HDMI:EDID found preferred DMT detail timing format: 1440x900p @ 60 Hz (47) MESS:00:00:18.747656:0: hdmi: HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II MESS:00:00:18.757289:0: hdmi: HDMI:EDID found DMT format: code 5, 640x480p @ 72 Hz in established timing I/II MESS:00:00:18.766924:0: hdmi: HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II MESS:00:00:18.776560:0: hdmi: HDMI:EDID found DMT format: code 8, 800x600p @ 56 Hz in established timing I/II MESS:00:00:18.786195:0: hdmi: HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II MESS:00:00:18.795831:0: hdmi: HDMI:EDID found DMT format: code 10, 800x600p @ 72 Hz in established timing I/II MESS:00:00:18.805553:0: hdmi: HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II MESS:00:00:18.815277:0: hdmi: HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II MESS:00:00:18.825084:0: hdmi: HDMI:EDID found DMT format: code 17, 1024x768p @ 70 Hz in established timing I/II MESS:00:00:18.834894:0: hdmi: HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II MESS:00:00:18.844705:0: hdmi: HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II MESS:00:00:18.854646:0: hdmi: HDMI:EDID standard timings block x 8: 0x950F 8180 8140 714F 8100 0101 0101 0101 MESS:00:00:18.864336:0: hdmi: HDMI:EDID found DMT format: code 48, 1440x900p @ 75 Hz (16:10) in standard timing 0 MESS:00:00:18.874316:0: hdmi: HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 1 MESS:00:00:18.884211:0: hdmi: HDMI:EDID found DMT format: code 32, 1280x960p @ 60 Hz (4:3) in standard timing 2 MESS:00:00:18.894019:0: hdmi: HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 3 MESS:00:00:18.903829:0: hdmi: HDMI:EDID found DMT format: code 28, 1280x800p @ 60 Hz (16:10) in standard timing 4 MESS:00:00:18.926770:0: hdmi: HDMI:EDID parsing v1 CEA extension MESS:00:00:18.931103:0: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4) MESS:00:00:18.939353:0: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 50 Hz (19) MESS:00:00:18.947685:0: hdmi: HDMI:EDID found CEA detail timing format: 720x576p @ 50 Hz (17) MESS:00:00:18.955929:0: hdmi: HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2) MESS:00:00:18.964082:0: hdmi: HDMI:EDID moving support for CEA mode 4 to DMT mode 85 because sink does not support HDMI MESS:00:00:18.974587:0: hdmi: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023 MESS:00:00:18.984113:0: hdmi: HDMI:EDID preferred mode remained as DMT (47) 1440x900p @ 60 Hz with pixel clock 106 MHz MESS:00:00:18.994358:0: hdmi: HDMI: hotplug attached with DVI support MESS:00:00:19.000539:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead MESS:00:00:19.011672:0: hdmi: HDMI: power_on to DMT mode 1440x900@60 MESS:00:00:19.019479:0: hdmi: HDMI: Action callback added to queue to happen at frame 0 MESS:00:00:19.036338:0: *** Restart logging MESS:00:00:19.038828:0: brfs: File read: 1685 bytes MESS:00:00:19.898990:0: brfs: File read: /mfs/sd/cmdline.txt MESS:00:00:19.902989:0: Read command line from file 'cmdline.txt': MESS:00:00:19.908858:0: 'dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=43be32d2-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait rootdelay=5' MESS:00:00:19.924817:0: brfs: File read: 154 bytes MESS:00:00:28.410284:0: brfs: File read: /mfs/sd/kernel7.img MESS:00:00:28.414243:0: Loading 'kernel7.img' to 0x8000 size 0x4b6950 MESS:00:00:28.424740:0: No kernel trailer - assuming DT-capable MESS:00:00:28.428986:0: brfs: File read: 4942160 bytes MESS:00:00:28.971100:0: brfs: File read: /mfs/sd/bcm2710-rpi-3-b.dtb MESS:00:00:28.975757:0: Loading 'bcm2710-rpi-3-b.dtb' to 0x4be950 size 0x62df MESS:00:00:29.122897:0: brfs: File read: 25311 bytes MESS:00:00:29.585431:0: brfs: File read: /mfs/sd/config.txt MESS:00:00:29.589873:0: dtparam: audio=on MESS:00:00:29.612091:0: brfs: File read: 1685 bytes MESS:00:00:30.469550:0: brfs: File read: /mfs/sd/overlays/w1-gpio.dtbo MESS:00:00:30.483050:0: Loaded overlay 'w1-gpio' MESS:00:00:31.694948:0: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined MESS:00:00:31.816814:0: Device tree loaded to 0x2eff9700 (size 0x6806) MESS:00:00:31.822873:0: uart: Set PL011 baud rate to 103448.300000 Hz MESS:00:00:31.829354:0: uart: Baud rate change done... MESS:00:00:31.832786:0: uart: Baud rate change done... MESS:00:00:34.470662:0: vchiq_core: vchiq_init_state: slot_zero = 0xfad80000, is_master = 1 MESS:00:00:34.481956:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead MESS:00:00:34.494813:0: TV service:host side not connected, dropping notification 0x00000002, 0x00000002, 0x0000002f

Raspberry Pi Bootcode

USB MSD boot Read File: config.txt, 1685 (bytes)

Raspberry Pi Bootcode Read File: config.txt, 1685 Read File: start.elf, 2869092 (bytes) Read File: fixup.dat, 6695 (bytes) MESS:00:00:16.850706:0: brfs: File read: /mfs/sd/config.txt MESS:00:00:16.855473:0: brfs: File read: 1685 bytes MESS:00:00:17.302039:0: HDMI:EDID version 1.3, 1 extensions, screen size 41x26 cm MESS:00:00:17.307868:0: HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF MESS:00:00:17.325680:0: HDMI:EDID found preferred DMT detail timing format: 1440x900p @ 60 Hz (47) MESS:00:00:17.334320:0: HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II MESS:00:00:17.343431:0: HDMI:EDID found DMT format: code 5, 640x480p @ 72 Hz in established timing I/II MESS:00:00:17.352545:0: HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II MESS:00:00:17.361660:0: HDMI:EDID found DMT format: code 8, 800x600p @ 56 Hz in established timing I/II MESS:00:00:17.370774:0: HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II MESS:00:00:17.379890:0: HDMI:EDID found DMT format: code 10, 800x600p @ 72 Hz in established timing I/II MESS:00:00:17.389091:0: HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II MESS:00:00:17.398294:0: HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II MESS:00:00:17.407581:0: HDMI:EDID found DMT format: code 17, 1024x768p @ 70 Hz in established timing I/II MESS:00:00:17.416869:0: HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II MESS:00:00:17.426160:0: HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II MESS:00:00:17.435579:0: HDMI:EDID standard timings block x 8: 0x950F 8180 8140 714F 8100 0101 0101 0101 MESS:00:00:17.444748:0: HDMI:EDID found DMT format: code 48, 1440x900p @ 75 Hz (16:10) in standard timing 0 MESS:00:00:17.454208:0: HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 1 MESS:00:00:17.463582:0: HDMI:EDID found DMT format: code 32, 1280x960p @ 60 Hz (4:3) in standard timing 2 MESS:00:00:17.472869:0: HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 3 MESS:00:00:17.482158:0: HDMI:EDID found DMT format: code 28, 1280x800p @ 60 Hz (16:10) in standard timing 4 MESS:00:00:17.504580:0: HDMI:EDID parsing v1 CEA extension MESS:00:00:17.508385:0: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4) MESS:00:00:17.516113:0: HDMI:EDID found CEA detail timing format: 1280x720p @ 50 Hz (19) MESS:00:00:17.523925:0: HDMI:EDID found CEA detail timing format: 720x576p @ 50 Hz (17) MESS:00:00:17.531649:0: HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2) MESS:00:00:17.539280:0: HDMI:EDID moving support for CEA mode 4 to DMT mode 85 because sink does not support HDMI MESS:00:00:17.549265:0: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023 MESS:00:00:17.558269:0: HDMI:EDID preferred mode remained as DMT (47) 1440x900p @ 60 Hz with pixel clock 106 MHz MESS:00:00:18.448920:0: brfs: File read: /mfs/sd/config.txt MESS:00:00:18.453552:0: HDMI:Setting property pixel encoding to Default MESS:00:00:18.459135:0: HDMI:Setting property pixel clock type to PAL MESS:00:00:18.465298:0: HDMI:Setting property content type flag to No data MESS:00:00:18.471896:0: HDMI:Setting property fuzzy format match to enabled MESS:00:00:18.478674:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:18.681021:0: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined MESS:00:00:18.688463:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:18.694468:0: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<< MESS:00:00:18.713950:0: hdmi: HDMI:EDID version 1.3, 1 extensions, screen size 41x26 cm MESS:00:00:18.720307:0: hdmi: HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF MESS:00:00:18.738644:0: hdmi: HDMI:EDID found preferred DMT detail timing format: 1440x900p @ 60 Hz (47) MESS:00:00:18.747800:0: hdmi: HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II MESS:00:00:18.757433:0: hdmi: HDMI:EDID found DMT format: code 5, 640x480p @ 72 Hz in established timing I/II MESS:00:00:18.767068:0: hdmi: HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II MESS:00:00:18.776704:0: hdmi: HDMI:EDID found DMT format: code 8, 800x600p @ 56 Hz in established timing I/II MESS:00:00:18.786339:0: hdmi: HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II MESS:00:00:18.795975:0: hdmi: HDMI:EDID found DMT format: code 10, 800x600p @ 72 Hz in established timing I/II MESS:00:00:18.805697:0: hdmi: HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II MESS:00:00:18.815421:0: hdmi: HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II MESS:00:00:18.825228:0: hdmi: HDMI:EDID found DMT format: code 17, 1024x768p @ 70 Hz in established timing I/II MESS:00:00:18.835038:0: hdmi: HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II MESS:00:00:18.844850:0: hdmi: HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II MESS:00:00:18.854790:0: hdmi: HDMI:EDID standard timings block x 8: 0x950F 8180 8140 714F 8100 0101 0101 0101 MESS:00:00:18.864480:0: hdmi: HDMI:EDID found DMT format: code 48, 1440x900p @ 75 Hz (16:10) in standard timing 0 MESS:00:00:18.874460:0: hdmi: HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 1 MESS:00:00:18.884355:0: hdmi: HDMI:EDID found DMT format: code 32, 1280x960p @ 60 Hz (4:3) in standard timing 2 MESS:00:00:18.894163:0: hdmi: HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 3 MESS:00:00:18.903973:0: hdmi: HDMI:EDID found DMT format: code 28, 1280x800p @ 60 Hz (16:10) in standard timing 4 MESS:00:00:18.926914:0: hdmi: HDMI:EDID parsing v1 CEA extension MESS:00:00:18.931247:0: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4) MESS:00:00:18.939497:0: hdmi: HDMI:EDID found CEA detail timing format: 1280x720p @ 50 Hz (19) MESS:00:00:18.947829:0: hdmi: HDMI:EDID found CEA detail timing format: 720x576p @ 50 Hz (17) MESS:00:00:18.956074:0: hdmi: HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2) MESS:00:00:18.964226:0: hdmi: HDMI:EDID moving support for CEA mode 4 to DMT mode 85 because sink does not support HDMI MESS:00:00:18.974731:0: hdmi: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023 MESS:00:00:18.984258:0: hdmi: HDMI:EDID preferred mode remained as DMT (47) 1440x900p @ 60 Hz with pixel clock 106 MHz MESS:00:00:18.994503:0: hdmi: HDMI: hotplug attached with DVI support MESS:00:00:19.000683:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead MESS:00:00:19.011816:0: hdmi: HDMI: power_on to DMT mode 1440x900@60 MESS:00:00:19.019622:0: hdmi: HDMI: Action callback added to queue to happen at frame 0 MESS:00:00:19.036481:0: *** Restart logging MESS:00:00:19.038971:0: brfs: File read: 1685 bytes MESS:00:00:19.899117:0: brfs: File read: /mfs/sd/cmdline.txt MESS:00:00:19.903115:0: Read command line from file 'cmdline.txt': MESS:00:00:19.908984:0: 'dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=43be32d2-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait rootdelay=5' MESS:00:00:19.924943:0: brfs: File read: 154 bytes MESS:00:00:41.138457:0: No kernel trailer - assuming DT-capable MESS:00:00:42.155123:0: Failed to load Device Tree file '?' MESS:00:00:42.159505:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:46.968900:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:51.777378:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined MESS:00:00:56.585863:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined [... repeated many times...]

any idea?

pelwell commented 5 years ago

The 21 second gap in the log, and the illegal Device Tree name, are baffling:

MESS:00:00:19.924943:0: brfs: File read: 154 bytes
MESS:00:00:41.138457:0: No kernel trailer - assuming DT-capable
MESS:00:00:42.155123:0: Failed to load Device Tree file '?'

So, to be clear, this only happens on a reboot? How are you triggering the reboot?

blacktek commented 5 years ago

Yes, 99% of times happens with reboots or if i quickly remove and reinsert power cord. I issue the reboot with "sudo reboot" from command line.

ghollingworth commented 5 years ago

Quickly remove / replug seems to suggest the problem is the same as the one I've just fixed, which also effected the crash response (you can check this by hitting Ctrl-Alt-B to crash and reboot, the old bootcode.bin wouldn't reboot)

blacktek commented 5 years ago

Gordon , how did you fix it? do you have a link to a post where I can see your solution? I would avoid putting the boot code on an external SD card. I wouldn't give this win to raspi :D