Radxa Dragon Q6A with DDR problem?

Dragon Series Q6A
1

Hello,

I’ve received my Dragon Q6A in the past days, tried booting with SD/NVME/UFS, but it just keeps blinking a Green Light.

Then I connected my RPi Debug probe and this is the serial output:

Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.MXF.1.0.c1-00364-KODIAKLA-1
S - IMAGE_VARIANT_STRING=SocKodiakLAA
S - OEM_IMAGE_VERSION_STRING=wa-lxc
S - Boot Interface: SPI
S - Secure Boot: Off
S - Boot Config @ 0x00786070 = 0x000000c9
S - JTAG ID @ 0x00786130 = 0x001980e1
S - OEM ID @ 0x00786138 = 0x00000000
S - Serial Number @ 0x00786134 = 0xe1dcb367
S - OEM Config Row 0 @ 0x007841c0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841c8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x00784148 = 0x0000000000000000
S - Feature Config Row 1 @ 0x00784150 = 0x0000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 1
D -      6632 - pbl_apps_init_timestamp
D -      3408 - bootable_media_detect_timestamp
D -       702 - bl_elf_metadata_loading_timestamp
D -       706 - bl_hash_seg_auth_timestamp
D -     27927 - bl_elf_loadable_segment_loading_timestamp
D -      4844 - bl_elf_segs_hash_verify_timestamp
D -     17433 - bl_sec_hash_seg_auth_timestamp
D -       811 - bl_sec_segs_hash_verify_timestamp
D -        31 - pbl_populate_shared_data_and_exit_timestamp
S -     62494 - PBL, End
B -     71461 - SBL1, Start
B -    192058 - SBL1 BUILD @ 16:52:49 on Oct 13 2025
B -    196115 - usb: HS: device tree Not available , 0x3
B -    199500 - usb: eud_serial_upd , 0xe1dcb367
D -    204685 - sbl1_hw_init
D -     10705 - media_init:1
D -         0 - smss_load_cancel
D -         0 - boot_sail_pbl_edl_check
D -         0 - sail_execute_bist_sequence
B -    229299 - SMSS -  Image Load, Start
D -      3934 - SMSS -  Image Loaded, Delta - (0 Bytes)
D -      1007 - Auth Metadata
D -      5886 - sbl1_xblconfig_init
B -    244945 - XBL Config -  Image Load, Start
B -    249429 - DTB  Found: [pre-ddr][7601f201000000][0]
D -      4392 - boot_pre_ddr_dtb_load
D -        31 - media_init:2
D -         0 - media_init:3
D -         0 - boot_proc_bootset
D -         0 - shrm_load_cancel
B -    269833 - SHRM -  Image Load, Start
D -       641 - Auth Metadata
D -      1311 - Segments hash check
D -     12414 - SHRM -  Image Loaded, Delta - (35752 Bytes)
D -         0 - boot_default_cdt_init
D -       396 - boot_cdt_init
B -    294477 - CDT -  Image Load, Start
B -    297283 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:2
D -     16561 - sbl1_hw_platform_pre_ddr
D -         0 - devcfg init
B -    323269 - PMIC A:2.0 B:1.0 C:2.2 I:1.0
B -    325984 - PM: Reset by PSHOLD
B -    327417 - PM: Reset Type: Hard Reset
B -    582611 - PM: SET_VAL:Skip
B -    582641 - PM: Verifying PON-Trigger specific configurations & current PON-Trigger
B -    591395 - PM: All PON-Trigger specific configs verified. Proceeding to BOOT
B -    601185 - PM: PSI: b0x06_v0x3f
B -    603869 - PM: OEM_PSI Start
B -    604784 - PM: OEM_PSI Done
B -    607743 - PM: Device Init # SPMI Transn: 15313
D -    296948 - pm_device_init, Delta
B -    615581 - pm_driver_init, Start
B -    627049 - PM: Driver Init # SPMI Transn: 520
D -      7991 - pm_driver_init, Delta
B -    632692 - PM: Battery ID: 10096Ohm
B -    635223 - PM: debug board connected
B -    638975 - vsense_init, Start
D -         0 - vsense_init, Delta
D -    341631 - sbl1_hw_pre_ddr_init
D -         0 - boot_dload_handle_forced_dload_timeout
D -      2959 - sbl1_load_ddr_training_data
B -    663863 - Pre_DDR_clock_init, Start
D -        91 - Pre_DDR_clock_init, Delta
D -     12901 - sbl1_ddr_set_params
B -    675575 - sbl1_ddr_init, Start
B -    678991 - LP5 DDR detected
B -    694027 - DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED,FREQ=DC,CHANNEL=0,CHIPSELECT=DC,BYTE=DC,BIT=DC,LIMIT=0x0,VALUE=0

B -    699944 - Error code 84 at boot_platforminfo.c Line 76
B -    705373 - Call Stack:
B -    710894 - func_addr  :   14855C74
B -    713517 - func_addr  :   14884A5C
B -    717177 - ^^^^^^^^^^^^^^^^^^^^^
B -    720837 - sbl_error_handler FAIL: D�Format: Log Type - Time(microsec) - Message - Optional Info

It seems my board is not correctly detecting the DDR memory. Does anyone what may I try? (reflashing the SPI did not fix this problem, but I didn’t try a full erase of the SPI because I was afraid of completely bricking this board).

2

The Q6A can never be bricked, in the edl mode you can flash the firmware for the SPI Flash. Check if flashing the SPI image can save the board, if not ask for an RMA:

烧录 SPI 启动固件 | Radxa Docs

1 Like
3

I tried flashing SPI again, but it seems to disconnect from EDL after loading the loader.

Then I tried doing a full erase, it also disconnects the same way and I can’t proceed with erasing.

Here is my terminal output:

thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 005: ID 0424:4206 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 006: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 001 Device 007: ID 0424:4256 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 008: ID 0424:4252 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 009: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 010: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 001 Device 011: ID 0424:7260 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 012: ID 2dc8:5206 8BitDo 8BitDo Retro R8 Mouse Adapter
Bus 001 Device 013: ID 2dc8:520a 8BitDo 8BitDo Retro 108 Adapter
Bus 001 Device 014: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 026: ID 2e8a:000c Raspberry Pi Debug Probe (CMSIS-DAP)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 003: ID 0424:7206 Microchip Technology, Inc. (formerly SMSC) USB7206 Smart Hub
Bus 002 Device 004: ID 0424:7206 Microchip Technology, Inc. (formerly SMSC) USB7206 Smart Hub
Bus 002 Device 005: ID 0424:7206 Microchip Technology, Inc. (formerly SMSC) USB7206 Smart Hub
Bus 002 Device 007: ID 05e3:0756 Genesys Logic, Inc. USB Storage
Bus 002 Device 021: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)


thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ sudo edl-ng --memory spinor erase-part ddr -l prog_firehose_ddr.elf
09:08:30.928 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
09:08:30.929 [INFO]  Kernel driver is active on interface 0, attempting manual detach...
09:08:30.929 [INFO]  Manual detach successful.
09:08:30.929 [INFO]  Detected device mode: Sahara
09:08:30.929 [INFO]  Device is in Sahara mode. Uploading loader...
09:08:30.930 [INFO]  Serial Number: E1DCB367
09:08:30.930 [INFO]  Product ID: 408 (QCS_KODIAK)
09:08:31.032 [INFO]  Uploading loader: /home/thiago/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a/prog_firehose_ddr.elf
09:08:31.225 [INFO]  Loader uploaded and started successfully via Sahara.
09:08:31.726 [WARN]  LibUsbDotNet device detection failed or no device found. Falling back to Serial Port (ttyUSB/ttyACM) detection on Linux...
09:08:31.726 [ERROR] Serial Port is known to be broken on Linux. Please double check why LibUsb is not working if device detection succeeds with Serial Port.
09:08:31.726 [INFO]  Searching for Qualcomm EDL device on Linux (/dev/ttyUSB* or /dev/ttyACM*)...
09:08:31.728 [ERROR] No matching Qualcomm EDL serial devices found.
09:08:31.728 [ERROR] An unexpected error occurred in 'erase-part': Device did not re-enumerate in Firehose mode after loader upload, or could not be found.


thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon 
Q6a/flat_build/flat_build/spinor/dragon-q6a$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 005: ID 0424:4206 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 006: ID 8087:0033 Intel Corp. AX211 Bluetooth
Bus 001 Device 007: ID 0424:4256 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 008: ID 0424:4252 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 009: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 010: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 001 Device 011: ID 0424:7260 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 012: ID 2dc8:5206 8BitDo 8BitDo Retro R8 Mouse Adapter
Bus 001 Device 013: ID 2dc8:520a 8BitDo 8BitDo Retro 108 Adapter
Bus 001 Device 014: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 026: ID 2e8a:000c Raspberry Pi Debug Probe (CMSIS-DAP)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 003: ID 0424:7206 Microchip Technology, Inc. (formerly SMSC) USB7206 Smart Hub
Bus 002 Device 004: ID 0424:7206 Microchip Technology, Inc. (formerly SMSC) USB7206 Smart Hub
Bus 002 Device 005: ID 0424:7206 Microchip Technology, Inc. (formerly SMSC) USB7206 Smart Hub
Bus 002 Device 007: ID 05e3:0756 Genesys Logic, Inc. USB Storage
thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$

I do hear a disconnection sound after this line:

09:08:31.225 [INFO]  Loader uploaded and started successfully via Sahara.

Any other thing I can try?

4

Based on this other topic ( Brick Q6A for flash ) I changed my approach to use use Firehose Lite (instead of Firehose DDR) and it seemed to work:

thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ sudo edl-ng --memory=spinor --loader prog_firehose_lite.elf erase-part ddr
[sudo: authenticate] Password: 
10:36:12.850 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:36:12.850 [INFO]  Kernel driver is active on interface 0, attempting manual detach...
10:36:12.850 [INFO]  Manual detach successful.
10:36:12.850 [INFO]  Detected device mode: Sahara
10:36:12.850 [INFO]  Device is in Sahara mode. Uploading loader...
10:36:12.851 [INFO]  Serial Number: E1DCB367
10:36:12.852 [INFO]  Product ID: 408 (QCS_KODIAK)
10:36:12.953 [INFO]  Uploading loader: /home/thiago/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a/prog_firehose_lite.elf
10:36:13.140 [INFO]  Loader uploaded and started successfully via Sahara.
10:36:13.640 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:36:14.701 [INFO]  Sending Firehose configure command...
10:36:14.728 [INFO]  Firehose configured for Memory: SPINOR, MaxPayload: 1048576

10:36:14.871 [INFO]  Found partition 'ddr' on LUN 0 with sector size 4096.
10:36:14.872 [INFO]  Attempting to erase partition 'ddr' (LUN 0, LBA 7, 20 sectors)...
10:36:14.887 [INFO]  Successfully erased partition 'ddr' in 0.02s.
thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ sudo edl-ng --memory=spinor --loader prog_firehose_lite.elf erase-part uefi
10:37:05.764 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:37:06.329 [INFO]  Detected device mode: Firehose
10:37:06.330 [INFO]  Sending Firehose configure command...
10:37:06.360 [INFO]  Firehose configured for Memory: SPINOR, MaxPayload: 1048576

10:37:06.498 [INFO]  Found partition 'uefi' on LUN 0 with sector size 4096.
10:37:06.498 [INFO]  Attempting to erase partition 'uefi' (LUN 0, LBA 500, 1280 sectors)...
10:37:41.006 [INFO]  Successfully erased partition 'uefi' in 34.51s.
thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ sudo edl-ng --memory=spinor --loader prog_firehose_lite.elf erase-part devcfg
10:37:50.564 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:37:51.129 [INFO]  Detected device mode: Firehose
10:37:51.129 [INFO]  Sending Firehose configure command...
10:37:51.160 [INFO]  Firehose configured for Memory: SPINOR, MaxPayload: 1048576

