FindOMAPDevicesWithUnsignedBootloderFromUSB » History » Version 1
Denis 'GNUtoo' Carikli, 03/28/2020 11:16 PM
move from 9100GBootloader
| 1 | 1 | Denis 'GNUtoo' Carikli | h1. OmapUsbBootCheckSignedSOC |
|---|---|---|---|
| 2 | |||
| 3 | h3. How to check with command line utilities |
||
| 4 | |||
| 5 | To get the bootrom to try to boot on USB, you need to do the following: |
||
| 6 | * Connect the USB cable to the device but make sure it's not connected on the computer. |
||
| 7 | * Power off the device |
||
| 8 | * Connect the USB cable |
||
| 9 | |||
| 10 | If we do that, we get the following in the kernel log of your laptop: |
||
| 11 | <pre> |
||
| 12 | usb 1-1: new high-speed USB device number 24 using ehci-pci |
||
| 13 | usb 1-1: unable to get BOS descriptor or descriptor too short |
||
| 14 | usb 1-1: New USB device found, idVendor=0451, idProduct=d00f, bcdDevice= 0.00 |
||
| 15 | usb 1-1: New USB device strings: Mfr=33, Product=37, SerialNumber=0 |
||
| 16 | usb 1-1: Product: OMAP4430 |
||
| 17 | usb 1-1: Manufacturer: Texas Instruments |
||
| 18 | </pre> |
||
| 19 | |||
| 20 | Note that your kernel might need to be compiled with CONFIG_USB_ANNOUNCE_NEW_DEVICES=y |
||
| 21 | to print that. In Parabola CONFIG_USB_ANNOUNCE_NEW_DEVICES=y is enabled. |
||
| 22 | |||
| 23 | We can also try to get a bit more infos with omap-usb-boot: |
||
| 24 | <pre> |
||
| 25 | $ sudo omap-usb-boot -v -w boot invalidbootmedia |
||
| 26 | Finding and opening USB device |
||
| 27 | Found and opened omap4 USB device: OMAP4430 |
||
| 28 | ASIC device id: 4430, HS device |
||
| 29 | Booting from device invalidbootmedia... |
||
| 30 | Booting device invalidbootmedia not found |
||
| 31 | Booting from device failed |
||
| 32 | </pre> |
||
| 33 | |||
| 34 | Here we know the device is signed because it's a "HS device". |
||
| 35 | If it was not signed it would print "GP device" instead. |