ESP8266 Community Forum

- Sun Feb 17, 2019 1:45 pm #80610

i'm having a bit of trouble following the documentation because some of the instructions are now a bit outdated.

That's entirely true. I gave up on updating the documentation as apparently nobody was using it.

i successfully flashed version 11 as is the latest single .bin image. i'm having trouble flashing any other version that is made up of two or more images. every time i try to flash it i get garbage on 78500 baud.

I don't exactly understand what you mean. BTW I develop primarily for "ota" images, the "flash" image should still be working but may becoming a bit crowded nowadays. But I never test them, to be honest.

You may need to do a complete erase first, especially the SDK RF parameters areas.

The baud rate is something you can configure, why do you set it to 78500 baud? It can be anything as long as it's divisible from 80 Mhz by an integer number.

followed your instructions from here viewtopic.php?f=6&t=3959&start=180#p73560 but esptool returns an memory ovelapping error. as a matter of fact i read and tried avey solution posted on this thread.

I don't know this error, what does it say exactly?

1. Can you post your exact list of arguments for the esptool and version of esptool?

As said I never use the "flash" image, but new ESP's need to be initialled flashed, but I am using the OTA image then. See the makefile for what is used for "ota" images:

Code: Select all~/bin/esptool write_flash --flash_size 16m-c1 --flash_mode qio \
                  0x000000 espiobridge-rboot-boot.bin \
                  0x001000 rboot-config.bin \
                  0x002000 espiobridge-rboot-image.bin \
                  0x1fc000 esp_init_data_default_v08.bin \
                  0xfb000 blank1.bin \
                  0x1fd000 blank3.bin

For "flash" images:

Code: Select all~/bin/esptool write_flash --flash_size 16m-c1 --flash_mode qio \
                  0x000000 espiobridge-plain-iram-0x000000.bin \
                  0x010000 espiobridge-plain-irom-0x010000.bin \
                  0x07c000 esp_init_data_default_v08.bin \
                  0x7b000 blank1.bin \
                  0x07d000 blank3.bin

~/bin/esptool is just a wrapper to esptool.py that sets the correct device. You may need to change the flash_size argument.

2. Given the fact that the my ESP12E has 4MB of flash, OTA is out of the question, right? i can't quite figure this out.

If it's 4 Mbyte, it will work. If it's 4 Mbit (= 500 Kbyte) then it won't. We need to have two slots of 1 Mbyte for OTA. For some boards that only have 4 Mbit or less, I replace the flash with a larger one.

3. How are thing looking for the WS2812 support ? This will be a very nice feature.

It's already in, in the non-released (but public) source code. It can use either UART so one of two pins can be used, at will.

If you can manage to compile this yourself, you'll always have the latest version and you also may be able to tweak or improve some things.

- Sun Feb 17, 2019 1:47 pm #80611 BTW I am quite busy at the moment, but if you can't get it working, I may have a go at trying it myself, making a "flash" image and test it. But that's probably not going to happen before next weekend.

- Mon Feb 18, 2019 1:59 pm #80643 Something is definitely broken, indeed. I have flashed a "plain" image on a 32 Mbit device and it keeps resetting. Needs to be checked out. The "ota" image works.

Code: Select all ets Jan  8 2013,r�� cause:2, bo�� mod�:(3,6)

load 0x40100000, len 32188, ���m 16
tail 12
chksum 0x6�
h� 0 ta�l 12 room 4
load 0x3ffe8000, len 2400, �oom 12
tail 4
chksum 0x11
load 0x3ffe8960, len 12708, room 4
�ail 0
chksum 0x29
csum 0x29
�
 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

l�ad 0x40100000, �en 32188, room 16
tai� 12


- Mon Feb 18, 2019 3:04 pm #80644 I am definitely on to something.

Can you check for me the actual size of the flash on your ESP module? Is it 4 Mbits (0.5 Mbyte) or is it 8 Mbits (1 Mbyte)? I have checked here with a ESP201, which apparently has 8 Mbits flash. I got it working with an "8 Mbit" image instead of "4 Mbit". The code can fit in 512 Mbyte, but apparently there is "something" that prevents it.

So if you have 1 Mbyte flash, that will be an easy solution. If you only have 0.5 Mbyte, I will have to drop some code/functionality for minimal "plain" images. The i2c sensors code is quite big and is a candidate here.

As soon as I know I will upload a new version on github with working "plain" image. It will also include the ws2812 code.