10:37:51.298 [INFO]  Found partition 'devcfg' on LUN 0 with sector size 4096.
10:37:51.299 [INFO]  Attempting to erase partition 'devcfg' (LUN 0, LBA 2868, 32 sectors)...
10:37:51.706 [INFO]  Successfully erased partition 'devcfg' in 0.41s.
thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ sudo edl-ng --memory=spinor --loader prog_firehose_lite.elf erase-part xbl
10:37:58.158 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:37:58.723 [INFO]  Detected device mode: Firehose
10:37:58.724 [INFO]  Sending Firehose configure command...
10:37:58.755 [INFO]  Firehose configured for Memory: SPINOR, MaxPayload: 1048576

10:37:58.893 [INFO]  Found partition 'xbl' on LUN 0 with sector size 4096.
10:37:58.893 [INFO]  Attempting to erase partition 'xbl' (LUN 0, LBA 52, 256 sectors)...
10:38:05.381 [INFO]  Successfully erased partition 'xbl' in 6.49s.

After that, I tried reflashing the Firmware with Firehose DDR, still no go:

sa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ sudo edl-ng --memory=spinor rawprogram rawprogram0.xml patch0.xml --loader=prog_firehose_ddr.elf
10:38:37.113 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:38:37.113 [INFO]  Kernel driver is active on interface 0, attempting manual detach...
10:38:37.113 [INFO]  Manual detach successful.
10:38:37.113 [INFO]  Detected device mode: Sahara
10:38:37.113 [INFO]  Device is in Sahara mode. Uploading loader...
10:38:37.114 [INFO]  Serial Number: E1DCB367
10:38:37.115 [INFO]  Product ID: 408 (QCS_KODIAK)
10:38:37.217 [INFO]  Uploading loader: /home/thiago/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a/prog_firehose_ddr.elf
10:38:37.410 [INFO]  Loader uploaded and started successfully via Sahara.
10:38:37.910 [WARN]  LibUsbDotNet device detection failed or no device found. Falling back to Serial Port (ttyUSB/ttyACM) detection on Linux...
10:38:37.910 [ERROR] Serial Port is known to be broken on Linux. Please double check why LibUsb is not working if device detection succeeds with Serial Port.
10:38:37.910 [INFO]  Searching for Qualcomm EDL device on Linux (/dev/ttyUSB* or /dev/ttyACM*)...
10:38:37.911 [ERROR] No matching Qualcomm EDL serial devices found.
10:38:37.911 [ERROR] An unexpected error occurred in 'rawprogram': Device did not re-enumerate in Firehose mode after loader upload, or could not be found.
10:38:37.911 [INFO]  'rawprogram' command finished in 0.81s.

Then flashing with Firehose Lite completed fine:

thiago@Bessa-LinuxMain:~/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a$ sudo edl-ng --memory=spinor rawprogram rawprogram0.xml patch0.xml --loader=prog_firehose_lite.elf
10:38:55.840 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:38:55.840 [INFO]  Kernel driver is active on interface 0, attempting manual detach...
10:38:55.841 [INFO]  Manual detach successful.
10:38:55.841 [INFO]  Detected device mode: Sahara
10:38:55.841 [INFO]  Device is in Sahara mode. Uploading loader...
10:38:55.841 [INFO]  Serial Number: E1DCB367
10:38:55.842 [INFO]  Product ID: 408 (QCS_KODIAK)
10:38:55.944 [INFO]  Uploading loader: /home/thiago/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a/prog_firehose_lite.elf
10:38:56.130 [INFO]  Loader uploaded and started successfully via Sahara.
10:38:56.630 [INFO]  Found device using LibUsbDotNet on Linux / MacOS.
10:38:57.690 [INFO]  Sending Firehose configure command...
10:38:57.718 [INFO]  Firehose configured for Memory: SPINOR, MaxPayload: 1048576

10:38:57.718 [INFO]  --- Processing LUN 0 using rawprogram0.xml ---
Writing cdt (cdt.bin):                 100.0% (  0.00 /   0.00 MiB) [N/A       ]    
Writing XBL (xbl.elf):                 100.0% (  0.80 /   0.80 MiB) [264.44 KiB/s]    
Writing XblRamdump (XblRamdump.elf):   100.0% (  0.19 /   0.19 MiB) [102.78 KiB/s]    
Writing XBL_CONFIG (xbl_config.elf):   100.0% (  0.31 /   0.31 MiB) [95.25 KiB/s]    
Writing UEFI (uefi.elf):               100.0% (  4.51 /   4.51 MiB) [267.21 KiB/s]    
Writing AOP (aop.mbn):                 100.0% (  0.20 /   0.20 MiB) [97.29 KiB/s]    
Writing TZ (tz.mbn):                   100.0% (  3.98 /   3.98 MiB) [85.85 KiB/s]    
Writing DEVCFG (devcfg.mbn):           100.0% (  0.05 /   0.05 MiB) [N/A       ]    
Writing HYP (hypvm.mbn):               100.0% (  1.46 /   1.46 MiB) [88.01 KiB/s]    
Writing QUP (qupv3fw.elf):             100.0% (  0.05 /   0.05 MiB) [166.85 KiB/s]    
Writing CPUCP (cpucp.elf):             100.0% (  0.18 /   0.18 MiB) [104.56 KiB/s]    
Writing SHRM (shrm.elf):               100.0% (  0.04 /   0.04 MiB) [241.05 KiB/s]    
Writing ImageFv (imagefv.elf):         100.0% (  0.02 /   0.02 MiB) [N/A       ]    
10:40:35.465 [ERROR] Error: Image file '/home/thiago/Downloads/ISOs/Radxa Dragon Q6a/flat_build/flat_build/spinor/dragon-q6a/fat12test.bin' for <program> (Label: FATTEST) not found. Skipping this file.
Writing PrimaryGPT (gpt_main0.bin):    100.0% (  0.02 /   0.02 MiB) [N/A       ]    
Writing BackupGPT (gpt_backup0.bin):   100.0% (  0.02 /   0.02 MiB) [N/A       ]    
10:40:36.069 [INFO]  --- Patching LUN 0 using patch0.xml ---

