Flash bootloader

hi,
I followed here https://www.96boards.org/documentation/consumer/dragonboard/qualcomm-robotics-rb5/installation/linux-fastboot.md.html, flashed all bootloader images, but after that, I cannot enter fastboot mode and console print out :

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.XF.3.2-00310-SM8250-1
S - IMAGE_VARIANT_STRING=Soc8250LAA
S - OEM_IMAGE_VERSION_STRING=crm-ubuntu12
S - Boot Interface: UFS
S - Secure Boot: Off
S - Boot Config @ 0x00786070 = 0x00000001
S - JTAG ID @ 0x00786130 = 0x0015a0e1
S - OEM ID @ 0x00786138 = 0x00000000
S - Serial Number @ 0x00786134 = 0x96e030cd
S - OEM Config Row 0 @ 0x007841e0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841e8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x007841f8 = 0x0040200000000400
S - Feature Config Row 1 @ 0x00784200 = 0xc000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 5
S - PBL freq: 600 MHZ
D - 6210 - pbl_apps_init_timestamp
D - 31711 - bootable_media_detect_timestamp
D - 957 - bl_elf_metadata_loading_timestamp
D - 715 - bl_hash_seg_auth_timestamp
D - 6223 - bl_elf_loadable_segment_loading_timestamp
D - 5504 - bl_elf_segs_hash_verify_timestamp
D - 7011 - bl_sec_hash_seg_auth_timestamp
D - 819 - bl_sec_segs_hash_verify_timestamp
D - 35 - pbl_populate_shared_data_and_exit_timestamp
S - 59185 - PBL, End
B - 73108 - SBL1, Start
B - 188337 - SBL1 BUILD @ 06:31:20 on Nov 20 2020
B - 192485 - usb: usb_shared_hs_phy_init: hs phy cfg size , 0xc
D - 10614 - sbl1_hw_init
D - 0 - boot_flash_init
B - 268125 - UFS INQUIRY ID: SAMSUNG KLUDG4UHDB-B2D1 0400
B - 269620 - UFS Boot LUN: 1
D - 915 - Auth Metadata
D - 79574 - sbl1_xblconfig_init
D - 0 - boot_config_data_table_default_init
B - 289292 - Using default CDT
D - 4758 - boot_config_data_table_init
B - 297100 - CDT Version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:0
D - 17324 - sbl1_hw_platform_pre_ddr
D - 0 - devcfg init
B - 326075 - PM: PM 0=0x4000008000000040:0x200040
B - 326167 - PM: PM 1=0x4000008000000040:0x800
B - 331077 - PM: PM 2=0x4000008000000020:0x800
B - 335744 - PM: PM 5=0x400000000000000:0x0
B - 340380 - PM: POWER ON by CBLPWR, POWER OFF due to FAULT UVLO
B - 352976 - PM: PMA_2 PON:CBL ON:PON OFF:FLT FAULT1:UVLO S3:WD
B - 358710 - PM: PMA_3 PON:CBL ON:PON OFF:S3 FAULT1:UVLO S3:WD
B - 464545 - PM: SET_VAL:Skip
B - 465033 - PM: PSI: b0x00_v0x53
B - 471164 - PM: Device Init # SPMI Transn: 5240
B - 471194 - Mem dump cmd, entry
D - 0 - Mem dump cmd, exit
B - 479246 - Error code 22000080 at sbl1_hw.c Line 547
B - 482449 - ^^^^- Printing Call Stack -^^^^
B - 487725 - func_addr : 148171A8
B - 492087 - func_addr : 14824064
B - 495777 - func_addr : 14824120
B - 499437 - func_addr : 1482466C
B - 503097 - func_addr : 1481584C
B - 506757 - ^^^^^- Done Printing -^^^^^
B - 510448 - sbl_error_handler FAIL: DDR not initialized

please check, what I did wrongly?

@jackyard
We have released new rescue package .
You will have to use QDL to flash it. Compile QDL, unzip the rescue package and change dir to it. Power off the RB5 completely (remove power plug and USB-C connector). Insert power plug, press the F_DL button, insert USB-C cable connected to your host, release F_DL. Now run:

sudo qdl prog_firehose_ddr.elf rawprogram?.xml patch?.xml

1 Like