Atom Echo install not working

[modem7]

When installing (plain) on an atom echo, I get an unhandled exception.

ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8
Guru Meditation Error: Core  1 panic'ed (StoreProhibited). Exception was unhandled.
Core 1 register dump:
PC      : 0x40146887  PS      : 0x00060b30  A0      : 0x80146854  A1      : 0x3ffb1d70  
A2      : 0x00000010  A3      : 0x00000002  A4      : 0x00060f20  A5      : 0x00000001  
A6      : 0x00060f20  A7      : 0x00000000  A8      : 0x80146854  A9      : 0x3ffb1d50  
A10     : 0x00000000  A11     : 0x00060f23  A12     : 0x00060f2Guru Meditation Error: Core  1 panic'ed (StoreProhibited). Exception was unhandled.
Core 1 register dump:
PC      : 0x40146887  PS      : 0x00060b30  A0      : 0x80146854  A1      : 0x3ffb1d70  
A2      : 0x00000010  A3      : 0x00000002  A4      : 0x00060f20  A5      : 0x00000001  
A6      : 0x00060f20  A7      : 0x00000000  A8      : 0x80146854  A9      : 0x3ffb1d50  
A10     : 0x00000000  A11     : 0x00060f23  A12     : 0x00060f20  A13     : 0x3ffb1efc  
A14     : 0x000000ff  A15     : 0x3ffb0060  SAR     : 0x00000010  EXCCAUSE: 0x0000001d  
EXCVADDR: 0x0000004c  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000000  

ELF file SHA256: 0000000000000000

Backtrace: 0x40146884:0x3ffb1d70 0x40146851:0x3ffb1d90 0x40144e56:0x3ffb1db0 0x400ee20b:0x3ffb1de0 0x400ee7f6:0x3ffb1e30 0x400f04f6:0x3ffb1e70 0x400f0632:0x3ffb1e90 0x400f06d1:0x3ffb1ec0 0x400eb4bd:0x3ffb1ee0 0x4010f889:0x3ffb1f20 0x40112226:0x3ffb1f40 0x401132ae:0x3ffb1f90 0x40132516:0x3ffb1fb0 0x4008b89e:0x3ffb1fd0

Rebooting...

https://github.com/Aircoookie/WLED/issues/4109

[blazoncek]

For ESP32-PICO model you will need special binary for version 0.14.4 (with different default GPIO for LEDs). Unfortunately it is not provided with installer and you will need to compile it yourself or find someone who will compile it for you.

Beta version of 0.15 should provide support for PICO either natively or with WROVER binary (provided on WLED Github releases page). In the latter case use esptool to flash binary.

I am not sure if web installer already supports WROVER but perhaps @lost-hope knows.

[modem7]

Thanks for the quick response!

Just an FYI, I also tried the 0.15.0-b4 via the web installer, but I couldn't see any logs appearing when I checked.

[lost-hope]

I am not sure if web installer already supports WROVER but perhaps @lost-hope knows.

The webinstaller only delivers the default esp32dev build. The difference between those two is the PSRAM right?

[blazoncek]

The difference between those two is the PSRAM right?

Yes. For ESP32 rev.3 or later standard binary (0.15.0-b4 or later) should suffice but for ESP32 rev.1 you need WROVER binary. Unfortunately I do not own Pico (I know that @srg74 has them) so can't confirm 100% if that is truly the case with standard binary.

The actual problem with Pico is not PSRAM support but default GPIO16 used for LEDs. It clashes with PSRAM GPIO. Still 0.15.0-b4 should detect Pico and adjust accordingly.

@modem7 if you did not erase entire flash when uploading 0.15.0-b4 then previous configuration may have affected your ESP.

[netmindz]

Surely PinManager should just spot the pin in unavailable and stop initialization of the bus rather than crash? @blazoncek

[blazoncek]

spot the pin in unavailable

Pin is available, just connected to PSRAM, which triggers a crash if used. Newer PlatformIO/Arduino core (v4) correctly detects PICO and will block GPIO16 use.