10:40:36.856 [INFO]  'rawprogram' command finished in 101.03s.
10:40:36.856 [INFO]  'rawprogram' command finished successfully.

But still, same problem with DDR not detected:

Serial  Port opened
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.MXF.1.0.c1-00364-KODIAKLA-1
S - IMAGE_VARIANT_STRING=SocKodiakLAA
S - OEM_IMAGE_VERSION_STRING=wa-lxc
S - Boot Interface: SPI
S - Secure Boot: Off
S - Boot Config @ 0x00786070 = 0x000000c9
S - JTAG ID @ 0x00786130 = 0x001980e1
S - OEM ID @ 0x00786138 = 0x00000000
S - Serial Number @ 0x00786134 = 0xe1dcb367
S - OEM Config Row 0 @ 0x007841c0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841c8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x00784148 = 0x0000000000000000
S - Feature Config Row 1 @ 0x00784150 = 0x0000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 1
D -      6633 - pbl_apps_init_timestamp
D -      3409 - bootable_media_detect_timestamp
D -       702 - bl_elf_metadata_loading_timestamp
D -       702 - bl_hash_seg_auth_timestamp
D -     27925 - bl_elf_loadable_segment_loading_timestamp
D -      4842 - bl_elf_segs_hash_verify_timestamp
D -     17439 - bl_sec_hash_seg_auth_timestamp
D -       813 - bl_sec_segs_hash_verify_timestamp
D -        31 - pbl_populate_shared_data_and_exit_timestamp
S -     62496 - PBL, End
B -     71553 - SBL1, Start
B -    192363 - SBL1 BUILD @ 16:52:49 on Oct 13 2025
B -    196389 - usb: HS: device tree Not available , 0x3
B -    199805 - usb: eud_serial_upd , 0xe1dcb367
D -    205021 - sbl1_hw_init
D -     10736 - media_init:1
D -         0 - smss_load_cancel
D -         0 - boot_sail_pbl_edl_check
D -         0 - sail_execute_bist_sequence
B -    229634 - SMSS -  Image Load, Start
D -      3965 - SMSS -  Image Loaded, Delta - (0 Bytes)
D -       976 - Auth Metadata
D -      5917 - sbl1_xblconfig_init
B -    245311 - XBL Config -  Image Load, Start
B -    249795 - DTB  Found: [pre-ddr][7601f201000000][0]
D -      4392 - boot_pre_ddr_dtb_load
D -         0 - media_init:2
D -         0 - media_init:3
D -         0 - boot_proc_bootset
D -         0 - shrm_load_cancel
B -    270230 - SHRM -  Image Load, Start
D -       671 - Auth Metadata
D -      1312 - Segments hash check
D -     12413 - SHRM -  Image Loaded, Delta - (35752 Bytes)
D -         0 - boot_default_cdt_init
D -       396 - boot_cdt_init
B -    294904 - CDT -  Image Load, Start
B -    297710 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:2
D -     16592 - sbl1_hw_platform_pre_ddr
D -        30 - devcfg init
B -    323757 - PMIC A:2.0 B:1.0 C:2.2 I:1.0
B -    326350 - PM: PM8 0x4
B -    328058 - PM: xVdd reset
B -    330498 - PM: PON by PWR key DEB
B -    586637 - PM: SET_VAL:Skip
B -    586667 - PM: Verifying PON-Trigger specific configurations & current PON-Trigger
B -    595421 - PM: All PON-Trigger specific configs verified. Proceeding to BOOT
B -    605211 - PM: PSI: b0x06_v0x3f
B -    607895 - PM: OEM_PSI Start
B -    608810 - PM: OEM_PSI Done
B -    611769 - PM: Device Init # SPMI Transn: 15440
D -    300547 - pm_device_init, Delta
B -    619638 - pm_driver_init, Start
B -    631106 - PM: Driver Init # SPMI Transn: 520
D -      7991 - pm_driver_init, Delta
B -    636748 - PM: Battery ID: 10073Ohm
B -    639249 - PM: debug board connected
B -    643001 - vsense_init, Start
D -         0 - vsense_init, Delta
D -    345229 - sbl1_hw_pre_ddr_init
D -         0 - boot_dload_handle_forced_dload_timeout
D -      2989 - sbl1_load_ddr_training_data
B -    667919 - Pre_DDR_clock_init, Start
D -        91 - Pre_DDR_clock_init, Delta
D -     12902 - sbl1_ddr_set_params
B -    679631 - sbl1_ddr_init, Start
B -    683017 - LP5 DDR detected
B -    698053 - DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED,FREQ=DC,CHANNEL=0,CHIPSELECT=DC,BYTE=DC,BIT=DC,LIMIT=0x0,VALUE=0

B -    703970 - Error code 84 at boot_platforminfo.c Line 76
B -    709399 - Call Stack:
B -    714920 - func_addr  :   14855C74
B -    717512 - func_addr  :   14884A5C
B -    721203 - ^^^^^^^^^^^^^^^^^^^^^
B -    724863 - sbl_error_handler FAIL: D�Format: Log Type - Time(microsec) - Message - Optional Info

It seems I got a device from a bad batch with Memory problems? :frowning:

5

I’m sorry but it could be a problem with the DDR memory. Please ask for an RMA.

6

Hi, I have exactly the same problem as OP. Tried all available SPI images, with full erase before flashing, but always ended up with DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED message.

My question is if it is possbile that problem is caused by my board version not compatible with those images?

I have:

  • DRAGON Q6A 12 GB RAM,
  • revision v1.216,
  • memory chip labelled as CA12,
  • CDT Version:3, Platform ID:32, Major ID:1, Minor ID:0, Subtype:7

If there is some specific SPI image for this particular version I would like to try it as a last resort before sending device back.

