Notifications
Clear all

[Solved] WiFi will NOT connect, constant NOT WL_CONNECTED

2 Posts
1 Users
0 Reactions
71 Views
Ron
 Ron
(@zander)
Father of a miniature Wookie
Joined: 4 years ago
Posts: 7140
Topic starter  

I have a sketch with a product so I am sure it is correct, and I am pretty sure it worked a few weeks ago.

The only thing I noticed that seems weird to me is that the status changes roughly on the 8th loop from 7 (WL_DISCONNECTED) to 1 (something wrong with SSID) 

That sounds like somebody is walking on memory. I have NO idea how to debug or use a debugger on this hardware (Wemos D1) like I am used to doing professionally.

Any ideas?

First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.


   
Quote
Ron
 Ron
(@zander)
Father of a miniature Wookie
Joined: 4 years ago
Posts: 7140
Topic starter  

Problem found and fixed. The HOSTNAME was recently expanded and ended up exactly 32 chars. This is NOT an RFC standard style which is limited to 24, but it is limited for OS-SDK use at 32 (full DHCP can go as high as 60 or so) The problem is, now they want to change a char[32] array to a String. That requires the addition of a null terminator. That stomped on a piece of my memory and somehow caused the failure.

I have tested 2 different sketches, one quite short and simple, the other quite long and complex. Both of these will work when the HOSTNAME is 26 chars, and will consistently fail at 32 chars.

First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.


   
ReplyQuote