AT+CIUPDATE with default AT FW not working

cperez
Posts: 1
Joined: Thu Apr 19, 2018 9:07 am

AT+CIUPDATE with default AT FW not working

Postby cperez » Tue Aug 28, 2018 12:37 pm

Hi everyone!

I am not able to OTA update AT FW version by using AT+CIUPDATE command.
I have serialy flashed AT version 1.1 from github on my ESP-WROOM-32 without modifying configuration. So upgrading parameters (server and token) are set to default values:
AT FW config.jpg
AT FW config.jpg (31.96 KiB) Viewed 4089 times
I have configured ESP32 to work as station and I have succesfully conected it to a network with internet connection:

Code: Select all


rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3fff0018,len:4

load:0x3fff001c,len:5584

ho 0 tail 12 room 4

load:0x40078000,len:0

load:0x40078000,len:13724

entry 0x40078fb4

I (30) boot: ESP-IDF v3.0-rc1-229-g5ee7233b-dirty 2nd stage bootloader

I (30) boot: compile time 10:56:49

I (31) boot: Enabling RNG early entropy source...

I (37) boot: SPI Speed      : 40MHz

I (41) boot: SPI Mode       : DIO

I (45) boot: SPI Flash Size : 4MB

I (49) boot: Partition Table:

I (53) boot: ## Label            Usage          Type ST Offset   Length

I (60) boot:  0 phy_init         RF data          01 01 0000f000 00001000

I (67) boot:  1 otadata          OTA data         01 00 00010000 00002000

I (75) boot:  2 nvs              WiFi data        01 02 00012000 0000e000

I (82) boot:  3 at_customize     unknown          40 00 00020000 000e0000

I (90) boot:  4 ota_0            OTA app          00 10 00100000 00180000

I (97) boot:  5 ota_1            OTA app          00 11 00280000 00180000

I (105) boot: End of partition table

I (109) esp_image: segment 0: paddr=0x00100020 vaddr=0x3f400020 size=0x208f8 (133368) map

I (164) esp_image: segment 1: paddr=0x00120920 vaddr=0x3ffc0000 size=0x0318c ( 12684) load

I (170) esp_image: segment 2: paddr=0x00123ab4 vaddr=0x40080000 size=0x00400 (  1024) load

I (172) esp_image: segment 3: paddr=0x00123ebc vaddr=0x40080400 size=0x0c154 ( 49492) load

I (200) esp_image: segment 4: paddr=0x00130018 vaddr=0x400d0018 size=0xd9604 (890372) map

I (510) esp_image: segment 5: paddr=0x00209624 vaddr=0x4008c554 size=0x08d9c ( 36252) load

I (525) esp_image: segment 6: paddr=0x002123c8 vaddr=0x400c0000 size=0x00064 (   100) load

I (537) boot: Loaded app from partition at offset 0x100000

I (537) boot: Disabling RNG early entropy source...

I (642) wifi: wifi firmware version: c98fbd5

I (643) wifi: config NVS flash: enabled

I (643) wifi: config nano formating: disabled

I (652) wifi: Init dynamic tx buffer num: 32

I (653) wifi: Init data frame dynamic rx buffer num: 32

I (653) wifi: Init management frame dynamic rx buffer num: 32

I (658) wifi: wifi driver task: 3ffdf5e8, prio:23, stack:4096

I (663) wifi: Init static rx buffer num: 10

I (667) wifi: Init dynamic rx buffer num: 32

I (671) wifi: wifi power manager task: 0x3ffe3ce4 prio: 21 stack: 2560

I (704) wifi: mode : sta (30:ae:a4:41:40:28) + softAP (30:ae:a4:41:40:29)



ready

WIFI CONNECTED

AT+GMR

AT version:1.1.b2.0(b7082b1 - Mar 30 2018 08:38:03)

SDK version:v3.0-rc1-229-g5ee7233b-dirty

compile time:Apr 16 2018 10:58:44



OK

WIFI GOT IP

AT+CIPSTATUS

STATUS:2



OK

AT+CIPSTA?

+CIPSTA:ip:"192.168.34.14"

+CIPSTA:gateway:"192.168.35.250"

+CIPSTA:netmask:"255.255.254.0"



OK

At this point I am able to ping the ESP32 from a PC connected to the same network but when I run AT+CIUPDATE command I get this output:

Code: Select all


AT+CIUPDATE

ota_mode:0


+CIPUPDATE:1

+CIPUPDATE:2

http request length 389 bytes


+CIPUPDATE:3

rom_version error!




ERROR

AT+CIUPDATE=1

ota_mode:1


+CIPUPDATE:1

+CIPUPDATE:2

http request length 390 bytes


+CIPUPDATE:3

rom_version error!




ERROR
None SSL or normal FOTA are working.

I have checked that .bin file referenced by token dd93253c287f725de50d4071a05dd28b72056ca7 exists.

Could you help me find whats going on??

I wanted to try specifying the AT version on AT+CIUPDATE command but I am not sure about the expected format. I have tried:
AT+CIUPDATE=1,another-existing-token
AT+CIUPDATE=1,0.1
but none of them seems to be correct. What I am supposed to set on version area?

Thank you in advance!

Helen L
Posts: 71
Joined: Thu Aug 16, 2018 9:07 am

Re: AT+CIUPDATE with default AT FW not working

Postby Helen L » Wed Aug 29, 2018 2:50 am

Only the official AT bin can run command `AT+CIUPDATE` by default. If you compiled your own AT firmware, then you need to implement your own FOTA function, even if you did not change anything, just re-compile it.

Who is online

Users browsing this forum: Bing [Bot] and 127 guests