RB5 does not get into fastboot after bootloader

Hello,

I am trying to install linaro OS on RB5. I downloaded the bootloader from here: Debian Downloads for Qualcomm Robotics RB5 - 96Boards

And proceeded to follow the steps provided here: Linux Host Installation for Qualcomm Robotics RB5 development kit - 96Boards

Unfortunately, my device does not reboot in fastboot mode after Step 4: sudo ./flashall.

After this step, the device seems to be ‘bricked’ and I have recover it by putting in QDL mode.

Here is the output of flashall script:
*sudo ./flashall *

  • target reported max download size of 805306368 bytes*
  • sending ‘partition:0’ (44 KB)…*
  • OKAY [ 0.010s]*
  • writing ‘partition:0’…*
  • OKAY [ 0.923s]*
  • finished. total time: 0.934s*
  • target reported max download size of 805306368 bytes*
  • sending ‘partition:1’ (44 KB)…*
  • OKAY [ 0.003s]*
  • writing ‘partition:1’…*
  • OKAY [ 0.144s]*
  • finished. total time: 0.148s*
  • target reported max download size of 805306368 bytes*
  • sending ‘partition:2’ (44 KB)…*
  • OKAY [ 0.008s]*
  • writing ‘partition:2’…*
  • OKAY [ 0.159s]*
  • finished. total time: 0.168s*
  • target reported max download size of 805306368 bytes*
  • sending ‘partition:3’ (44 KB)…*
  • OKAY [ 0.001s]*
  • writing ‘partition:3’…*
  • OKAY [ 0.166s]*
  • finished. total time: 0.168s*
  • target reported max download size of 805306368 bytes*
  • sending ‘partition:4’ (44 KB)…*
  • OKAY [ 0.005s]*
  • writing ‘partition:4’…*
  • OKAY [ 0.212s]*
  • finished. total time: 0.217s*
  • target reported max download size of 805306368 bytes*
  • sending ‘partition:5’ (44 KB)…*
  • OKAY [ 0.001s]*
  • writing ‘partition:5’…*
  • OKAY [ 0.222s]*
  • finished. total time: 0.223s*
  • target reported max download size of 805306368 bytes*
  • sending ‘aop_a’ (198 KB)…*
  • OKAY [ 0.009s]*
  • writing ‘aop_a’…*
  • OKAY [ 0.003s]*
  • finished. total time: 0.012s*
  • target reported max download size of 805306368 bytes*
  • sending ‘apdp’ (25 KB)…*
  • OKAY [ 0.007s]*
  • writing ‘apdp’…*
  • OKAY [ 0.004s]*
  • finished. total time: 0.011s*
  • target reported max download size of 805306368 bytes*
  • sending ‘cmnlib64_a’ (496 KB)…*
  • OKAY [ 0.009s]*
  • writing ‘cmnlib64_a’…*
  • OKAY [ 0.004s]*
  • finished. total time: 0.013s*
  • target reported max download size of 805306368 bytes*
  • sending ‘cmnlib_a’ (383 KB)…*
  • OKAY [ 0.010s]*
  • writing ‘cmnlib_a’…*
  • OKAY [ 0.005s]*
  • finished. total time: 0.015s*
  • erasing ‘ddr’…*
  • OKAY [ 0.004s]*
  • finished. total time: 0.004s*
  • target reported max download size of 805306368 bytes*
  • sending ‘devcfg_a’ (47 KB)…*
  • OKAY [ 0.007s]*
  • writing ‘devcfg_a’…*
  • OKAY [ 0.003s]*
  • finished. total time: 0.010s*
  • target reported max download size of 805306368 bytes*
  • sending ‘dsp_a’ (65536 KB)…*
  • OKAY [ 0.329s]*
  • writing ‘dsp_a’…*
  • OKAY [ 0.236s]*
  • finished. total time: 0.565s*
  • target reported max download size of 805306368 bytes*
  • sending ‘featenabler_a’ (84 KB)…*
  • OKAY [ 0.007s]*
  • writing ‘featenabler_a’…*
  • OKAY [ 0.002s]*
  • finished. total time: 0.010s*
  • target reported max download size of 805306368 bytes*
  • sending ‘hyp_a’ (442 KB)…*
  • OKAY [ 0.010s]*
  • writing ‘hyp_a’…*
  • OKAY [ 0.004s]*
  • finished. total time: 0.014s*
  • target reported max download size of 805306368 bytes*
  • sending ‘keymaster_a’ (244 KB)…*
  • OKAY [ 0.008s]*
  • writing ‘keymaster_a’…*
  • OKAY [ 0.004s]*
  • finished. total time: 0.012s*
  • target reported max download size of 805306368 bytes*
  • sending ‘multiimgoem_a’ (13 KB)…*
  • OKAY [ 0.008s]*
  • writing ‘multiimgoem_a’…*
  • OKAY [ 0.002s]*
  • finished. total time: 0.011s*
  • target reported max download size of 805306368 bytes*
  • sending ‘qupfw_a’ (52 KB)…*
  • OKAY [ 0.009s]*
  • writing ‘qupfw_a’…*
  • OKAY [ 0.005s]*
  • finished. total time: 0.014s*
  • target reported max download size of 805306368 bytes*
  • sending ‘spunvm’ (348 KB)…*
  • OKAY [ 0.007s]*
  • writing ‘spunvm’…*
  • OKAY [ 0.004s]*
  • finished. total time: 0.011s*
  • target reported max download size of 805306368 bytes*
  • sending ‘tz_a’ (3232 KB)…*
  • OKAY [ 0.021s]*
  • writing ‘tz_a’…*
  • OKAY [ 0.012s]*
  • finished. total time: 0.032s*
  • target reported max download size of 805306368 bytes*
  • sending ‘uefisecapp_a’ (120 KB)…*
  • OKAY [ 0.002s]*
  • writing ‘uefisecapp_a’…*
  • OKAY [ 0.004s]*
  • finished. total time: 0.006s*
  • target reported max download size of 805306368 bytes*
  • sending ‘xbl_a’ (3408 KB)…*
  • OKAY [ 0.020s]*
  • writing ‘xbl_a’…*
  • OKAY [ 0.073s]*
  • finished. total time: 0.093s*
  • target reported max download size of 805306368 bytes*
  • sending ‘xbl_config_a’ (95 KB)…*
  • OKAY [ 0.009s]*
  • writing ‘xbl_config_a’…*
  • OKAY [ 0.008s]*
  • finished. total time: 0.017s*
  • target reported max download size of 805306368 bytes*
  • sending ‘abl_a’ (148 KB)…*
  • OKAY [ 0.004s]*
  • writing ‘abl_a’…*
  • OKAY [ 0.002s]*
  • finished. total time: 0.007s*

