Enable EDL mode in a WP982 rev. B access point with IPQ53xx

Hello,

I have an AP with the main board is WP982 rev B. It uses a chip IPQ53xx. I’m building QSDK to it.

The problem is I made a mistake and erased u-boot, so now I need to find a way to enable EDL mode to rewrite the basic files. I couldn’t find anything like test points (I can send a photo).

Here is the log I got from USB-C port:

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.0.3.1.1-00086-IPQ90xxLZB-2
S - IMAGE_VARIANT_STRING=IPQ5332LA
S - OEM_IMAGE_VERSION_STRING=crm-ubuntu142
S - Boot Interface: NAND
S - Secure Boot: Off
S - Boot Config @ 0x000a602c = 0x000002c5
S - JTAG ID @ 0x000a607c = 0x1023d0e1
S - OEM ID @ 0x000a6080 = 0x00000000
S - Serial Number @ 0x000a60a8 = 0xd76fb737
S - OEM Config Row 0 @ 0x000a4058 = 0x0000000000000000
S - OEM Config Row 1 @ 0x000a4060 = 0x0000000000000000
S - Feature Config Row 0 @ 0x000a4018 = 0x0000800004000001
S - Feature Config Row 1 @ 0x000a4020 = 0x0000000000000000
S - Feature Config Row 2 @ 0x000a4028 = 0x0000000000000000
S - FM_VERSION @ 0x000a4004 = 0x00000005
S - TAG_VERSION @ 0x000a4004 = 0x00000000
S - FEATURE ID @ 0x000a4000 = 0x00000000
S - PBL Patch Ver: 1
S - TME-L LCS: 0x0b
S - I-cache: Off
S - D-cache: Off
B -      3413 - PBL, Start
B -       959 - bootable_media_detect_entry, Start
B -      2474 - bootable_media_detect_success, Start
B -      4459 - elf_loader_entry, Start
B -      4462 - auth_hash_seg_entry, Start
B -      9736 - auth_hash_seg_exit, Start
B -     10387 - elf_segs_hash_verify_entry, Start
B -    214277 - elf_segs_hash_verify_exit, Start
B -    282999 - auth_xbl_sec_hash_seg_entry, Start
B -    283059 - auth_xbl_sec_hash_seg_exit, Start
B -    305226 - xbl_sec_segs_hash_verify_entry, Start
B -    305228 - xbl_sec_segs_hash_verify_exit, Start
B -    325028 - PBL, End
B -    280813 - SBL1, Start
B -   1084061 - GCC [RstStat:0x10, RstDbg:0x600000] WDog Stat : 0x4
B -   1086837 - System Reset Reason : Power on Reset [0x20]
B -   1092388 - clock_init, Start
D -       579 - clock_init, Delta
B -   1100348 - boot_flash_init, Start
D -     30591 - boot_flash_init, Delta
B -   1133990 - sbl1_ddr_set_default_params, Start
D -        61 - sbl1_ddr_set_default_params, Delta
B -   1140578 - boot_config_data_table_init, Start
D -      3721 - boot_config_data_table_init, Delta - (615 Bytes)
B -   1149484 - CDT Version:2,Platform ID:8,Major ID:6,Minor ID:0,Subtype:0
B -   1155187 - Image Load, Start
D -      6619 - OEM_MISC Image Loaded, Delta - (0 Bytes)
B -   1164581 - Image Load, Start
D -      5002 - PMIC Image Loaded, Delta - (0 Bytes)
B -   1172450 - sbl1_ddr_set_params, Start
B -   1177208 - CPR configuration: 0x3a7
B -   1180655 - Pre_DDR_clock_init, Start
D -        30 - Pre_DDR_clock_init, Delta
D -         0 - sbl1_ddr_set_params, Delta
B -   1253153 - Image Load, Start
D -       122 - APDP Image Loaded, Delta - (0 Bytes)
B -   1259162 - Image Load, Start
D -     34434 - TME-L FW Image Loaded, Delta - (49592 Bytes)
B -   1293779 - Image Load, Start
D -      2288 - Auth Metadata
D -      4727 - Segments hash check
D -     24126 - QSEE Dev Config Image Loaded, Delta - (35096 Bytes)
B -   1320040 - Image Load, Start
D -    126270 - Auth Metadata
D -    198220 - Segments hash check
D -    684969 - QSEE Image Loaded, Delta - (1466408 Bytes)
B -   2005649 - Image Load, Start
B -   2011841 - Error code 3700fffe at /local/mnt/workspace/CRMBuilds/BOOT.XF.0.3.1.1-00086-IPQ90xxLZB-2_20230829_231234/b/boot_images/QcomPkg/XBLLoader/boot_config.c Line 488

Anyone have any idea about how to rewrite the basic files?

Thanks for any help.

This is not from the OpenWrt project. You need to reach out to Qualcomm or whoever provided the SDK.

I posted here because I saw folks talking about IPQ53xx. It’s not actually about OpenWrt/QSDK, but the hardware level. Got it?

precisely.

You're using an SDK that is not provided by the OpenWrt project. That means that things behave differently, regardless of the underlying hardware. That is why you need to ask the vendor of the SDK.

I moved the question to hardware. If anyone knows this board maybe they could provide a tip.