On 11/24/2022 1:14 PM, Andy Green wrote:
On 11/24/22 09:42, Arend van Spriel wrote:On 11/18/2022 6:41 AM, Andy Green wrote:On 11/17/22 21:52, Arend Van Spriel wrote:I see. So could you load bcmdhd and provide log. Preferably with higher debug level. It also has a module parameter for it. I think it is called dhd_msg_level and please set it to 0x817.It's here: https://warmcat.com/ap6275p-dhd-log1.txtHi Andy,Thanks for the log. Together with the dhd driver sources I could make some sense of it. Perhaps you can try the following hack and see if we make it over the first hurdle.OH! I found that the line below should be count, not sizeof(count).
Good job! I was testing you obviously. You passed. Nah, I just feel stupid.
+ addr -= sizeof(count); + memcpy_toio(devinfo->tcm + addr, seed, count); +}With that, you were right on the money, the firmware comes up[ 3.796062] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 12 2022 18:54:54 version 18.35.387.23.146 (g412cc5ec) FWID 01-93c53be6along with wlP2p33s0: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether d4:9c:dd:f5:bf:7e txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I will try get it to scan... ... any way, good job!
Thanks. Will clean it up and formally submit it. I also had a quick look at the SDIO variant, but not seeing anything obvious there in terms of firmware loading.
Regards, Arend
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