hey,

I am not sure if this is the real issue… but I noticed that the link to the bootloader/rescue package on that documentation page is wrong. Can you please retry the instructions, but use the bootloader from

https://releases.linaro.org/96boards/rb5/linaro/rescue/21.08/

(e.g. 21.08 instead of 21.04)

I will get the page updated in the meantime.

The most recent release can be found here in general:
http://releases.linaro.org/96boards/rb5/linaro/debian/latest

Thank you for the response. Your note helped. But I do not see a desktop show up when connected to HDMI.

Setup:
Successfully installed:
rb5-bootloader-ufs-linux-14.zip
linaro-sid-gnome-qrb5165-rb5-115.img
boot-linaro-sid-qrb5165-rb5-115.img

and DIP_SW_0 == 011000

I connect the power and HDMI cable to the board, and I see the following LEDs:

  • USER LEDS : 0- blinking green. 1- solid green. Others off.
  • BT LED is solid green
  • Wifi LED is off
  • LED next to power adapter is solid green.

BUT I DO NOT SEE any output on the HDMI screen. There is a latest HDMI monitor, and RB3 linaro displays well with this monitor.

Please let me know how to debug this?

Thank you

It looks like the Debian release notes is missing an important information, which we only included in the OpenEmbedded release notes (we typically do OE and Debian releases simultaneously), see Linaro Releases.

