Help please I have an ESP32 WROOM-32 I got a bunch of error with espruino 2v17.55

[espruino-discuss3]

Posted at 2023-05-01 by user155342

Hello, i Flashed the bootloader, partitions and bin from here: http://www.espruino.com/binaries/travis/master/

The flash goes well but I got this error when I connect my esp with espruino ide web:

---

| |_ ___ ___ _ ||___ ___
| | -| . | | | | | | . |
||| || |||||_|
|| espruino.com
2v17.55 (c) 2021 G.Williams
Espruino is Open Source. Our work is supported
only by sales of official boards and donations:
http://espruino.com/Donate

WARNING: Scan stop failed
WARNING: set rssi scan not implemeted yet
Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC : 0x40112b04 PS : 0x00060030 A0 : 0x801137db A1 : 0x3ffea370
A2 : 0x00000001 A3 : 0x00003fff A4 : 0x00000001 A5 : 0x00000000
A6 : 0x00000000 A7 : 0x0000000a A8 : 0x00003fff A9 : 0x3ffea350
A10 : 0x00000000 A11 : 0x00037ff2 A12 : 0x3ffea364 A13 : 0x00000000
A14 : 0x00000001 A15 : 0x3ffb9701 SAR : 0x00000002 EXCCAUSE: 0x0000001c
EXCVADDR: 0x0000000c LBEG : 0x400924d8 LEND : 0x400924f4 LCOUNT : 0xffffffff
ELF file SHA256: 0000000000000000
Backtrace: 0x40112b01:0x3ffea370 0x401137d8:0x3ffea390 0x40128b96:0x3ffea3b0 0x40128cf5:0x3ffea460 0x40136e84:0x3ffea480
Rebooting...
ets Jul 29 2019 12:21:46
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:2984
load:0x40078000,len:10700
load:0x40080400,len:5236
entry 0x40080658
E (29) boot: ota data partition invalid, falling back to factory
E (567) psram: PSRAM ID read error: 0xffffffff
E (567) spiram: SPI RAM enabled but initialization failed. Bailing out.
E (567) spiram: SPI RAM not initialized

I don't know how to fix these errors. I can't upload any code on ram ( I understand that I have not the spi ram )

How can I fix these errors?

Thank you so much!

[espruino-discuss3]

Posted at 2023-05-09 by @SimonGAndrews

Hello,
I was getting similiar issues.
There was a fix deployed in v 2v17.74 on the May 5 which may fix this. You can find the bins in the same travis/master directory you referecne above. Maybe try again with the new version.