I’ve run in to a problem when using a custom board I’ve created where I don’t see the problem with the mass produced esp32-dev boards, while effectively running the same build.
Basically I’m not even sure what the problem is, after setting the debug level to 3 this is all I’m getting:
[Feb 23 20:49:41.047] mgos_sys_config.c:368 MAC: c4:dd:57:8d:27:f0 [Feb 23 20:49:41.047] mgos_sys_config.c:376 WDT: 30 seconds [Feb 23 20:49:41.047] mgos_core.c:104 Setting TZ to 'XXXXXXXXXXXXXXXX' [Feb 23 20:49:41.047] mgos_deps_init.c:172 Init adc 1.0.0... [Feb 23 20:49:41.047] mgos_deps_init.c:172 Init spi 1.0... [Feb 23 20:49:41.047] ets Jul 29 2019 12:21:46 [Feb 23 20:49:41.047] [Feb 23 20:49:41.047] rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
Basically the device just goes in to a boot loop always dying at the same point
mgos_deps_init.c:172 Init spi 1.0...
I can run the basic
esp32 project and it all works as expected on the board. I can flash and run Arduino code and it runs fine, but the project I’ve been working on for a while seems to be causing issues.
When I flash the FW to the non-custom devices the next message I see on the terminal after
[Feb 23 21:01:44.486] esp32_spi_master.c:94 SPI3 init ok (MISO: 19, MOSI: 23, SCLK: 18; CS0/1/2: 5/27/-1; native? yes)
Any thoughts on how I can debug/troubleshoot would be much appreciated.