IPQ6018 issues

John Crispin john at phrozen.org
Tue May 4 09:50:15 PDT 2021


On 04.05.21 18:35, Robert Marko wrote:
> Hi,
>
> I am trying to use ath11k on multiple IPQ6018 and IPQ6010 boards,
> unfortunately, they will all fail like this:

I have observed the same on ipq807x. This crash happens when the driver 
does the first access to AHB memory if i recall correctly

     John


>> # echo c000000.wifi > /sys/bus/platform/drivers/ath11k/bind
>> [   12.417214] ath11k c000000.wifi: event type: 0
>> [   12.417557] ath11k c000000.wifi: qmi ignore invalid mem req type 3
>> [   12.420605] ath11k c000000.wifi: event type: 2
>> [   12.427191] ath11k c000000.wifi: event type: 3
>> [   12.431312] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0xff soc_id 0xffffffff
>> [   12.435626] ath11k c000000.wifi: fw_version 0x240606c6 fw_build_timestamp 2021-02-12 03:17 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HK.2.4.0.1-01734-QCAHKSWPL_SILICONZ-1
>> [   12.447560] ath11k c000000.wifi: event type: 4
>> [   12.459215] ath11k c000000.wifi: ATH11K_QMI_EVENT_FW_READY
>> [   12.463551] ath11k c000000.wifi: ath11k_core_qmi_firmware_ready
>> [   12.469013] ath11k c000000.wifi: ath11k_core_qmi_firmware_ready start
>> [   12.474900] ath11k c000000.wifi: ath11k_ce_init_pipes pass
>> # [   12.491124] ath11k c000000.wifi: ath11k_crypto_mode: 0
>>
>> 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-00098-IPQ60xxLZB-1
>> S - IMAGE_VARIANT_STRING=IPQ6018LA
>> S - OEM_IMAGE_VERSION_STRING=crm-ubuntu121
>> S - Boot Interface: SPI
>> S - Secure Boot: Off
>> S - Boot Config @ 0x000a602c = 0x000002e1
>> S - JTAG ID @ 0x000a607c = 0x0013a0e1
>> S - OEM ID @ 0x000a6080 = 0x00000000
>> S - Serial Number @ 0x000a4128 = 0xd92ca102
>> S - OEM Config Row 0 @ 0x000a4188 = 0x0000000000000000
>> S - OEM Config Row 1 @ 0x000a4190 = 0x0000000000000000
>> S - Feature Config Row 0 @ 0x000a4130 = 0x0000000008000001
>> S - Feature Config Row 1 @ 0x000a4138 = 0x02c3e83383000009
>> S - PBL Patch Ver: 1
>> S - I-cache: On
>> S - D-cache: On
>> B -      3413 - PBL, Start
>> B -       592 - bootable_media_detect_entry, Start
>> B -      4339 - bootable_media_detect_success, Start
>> B -      4435 - elf_loader_entry, Start
>> B -      4607 - auth_hash_seg_entry, Start
>> B -     10854 - auth_hash_seg_exit, Start
>> B -     11350 - elf_segs_hash_verify_entry, Start
>> B -    357983 - elf_segs_hash_verify_exit, Start
>> B -    362173 - auth_xbl_sec_hash_seg_entry, Start
>> B -    362318 - auth_xbl_sec_hash_seg_exit, Start
>> B -    368868 - xbl_sec_segs_hash_verify_entry, Start
>> B -    368869 - xbl_sec_segs_hash_verify_exit, Start
>> B -    369798 - PBL, End
>> B -    296002 - SBL1, Start
>> B -    435814 - GCC [RstStat:0x2, RstDbg:0x420100] WDog Stat : 0x4
>> B -    438254 - clock_init, Start
>> D -      3812 - clock_init, Delta
>> B -    447862 - boot_flash_init, Start
>> D -      8082 - boot_flash_init, Delta
>> B -    458201 - sbl1_ddr_set_default_params, Start
>> D -       274 - sbl1_ddr_set_default_params, Delta
>> B -    464820 - boot_config_data_table_init, Start
>> D -      1891 - boot_config_data_table_init, Delta - (575 Bytes)
>> B -    473970 - CDT Version:2,Platform ID:8,Major ID:3,Minor ID:0,Subtype:0
>> B -    479490 - Image Load, Start
>> D -      6619 - OEM_MISC Image Loaded, Delta - (0 Bytes)
>> B -    488823 - Image Load, Start
>> D -      5063 - PMIC Image Loaded, Delta - (0 Bytes)
>> B -    496692 - sbl1_ddr_set_params, Start
>> B -    501694 - CPR configuration: 0x366
>> B -    504897 - Pre_DDR_clock_init, Start
>> D -       183 - Pre_DDR_clock_init, Delta
>> D -         0 - sbl1_ddr_set_params, Delta
>
> I added most of the prints to figure out where it dies.
> If cold-boot calibration is enabled then it will die on the
> ath11k_qmi_process_coldboot_calibration(), to be exact on the
>> ret = ath11k_qmi_wlanfw_mode_send(ab, ATH11K_FIRMWARE_MODE_COLD_BOOT);
>
> But, if cold-boot calibration is disabled then ti will fail in
> ath11k_core_qmi_firmware_ready at or after ath11k_crypto_mode switch.
>
> A big issue is that it will crash the board and it will get stuck in
> SBL, only removing the power will help.
>
> The hardware I tried on is:
> * Wallys CP01-C1
> * Wallys CP03-C1
> * Alfa AP1800C-AX PRO
>
> I also tried fw versions from 2.1.0.1 to 2.5.0.1-R2
>
> Does anybody have an idea how to solve this?
>



More information about the ath11k mailing list