OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/xtensa/esp32/esp32_defconfig

46 lines
800 B
Plaintext
Raw Normal View History

boards: xtensa: Add ESP32 board This is based on the work of Rajavardhan Gundi. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-05-04 05:29:36 +08:00
CONFIG_XTENSA=y
CONFIG_XTENSA_RESET_VECTOR=n
CONFIG_BOARD_ESP32=y
CONFIG_SOC_ESP32=y
CONFIG_MAIN_STACK_SIZE=2048
esp32: Fix board cycle frequency The ESP-WROOM-32 board exits the bootloader at 40 MHz, not 160 MHz as suggested by documentation. The CCOUNT special register works as advertised, but not at the expected rate. This was verified by timestamping (at the host) the output of a dependency-free loop that looks like: int key = irq_lock(); while(1) { u32_t i, count; volatile int dummy; for(i = 0; i < 5000000; i++) { dummy++; } __asm__ volatile ("rsr.ccount %0" : "=a"(count)); printk("%d\n", count); } The SoC has a fairly robust set of possible CPU clocking modes, but we don't have a driver for that yet. Until we do, set the single configured CPU frequency to the one we get at runtime. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2017-08-10 06:06:56 +08:00
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=40000000
drivers: esp32: Add minimal UART driver based on ROM routines This is a minimal driver enabling console output during the port bringup. While the driver works, only one of the three UART devices are supported, and there isn't any way to change any parameters or use interrupts. This will most likely be superceded by a proper driver after the port has matured. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-05-11 08:12:12 +08:00
CONFIG_CONSOLE=y
CONFIG_SERIAL_HAS_DRIVER=y
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE_ON_DEV_NAME="ROMUART"
CONFIG_UART_CONSOLE=y
CONFIG_UART_ESP32=y
soc: esp32: Define __start as a C function The first stage bootloader, part of the ESP32 ROM, already sets up a stack that's sufficient to execute C programs. So, instead of implementing __stack() in assembly, do it in C to simplify things slightly. This ESP32-specific initialization will perform the following: - Disable the watchdog timer that's enabled by the bootloader - Move exception handlers to IRAM - Disable normal interrupts - Disable the second CPU - Zero out the BSS segment Things that might be performed in the future include setting up the CPU frequency, memory protection regions, and enabling the flash cache. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-06-14 01:48:38 +08:00
CONFIG_XTENSA_USE_CORE_CRT1=n
drivers: pinmux: Add pin multiplexer driver for ESP32 This implements a driver for the pin multiplexer as present in the ESP32 SoCs. All APIs are supported. Jira: ZEP-2297 Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-06-27 08:07:43 +08:00
CONFIG_PINMUX=y
CONFIG_PINMUX_ESP32=y
drivers: gpio: esp32: Add ESP32 GPIO driver This provides basic GPIO support, with interrupts, and the ability to read and write to ports on a pin-by-pin basis. Jira: ZEP-2286 Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-06-20 07:58:29 +08:00
CONFIG_GPIO=y
CONFIG_GPIO_ESP32=y
drivers: random: Add ESP32 random number generator driver The random number generator from ESP32 uses noise from Wi-Fi and Bluetooth radios. If these are off, a pseudo-random number is generated instead; this is currently the case, but even though it's a black box, it's arguably better than returning a timestamp as a pseudo-random number generator. According to the ESP32 Technical Reference manual, the RNG passed the Dieharder Random Number Test suite (version 3.31.1)[1], but nothing has been said about the quality of the PRNG. The RNG register is read directly; no effort is made to use its contents to feed an entropy pool in a way that's similar to /dev/random on POSIX systems, as no such subsystem exists on Zephyr at the moment. [1] http://webhome.phy.duke.edu/~rgb/General/dieharder.php Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-07-01 01:12:07 +08:00
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
CONFIG_ENTROPY_ESP32_RNG=y
arch: xtensa: Convert Xtensa port to use gen_isr_table The Xtensa port was the only one remaining to be converted to the new way of connecting interrupts in Zephyr. Some things are still unconverted, mainly the exception table, and this will be performed another time. Of note: _irq_priority_set() isn't called on _ARCH_IRQ_CONNECT(), since IRQs can't change priority on Xtensa: while the architecture has the concept of interrupt priority levels, each line has a fixed level and can't be changed. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-07-08 01:35:18 +08:00
CONFIG_SW_ISR_TABLE=y
CONFIG_GEN_ISR_TABLES=y
CONFIG_GEN_IRQ_VECTOR_TABLE=n
drivers: esp32: I2C driver implementation Supports both master and slave mode, standard and fast modes, configurable timeouts, and a few other tunable settings. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-08-24 08:24:40 +08:00
CONFIG_I2C=y
CONFIG_I2C_ESP32=y
CONFIG_I2C_0=y
CONFIG_I2C_1=y
CONFIG_I2C_2=n
CONFIG_I2C_3=n
# FIXME: ESP32 port should support DTS.
CONFIG_HAS_DTS_I2C=n
# IRQ priorities are fixed on Xtensa, but Kconfig will ask for these
# if not set.
CONFIG_I2C_0_IRQ_PRI=1
CONFIG_I2C_1_IRQ_PRI=1