-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regarding system and RF parameters on esp-open-sdk #255
Comments
Can anyone please response? Thanks! |
Things have changed since sdk v1.3. The SDK attempts to load the RF calibration data from a sector of flash. Supposedly that should be done automatically if you flash it to the correct sector, but I've never been able to get it to work like that with esp-open-sdk, at least not with my project. The other thing is that init data default has configuration info that may not work for every esp, or you may want to change some of the things. What I do:
Also, for init_data_default, I copied the relevant parts from nodemcu. This injects the init_data_default into a known part of the program binary. |
em... interesting, I have found this function under "esp_open_sdk/user_rf_cal_sector_set.c", the default loading sector is to the forth from the end of flash.
BTW, I am very interested in how do you find this function, I tried to search about this on internet for long, but couldn't found a document explain it well. I am still not clear about how do I include it in a project like "esp_open_rtos"? Thanks very much @someburner . |
Seems esp-open-sdk does not load such parameters equal as ESP8266_RTOS_SDK,
In "esp-open-sdk/common.mk", the "bootloader/firmware_prebuilt/blank_config.bin" is hardcoded to flash to 0x1000, while the RF parameter "esp_init_data_default.bin" is not included.
According with documents from ESP8266 "2A-ESP8266__IOT_SDK_User_Manual__EN_v1.3.0.pdf", in section 6.1 mentioned that:
blank.bin shall be programmed to the second section from the end of flash
esp_init_data_default.bin stores default RF parameter values and to be written to the forth sector from the end of flash
The physical address is different according with flash size.
I am very curious that why does esp-open-sdk has this different settings? And the RF parameter is ignored? Does anyone know that?
@pfalcon
The text was updated successfully, but these errors were encountered: