Flashing the esp_iot_sdk_v1.1.1 AT-example to ESP-01

[dejavu]

Hello,

I've been trying to compile and flash the firmware of my ESP8266 module.
I've got the following ESP-01 module with a Flash-Chip called "GD25Q41B" (Datasheet says, it has 4MBit).

I have compiled the AT-Example from the newes SDK: esp_iot_sdk_v1.1.1.
I used the following settings in the compilation wizard which I ran in the Linux-Virtual machine:

boot mode: none
generate bin: eagle.flash.bin+eagle.irom0text.bin
spi speed: 40 MHz
spi size: 512KB
spi ota map: 256KB + 256KB

Then I'm flashing the eagle.flash.bin to 0x00000 and the eagle.irom0text.bin to 0x40000.
I've got the following settings in the Download Tool:

downloadtool.PNG (29.32 KiB) Viewed 10933 times

After flashing the device, I can establish serial connection with 115200 Baud.
The AT+GMR command gives the following output:

Code: Select all

AT version:0.25.0.0(Jun  5 2015 16:27:16)
SDK version:1.1.1
compile time:Jun 11 2015 01:24:59

AT+RST gives the following output:

Code: Select all

 ets Jan  8 2013,rst cause:1, boot mode:(3,7)

load 0x40100000, len 28904, room 16
tail 8
chksum 0xba
load 0x3ffe8000, len 4188, room 0
tail 12
chksum 0xda
ho 0 tail 12 room 4
load 0x3ffe9060, len 9608, room 12
tail 12
chksum 0xd4
csum 0xd4
rlŽ‚rú
ready


Here comes the problem:
I want to set the Baudrate to 9600 using the command "AT+IPR=9600". After sending this command, the module is set to 9600 Baud and responds to commands (like "AT"). But when I'm rebooting the module, it only returns some strange characters. The Baud-Rate is now neither 9600, nor 115200.
When I want to use the module again, I have to reflash the image.

Can someone please tell me, what I'm doing wrong?
I'm already trying to get it working for 4 days and I have no idea, why it doesn't work.


Thank you,

Greetings
Marcel

[ESP_Faye]

Hi,

Please refer to document "4A-ESP8266__AT Instruction Set" which in \esp_iot_sdk\document

The command to set UART is "AT+UART=xxxx", please have a try.

Thanks for your interest in ESP8266 !

[trickedj]

I think this may be related to this problem


viewtopic.php?f=16&t=400

Recent At builds require 1Mbyte, 8Mbit memory. In your case changing the baud rate writes to the user data area which the recent larger firmware spills into, overwriting the firmware causing a crash.

[dejavu]

hi,

thanks for your fast reply.
When I am using the following command, the result is the same:
AT+UART_DEF=9600,8,1,0,3
Instead of setting the baud rate, it just crashes and doesn't boot again until I flash the firmware again.

@trickedj: I think you are right. Is there any way to get it working with the new AT firmware?
I need it because it supports the "Ping"-command. If everything else fails, I will try to flash the latest Firmware with 512KB. But this should be my last option.

greetings from germany
Marcel

[trickedj]

There was a work around for v23 if over the air updating was not used, it is detailed in the post I quoted above along with a binary. I assume this is the method you used on the current firmware, so perhaps the work around is not valid anymore. I think that v23 had the ping command so perhaps you can use that.

It was hoped that espressif would produce a special build for 512Mbyte modules, with some features omitted to save space, but they seem to have abandoned the most common modules available !