<warpme_>
i tested fw ver 7.45.96.61 and also a bit newer ver. (7.45.96.68). both are giving the same error. removing firmware changes nothing - so i think issue is in frcmfmac kernel code which is not ready yet for chip variant used in radxa-zero ap6256 wifi module
<warpme_>
re: mmc errors: pls find bootlog: https://pastebin.com/VT1tQUJY - i don't see any sdio related errors here. re: bsp driver - i asked radxa for access and awaiting for response. btw: generally: this small board is really killer for price-value. UI & general experience is very smooth. only issues so far are: wifi and cec.
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-amlogic
<warpme_>
interesting that F1 sig 0x15294345 is known (socitype:0x1 chip:0x4345 rev:0x9 pkg:0x2)
hipboi has quit [Remote host closed the connection]
hipboi has joined #linux-amlogic
sputnik has quit [Ping timeout: 265 seconds]
<xdarklight>
warpme_: [ 1.668438] mmc2: new ultra high speed SDR50 SDIO card at address 0001 => can you remove the UHS modes from &sd_emmc_a temporarily and see if that makes a difference?
<xdarklight>
warpme_: we had problems with eMMC and high clock speeds for a long time (there were some changes to the clock phase in the MMC driver). if it works then performance won't be as good but then at least we have narrowed it down a bit
<warpme_>
xdarklight: ok. i removed uhs modes in dt; dmesg now says "mmc2: new SDIO card at address 0001" Unfortunatelly error is exactly the same...
<xdarklight>
warpme_: too bad :-(
<xdarklight>
warpme_: since there are no MMC transfer errors (at least none that I can see) maybe some special handling is required for that chip (even though it seems to be supported). my suggestion is an email to the brcmfmac maintainers and asking for their advice on how to debug this
<warpme_>
indeed - that was also my idea :-). May you hint me how can i get current e-mail address?