How can I recover my board?

Products Support DragonBoard 820c
#1

I’ve been trying to install Ubuntu 16.04 on the DragonBoard 820c. But, I coudn’t do it. So, I will describe what I did for installing Ubuntu 16.04 on the DB. If you can, plz help me resolve this problem.

  1. Try booting in Debian
  • Power off the DB.
  • Set switch S1 to ON, ON, ON, ON.
  • Connect a monitor to the DB with a HDMI cable.
  • Connect a keyboard and a mouse to the DB via USB.
  • Power on the DB.
  • Succeed in booting in Debian.
  1. Try booting in Fastboot
  • Power off the DB.
  • Set switch S1 to OFF, OFF, OFF, OFF.
  • Connect the DB and Ubuntu host PC via micro USB.
  • Power on S2 while pressing S4(Volume down).
  • Execute a minicom but, nothing show up in the UART console.
  • On the host PC, verify the fastboot mode of the DB using the following command.
    $ sudo fastboot devices
  • After that, nothing happened.
  • Recognize the DB as a qualcomm device via USB using the following the command.
    $ ls /dev/usbTTY0
  • Try removing the boot partition as the following, but it didn’t work with an error message which means the shortage on the memory.
    $ cat /dev/zero > /dev/disk/by-partlabel/boot
  1. reflashing bootloader on the DB
  • Try installing a different version of the bootloaders on the DB.
  • Using USB flashing tool
  • Installing Qualcomm USB flasing tool

type the following command

$ git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git
$ sudo apt-get install libxml2-dev
$ sudo systemctl stop ModemManager

download the recent bootloader image

> Download dragonboard-820c-bootloader-ufs-linux-38.zip and unpack the file
> Set switch S1 to OFF, ON, ON, OFF and run the following command.
  $ cd dragonboard-820c-bootloader-ufs-linux-38/
  $ sudo <PATH to qdl>/qdl prog_ufs_firehose_8996_ddr.elf rawprogram.xml patch.xml
> No reaction
> Set switch S1 to OFF, ON, OFF, OFF and the following command.
  $ cd dragonboard-820c-bootloader-ufs-linux-38/
  $ sudo <PATH to qdl>/qdl prog_ufs_firehose_8996_ddr.elf rawprogram.xml patch.xml
> A few second later, the following message showed up.
     Update Backup Header with CRC of Backup Header.
     LOG: crc start sector 393215, over bytes 92
     LOG: Patched sector 393215 with 8FDB38DF
     LUN1 is now bootable device
     LOG: Inside handlePower() - Requested POWER_RESET
     LOG: Issuing bsp_target_reset() after 1 seconds, if this hangs, do you have WATCHDOG enabled?
  1. Trying booting in the fastboot mode once again
  • Power off
  • Set switch S1 to OFF, OFF, OFF, OFF
  • Connect the DB and Ubuntu host PC via a micro USB.
  • Power on switch S2 while pressing switch S4.
  • Try communicating with Minicom, however it failed.
  • Do NOT recognize the DB as a device. FAILED.
  • Power off again.
  • Set switch S1 to ON, ON, ON, ON
  • Try booting in Debian, but it didn’t work.
  1. Try booting in SD card Recovery image
  • Download the dragonboard-820c-sdcard-rescue-38.zip and unpack it.
  • Write the image on SD card using the following command.
    $ sudo dd if=dragonboard-820c-sdcard-rescue-38.img of=/dev/ bs=4M oflag=sync status=noxfer
  • Power off
  • Insert SD card on the DB then set switch S1 to OFF, ON, ON, OFF
  • connect the DB and Ubuntu host PC via micro USB.
  • Power on switch S2 button while pressing switch S4(Volume down) button, but nothing happended.
  • Verify the fastboot mode of the DB using the following command, but nothing shows up.
    $ sudo fastboot devices
  • NOT find the DB via USB using the following command:
    $ ls /dev/ttyUSB0
  • Power off the DB.
  • Set switch S1 to ON, ON, ON, ON.
  • Power on the DB.
  • It could NOT boot in Debian.
  • Substitute two different version of the SD card rescue image(dragonboard-820c-sdcard-rescue-37.img and dragonboard-820c-sdcard-rescue-36.img, respectively) for the image(dragonboard-820c-sdcard-rescue-38.img). Unfortunately, every efforts are useless. Fastboot mode FAILED. NOT recognize the DB as an USB device. Debian booting FAILED.

This is all whiat I did to install Ubuntu on the DB. Plz give me a clue to recover my board.