Impact to WiFi Stability issues in NONOS sdk 2.1.0->2.2.0+

I’ve been on 2.1.0 for quite sometime and decided to take the leap to 3.0.0. After I did I started experiencing intermittent connection issues with my Wifi. Then also creating a snapshot I moved back to 2.1.0 and everything works great again. I also tested 3.0.1 and 3.0.2 and all yield the same issue and rolling back to 2.1.0 everything works. Does this having something to do with the new RF_CAL param added in userland or something else I may be missing from my upgrade? Any help would be amazing as I am currently stuck in the water right now with this specific issue.

As you can see in the first picture that is of my NONOS SDK 2.1.0. In the 2nd is the same exact code running on 2.2.0 and I get the same results and error each time unless I revert back to 2.1.0. It almost seems like when I do my Station_Init something in the new SDK or maybe the way I MAKE the sdk is jacking up the Radio. It seems at runtime the radio gets stuck in an off position or something I am not seeing but the 2.1.0 you see it kick off with “mode: 0 -> 3” and yet you never see that happen in the new versions. It seems like something in the SDK changed the behavior of connecting via Wifi? Futhermore, When I do a custom scan I can see one accesspoint that is on channel 9 but not my default “HHN” network that is on channel 6.

To add, This may be an issue on how I am upgrading my SDK. I use PFalcon’s toolchain and modify the make file to include the other sdk’s then run the following.

make clean-sdk clean-sysroot all Once completed I have to run a few post commands to fix a few things to get my SDK to run.

Fix1: Copy all the ld files located in esp-open-sdk/ESP8266_NONO_SDK-{VER} -> esp-open-sdk/xtensa-lx106-elf/sysroot/usr/lib. I then have to go into the files and update the include locations within the files to correct this. /* get ROM code address */ INCLUDE “../ld/eagle.rom.addr.v6.ld” -> INCLUDE “/eagle.rom.addr.v6.ld”

Fix2:[osboxes@osboxes i2c]$ make fresh xtensa-lx106-elf-gcc main.o -nostdlib -Wl,–start-group -lmain -lpwm -lnet80211 -lwpa -llwip -lpp -lphy -lc -Wl,–end-group -lgcc -o main /home/osboxes/esp-open-sdk/xtensa-lx106-elf/lib/gcc/xtensa-lx106-elf/4.8.5/../../../../xtensa-lx106-elf/bin/ld: main section .text' will not fit in regioniram1_0_seg’ /home/osboxes/esp-open-sdk/xtensa-lx106-elf/lib/gcc/xtensa-lx106-elf/4.8.5/../../../../xtensa-lx106-elf/bin/ld: region `iram1_0_seg’ overflowed by 956 bytes collect2: error: ld returned 1 exit status make: *** [main] Error 1

To fix this I then have to copy the libgcc.a to and from the location below esp-open-sdk/ESP8266_NONO_SDK-{VER}/lib/ -> esp-open-sdk/xtensa-lx106-elf/lib/gcc/xtensa-lx106-elf/4.8.5

I think I may have figured it out.. It appears in SDK 2.2.0 from 2.2.1 seems to have added an RSSI threshold to the Station_Config structure and I think that was filtering out my SSID’s during its scan, During the normal operation, I read back a flash structure and populate the structure with Data but maybe there’s Junk data that lives inside that structure when I try to use it in the NEW sdk and thus filters out my AccessPoint.. maybe due to invalid values in that structure member or that it is indeed valid but my SSID doesn’t mean the RSSI burden of whatever the Junk data was inside.

My sample code of what may have been getting affected by this new change in 2.2.0

Leave a comment

Your email address will not be published. Required fields are marked *