OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/shields/esp_8266/esp_8266_arduino.overlay

17 lines
272 B
Plaintext
Raw Normal View History

boards: shields: esp_8266: Add disco_l475_iot1 configs Add DISCO_L475_IOT1 board configurations to enable ESP-8266 WIFI modules. Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
2020-04-28 09:15:39 +08:00
/*
* Copyright (c) 2020 Gerson Fernando Budke <nandojve@gmail.com>
*
* SPDX-License-Identifier: Apache-2.0
*/
&arduino_serial {
status = "okay";
current-speed = <115200>;
esp8266 {
drivers: wifi: esp_at: rename driver from esp Recently WiFi ESP32 driver (utilizing WiFi radio in ESP32 SoC) was introduced into drivers/wifi/esp32/ and it already caused confusion as there was existing drivers/wifi/esp/ directory for ESP-AT driver (utilizing external WiFi chip, by communicating using AT commands from any serial capable platform). So question has arisen whether it is good to merge both, while they are totally different drivers. Rename ESP-AT driver to be placed in drivers/wifi/esp_at/, so that it is easier to figure out difference between "esp32" and "esp_at" just by looking at driver name. Rename also DT compatible and all Kconfig options for the same reason. Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
2021-05-06 16:51:46 +08:00
compatible = "espressif,esp-at";
boards: shields: esp_8266: Add disco_l475_iot1 configs Add DISCO_L475_IOT1 board configurations to enable ESP-8266 WIFI modules. Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
2020-04-28 09:15:39 +08:00
label = "esp8266";
status = "okay";
};
};