Serial log dump for reference:


 Serial  Port opened
 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.MXF.1.0.1-00549-KODIAKWP-1
S - IMAGE_VARIANT_STRING=SocKodiakWP
S - OEM_IMAGE_VERSION_STRING=wa-lxc
S - Boot Interface: SPI
S - Secure Boot: Off
S - Boot Config @ 0x00786070 = 0x000000c9
S - JTAG ID @ 0x00786130 = 0x001980e1
S - OEM ID @ 0x00786138 = 0x00000000
S - Serial Number @ 0x00786134 = 0x25313cae
S - OEM Config Row 0 @ 0x007841c0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841c8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x00784148 = 0x0000000000000000
S - Feature Config Row 1 @ 0x00784150 = 0x0000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 1
D -      6617 - pbl_apps_init_timestamp
D -      3434 - bootable_media_detect_timestamp
D -       811 - bl_elf_metadata_loading_timestamp
D -       703 - bl_hash_seg_auth_timestamp
D -     26497 - bl_elf_loadable_segment_loading_timestamp
D -      4621 - bl_elf_segs_hash_verify_timestamp
D -     17367 - bl_sec_hash_seg_auth_timestamp
D -       821 - bl_sec_segs_hash_verify_timestamp
D -        29 - pbl_populate_shared_data_and_exit_timestamp
S -     60900 - PBL, End
B -     70516 - SBL1, Start
B -    200171 - SBL1 BUILD @ 23:26:40 on Dec 30 2025
B -    204380 - usb: eud_serial_upd , 0x25313cae
D -    207705 - sbl1_hw_init
D -     10980 - boot_media_init
D -         0 - smss_load_cancel
B -    226188 - SMSS -  Image Load, Start
D -      3080 - SMSS -  Image Loaded, Delta - (0 Bytes)
D -       885 - Auth Metadata
D -      6131 - sbl1_xblconfig_init
B -    241133 - XBL Config -  Image Load, Start
D -         0 - shrm_load_cancel
B -    248910 - SHRM -  Image Load, Start
D -       549 - Auth Metadata
D -      1281 - Segments hash check
D -     12475 - SHRM -  Image Loaded, Delta - (39616 Bytes)
D -         0 - boot_default_cdt_init
D -       396 - boot_cdt_init
B -    273768 - CDT -  Image Load, Start
B -    276574 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:7
D -     16744 - sbl1_hw_platform_pre_ddr
D -         0 - devcfg init
B -    302895 - PMIC A:2.0 B:1.0 C:2.2 I:1.0
B -    304695 - PM: PM8 0x4
B -    307104 - PM: xVdd reset
B -    309697 - PM: PON by PWR key DEB
B -    565897 - PM: SET_VAL:Skip
B -    567422 - PM: PSI: b0x06_v0x3f
B -    571509 - PM: Device Init # SPMI Transn: 15424
D -    278983 - pm_device_init, Delta
B -    577151 - pm_driver_init, Start
B -    588345 - PM: Driver Init # SPMI Transn: 504
D -      7716 - pm_driver_init, Delta
B -    593255 - PM: damsink err_flag = 0x0
B -    596519 - PM: dam aicl err_flag = 0x0
B -    601277 - PM: Battery ID: 10120Ohm
B -    604479 - PM: debug board connected
B -    608231 - vsense_init, Start
D -         0 - vsense_init, Delta
D -    322690 - sbl1_hw_pre_ddr_init
D -         0 - boot_dload_handle_forced_dload_timeout
D -      2989 - sbl1_load_ddr_training_data
B -    626927 - Pre_DDR_clock_init, Start
D -       244 - Pre_DDR_clock_init, Delta
D -     12902 - sbl1_ddr_set_params
B -    638639 - sbl1_ddr_init, Start
B -    642025 - LP5 DDR detected
B -    657031 - DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED,FREQ=DC,CHANNEL=0,CHIPSELECT=DC,BYTE=DC,BIT=DC,LIMIT=0x0,VALUE=0

