OVMS3-idf/tools/unit-test-app/configs/psram_2

TEST_COMPONENTS=driver esp32 spi_flash
CONFIG_ESP32_SPIRAM_SUPPORT=y
CONFIG_ESP_INT_WDT_TIMEOUT_MS=800
CONFIG_SPIRAM_OCCUPY_NO_HOST=y
unit test: split psram config into two configs to free up IRAM 2018-10-16 04:46:17 +00:00			`TEST_COMPONENTS=driver esp32 spi_flash`
Rename Kconfig options (components/esp32) 2019-04-30 10:51:55 +00:00			`CONFIG_ESP32_SPIRAM_SUPPORT=y`
ci: Increase INT_WDT_TIMEOUT_MS for PSRAM configs This shouldn't be necessary, it's a workaround for a bug in the config system. 2019-10-25 21:48:17 +00:00			`CONFIG_ESP_INT_WDT_TIMEOUT_MS=800`
ci: fix one ut issue when using Wrover-B module with newer ver of PSRAM The workaround for PSRAM that will occupy an SPI bus is enabled only when: 1. used on 32MBit ver 0 PSRAM. 2. work at 80MHz. The test used to only check 32MBit by the config option, but for PSRAM on Wrover-B module seems to use a newer version of 32MBit PSRAM. So it expects the workaround to be enabled, but actually not. This commit split the unit test into two parts: 1. check all SPI buses are available, for all configs except psram_hspi and psram_vspi, run on regular runners (including Wrover and Wrover-B). a hidden option is enabled so that the compiler knows it's not building psram_hspi or psram_vspi. 2. check the specified bus are acquired, for config psram_hspi and psram_vspi. This only run on special runner (legacy Wrover module). 2019-10-31 04:00:46 +00:00			`CONFIG_SPIRAM_OCCUPY_NO_HOST=y`