HDC67

@Mateusz-Gwara I think you should create another GitHub issue for your instability problems. Microchip have indicated they won't fix their flawed method of determining transmit power without a business case...

For anyone following, Microchip have refused to fix this issue saying because they are focusing on new development and it's in the "backlog" whatever that means. i.e. I'd consider this...

Probably worth reading the response here: https://github.com/linux4wilc/driver/issues/30 We're told this is the official version, but yes there seems to be semi parallel efforts. So in the two years, no progress...

Do you know how to trigger it? I don't think I've seen that one before.

That works OK but is not what I listed in the reproduction method. You're also not using an SDIO connected device. Please try with what I posted, not something else....

Using -dev "updated demo binaries for release 15.2 RC1" is the commit message so no it doesn’t give the driver version. The master driver is much too old/broken to use....

Yes we are still seeing this. It seems more of a problem when the module is receiving traffic e.g. flood ping it or do a constant UDP iperf from another...

> > Yes we are still seeing this. It seems more of a problem when the module is receiving traffic e.g. flood ping it or do a constant UDP iperf...

> Hi, AdhamAbozaeid > can you get me a exact link to post this issue. The link you post above make me confuse. https://microchipsupport.force.com/s/article/How-to-submit-a-case

hostapd appears to work here too. However, the driver is logging an ERROR level message. So that's an ERROR, right? If this is defensive coding, the root cause should still...