B -    662765 - Error code 84 at ddr_external_api.c Line 464
B -    668377 - Call Stack:
B -    673897 - func_addr  :   1484CF64
B -    676490 - func_addr  :   1487BCE4
B -    680180 - ^^^^^^^^^^^^^^^^^^^^^
B -    683840 - sbl_error_handler FAIL: DDR not initialized
B -    687348 - sbl_crashdump_reset_with_dload: Ramdump not allowed. GoiFormat: 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.MXF.1.0.1-00549-KODIAKWP-1
S - IMAGE_VARIANT_STRING=SocKodiakWP
S - OEM_IMAGE_VERSION_STRING=wa-lxc
S - Boot Interface: SPI
S - Secure Boot: Off
S - Boot Config @ 0x00786070 = 0x000000c9
S - JTAG ID @ 0x00786130 = 0x001980e1
S - OEM ID @ 0x00786138 = 0x00000000
S - Serial Number @ 0x00786134 = 0x25313cae
S - OEM Config Row 0 @ 0x007841c0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841c8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x00784148 = 0x0000000000000000
S - Feature Config Row 1 @ 0x00784150 = 0x0000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 1
D -      6616 - pbl_apps_init_timestamp
D -      3434 - bootable_media_detect_timestamp
D -       811 - bl_elf_metadata_loading_timestamp
D -       703 - bl_hash_seg_auth_timestamp
D -     26496 - bl_elf_loadable_segment_loading_timestamp
D -      4621 - bl_elf_segs_hash_verify_timestamp
D -     17361 - bl_sec_hash_seg_auth_timestamp
D -       824 - bl_sec_segs_hash_verify_timestamp
D -        29 - pbl_populate_shared_data_and_exit_timestamp
S -     60895 - PBL, End
B -     69692 - SBL1, Start
B -    197853 - SBL1 BUILD @ 23:26:40 on Dec 30 2025
B -    201971 - usb: eud_serial_upd , 0x25313cae
D -    205295 - sbl1_hw_init
D -     10828 - boot_media_init
D -         0 - smss_load_cancel
B -    223565 - SMSS -  Image Load, Start
D -      3050 - SMSS -  Image Loaded, Delta - (0 Bytes)
D -       915 - Auth Metadata
D -      6039 - sbl1_xblconfig_init
B -    238327 - XBL Config -  Image Load, Start
D -         0 - shrm_load_cancel
B -    246013 - SHRM -  Image Load, Start
D -       610 - Auth Metadata
D -      1250 - Segments hash check
D -     12291 - SHRM -  Image Loaded, Delta - (39616 Bytes)
D -         0 - boot_default_cdt_init
D -       396 - boot_cdt_init
B -    270565 - CDT -  Image Load, Start
B -    273341 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:7
D -     16561 - sbl1_hw_platform_pre_ddr
D -         0 - devcfg init
B -    299357 - PMIC A:2.0 B:1.0 C:2.2 I:1.0
B -    301126 - PM: Reset by PSHOLD
B -    303475 - PM: Reset Type: Warm Reset
B -    306799 - PM: Warm reset count:0x1
B -    562572 - PM: SET_VAL:Skip
B -    564128 - PM: PSI: b0x06_v0x3f
B -    568184 - PM: Device Init # SPMI Transn: 15298
D -    279105 - pm_device_init, Delta
B -    573857 - pm_driver_init, Start
B -    585051 - PM: Driver Init # SPMI Transn: 504
D -      7747 - pm_driver_init, Delta
B -    589931 - PM: damsink err_flag = 0x0
B -    593225 - PM: dam aicl err_flag = 0x0
B -    597952 - PM: Battery ID: 10120Ohm
B -    601155 - PM: debug board connected
B -    604906 - vsense_init, Start
D -         0 - vsense_init, Delta
D -    322812 - sbl1_hw_pre_ddr_init
D -         0 - boot_dload_handle_forced_dload_timeout
B -    618631 - Pre_DDR_clock_init, Start
D -       213 - Pre_DDR_clock_init, Delta
D -      8906 - sbl1_ddr_set_params
B -    631289 - sbl1_ddr_init, Start
B -    634705 - LP5 DDR detected
B -    638243 - PASS1 Cookie =  0xff7fffff
B -    641079 - ALT_ARES Set, Before HAL_DDR_Init(), DBG PDC Tr = 0x0, First Pass expire = 0x0, First Pass complete = 0x0 , BIMC Alt ARES  = 0x0 , PASS2 Cookie = 0xdeadbabe 
B -    656421 - SHRM run state = 0x1 
B -    672159 - DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED,FREQ=DC,CHANNEL=0,CHIPSELECT=DC,BYTE=DC,BIT=DC,LIMIT=0x0,VALUE=0

B -    678289 - Error code 84 at ddr_external_api.c Line 464
B -    683505 - Call Stack:
B -    689025 - func_addr  :   1484CF64
B -    691618 - func_addr  :   1487BCE4
B -    695308 - ^^^^^^^^^^^^^^^^^^^^^
B -    698968 - sbl_error_handler FAIL: DDR not initialized
B -    702445 - boot_error_handler: Ramdump allowed. Trying to enter DLOAD
B -
7

I had a similar issue. The problem came from a faulty charger, that did not actually provide 12V even though it was labeled as 12v compliant. I changed the power supply and had no issues afterwards.

8

I forgot to mention that I tried many PSUs, all are OK and capable to deliver current way bigger than Dragon Q6A draws even in peak, e.g. laptop 65W USB-C PD PSU which is rated 5A on 12V.

9

Hello, I seem to fall exactly in the same category as some other people here before me.
I tried flashing all the available versions of the SPI firmware, they all fail at the same point.

Sequence: LP5 DDR detected → ch0 ok → ch1 probe → NO DEVICE → fatal abort

here’s a detailed report

Question:
Is there a firmware build or CDT configuration for the Dragon Q6A that supports single-channel LPDDR5 operation (ch0 only)? All published builds assume dual-channel, but channel 1 returns NO_MEMORY_DEVICE_DETECTED on this unit.

Alternatively: is DDR channel 1 expected to be present on all Dragon Q6A 6GB units? If so, this board may have a hardware defect on channel 1.

Do I understand correctly that the only way to solve this is to ask for an RMA?
Thank you for the support,

Patrick Predella

================================================================================
RADXA DRAGON Q6A — DDR INIT FAILURE — FULL BUILD COMPARISON
Board: Radxa Dragon Q6A, QCS6490 (Kodiak), 6GB LPDDR5
Serial: 0x1183CA6F
Date tested: 2026-05-25
================================================================================

RESULT: All 4 official Radxa firmware builds fail identically at DDR init.
        CHANNEL=1 probe returns no device, causing a fatal abort on every build.

--------------------------------------------------------------------------------
BUILD                  DATE        VARIANT     CDT       ERROR LOCATION
--------------------------------------------------------------------------------
flat_build_250801      Aug 2025    KODIAKLA    Sub:2     boot_platforminfo.c:76
                                  (LE/Linux)            14855D80 ← 14884B68

flat_build_251013      Oct 2025    KODIAKLA    Sub:2     boot_platforminfo.c:76
                                  (LE/Linux)            14855C74 ← 14884A5C

flat_build_wp_251230   Dec 2025    KODIAKWP    Sub:7     ddr_external_api.c:464
                                  (Windows)             1484CF64 ← 1487BCE4

flat_build_wp_260120   Jan 2026    KODIAKWP    Sub:7     ddr_external_api.c:464
                                  (Windows)             1484CF64 ← 1487BCE4
--------------------------------------------------------------------------------

COMMON FAILURE on all builds:
  DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED,FREQ=DC,CHANNEL=1,
             CHIPSELECT=DC,BYTE=DC,BIT=DC,LIMIT=0x0,VALUE=0
  Error code: 84
  Sequence: LP5 DDR detected → ch0 ok → ch1 probe → NO DEVICE → fatal abort

