Mini 5+ Wifi not working any more

Chriss

Hi *,

I have a Mini5+ here on my desk, just for testing purposes so it has no "usual" working configuration. I paned to play with the LEDs a bit but it is not connection to wifi any more.
I flashed 3.4 final a while ago the to board. The status LED is blinking in the usual rhythm, so I guess that the firmware booted.
I connected to the serial interface and tried to remove all known SSIDs to enter my SSID again.

The answer to "M558 S"*" was:

Error: M588: Failed to reset the WiFi module to factory settings: SPI timeout

The WiFi Module is started.

If I try to add my SSID again:

Error: M587: Failed to add SSID to remembered list: SPI timeout

M122

=== Diagnostics ===␊
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)␊
Board ID: 7LU1X-X296U-D65J0-40KML-2H03Z-RS9Y6␊
Used output buffers: 1 of 40 (1 max)␊
=== RTOS ===␊
Static ram: 103684␊
Dynamic ram: 108912 of which 204 recycled␊
Never used RAM 26056, free system stack 144 words␊
Tasks: NETWORK(ready,7.1%,373) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.0%,123) MAIN(running,92.0%,464) IDLE(ready,0.0%,29) AIN(delaying,0.8%,273), total 100.0%␊
Owned mutexes: USB(MAIN)␊
=== Platform ===␊
Last reset 00:35:12 ago, cause: power up␊
Last software reset details not available␊
Error status: 0x00␊
MCU revision 3, ADC conversions started 2112196, completed 2112194, timed out 0, errs 0␊
Step timer max interval 744␊
MCU temperature: min 19.4, current 25.4, max 25.9␊
Supply voltage: min 0.4, current 0.8, max 0.8, under voltage events: 0, over voltage events: 0, power good: no␊
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0␊
Events: 0 queued, 0 completed␊
Driver 0: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0␊
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0␊
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0␊
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0␊
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0␊
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0␊
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0␊
Date/time: 1970-01-01 00:00:00␊
Cache data hit count 4294967295␊
Slowest loop: 200.45ms; fastest: 0.12ms␊
=== Storage ===␊
Free file entries: 10␊
SD card 0 detected, interface speed: 22.5MBytes/sec␊
SD card longest read time 3.2ms, write time 0.0ms, max retries 0␊
=== Move ===␊
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000␊
=== MainDDARing ===␊
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1␊
=== AuxDDARing ===␊
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1␊
=== Heat ===␊
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0␊
=== GCodes ===␊
Segments left: 0␊
Movement lock held by null␊
HTTP is idle in state(s) 0␊
Telnet is idle in state(s) 0␊
File is idle in state(s) 0␊
USB is ready with "M122" in state(s) 0␊
Aux is idle in state(s) 0␊
Trigger is idle in state(s) 0␊
Queue is idle in state(s) 0␊
LCD is idle in state(s) 0␊
SBC is idle in state(s) 0␊
Daemon is idle in state(s) 0␊
Aux2 is idle in state(s) 0␊
Autopause is idle in state(s) 0␊
Code queue is empty␊
=== CAN ===␊
Messages queued 10561, received 0, lost 0, boc 0␊
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 10561/0/0␊
Tx timeouts 0,0,10560,0,0,0 last cancelled message type 30 dest 127␊
=== Network ===␊
Slowest loop: 41.89ms; fastest: 0.00ms␊
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions␊
HTTP sessions: 0 of 8␊
- WiFi -␊
Network state is changingMode␊
WiFi module is idle␊
Failed messages: pending 0, notready 0, noresp 2␊
Failed to get WiFi status␊
Socket states: 0 0 0 0 0 0 0 0␊
ok␊

I reflashed the Firmware and tried to create a SSID based on the wifi module:

Error: M589: Failed to configure access point parameters: SPI timeout

Is there anything I can do?

Wifi Module somehow bricked?

Cheers, Chriss

Phaedrux

Can you try sending these commands and report back what it says?

M552 S-1
M552 S0
M552 S1
M997 S1

Chriss

@phaedrux

M552 S-1

WiFi module stopped
ok

M552 S0

ok
WiFi module started

M552 S1

ok
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle

M997 S1

Trying to connect at 230400 baud:  success
Erasing 4096 bytes...
Erasing 196608 bytes...
Uploading file...
5% complete
10% complete
15% complete
20% complete
25% complete
30% complete
35% complete
40% complete
45% complete
50% complete
55% complete
60% complete
65% complete
70% complete
75% complete
80% complete
85% complete
90% complete
95% complete
Upload successful
ok␊
WiFi module started
WiFi reported error: no known networks found
WiFi module is idle
WiFi reported error: no known networks found
WiFi module is idle

I tried this afterwards:

M589 S"DuetSSID" P"12344321" I192.168.0.1 C1

And got the same error:

Error: M589: Failed to configure access point parameters: SPI timeout

Cheers, Chriss

jay_s_uk

@chriss send M552 S0 before sending your wifi details with M587

Chriss

@jay_s_uk

Still the same:

Error: M589: Failed to configure access point parameters: SPI timeout

Edit: I guessed that your M587 was a typo, M589....

But M587 reports the same anyway....

Cheers, Chriss

Phaedrux

Are you intending to set it up in access point mode or normal wireless client mode?

https://docs.duet3d.com/User_manual/Reference/Gcodes#m589-configure-access-point-parameters

Can you send M588 S"*" to clear out any saved SSIDs?

Then try sending M552 S0 and then try adding an SSID with M587.

https://docs.duet3d.com/User_manual/Reference/Gcodes#m587-add-wifi-host-network-to-remembered-list-or-list-remembered-networks

Do you still get the same SPI timeout error?

Can you take some close up photos of the solder points around the wifi module?

Chriss

@phaedrux said in Mini 5+ Wifi not working any more:

Are you intending to set it up in access point mode or normal wireless client mode?

It should be a normal wireless client. The idea to set it in AP mode was a just to see whether I can get it somehow working.

Can you send M588 S"*" to clear out any saved SSIDs?

Error: M588: Failed to reset the WiFi module to factory settings: SPI timeout
ok

Then try sending M552 S0 and then try adding an SSID with M587.

Wow, that did it somehow.... My understanding is that this is something I did in the past a couple of times without success. The Deletion reported the SPI timeout, the M587 S...... reported a ok now, the very first time and the M552 S1 did it with the wifi connection.

Can you take some close up photos of the solder points around the wifi module?

I guess that you do not need that any more after it is back working, don't you?

I do not understand why "M558 S"*" does report that error. Die the module be enabled for that? Or does it report that error when there is no SSID configured?

Cheers, Chriss

Phaedrux

I'm not really sure, but I'm glad it's working now.

Chriss

@phaedrux

Me too..... that is my "firmware" and "Config test" board here on my desk. I do not need that very often but it should smoothly work if I do not it.

It is a bit confusing that a shutdown period of 2 month resulted in a work like that. I hope that the board remains stable now.... The board is 4-5 month old....

Cheers, Chriss

dc42

@chriss I've seen "SPI timeout" messages occasionally when doing M587/588/589 operations, where the operation has actually succeeded. I think they occur when the wifi chip has to perform an erase operation on the area of flash memory used to hold the data.