MicroPython Forum (Archive)

I could flash other firmwares (NodeMCU) on this very modules in QIO and it worked fine... I know the ESP8285 needs to be flashed in DIO, and the ESP8266EX does use external SPI flash (that uses one of the two hardware SPI buses, which is why you should use HSPI), but I didn't change physical modules...

Well I'll be a monkey's uncle....

I flashed it in DIO and it worked....

What does this mean? Why did other binaries flash fine in QIO?

I always thought the ESP8285 needed to be flashed in DOUT because of the SPI flash chip...

Can anyone explain, this intrigues me..?

@roberthh : Those are SPI communication modes, basically speed and duplex... I've flashed firmware to it already in QIO, I've been working with the NodeMCU Lua firmware for close to a year now, it's just that I need to communicate with an I2C module, and control the ACK signals being sent. It's not ...

@rpr : I just tried again to flash the precompiled binary image just to make sure (I wasn't sure I tried after erasing the flash), and same result, I just get the bootloader with a csum error. @jomas : I've been working with that specific module for a while, almost a year... it's autodetected as a 4...

Hello, I'm trying to try MicroPython after a shortcoming of the NodeMCU firmware (I2C ACK) motivated me to learn Python, and make the switch. I can successfully build the firmware, and I can successfully flash it, however, when booting I only get the bootloader: load 0x40100000, len 31084, room 16 t...