memory_layout issue

georgecarlo
Posts: 16
Joined: Fri Jan 18, 2019 5:55 am

memory_layout issue

Postby georgecarlo » Sat Mar 16, 2019 12:59 pm

Hello Community,

I recently used a QUESTAR G702-001UB - GPS Module on esp32. I used kolban's esp32 gps snippets (https://github.com/nkolban/esp32-snippe ... re/gps/gps)

I get the following stuff, could'nt identify where's the problem.

Code: Select all

rst:0x1 (POWERON_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:4544
ho 0 tail 12 room 4
load:0x40078000,len:10756
load:0x40080400,len:6320
entry 0x4008070c
I (92) cpu_start: Pro cpu up.
I (92) cpu_start: Application information:
I (92) cpu_start: Project name:     app-template
I (92) cpu_start: App version:      1
I (95) cpu_start: Compile time:     17:00:37
I (99) cpu_start: Compile date:     Mar 14 2019
I (103) cpu_start: ESP-IDF:          v3.3-beta1-136-g97eecfa-dirty
I (109) cpu_start: Single core mode
V (113) memory_layout: reserved range is 0x3f406650 - 0x3f406668
D (118) memory_layout: Checking 5 reserved memory ranges:
D (123) memory_layout: Reserved memory range 0x3ffae000 - 0x3ffae6e0
D (129) memory_layout: Reserved memory range 0x3ffb0000 - 0x3ffb2aa0
D (135) memory_layout: Reserved memory range 0x3ffe0000 - 0x3ffe0440
D (142) memory_layout: Reserved memory range 0x40070000 - 0x40078000
D (148) memory_layout: Reserved memory range 0x40080000 - 0x40088094
0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

D (154) memory_layout: Building list of available memory regions:
V (160) memory_layout: Examining memory region 0x3ffae000 - 0x3ffb0000
V (166) memory_layout: Start of region 0x3ffae000 - 0x3ffb0000 overlaps reserved 0x3ffae000 - 0x3ffae6e0
D (175) memory_layout: Available memory region 0x3ffae6e0 - 0x3ffb0000
V (181) memory_layout: Examining memory region 0x3ffb0000 - 0x3ffb8000
V (187) memory_layout: Start of region 0x3ffb0000 - 0x3ffb8000 overlaps reserved 0x3ffb0000 - 0x3ffb2aa0
D (197) memory_layout: Available memory region 0x3ffb2aa0 - 0x3ffb8000
V (203) memory_layout: Examining memory region 0x3ffb8000 - 0x3ffc0000
D (209) memory_layout: Available memory region 0x3ffb8000 - 0x3ffc0000
V (215) memory_layout: Examining memory region 0x3ffc0000 - 0x3ffc2000
D (222) memory_layout: Available memory region 0x3ffc0000 - 0x3ffc2000
V (228) memory_layout: Examining memory region 0x3ffc2000 - 0x3ffc4000
D (234) memory_layout: Available memory region 0x3ffc2000 - 0x3ffc4000
V (240) memory_layout: Examining memory region 0x3ffc4000 - 0x3ffc6000
D (247) memory_layout: Available memory region 0x3ffc4000 - 0x3ffc6000
V (253) memory_layout: Examining memory region 0x3ffc6000 - 0x3ffc8000
D (259) memory_layout: Available memory region 0x3ffc6000 - 0x3ffc8000
V (265) memory_layout: Examining memory region 0x3ffc8000 - 0x3ffca000
D (272) memory_layout: Available memory region 0x3ffc8000 - 0x3ffca000
V (278) memory_layout: Examining memory region 0x3ffca000 - 0x3ffcc000
D (284) memory_layout: Available memory region 0x3ffca000 - 0x3ffcc000
V (290) memory_layout: Examining memory region 0x3ffcc000 - 0x3ffce000
D (297) memory_layout: Available memory region 0x3ffcc000 - 0x3ffce000
V (303) memory_layout: Examining memory region 0x3ffce000 - 0x3ffd0000
D (309) memory_layout: Available memory region 0x3ffce000 - 0x3ffd0000
V (315) memory_layout: Examining memory region 0x3ffd0000 - 0x3ffd2000
D (322) memory_layout: Available memory region 0x3ffd0000 - 0x3ffd2000
V (328) memory_layout: Examining memory region 0x3ffd2000 - 0x3ffd4000
D (334) memory_layout: Available memory region 0x3ffd2000 - 0x3ffd4000
V (340) memory_layout: Examining memory region 0x3ffd4000 - 0x3ffd6000
D (347) memory_layout: Available memory region 0x3ffd4000 - 0x3ffd6000
V (353) memory_layout: Examining memory region 0x3ffd6000 - 0x3ffd8000
D (359) memory_layout: Available memory region 0x3ffd6000 - 0x3ffd8000
V (365) memory_layout: Examining memory region 0x3ffd8000 - 0x3ffda000
D (372) memory_layout: Available memory region 0x3ffd8000 - 0x3ffda000
V (378) memory_layout: Examining memory region 0x3ffda000 - 0x3ffdc000
D (384) memory_layout: Available memory region 0x3ffda000 - 0x3ffdc000
V (390) memory_layout: Examining memory region 0x3ffdc000 - 0x3ffde000
D (397) memory_layout: Available memory region 0x3ffdc000 - 0x3ffde000
V (403) memory_layout: Examining memory region 0x3ffde000 - 0x3ffe0000
D (409) memory_layout: Available memory region 0x3ffde000 - 0x3ffe0000
V (415) memory_layout: Examining memory region 0x3ffe0000 - 0x3ffe4000
V (422) memory_layout: Start of region 0x3ffe0000 - 0x3ffe4000 overlaps reserved 0x3ffe0000 - 0x3ffe0440
D (431) memory_layout: Available memory region 0x3ffe0440 - 0x3ffe4000
V (437) memory_layout: Examining memory region 0x3ffe4000 - 0x3ffe8000
D (443) memory_layout: Available memory region 0x3ffe4000 - 0x3ffe8000
V (450) memory_layout: Examining memory region 0x3ffe8000 - 0x3fff0000
D (456) memory_layout: Available memory region 0x3ffe8000 - 0x3fff0000
V (462) memory_layout: Examining memory region 0x3fff0000 - 0x3fff8000
D (468) memory_layout: Available memory region 0x3fff0000 - 0x3fff8000
V (475) memory_layout: Examining memory region 0x3fff8000 - 0x3fffc000
D (481) memory_layout: Available memory region 0x3fff8000 - 0x3fffc000
V (487) memory_layout: Examining memory region 0x3fffc000 - 0x40000000
D (493) memory_layout: Available memory region 0x3fffc000 - 0x40000000
V (500) memory_layout: Examining memory region 0x40070000 - 0x40078000
V (506) memory_layout: Region 0x40070000 - 0x40078000 inside of reserved 0x40070000 - 0x40078000
V (514) memory_layout: Examining memory region 0x40078000 - 0x40080000
0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

D (521) memory_layout: Available memory region 0x40078000 - 0x40080000
0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

V (527) memory_layout: Examining memory region 0x40080000 - 0x40082000
0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

0x40082000: heap_caps_realloc at /home/admatic/esp/esp-idf/components/heap/heap_caps.c:307

V (533) memory_layout: Region 0x40080000 - 0x40082000 inside of reserved 0x40080000 - 0x40088094
0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

0x40082000: heap_caps_realloc at /home/admatic/esp/esp-idf/components/heap/heap_caps.c:307

0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

V (542) memory_layout: Examining memory region 0x40082000 - 0x40084000
0x40082000: heap_caps_realloc at /home/admatic/esp/esp-idf/components/heap/heap_caps.c:307

0x40084000: commonErrorHandler at /home/admatic/esp/esp-idf/components/esp32/panic.c:707

V (548) memory_layout: Region 0x40082000 - 0x40084000 inside of reserved 0x40080000 - 0x40088094
0x40082000: heap_caps_realloc at /home/admatic/esp/esp-idf/components/heap/heap_caps.c:307

0x40084000: commonErrorHandler at /home/admatic/esp/esp-idf/components/esp32/panic.c:707

0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

V (556) memory_layout: Examining memory region 0x40084000 - 0x40086000
0x40084000: commonErrorHandler at /home/admatic/esp/esp-idf/components/esp32/panic.c:707

0x40086000: prvDeleteTCB at /home/admatic/esp/esp-idf/components/freertos/tasks.c:4590

V (563) memory_layout: Region 0x40084000 - 0x40086000 inside of reserved 0x40080000 - 0x40088094
0x40084000: commonErrorHandler at /home/admatic/esp/esp-idf/components/esp32/panic.c:707

0x40086000: prvDeleteTCB at /home/admatic/esp/esp-idf/components/freertos/tasks.c:4590

0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

V (571) memory_layout: Examining memory region 0x40086000 - 0x40088000
0x40086000: prvDeleteTCB at /home/admatic/esp/esp-idf/components/freertos/tasks.c:4590

0x40088000: multi_heap_register_impl at /home/admatic/esp/esp-idf/components/heap/multi_heap.c:336

V (577) memory_layout: Region 0x40086000 - 0x40088000 inside of reserved 0x40080000 - 0x40088094
0x40086000: prvDeleteTCB at /home/admatic/esp/esp-idf/components/freertos/tasks.c:4590

0x40088000: multi_heap_register_impl at /home/admatic/esp/esp-idf/components/heap/multi_heap.c:336

0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

V (586) memory_layout: Examining memory region 0x40088000 - 0x4008a000
0x40088000: multi_heap_register_impl at /home/admatic/esp/esp-idf/components/heap/multi_heap.c:336

V (592) memory_layout: Start of region 0x40088000 - 0x4008a000 overlaps reserved 0x40080000 - 0x40088094
0x40088000: multi_heap_register_impl at /home/admatic/esp/esp-idf/components/heap/multi_heap.c:336

0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

D (601) memory_layout: Available memory region 0x40088094 - 0x4008a000
V (608) memory_layout: Examining memory region 0x4008a000 - 0x4008c000
D (614) memory_layout: Available memory region 0x4008a000 - 0x4008c000
V (620) memory_layout: Examining memory region 0x4008c000 - 0x4008e000
D (626) memory_layout: Available memory region 0x4008c000 - 0x4008e000
V (633) memory_layout: Examining memory region 0x4008e000 - 0x40090000
D (639) memory_layout: Available memory region 0x4008e000 - 0x40090000
V (645) memory_layout: Examining memory region 0x40090000 - 0x40092000
D (651) memory_layout: Available memory region 0x40090000 - 0x40092000
V (658) memory_layout: Examining memory region 0x40092000 - 0x40094000
D (664) memory_layout: Available memory region 0x40092000 - 0x40094000
V (670) memory_layout: Examining memory region 0x40094000 - 0x40096000
D (676) memory_layout: Available memory region 0x40094000 - 0x40096000
V (683) memory_layout: Examining memory region 0x40096000 - 0x40098000
D (689) memory_layout: Available memory region 0x40096000 - 0x40098000
V (695) memory_layout: Examining memory region 0x40098000 - 0x4009a000
D (701) memory_layout: Available memory region 0x40098000 - 0x4009a000
V (708) memory_layout: Examining memory region 0x4009a000 - 0x4009c000
D (714) memory_layout: Available memory region 0x4009a000 - 0x4009c000
V (720) memory_layout: Examining memory region 0x4009c000 - 0x4009e000
D (726) memory_layout: Available memory region 0x4009c000 - 0x4009e000
V (733) memory_layout: Examining memory region 0x4009e000 - 0x400a0000
D (739) memory_layout: Available memory region 0x4009e000 - 0x400a0000
I (745) heap_init: Initializing. RAM available for dynamic allocation:
D (751) heap_init: New heap initialised at 0x3ffae6e0
I (756) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
D (761) heap_init: New heap initialised at 0x3ffb2aa0
I (766) heap_init: At 3FFB2AA0 len 0002D560 (181 KiB): DRAM
I (771) heap_init: At 3FFE0440 len 0001FBC0 (126 KiB): D/IRAM
D (777) heap_init: New heap initialised at 0x40078000
I (782) heap_init: At 40078000 len 00008000 (32 KiB): IRAM
D (787) heap_init: New heap initialised at 0x40088094
I (792) heap_init: At 40088094 len 00017F6C (95 KiB): IRAM
I (797) cpu_start: Pro cpu start user code
D (808) clk: RTC_SLOW_CLK calibration value: 3231514
V (146) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (146) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (150) intr_alloc: Connected src 46 to int 2 (cpu 0)
V (155) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (161) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xC0E
D (169) intr_alloc: Connected src 57 to int 3 (cpu 0)
V (173) esp_dbg_stubs: esp_dbg_stubs_init stubs 3ffb1e88
V (179) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (184) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0x40E
D (192) intr_alloc: Connected src 24 to int 9 (cpu 0)
I (197) cpu_start: Starting scheduler on PRO CPU.
D (202) heap_init: New heap initialised at 0x3ffe0440
V (206) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (206) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (206) intr_alloc: Connected src 16 to int 12 (cpu 0)
D (225) gps: >> doGPS
V (227) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (227) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (227) intr_alloc: Connected src 35 to int 13 (cpu 0)
Can you please guide me through this.
Thanks in advance.

WiFive
Posts: 2151
Joined: Tue Dec 01, 2015 7:35 am

Re: memory_layout issue

Postby WiFive » Sun Mar 17, 2019 12:30 pm

Messages like this are just false detections by idf_monitor

Code: Select all

0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

georgecarlo
Posts: 16
Joined: Fri Jan 18, 2019 5:55 am

Re: memory_layout issue

Postby georgecarlo » Mon Mar 18, 2019 4:41 am

WiFive wrote:
Sun Mar 17, 2019 12:30 pm
Messages like this are just false detections by idf_monitor

Code: Select all

0x40080000: _WindowOverflow4 at /home/admatic/esp/esp-idf/components/freertos/xtensa_vectors.S:1685
Thanks for the reply.
Those are not my issues, gps lines(values from my gps sensor) are not given in the monitor, instead

Code: Select all

V (146) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (146) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (150) intr_alloc: Connected src 46 to int 2 (cpu 0)
V (155) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (161) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xC0E
D (169) intr_alloc: Connected src 57 to int 3 (cpu 0)
V (173) esp_dbg_stubs: esp_dbg_stubs_init stubs 3ffb1e88
V (179) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (184) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0x40E
D (192) intr_alloc: Connected src 24 to int 9 (cpu 0)
I (197) cpu_start: Starting scheduler on PRO CPU.
D (202) heap_init: New heap initialised at 0x3ffe0440
V (206) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (206) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (206) intr_alloc: Connected src 16 to int 12 (cpu 0)
D (225) gps: >> doGPS
V (227) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (227) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (227) intr_alloc: Connected src 35 to int 13 (cpu 0)
I dont know what they mean. and how do i solve it.

WiFive
Posts: 2151
Joined: Tue Dec 01, 2015 7:35 am

Re: memory_layout issue

Postby WiFive » Mon Mar 18, 2019 6:07 am

Well the title of your post is "memory_layout issue". There are no errors shown. Are you sure there is serial data coming in on the correct pin?

Return to “General Discussion”

Who is online

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