Strange Errors on AT Command. Usart2

Nikola Kirov
Posts: 4
Joined: Fri Sep 15, 2017 9:35 am

Strange Errors on AT Command. Usart2

Postby Nikola Kirov » Fri Sep 15, 2017 9:47 am

Hi,
I program AT firmware on my ESP32 DEV KIT V1.
But I receive stange errors on any input.
This is on Usart2.

Code: Select all

ERR CODE: 0x010b0000
bussy p...
ERR CODE: 0x01030000
I clear all memory first, and load all files.
Picture1.png
Picture1.png (33.47 KiB) Viewed 4850 times
Startup log seems normal.

Code: Select all

<  ets Jun  8 2016 00:22:57
<  rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
<  ets Jun  8 2016 00:22:57
<  rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
<  configsip: 0, SPIWP:0x00
<  clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
<  mode:DIO, clock div:2
<  load:0x3fff0008,len:8
<  load:0x3fff0010,len:3472
<  load:0x40078000,len:7804
<  load:0x40080000,len:252
<  entry 0x40080034
<  [0;32mI (43) boot: ESP-IDF v2.0 2nd stage bootloader[0m
<  [0;32mI (43) boot: compile time 03:23:43[0m
<  [0;32mI (43) boot: Enabling RNG early entropy source...[0m
<  [0;32mI (59) boot: SPI Speed      : 40MHz[0m
<  [0;32mI (72) boot: SPI Mode       : DIO[0m
<  [0;32mI (84) boot: SPI Flash Size : 4MB[0m
<  [0;32mI (96) boot: Partition Table:[0m
<  [0;32mI (107) boot: ## Label            Usage          Type ST Offset   Length[0m
<  [0;32mI (130) boot:  0 phy_init         RF data          01 01 0000f000 00001000[0m
<  [0;32mI (153) boot:  1 otadata          OTA data         01 00 00010000 00002000[0m
<  [0;32mI (177) boot:  2 nvs              WiFi data        01 02 00012000 0000e000[0m
<  [0;32mI (200) boot:  3 ble_data         unknown          40 00 00020000 00003000[0m
<  [0;32mI (223) boot:  4 ota_0            OTA app          00 10 00100000 00180000[0m
<  [0;32mI (246) boot:  5 ota_1            OTA app          00 11 00280000 00180000[0m
<  [0;32mI (270) boot: End of partition table[0m
<  [0;32mI (283) boot: Disabling RNG early entropy source...[0m
<  [0;32mI (300) boot: Loading app partition at offset 00100000[0m
<  [0;32mI (1475) boot: segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
<  [0;32mI (1476) boot: segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5d0 (116176) map[0m
<  [0;32mI (1492) boot: segment 2: paddr=0x0012c5e0 vaddr=0x3ffb0000 size=0x0215c (  8540) load[0m
<  [0;32mI (1523) boot: segment 3: paddr=0x0012e744 vaddr=0x40080000 size=0x00400 (  1024) load[0m
<  [0;32mI (1546) boot: segment 4: paddr=0x0012eb4c vaddr=0x40080400 size=0x1b028 (110632) load[0m
<  [0;32mI (1625) boot: segment 5: paddr=0x00149b7c vaddr=0x400c0000 size=0x00034 (    52) load[0m
<  [0;32mI (1626) boot: segment 6: paddr=0x00149bb8 vaddr=0x00000000 size=0x06450 ( 25680) [0m
<  [0;32mI (1642) boot: segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a544 (501060) map[0m
<  [0;32mI (1670) heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
<  [0;32mI (1692) heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM[0m
<  [0;32mI (1713) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM[0m
<  [0;32mI (1735) heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM[0m
<  [0;32mI (1755) cpu_start: Pro cpu up.[0m
<  [0;32mI (1767) cpu_start: Single core mode[0m
<  [0;32mI (1780) cpu_start: Pro cpu start user code[0m
<  [0;32mI (1841) cpu_start: Starting scheduler on PRO CPU.[0m
<  [0;32mI (2098) uart: queue free spaces: 10[0m
<  I (2100) wifi: wifi firmware version: c604573
<  I (2100) wifi: config NVS flash: enabled
<  I (2100) wifi: config nano formating: disabled
<  I (2107) wifi: Init dynamic tx buffer num: 32
<  I (2108) wifi: wifi driver task: 3ffc4da4, prio:23, stack:3584
<  I (2113) wifi: Init static rx buffer num: 10
<  I (2117) wifi: Init dynamic rx buffer num: 0
<  I (2121) wifi: Init rx ampdu len mblock:7
<  I (2125) wifi: Init lldesc rx ampdu entry mblock:4
<  I (2129) wifi: wifi power manager task: 0x3ffca14c prio: 21 stack: 2560
<  I (2136) wifi: wifi timer task: 3ffcb1cc, prio:22, stack:3584
<  [0;31mE (2141) phy_init: PHY data partition validated[0m
<  [0;32mI (2177) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0[0m
<  I (2177) wifi: mode : softAP (30:ae:a4:06:4f:b9)
<  I (2180) wifi: mode : sta (30:ae:a4:06:4f:b8) + softAP (30:ae:a4:06:4f:b9)
<  I (2184) wifi: mode : softAP (30:ae:a4:06:4f:b9)

Nikola Kirov
Posts: 4
Joined: Fri Sep 15, 2017 9:35 am

Re: Strange Errors on AT Command. Usart2

Postby Nikola Kirov » Sat Sep 23, 2017 4:58 pm

Up

Nikola Kirov
Posts: 4
Joined: Fri Sep 15, 2017 9:35 am

Re: Strange Errors on AT Command. Usart2

Postby Nikola Kirov » Sat Oct 28, 2017 5:47 pm

Please help me.

brian.wyld
Posts: 2
Joined: Tue Feb 12, 2019 5:14 pm

Re: Strange Errors on AT Command. Usart2

Postby brian.wyld » Tue Feb 12, 2019 5:29 pm

Hi,

ANy answer for this problem?
I have the same issue with the latest AT binary downloaded from the site...
---
ready
AT
^J

ERR CODE:0x010b0000

busy p...

OK
AT+GMR
^J+GMR

ERR CODE:0x010b0000

busy p...
AT version:1.1.3.0(5a40576 - Nov 28 2018 12:50:55)
SDK version:v3.0.7
compile time:Dec 21 2018 09:04:56
Bin version:1.1.3(WROOM-32)

OK

Who is online

Users browsing this forum: No registered users and 139 guests