[SOLVED] Flashing WeMos D1 Mini Pro (16MB) with Espruino #6029
Replies: 1 comment
-
Posted at 2018-01-24 by DrAzzy esptool.py --port COM3 --baud 115200 write_flash --flash_freq 80m --flash_mode dio --flash_size 4MB-c1 0x0000 boot_v1.6.bin 0x1000 espruino_esp8266_user1.bin 0x3FC000 esp_init_data_default.bin 0x3FE000 blank.bin This command works for me for flashing 1v95 on clone D1 mini's Posted at 2018-01-24 by user85573 Can you confirm flash size? D1 Mini Pro is a 16MB device, the D1 Mini is 4MB. I ended up just purchasing two units of the D1 Mini, hoping it'll be an interim solution until the 16MB version is supported. Posted at 2018-01-24 by @MaBecker Hi @user85573, can you please share output of W25Q40BV ( 4 Mega Bits / 512K Byte ) = ID 4013h Edit: so it is W25Q128FV ( 128 Mega bits / 16 Mega Bytes ) = ID 4018h Posted at 2018-01-24 by @MaBecker
start with Posted at 2018-01-24 by user85573 Thanks for your help! Keep in mind that I think that what's happening here is that the 1v95 binaries are built for 512K and 4MB models. No matter where you flash the components, the runtime code doesn't point to the right memory addresses. Guess I'll have to wait until a 16MB combined binary is available. Posted at 2018-01-24 by @MaBecker A 4mb build has more save pages 16 versus 3 Posted at 2018-01-24 by user85573 Agreed, it's just that when I flashed But success!
On boot: In fact, it also works with just and with The takeaway seems to be, don't let Posted at 2018-01-24 by DrAzzy
IME, it appears to work, but when you do wifi.save(), it no longer boots and you have to reflash. Posted at 2018-01-24 by user85573 Ah ok, will test and report back on Posted at 2018-01-24 by user85573 Sure enough, with the 512/512 map, Posted at 2018-01-24 by @MaBecker Thanks for you test and feedback. Does is reconnect to the AP after Posted at 2018-01-26 by user85573 It does not...I've just been including Wifi in Posted at 2018-01-26 by @MaBecker there are now some updates on the ESP8266 page - check section Build Content Posted at 2018-01-26 by @MaBecker Just to recap: steps you did to get a stable Espruino:
Wifi stuff:
I am interested in output of console.log('connetion error',err); Posted at 2018-01-26 by user85573 Yes, the summary is accurate. That code doesn't work for me, even with tweaking. I'll need more time. Posted at 2018-04-03 by AndrewWakeling Just confirming that I was also able to correctly flash the d1 mini pro using 1v96 using the 4mb-c1 option too. Posted at 2018-04-03 by @MaBecker Thanks for sharing Posted at 2018-04-04 by AndrewWakeling For anybody else interested in getting the d1 mini pro up and running with Espruino, I've written a guide here: https://github.com/andrewwakeling/espruino-d1-mini-pro |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2018-01-24 by user85573
Could use some help on this device. I can flash this fine with a 512m image, but with a few errors writing from the IDE at Espruino boot:
Flash map exception, manuf 0xef chip 0x4018
and
Specs for the device claim 16M bytes(128M bit) Flash...but I am not sure how to take advantage of that with esptool.py and the fragmented binary image files.
0xffc000
should be the place where init data is stored in 16MB map.causes the device to just spew gibberish out of the serial console.
Flashing the combined 4MB image
espruino_1v95_esp8266_4mb_combined_4096.bin
does not work. Onlyespruino_1v95_esp8266_combined_512.bin
does, but this doesn't allow the amount of code I'm developing as per above.Beta Was this translation helpful? Give feedback.
All reactions