netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* wfx200 weird out-of-range power supply issue
@ 2025-06-05 13:40 Petko Manolov
  2025-06-06 12:13 ` Jérôme Pouiller
  0 siblings, 1 reply; 6+ messages in thread
From: Petko Manolov @ 2025-06-05 13:40 UTC (permalink / raw)
  To: netdev; +Cc: Jerome.Pouiller, David.Legoff

	Hey guys,

Apologies if this has been asked before, but i've searched and didn't find
anything related to this problem.  So here it goes: i'm upgrading the kernel of
a custom stm32mp15 board (from v5.4 to v6.6) and i've stumbled upon this when
wfx driver module get loaded:

wfx-spi spi0.0: sending configuration file wfx/wf200.pds      
wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20
... a bunch of "hif: 00000000: bc 04 e4 15 04 00 00 00 ec 00 74 76 f7 b7 cd 09" like messages ...
wfx-spi spi0.0: time out while polling control register       
wfx-spi spi0.0: chip is abnormally long to answer                                                       
wfx-spi spi0.0: chip did not answer                                                                     
wfx-spi spi0.0: hardware request CONFIGURATION (0x09) on vif 2 returned error -110                      
wfx-spi spi0.0: PDS:4: chip didn't reply (corrupted file?)                                              
wfx-spi: probe of spi0.0 failed with error -110       

Needless to say that v5.4 kernel setup works fine.  The only difference with
v6.6 is the wfx driver and kernel's DTB.  Now, i've verified that wf200 is
powered with 3.3V, in both cases, so that's not it.  I've also lowered the SPI
clock from 40000000 to 20000000 but it didn't make a difference.

By looking at the driver i'm fairly certain the above error is actually coming
from the wf200 firmware and the driver is just printing an error message so i
don't see reasonable ways of debugging this thing.  In short, any suggestion
would be greatly appreciated.


thanks guys,
Petko

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: wfx200 weird out-of-range power supply issue
  2025-06-05 13:40 wfx200 weird out-of-range power supply issue Petko Manolov
@ 2025-06-06 12:13 ` Jérôme Pouiller
  2025-06-06 14:01   ` Petko Manolov
  0 siblings, 1 reply; 6+ messages in thread
From: Jérôme Pouiller @ 2025-06-06 12:13 UTC (permalink / raw)
  To: netdev, Petko Manolov; +Cc: David.Legoff

On Thursday 5 June 2025 15:40:34 CEST Petko Manolov wrote:
>         Hey guys,
>
> Apologies if this has been asked before, but i've searched and didn't find
> anything related to this problem.  So here it goes: i'm upgrading the kernel of
> a custom stm32mp15 board (from v5.4 to v6.6) and i've stumbled upon this when
> wfx driver module get loaded:
> 
> wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20
> ... a bunch of "hif: 00000000: bc 04 e4 15 04 00 00 00 ec 00 74 76 f7 b7 cd 09" like messages ...
> wfx-spi spi0.0: time out while polling control register
> wfx-spi spi0.0: chip is abnormally long to answer
> wfx-spi spi0.0: chip did not answer
> wfx-spi spi0.0: hardware request CONFIGURATION (0x09) on vif 2 returned error -110
> wfx-spi spi0.0: PDS:4: chip didn't reply (corrupted file?)
> wfx-spi: probe of spi0.0 failed with error -110
> 
> Needless to say that v5.4 kernel setup works fine.  The only difference with
> v6.6 is the wfx driver and kernel's DTB.  Now, i've verified that wf200 is
> powered with 3.3V, in both cases, so that's not it.  I've also lowered the SPI
> clock from 40000000 to 20000000 but it didn't make a difference.
> 
> By looking at the driver i'm fairly certain the above error is actually coming
> from the wf200 firmware and the driver is just printing an error message so i
> don't see reasonable ways of debugging this thing.  In short, any suggestion
> would be greatly appreciated.

I believe you should have a trace with the firmware version (starting with
"started firmware x.x.x"). Could you provide the firmware versions?

The issue appears when the driver load the wf200.pds. Can you provide
the wf200.pds you used with 5.4 and with 6.6? Normally, you can't use
the same file since the format has changed in v5.17.

-- 
Jérôme Pouiller



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: wfx200 weird out-of-range power supply issue
  2025-06-06 12:13 ` Jérôme Pouiller
