Do you have any indication of cost? At the moment it just seems to be an expression of interest form.

I'm getting a similar kind of panic. The code is for the Espruino interpreter, and occurs when trying to set timers after about 150 iterations: ``` var count=0; function blip() { digitalPulse(21, 1, 15); } function start() { setInterval(blip, 30); } start(); ``` I have increase stack size in the vTa...

Yes - we use this in the esp32 port of espruino.

From memory, there is also a menuconfig option to store in nvs, so you don't need a phy partition to store the data, nvs is used instead.

I have a similar issue after flashing where I can't connect with the Espruino IDE after a flash and --after hard_reset The delay - close - delay update does not work. in the Espruino ide I get: Connected > Disconnected and in the console: >>> Sent ERROR: RECEIVE ERROR: {"connectionId":1,"error":"ove...

Could you please paste the output you get with GPIO15 is connected to ground? Thanks. Ok - there is a difference! With GPIO15 grounded: ;31mE (9) boot: ota data partition invalid, falling back to factorym ;32mI (1322) heap_alloc_caps: Initializing. RAM available for dynamic allocation:m ;32mI (1323...

ESP_igrr wrote:Bootstrapping GPIO15 to ground will also disable initial output from the ROM bootloader.

This does not appear to work for me. I have read GP015 state and it is ready zero with my jumper, but has no affect on boot.

WiFive wrote:You can set the log levels to none and use efuse to turn off ROM output.

How do youdo this? It sounds like this is on a per board basis and can it be undone?

So there is no way to do this in firmware?

Ideally I want to suppress bootloader output, but allow informational debug output.

Hi, how can these boot messages be suppressed? ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) ets Jun 8 2016 00:22:57 rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0x00 clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_d...

Does anyone know what changes are required to linking scripts for say an ota2 partition at 0x200000 ?