menu "ESP8266-specific" config APP_OFFSET hex default 0x1000 choice NEWLIB_STDOUT_LINE_ENDING prompt "Line ending for UART output" default NEWLIB_STDOUT_LINE_ENDING_CRLF help This option allows configuring the desired line endings sent to UART when a newline ('\n', LF) appears on stdout. Three options are possible: CRLF: whenever LF is encountered, prepend it with CR LF: no modification is applied, stdout is sent as is CR: each occurence of LF is replaced with CR This option doesn't affect behavior of the UART driver (drivers/uart.h). config NEWLIB_STDOUT_LINE_ENDING_CRLF bool "CRLF" config NEWLIB_STDOUT_LINE_ENDING_LF bool "LF" config NEWLIB_STDOUT_LINE_ENDING_CR bool "CR" endchoice config SOC_FULL_ICACHE bool "Enable full cache mode" default n help Enable this option, full 32 KB iram instead of 16 KB iram will be used as icache, so the heap use can use may reduce a lot. choice CONSOLE_UART_NUM prompt "UART peripheral to use for console output (0-1)" default CONSOLE_UART_CUSTOM_NUM_0 help Configrate output console UART for "ets_printf", "printf", "ESP_LOGX" and so on. config CONSOLE_UART_CUSTOM_NUM_0 bool "UART0" config CONSOLE_UART_CUSTOM_NUM_1 bool "UART1" endchoice config CONSOLE_UART_NUM int default 0 if CONSOLE_UART_CUSTOM_NUM_0 default 1 if CONSOLE_UART_CUSTOM_NUM_1 config CONSOLE_UART_BAUDRATE int "UART console baud rate" default 74880 range 1200 4000000 config CONSOLE_UART_SWAP_IO bool "Swap UART0 I/O pins" default n help Enable this option, UART0's I/O pins are swaped: TXD <-> RTS, RTX <-> CTS. endmenu menu WIFI config SCAN_AP_MAX int "Max scan AP number" range 1 64 default 32 help Function "esp_wifi_scan_get_ap_num" return value will be less than this. It is said that user cannot scan more than this. User can use own function "esp_wifi_scan_get_ap_num_max" to determin how many AP to scan , too. config WIFI_TX_RATE_SEQUENCE_FROM_HIGH bool "Set wifi tx rate from 54M to 1M" default n help If this option is enabled, Wifi will try to send packets first from high rate(54M). If it fails, it will try at low rate until the transmission is successful. endmenu menu PHY config ESP_PHY_CALIBRATION_AND_DATA_STORAGE bool "Store phy calibration data in NVS" default y help If this option is enabled, NVS will be initialized and calibration data will be loaded from there. PHY calibration will be skipped on deep sleep wakeup. If calibration data is not found, full calibration will be performed and stored in NVS. Normally, only partial calibration will be performed. If this option is disabled, full calibration will be performed. If it's easy that your board calibrate bad data, choose 'n'. Two cases for example, you should choose 'n': 1.If your board is easy to be booted up with antenna disconnected. 2.Because of your board design, each time when you do calibration, the result are too unstable. If unsure, choose 'y'. config ESP_PHY_INIT_DATA_IN_PARTITION bool "Use a partition to store PHY init data" default n help If enabled, PHY init data will be loaded from a partition. When using a custom partition table, make sure that PHY data partition is included (type: 'data', subtype: 'phy'). With default partition tables, this is done automatically. If PHY init data is stored in a partition, it has to be flashed there, otherwise runtime error will occur. If this option is not enabled, PHY init data will be embedded into the application binary. If unsure, choose 'n'. endmenu # PHY