@ 2025-06-06 14:01   ` Petko Manolov
  2025-06-06 14:42     ` Jérôme Pouiller
  0 siblings, 1 reply; 6+ messages in thread
From: Petko Manolov @ 2025-06-06 14:01 UTC (permalink / raw)
  To: Jérôme Pouiller; +Cc: netdev, David.Legoff

[-- Attachment #1: Type: text/plain, Size: 3086 bytes --]

On 25-06-06 14:13:18, Jérôme Pouiller wrote:
> On Thursday 5 June 2025 15:40:34 CEST Petko Manolov wrote:
> >         Hey guys,
> >
> > Apologies if this has been asked before, but i've searched and didn't find
> > anything related to this problem.  So here it goes: i'm upgrading the kernel of
> > a custom stm32mp15 board (from v5.4 to v6.6) and i've stumbled upon this when
> > wfx driver module get loaded:
> > 
> > wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> > wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20
> > ... a bunch of "hif: 00000000: bc 04 e4 15 04 00 00 00 ec 00 74 76 f7 b7 cd 09" like messages ...
> > wfx-spi spi0.0: time out while polling control register
> > wfx-spi spi0.0: chip is abnormally long to answer
> > wfx-spi spi0.0: chip did not answer
> > wfx-spi spi0.0: hardware request CONFIGURATION (0x09) on vif 2 returned error -110
> > wfx-spi spi0.0: PDS:4: chip didn't reply (corrupted file?)
> > wfx-spi: probe of spi0.0 failed with error -110
> > 
> > Needless to say that v5.4 kernel setup works fine.  The only difference with
> > v6.6 is the wfx driver and kernel's DTB.  Now, i've verified that wf200 is
> > powered with 3.3V, in both cases, so that's not it.  I've also lowered the SPI
> > clock from 40000000 to 20000000 but it didn't make a difference.
> > 
> > By looking at the driver i'm fairly certain the above error is actually coming
> > from the wf200 firmware and the driver is just printing an error message so i
> > don't see reasonable ways of debugging this thing.  In short, any suggestion
> > would be greatly appreciated.
> 
> I believe you should have a trace with the firmware version (starting with
> "started firmware x.x.x"). Could you provide the firmware versions?

Here's what i get with the new firmware:

wfx-spi spi0.0: started firmware 3.17.0 "WF200_ASIC_WFM_(Jenkins)_FW3.17.0" (API: 3.12, keyset: C0, caps: 0x00000000)                                                  
wfx-spi spi0.0: sending configuration file wfx/wf200.pds      
wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20 

This is with the old one:

wfx-spi spi0.0: started firmware 3.12.2 "WF200_ASIC_WFM_(Jenkins)_FW3.12.2" (API: 3.7, keyset: C0, caps: 0x00000000)
wfx-spi spi0.0: sending configuration file wfx/wf200.pds      
wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -21

Apart from the error number the rest is pretty much the same.  Both dumps from
using wf200-v6.6.pds (attached) as the old .pds won't load on v6.6.

> The issue appears when the driver load the wf200.pds. Can you provide
> the wf200.pds you used with 5.4 and with 6.6? Normally, you can't use
> the same file since the format has changed in v5.17.

Attached you'll find both, old and new, versions of the PDS.  This is what i
used to generate the v6.6 version:

pds_compress -l BRD8023A_Rev_B01.pds.in wf200-v6.6.pds

The old one used '-p' instead of '-l', but this is due to the format change, as
you mentioned above.

Thank you for your time, Jérôme.  Much appreciated.


		Petko


[-- Attachment #2: wf200-v5.4.pds --]
[-- Type: text/plain, Size: 596 bytes --]

{a:{a:4,b:1},b:{a:{a:4,b:0,c:0,d:0,e:A},b:{a:4,b:0,c:0,d:0,e:B},c:{a:4,b:0,c:0,d:0,e:C},d:{a:4,b:0,c:0,d:0,e:D},e:{a:4,b:0,c:0,d:0,e:E},f:{a:4,b:0,c:0,d:0,e:F},g:{a:4,b:0,c:0,d:0,e:G},h:{a:4,b:0,c:0,d:0,e:H},i:{a:4,b:0,c:0,d:0,e:I},j:{a:4,b:0,c:0,d:0,e:J},k:{a:4,b:0,c:0,d:0,e:K},l:{a:4,b:0,c:0,d:1,e:L},m:{a:4,b:0,c:0,d:1,e:M}},c:{a:{a:4},b:{a:6},c:{a:6,c:0},d:{a:6},e:{a:6},f:{a:6}},e:{b:0,c:1},h:{e:0,a:50,b:0,d:0,c:[{a:1,b:[0,0,0,0,0,0]},{a:2,b:[0,0,0,0,0,0]},{a:[3,9],b:[0,0,0,0,0,0]},{a:A,b:[0,0,0,0,0,0]},{a:B,b:[0,0,0,0,0,0]},{a:[C,D],b:[0,0,0,0,0,0]},{a:E,b:[0,0,0,0,0,0]}]},j:{a:0,b:0}}

[-- Attachment #3: wf200-v6.6.pds --]
[-- Type: application/octet-stream, Size: 625 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: wfx200 weird out-of-range power supply issue
  2025-06-06 14:01   ` Petko Manolov
@ 2025-06-06 14:42     ` Jérôme Pouiller
  2025-06-10 14:55       ` Petko Manolov
  2025-06-24 18:09       ` Petko Manolov
  0 siblings, 2 replies; 6+ messages in thread
From: Jérôme Pouiller @ 2025-06-06 14:42 UTC (permalink / raw)
  To: Petko Manolov; +Cc: netdev, David.Legoff

On Friday 6 June 2025 16:01:43 CEST Petko Manolov wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> 
> On 25-06-06 14:13:18, Jérôme Pouiller wrote:
> > On Thursday 5 June 2025 15:40:34 CEST Petko Manolov wrote:
> > >         Hey guys,
> > >
> > > Apologies if this has been asked before, but i've searched and didn't find
> > > anything related to this problem.  So here it goes: i'm upgrading the kernel of
> > > a custom stm32mp15 board (from v5.4 to v6.6) and i've stumbled upon this when
> > > wfx driver module get loaded:
> > >
> > > wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> > > wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20
> > > ... a bunch of "hif: 00000000: bc 04 e4 15 04 00 00 00 ec 00 74 76 f7 b7 cd 09" like messages ...
> > > wfx-spi spi0.0: time out while polling control register
> > > wfx-spi spi0.0: chip is abnormally long to answer
> > > wfx-spi spi0.0: chip did not answer
> > > wfx-spi spi0.0: hardware request CONFIGURATION (0x09) on vif 2 returned error -110
> > > wfx-spi spi0.0: PDS:4: chip didn't reply (corrupted file?)
> > > wfx-spi: probe of spi0.0 failed with error -110
> > >
> > > Needless to say that v5.4 kernel setup works fine.  The only difference with
> > > v6.6 is the wfx driver and kernel's DTB.  Now, i've verified that wf200 is
> > > powered with 3.3V, in both cases, so that's not it.  I've also lowered the SPI
> > > clock from 40000000 to 20000000 but it didn't make a difference.
> > >
> > > By looking at the driver i'm fairly certain the above error is actually coming
> > > from the wf200 firmware and the driver is just printing an error message so i
> > > don't see reasonable ways of debugging this thing.  In short, any suggestion
> > > would be greatly appreciated.
> >
> > I believe you should have a trace with the firmware version (starting with
> > "started firmware x.x.x"). Could you provide the firmware versions?
> 
> Here's what i get with the new firmware:
> 
> wfx-spi spi0.0: started firmware 3.17.0 "WF200_ASIC_WFM_(Jenkins)_FW3.17.0" (API: 3.12, keyset: C0, caps: 0x00000000)
> wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20
> 
> This is with the old one:
> 
> wfx-spi spi0.0: started firmware 3.12.2 "WF200_ASIC_WFM_(Jenkins)_FW3.12.2" (API: 3.7, keyset: C0, caps: 0x00000000)
> wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -21
> 
> Apart from the error number the rest is pretty much the same.  Both dumps from
> using wf200-v6.6.pds (attached) as the old .pds won't load on v6.6.
> 
> > The issue appears when the driver load the wf200.pds. Can you provide
> > the wf200.pds you used with 5.4 and with 6.6? Normally, you can't use
> > the same file since the format has changed in v5.17.
> 
> Attached you'll find both, old and new, versions of the PDS.  This is what i
> used to generate the v6.6 version:
> 
> pds_compress -l BRD8023A_Rev_B01.pds.in wf200-v6.6.pds
> 
> The old one used '-p' instead of '-l', but this is due to the format change, as
> you mentioned above.

Things are going to start to become fun. Your wf200-v6.6.pds is exactly the
same (same md5sum) than the one I use for ages. So the issue is not on this
side.

For info, I have a setup with kernel 6.1 + firmware 3.16.0 + Raspberry Pi
here.

Do you think your power supply could be unstable with your new DT? 

The voltage values reported by the driver (-21 and -20) are obviously not
correct. Maybe it would make sense to get the real value measured by the
chip. Do you have access to official Silabs support to make that request?




-- 
Jérôme Pouiller



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: wfx200 weird out-of-range power supply issue
  2025-06-06 14:42     ` Jérôme Pouiller
@ 2025-06-10 14:55       ` Petko Manolov
  2025-06-24 18:09       ` Petko Manolov
  1 sibling, 0 replies; 6+ messages in thread
From: Petko Manolov @ 2025-06-10 14:55 UTC (permalink / raw)
  To: Jérôme Pouiller; +Cc: netdev, David.Legoff

On 25-06-06 16:42:42, Jérôme Pouiller wrote:
> 
> Do you think your power supply could be unstable with your new DT?

The DT says it should be 3.3V, that part is OK.

> The voltage values reported by the driver (-21 and -20) are obviously not
> correct. Maybe it would make sense to get the real value measured by the chip.
> Do you have access to official Silabs support to make that request?

I'm on vacation and unfortunately my replies are delayed.

Funny enough the actual voltage measured is 0.65V which is way below the nominal
value.  It seems that i'll have to debug the stpmic1 now instead of wfx driver.
:)

Again, thanks for your time.


		Petko

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: wfx200 weird out-of-range power supply issue
  2025-06-06 14:42     ` Jérôme Pouiller
  2025-06-10 14:55       ` Petko Manolov
@ 2025-06-24 18:09       ` Petko Manolov
  1 sibling, 0 replies; 6+ messages in thread
From: Petko Manolov @ 2025-06-24 18:09 UTC (permalink / raw)
  To: Jérôme Pouiller; +Cc: netdev, David.Legoff

On 25-06-06 16:42:42, Jérôme Pouiller wrote:
> 
> Things are going to start to become fun. Your wf200-v6.6.pds is exactly the
> same (same md5sum) than the one I use for ages. So the issue is not on this
> side.
> 
> For info, I have a setup with kernel 6.1 + firmware 3.16.0 + Raspberry Pi
> here.
> 
> Do you think your power supply could be unstable with your new DT? 

Yes, this turned out to be the case.  Now the chip appears to be powered up and i
get nice and very promising:

[   33.960683] wfx-spi spi0.0: started firmware 3.17.0 "WF200_ASIC_WFM_(Jenkins)_FW3.17.0" (API: 3.12, keyset: C0, caps: 0x00000000)                                               
[   33.991401] wfx-spi spi0.0: sending configuration file wfx/wf200.pds                                                                                                            
[   34.006885] wfx-spi spi0.0: enable 'quiescent' power mode with wakeup GPIO and PDS file wfx/wf200.pds
[   34.007212] wfx-spi spi0.0: MAC address 0: 84:fd:27:71:72:f7                          
[   34.011703] wfx-spi spi0.0: MAC address 1: 84:fd:27:71:72:f8
[   34.045198] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'

However, when i do "ip link set dev wlan0 up" i get:

[  118.481024] wfx-spi spi0.0: timeout while wake up chip             
[  118.501051] wfx-spi spi0.0: timeout while wake up chip        
[  118.521142] wfx-spi spi0.0: timeout while wake up chip            
[  118.541059] wfx-spi spi0.0: max wake-up retries reached   

Could this be an issue with:

"enable 'quiescent' power mode with wakeup GPIO and PDS file wfx/wf200.pds"

from the kernel log?


thanks,
Petko

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2025-06-24 18:10 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-05 13:40 wfx200 weird out-of-range power supply issue Petko Manolov
2025-06-06 12:13 ` Jérôme Pouiller
2025-06-06 14:01   ` Petko Manolov
2025-06-06 14:42     ` Jérôme Pouiller
2025-06-10 14:55       ` Petko Manolov
2025-06-24 18:09       ` Petko Manolov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).