KEY OBSERVATIONS:
  1. Channel 0 DDR is functional — EDL firehose runs from DDR, flashing works perfectly.
  2. Channel 1 probe finds no device on every single firmware version.
  3. All firmware expects ch1 to be present (CDT Subtype:2 and Subtype:7 both include ch1).
  4. LE builds (KODIAKLA) and WP builds (KODIAKWP) are completely different XBL binaries
     with different crash addresses, but hit the same DDR_ABORT.
  5. LE builds load a pre-DDR device tree (DTB [pre-ddr][7601f201000000][0]); WP builds do not.
  6. Secure Boot: Off on all tests.
  7. PMIC, TZ, SHRM, AOP all load and authenticate successfully on all builds.
  8. The board has been tested with every available official firmware — no version boots.


UART LOGS:
  build_250801.txt       — full raw UART capture, Aug 2025 build
  build_251013_le.txt    — full raw UART capture, Oct 2025 LE build
  (Dec/Jan WP builds have identical output — available on request)
================================================================================


build_250801.txt

S - Format: Log Type - Time(microsec) - Message - Optional Info
S - Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.MXF.1.0.c1-00364-KODIAKLA-1
S - IMAGE_VARIANT_STRING=SocKodiakLAA
S - OEM_IMAGE_VERSION_STRING=wa-lxc
S - Boot Interface: SPI
S - Secure Boot: Off
S - Boot Config @ 0x00786070 = 0x000000c9
S - JTAG ID @ 0x00786130 = 0x001980e1
S - OEM ID @ 0x00786138 = 0x00000000
S - Seryal Number @ 0x00786134 = 0x1183ca6f
S - OEM Config Row 0 @ 0x007841c0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841c8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x00784148 = 0x0000000000000000
S - Feature Config Row 1 @ 0x00784150 = 0x0000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 1
D -      66?8 - pbl_apps_init_timestamp
D -      3408 - bootable_media_detect_timestamp
D -       701 - bl_elf_metadata_loading_timestamp
D -       712 - bl_hash_seg_auth_timestamp
D -     27925 - bl_elf_loadable_segment_loading_timestamp
D -      4839 - bl_elf_segs_hash_verify_timestamp
D -     17433 - bl_sec_hash_seg_auth_timestamp
D -       812 - bl_sec_segs_hash_verify_timestamp
D -        31 - pbl_populate_shared_data_and_exit_timestamp
S -     62479 - PBL, End
B -     70668 - SBL1, Start
B -    190076 - SBL1 BUILD @ 22:51:51 on Aug  1 2025
B -    194071 - usb: HS: device tree Not available , 0x3
B -    197426 - usb: eud_serial_upd , 0x1183ca6f
D -    202550 - sbl1_hw_init
D -     10614 - media_init:1
D -         0 - smss_load_cancel
D -         0 - boot_sail_pbl_edl_check
D -         0 - sail_execute_bist_sequence
B -    226889 - SMSS -  Image Load, Start
D -      3904 - SMSS -  ymage Loaded, Delta - (0 Bytes)
D -       976 - Auth Metadata
D -      5856 - sbl1_xblconfig_init
B -    242353 - XBL Config -  Image Load, Start
B -    246775 - DTB  Found: [pre-ddr][7601f201000000][0]
D -      4331 - boot_pre_ddr_dtb_load
D -         0 - media_init:2
D -         0 - media_init:3
D -         0 - boot_proc_bootset
D -        31 - shrm_load_cancel
B -    266966 - SHRM -  Image Load, Start
D -       610 - Auth Metadata
D -      1250 - Segments hash check
D -     12231 - SHRM -  Image Loaded, Delta - (35752 Bytes)
D -         0 - boot_default_cdt_init
D -       366 - boot_cdt_init
B -    291305 - CDT -  Image Load, Start
B -    294081 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:2
D -     16379 - sbl1_hw_platform_pre_ddr
D -         0 - devcfg init
B -    319792 - PMIC A:2.0 B:1.0 C:2.2 I:1.0
B -    321317 - PM: PM_DT_PARSING_ERR: charger
B -    324977 - PM: PM8 0x4
B -    328271 - PM: xVdd reset
B -    330681 - PM: PON by PWR key DEB
B -    586759 - PM: SET_VAL:Skip
B -    586759 - PM: Verifying PON-Trigger specific configurations & current PON-Trigger
B -    595512 - PM: All PON-Trigger specific configs verified. Proceeding to BOOT
B -    605303 - PM: PSI: b0x06_v0x3f
B -    607987 - PM: OEM_PSI Start
B -    608902 - PM: OEM_PSI Done
B -    611891 - PM: Device Init # SPMI Transn: 15440
D -    304451 - pm_device_init, Delta
B -    619729 - pm_driver_init, Start
B -    631197 - PM: Driver Init # SPMI Transn: 520
D -      8022 - pm_driver_init, Delta
B -    636840 - PM: Battery ID: 10105Ohm
B -    639371 - PM: debug board connected
B -    643092 - vsense_init, Start
D -        31 - vsense_init, Delta
D -    349134 - sbl1_hw_pre_ddr_init
D -         0 - boot_dload_handle_forced_dload_timeout
D -      2959 - sbl1_load_ddr_training_data
B -    668011 - Pre_DDR_clock_init, Start
D -        91 - Pre_DDR_clock_init, Delta
D -     12901 - sbl1_ddr_set_params
B -    679723 - sbl1_ddr_init, Start
B -    683139 - LP5 DDR detected
B -    698175 - DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED,FREQ=DC,CHANNEL=1,CHIPSELECT=DC,BYTE=DC,BIT=DC,LIMIT=0x0,VALUE=0

B -    704123 - Error code 84 at boot_platforminfo.c Line 76
B -    709552 - Call Stack:
B -    715072 - func_addr  :   14855D80
B -    717665 - func_addr  :   14884B68
B -    721325 - ^^^^^^^^^^^^^^^^^^^^^
B -    725015 - sbl_error_handler FAIL: D?

