When building STANDALONE=y toolchain fails to build do to lwip library
failing to build. Lwip library file "liblwip_open.a" fails to build
because its looking for xtensa-lx106-elf-ar in wrong path. Proposed fix
is to pass the correct AR path to esp-open-lwip/Makefile.open as it was
done with CC path.
"arch" directory (and somewhat "netif" too) aren't namespaced well enough,
but they're still kind of system headers, as lwIP is a foundation of ESP
networking, so any conflicts would be problem of conflicting packages.
Espressif releases are imported into https://github.com/pfalcon/esp-open-lwip
And that's what added as a submodule. Includes simple no-nonsense Makefile,
and going forward, may include patches or be switched to upstream lwIP with
ESP-specific patches altogether.
http://bbs.espressif.com/viewtopic.php?f=46&t=1702
"""
Release Notes
Resolved Issues(Bugs below are eligible for Bug Bounty Program):
Strange os_timer_arm behavior.
Optimization:
Added SDIO slave driver. Developers are now able to implement AT commands based on SDIO interface by themselves.
Optimized SSL shakehand.
Upgraded second-level boot to support HSPI flash.
Added AirKiss library.
Updated sample code smart_config (esp_iot_sdk\examples\smart_config).
The 114th byte of esp_init_data_default.bin is modified to be 1. Please use the latest esp_init_data_default.bin.
Added sample code at_espconn (esp_iot_sdk\examples\at_espconn), showing how to transmit AT commands via the internet.
Added APIs:
SDIO slave APIs
sdio_slave_init: initialize SDIO slave
sdio_load_data: upload data to SDIO buffer.
sdio_register_recv_cb: register Callbacks of data received by SDIO.
AirKiss APIs
airkiss_version: get version information of AirKiss.
airkiss_lan_recv: used to detect and analyze AirKiss data packets.
airkiss_lan_pack: used to analyze AirKiss data packets, and to organize response packets waiting to be responded.
AT UART simulation APIs
at_fake_uart_enable : enable AT UART simulation.
at_fake_uart_rx : AT UART RX for simulation.
Known Issue:
SSL misbehavior.
"""
1.5.0 factored out some crypto functions to libcrypto.a, but software built
with older SDK versions oftentimes doesn't link with that lib, so put related
objects back to a lib they were in previously, specifically merge libcrypto.a
content into libwpa.a.
Caveat: this may lead to further issues when using new libwpa2.a, so may need
tweaks in the future.
