Hi At version 2.0 of the SDK I was sailing along with hundreds of bytes of RAM left for code.... and yes I put all my functions into FLASH and have taken all the usual precautions.. However, by 2.1 of the SDK I am back to square one with the old "section `.text' will not fit in region `iram1_0_...

I don't have a flash_write_flash function... I have an rboot-ota.c rboot_write_flash function - I'm still (SDK 2.1.0) getting occasional E:M 5600 or thereabouts messages which mess up the OTA which of course makes RBOOT's OTA code fail...

Any ideas? I can't see a fix incorporated anywhere.

I'm on sdk 2.0 and the function has no effect - I used it just before putting the ESP into station mode

It's NOT working for me (SDK 2.0) and yet some guys who's Arduino/ESP code I'm using... their devices are showing up on my network with the names they've given them - but for me - I always get the default name.... HELP someone.

Am I missing something - this seems to be about a specific driver and I'm not seeing how the SPI master reads anything??

Did this go anywhere in terms of code for I2c slave? I'm not that hot on interrupts - it really would be nice to have an i2c slave.c and .h file as we do for the masters. Surprised Espressif have not followed up on this and included in the SDK.

So I am working on code so that ESP8266 is the master and an Atmega1284 is the slave. I send data to the Arduino - and I get data back. I'm having reliability issues in that the RETURN data is ok for one byte - but more than one byte I tend to get bad data - AND the ESP has a tendency to reboot. So ...

In the SDK there are routines to ERASE a sector - but then to read and write absolute addresses. So my questions are - given that in an OTA situation, an array in normal memory may be in one or two places.. So you ERASE a sector and start writing to it - that's easy enough. When you write - the dest...

It LOOKs like it was not RBOOT after all.. So two problems "solved" - this might be of use to others.. 1. I was not blowing the system file at the top of the 4MB on a new board- never had to before SDK 1.54 or thereabouts - now you do! 2. After my initialisation of ports - and other stuff ...

As you know there is something wrong - RBOOT isn't working properly and I've heard nothing back from the developers as to what changes might have stopped it working. I have people coming onto my site and asking why the code is no longer working properly. Hello, The upgrade process is similar, becaus...