build_251013_le.txt

?S - Format: Log Type - Time(microsec) - Mess?ge - ptional Info
S - Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.MXF.1.0.c1-00364-KODIAKLA-1
S - IMAGE_VARIANT_STRING=SocKodiaoLAA
S - OEM_IMAGE_VERSION_StRING=wa-lxc
S - Boot Interface: SPI
S - Secure Boot: Off
S - Boot Config @ 0x0?7??????????????j??*HK??TAG ID @ 0x00786130 = 0x001980e1
S - OEM?ID @ 0x00786138 = 0x00000000
S - Serial Number @ 0x00786134 = 0x1183ca6f
S - OEM Config Row 0 @ 0x007841c0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841c8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x00784148 = 0x0000000000000000
S - Feature Config Row 1 @ 0x00784150 = 0x0000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 1
D -      6618 - pbl_apps_init_timestamp
D -      3407 - b??W,,[Y??V?XE?W?,]E????????5R?K??     702 - bl_elf_metadata_loading_timestamp
D -       708 - bl_hash_seg_auth_timestamp
D -     27925 - bl_elf_loadable_segment_loading_timestamp
D -      4838 - bl_elf_segs_hash_verify?timestamp
D -     17436 - bl_sec_hash_seg_auth_timestamp
D -       813 - bl_sec_segs_hash_verify_timestamp
D -        30 - pbl_populate_shared_data_and_exit_timestamp
S -     62477 / PBL, End
B -     70607 - SBL1, Start
B -    189832 - SBL1 BUILD @ 16:52:49 on Oct 13 2025
B -    193827 - usb: HS: device tree Not available , 0x3
B -    197213 - usb: eud_serial_upd , 0x1183ca6f
D -    202337 - sbl1_hw_init
D -     10614 - media_init:1
D /         0 - smss_load_cancel
D -        31 - boot_sail_pbl_edl_check
D -         0 - sail_execute_bist_sequence
B -    226645 - SMSS -  Image Load, Start
| -      3904 - SMSS -  Image Loaded, Delta - (0?????j?<Q?K?      976 - Auth Metadata
D -      5825 - sbl1_xblconfig_init
B -    242139 - X?L Config -  Image Load, Start
B -    246531 - DTB  Found: [pre-ddr][7601f201000000][0]
D -      4331 - boot_pre_ddr_dtb_load
D -         0 - [Y?ia_init:2
D -         0 - media_init:3
D -       ? 0 - boot_proc_bootset
D -        31 - sh~m_load_cancel
B -    266722 - SHRM -  Image Load, Start
D -       641 - Auth Metadata
D -      1342 - Segments hash check
D -     12292 - SHRM -  Image Loaded, Delta - (35752 Bytes)
D -         0 - boot_default_cdt_init
D -       366 - boot_cdt_init
B -    291092 - CDT -  Image Load< Start
B -    293867 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:2
D -     16378 - sbl1_hw_platform_pre_ddr
D -         0 - devcfg init
B -    319579 - PMIC A:2.0 B:1.0 C:2.2 I:1.0
B -    322141 - PM: PM8 0x4
B -   ?323818 - PO: xVdd reset
B -    ?26228 - PM: PON by PWR key DEB
B -    582275 - PM: SET_VAL:Skip
B -    582306 - PM: Verifying PON-Trigger specific configurations & current PON-Trigger
B -    591059 - PM: All PON-Trigger specific configs verified. Proceeding to BOOT
B -    600850 - PM: PSI: b0x06_v0x3f
B -    603534 - PM: OEM_PSI Start
B -    604449 - PM: OEM_PSI Done
B -    607438 - PM: Device Init # SPMI Transn: 15440
D -    300211 - pm_device_init< Delta
B -    615276 - pm_driver_init, Start
B -    626744 - PM: Driver Init # SPMI Transn: 520
D -      7991 - pm_driver_init, Delta
B -    632387 - PM: Battery ID: 10?05Ohm
B -    634888 - PM: debug board connected
B -    638639 - vsense_init, Start
D -         0 - vsense_Z?it, Delta
D -    344925 - sbl1_hw_pre_ddr_init
D -        30 - boot_dload_handle_forced_dload_timeout
D -      2989 - sbl1_load_ddr_training_data
B -    663558 / Pre_DDR_clock_init? Start
D -        61 - Pre_DDR_clock_init, Delta
D -     12901 - sb?1_ddr_set_params
B -    675270 - sbl1_ddr_init, Start
B -    678655 - LP5 DDR detected
B -    693722 - DDR_ABO^T: REASON=NO_MEMORY_DEVICE_DETECTED,FREQ=DC,CHANNEL=1,CHIPSELECT=DC,BYTE=DC,BIT=DC?*?*?U???b???UT?R?Hx(HK?   699670 - Error code 84 at boot_platforminfo.c Line 76
B -    705099 - Call Stack:
B -    710619 - func_addr  :   14855C74?
B -    713212 - func_addr  :   14884A5C
B -    716872 - ^^^^^^^^^^^^^^^^^^^^^
B -    720562 - sbl_error_handle.H?PR?: D?
10

I have already sent my Q6A for after-sales service once. The engineer told me the board was fine and that clearing the SPI should fix the issue. It did boot normally for a few weeks, but now the same problem has appeared again.

I want to know the correct way to fully clear SPI.

Following the official document, erase-part uefi fails because the uefi partition cannot be found. My SPI layout seems to contain ddr, devcfg, and xbl, but not uefi or abl.

I tried erasing ddr, devcfg, and xbl, then reflashing SPI with prog_firehose_lite.elf. Flashing succeeds, but the board still cannot boot and the serial log still shows:

DDR_ABORT: REASON=NO_MEMORY_DEVICE_DETECTED

Could someone please confirm the correct SPI cleanup procedure for this case?

11

You should just do the normal BIOS update process. IIRC there are some data on the SPI that is not part of the BIOS update package.

12

Is there anything else I can try? or should I ask for an RMA? (see previous message)