I have now bought a Wemos D1 mini (D1 Mini NodeMcu mit ESP8266-12F WLAN Module CH340G Lua – AZ-Delivery) and reproduced the problem. It occurs immediately when flashing the blinky firmware.
The problem is the exact same as I have already solved before and reported: The ESP-8266-Non-OS build script doesn’t flash the esp_init_data_default.bin file to the correct address for the module. In fact, it doesn’t flash / compile it all (for all modules, not as only for 1MB modules as I assumed) when you look at the build / flash commands
//compiling image
"esptool" -eo .pioenvs\d1_mini_rtos\firmware.elf -bo .pioenvs\d1_mini_rtos\eagle.flash.bin -bm dio -bf 40 -bz 4M -bs .text -bs .data -bs .rodata -bc -ec -eo .pioenvs\d1_mini_rtos\firmware.elf -es .irom0.text .pioenvs\d1_mini_rtos\eagle.irom0text.bin -ec -v
//uplading
esptool -cd nodemcu -cb 921600 -cp "COM7" -ca 0x00000 -cf .pioenvs\d1_mini_rtos\eagle.flash.bin -ca 0x10000 -cf .pioenvs\d1_mini_rtos\eagle.irom0text.bin
The actuall correct uplaod command for me would be to load esp_init_data_default.bin to 0x3fc000 (4MB module). You can go into your tool-esptool folder and after-flash the file
esptool -cd nodemcu -cb 921600 -cp "COM7" -ca 0x3fc000 -cf "C:\Users\Maxi\.platformio\packages\framework-esp8266-nonos-sdk\bin\esp_init_data_default.bin"
Then the firmware comes right up and works.
Now it’s questionable for me if I should fix this because probably, the community-provided new ESP8266-RTOS/NONOS builders will be far better than the current one and will work with the most current SDK version (see here), so it doesn’t make sense to work on old stuff; that is, when it’s planned to integrate this builder into the main platform-espressif8266. Or what do you think @ivankravets?
But anyways, you have a fix now! 