Updating LT9611UXC firmware

LT9611UXC is a DSI-to-HDMI bridge that sits between QRB5165 and the HDMI connecter on the board. At the factory it is flashed with the firmware that works with the Qualcomm kernel, but does not work with the upstream kernel, used by Linaro release. Thus the LT9611UXC firmware needs to be updated after Linaro image has been flashed for the first time. In order to upgrade the firmware flash and boot the board, connect to it using the serial console and execute the following commands:

cat /sys/bus/i2c/devices/5-002b/lt9611uxc_firmware

If the reported version is greater or equal to 43, you don’t have to uprade.
Otherwise execute:

echo 1 > /sys/bus/i2c/devices/5-002b/lt9611uxc_firmware

The firmware will be updated (this process takes several minutes). After the process completes, reboot the board to get display up and running.

actually, it’s not missing from the release notes, it’s there. It’s not listed in the ‘important notes for this release’ though.

I was able to log in to device via ssh, but I get the following error:

linaro@linaro-gnome:/sys/bus/i2c/devices/5-002b$ ls -l lt9611uxc_firmware
-rwxr-xr-x 1 root root 4096 Sep 28 17:03 lt9611uxc_firmware
linaro@linaro-gnome:/sys/bus/i2c/devices/5-002b$ echo 1 > lt9611uxc_firmware
-bash: lt9611uxc_firmware: Permission denied
linaro@linaro-gnome:/sys/bus/i2c/devices/5-002b$ sudo !!
sudo echo 1 > lt9611uxc_firmware
-bash: lt9611uxc_firmware: Permission denied

Does not work as root, nor does it work by giving all users r,w,x capability.

Suggestions how to proceed?

indeed, the ‘sudo’ applies only to the first command (echo 1), not to the redirection.

If you can’t login as root, then try
sudo sh -c ‘echo 1 > lt9611uxc_firmware’

Hi,

  1. Cannot login to root with password linaro.

  2. linaro@linaro-gnome:/sys/bus/i2c/devices/5-002b$ sudo sh -c ‘echo 1 > lt9611uxc_firmware’
    sh: 1: echo: echo: I/O error

  3. I can become root by sudo su, but that gives the following error:
    linaro@linaro-gnome:/sys/bus/i2c/devices/5-002b$ sudo su
    root@linaro-gnome:/sys/devices/platform/soc@0/9c0000.geniqup/994000.i2c/i2c-5/5-002b# cd
    root@linaro-gnome:~# cd /sys/bus/i2c/devices/5-002b
    root@linaro-gnome:/sys/bus/i2c/devices/5-002b# ls

    lt9611uxc_firmware

    root@linaro-gnome:/sys/bus/i2c/devices/5-002b# echo 1 > lt9611uxc_firmware
    bash: echo: write error: No such file or directory

ok, #3 was the right thing to do to get root permission. But now, I don’t know why it fails. I will ask someone else to help.

@kshitijminhas It looks like you do not have the lt9612uxc firmware file. Could you please install firmware-misc-nonfree and retry?

Hi, thank you for following up.
I downloaded lt9611uxc_fw.bin from here https://github.com/lumag/linux-firmware/commit/63ab3db8399a504048716eb3feed2867da58876a.
I was able to execute the lt9611uxc_firmware script. Dmesg showed driver was successfully loaded.
But I did not see HDMI after reboot.

Any idea why?

I will try apt install firmware-misc-nonfree in the morning let you know.

Thanks

@kshitijminhas if you’ve used the lt9611uxc binary from the github, it should be fine. Could you please atttach a full dmesg here and a hexdump -C /sys/class/drm/card0-HDMI-A-1/edid

@Lumag here is dmesg_log.txt and hexdump.txt