Closed iceblu3710 closed 2 years ago
Repeating the process but with a new git clone of TRS-IO I get a little further.
I can connect to the AP and I get the IP 192.168.4.2 but TRS-IO.local or 192.168.4.1 say connection refused.
MONITOR
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun 8 2016 00:22:57
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:5400
load:0x40078000,len:10868
load:0x40080400,len:6412
entry 0x40080758
I (318) cpu_start: Pro cpu up.
I (318) cpu_start: Starting app cpu, entry point is 0x40081014
0x40081014: call_start_cpu1 at /home/uminded/esp/esp-idf/components/esp32/cpu_start.c:246
I (0) cpu_start: App cpu up.
D (320) memory_layout: Checking 7 reserved memory ranges:
D (326) memory_layout: Reserved memory range 0x3ffae000 - 0x3ffae6e0
D (332) memory_layout: Reserved memory range 0x3ffb0000 - 0x3ffd8c50
D (338) memory_layout: Reserved memory range 0x3ffe0000 - 0x3ffe0440
D (345) memory_layout: Reserved memory range 0x3ffe3f20 - 0x3ffe4350
D (351) memory_layout: Reserved memory range 0x40070000 - 0x40078000
D (358) memory_layout: Reserved memory range 0x40078000 - 0x40080000
0x40080000: _WindowOverflow4 at /home/uminded/esp/esp-idf/components/freertos/xtensa_vectors.S:1779
D (364) memory_layout: Reserved memory range 0x40080000 - 0x40090098
0x40080000: _WindowOverflow4 at /home/uminded/esp/esp-idf/components/freertos/xtensa_vectors.S:1779
D (371) memory_layout: Building list of available memory regions:
D (377) memory_layout: Available memory region 0x3ffae6e0 - 0x3ffb0000
D (383) memory_layout: Available memory region 0x3ffd8c50 - 0x3ffda000
D (390) memory_layout: Available memory region 0x3ffda000 - 0x3ffdc000
D (397) memory_layout: Available memory region 0x3ffdc000 - 0x3ffde000
D (403) memory_layout: Available memory region 0x3ffde000 - 0x3ffe0000
D (410) memory_layout: Available memory region 0x3ffe0440 - 0x3ffe3f20
D (416) memory_layout: Available memory region 0x3ffe4350 - 0x3ffe8000
D (423) memory_layout: Available memory region 0x3ffe8000 - 0x3fff0000
D (430) memory_layout: Available memory region 0x3fff0000 - 0x3fff8000
D (436) memory_layout: Available memory region 0x3fff8000 - 0x3fffc000
D (443) memory_layout: Available memory region 0x3fffc000 - 0x40000000
D (449) memory_layout: Available memory region 0x40090098 - 0x40092000
D (456) memory_layout: Available memory region 0x40092000 - 0x40094000
D (463) memory_layout: Available memory region 0x40094000 - 0x40096000
D (469) memory_layout: Available memory region 0x40096000 - 0x40098000
D (476) memory_layout: Available memory region 0x40098000 - 0x4009a000
D (482) memory_layout: Available memory region 0x4009a000 - 0x4009c000
D (489) memory_layout: Available memory region 0x4009c000 - 0x4009e000
D (496) memory_layout: Available memory region 0x4009e000 - 0x400a0000
I (502) heap_init: Initializing. RAM available for dynamic allocation:
D (509) heap_init: New heap initialised at 0x3ffae6e0
I (514) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
D (521) heap_init: New heap initialised at 0x3ffd8c50
I (526) heap_init: At 3FFD8C50 len 000073B0 (28 KiB): DRAM
I (532) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (538) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
D (545) heap_init: New heap initialised at 0x40090098
I (550) heap_init: At 40090098 len 0000FF68 (63 KiB): IRAM
I (556) cpu_start: Pro cpu start user code
D (568) clk: RTC_SLOW_CLK calibration value: 3421069
D (130) intr_alloc: Connected src 46 to int 2 (cpu 0)
D (131) intr_alloc: Connected src 57 to int 3 (cpu 0)
D (132) intr_alloc: Connected src 24 to int 9 (cpu 0)
I (136) cpu_start: Starting scheduler on PRO CPU.
D (0) intr_alloc: Connected src 25 to int 2 (cpu 1)
I (4) cpu_start: Starting scheduler on APP CPU.
D (160) heap_init: New heap initialised at 0x3ffe0440
D (166) heap_init: New heap initialised at 0x3ffe4350
D (171) intr_alloc: Connected src 16 to int 12 (cpu 0)
I (176) gpio: GPIO[4]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 1| Intr:0
I (185) gpio: GPIO[5]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 1| Intr:0
I (194) gpio: GPIO[21]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 1| Intr:0
I (204) gpio: GPIO[22]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
D (213) intr_alloc: Connected src 22 to int 13 (cpu 0)
D (219) nvs: nvs_flash_init_custom partition=nvs start=9 count=4
D (256) nvs: nvs_open_from_partition retrostore 1
I (258) wifi: wifi driver task: 3ffe360c, prio:23, stack:3584, core=0
I (258) wifi: wifi firmware version: 693c7b6
I (260) wifi: config NVS flash: disabled
I (264) wifi: config nano formating: disabled
I (268) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (277) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (288) wifi: Init dynamic tx buffer num: 32
I (291) wifi: Init data frame dynamic rx buffer num: 32
I (296) wifi: Init management frame dynamic rx buffer num: 32
I (301) wifi: Init management short buffer num: 32
I (306) wifi: Init static rx buffer size: 1600
I (310) wifi: Init static rx buffer num: 10
I (314) wifi: Init dynamic rx buffer num: 32
D (318) nvs: nvs_get_str_or_blob ssid
D (322) nvs: nvs_get ssid 4
D (325) RTC_MODULE: Wi-Fi takes adc2 lock.
D (329) phy_init: loading PHY init data from application binary
D (335) nvs: nvs_open_from_partition phy 0
D (339) nvs: nvs_get cal_version 4
D (342) nvs: nvs_get_str_or_blob cal_mac
D (347) nvs: nvs_get_str_or_blob cal_data
D (356) nvs: nvs_close 2
I (417) phy: phy_version: 4008, 544f89f, Jan 24 2019, 14:54:06, 0, 0
I (419) wifi: mode : softAP (84:0d:8e:e6:6d:a5)
I (420) wifi: Total power save buffer number: 16
I (422) wifi: Init max length of beacon: 752/752
I (427) wifi: Init max length of beacon: 752/752
D (431) event: SYSTEM_EVENT_AP_START
I (434) TRS-IO: wifi_init_ap finished.SSID:TRS-IO
D (436) tcpip_adapter: dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)
I (449) gpio: GPIO[12]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (458) gpio: GPIO[13]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (467) gpio: GPIO[14]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (476) gpio: GPIO[15]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (485) gpio: GPIO[16]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (495) gpio: GPIO[17]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (504) gpio: GPIO[18]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (513) gpio: GPIO[19]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (523) gpio: GPIO[32]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (532) gpio: GPIO[33]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (541) gpio: GPIO[34]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (550) gpio: GPIO[35]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (560) gpio: GPIO[36]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (569) gpio: GPIO[23]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (578) gpio: GPIO[39]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (588) gpio: GPIO[25]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (597) gpio: GPIO[27]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
E (5176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (5176) task_wdt: - IDLE0 (CPU 0)
E (5176) task_wdt: Tasks currently running:
E (5176) task_wdt: CPU 0: main
E (5176) task_wdt: CPU 1: io
E (10176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (10176) task_wdt: - IDLE0 (CPU 0)
E (10176) task_wdt: Tasks currently running:
E (10176) task_wdt: CPU 0: main
E (10176) task_wdt: CPU 1: io
E (15176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (15176) task_wdt: - IDLE0 (CPU 0)
E (15176) task_wdt: Tasks currently running:
E (15176) task_wdt: CPU 0: main
E (15176) task_wdt: CPU 1: io
E (20176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (20176) task_wdt: - IDLE0 (CPU 0)
E (20176) task_wdt: Tasks currently running:
E (20176) task_wdt: CPU 0: main
E (20176) task_wdt: CPU 1: io
E (25176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (25176) task_wdt: - IDLE0 (CPU 0)
E (25176) task_wdt: Tasks currently running:
E (25176) task_wdt: CPU 0: main
E (25176) task_wdt: CPU 1: io
E (30176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (30176) task_wdt: - IDLE0 (CPU 0)
E (30176) task_wdt: Tasks currently running:
E (30176) task_wdt: CPU 0: main
E (30176) task_wdt: CPU 1: io
E (35176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (35176) task_wdt: - IDLE0 (CPU 0)
E (35176) task_wdt: Tasks currently running:
E (35176) task_wdt: CPU 0: main
E (35176) task_wdt: CPU 1: io
E (40176) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
It seems the HTTP task is not running which is why you cannot connect. But you shouldn't get those watchdog timers either. What is the precise ESP32 model you are using?
The only one easily available was Digikey 1965-1003-ND. ESP32-WROOM-32D
Any ideas? The 32 and 32D are the same chip just a different die revision and layout under the can.
This is the ESP32 version I am using: https://www.amazon.com/gp/product/B0718T232Z/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
I know that @jaquinn also had some issues with other ESP32 flavors. If possible, could you try the version I am using?
There is a pending pull request which updates the build documentation to confirm the supported ESP32 modules and the orientation on the board.
Interestingly, I had similar issues with the Task Watchdog and it was due to omitting to solder of pin 1 on both the 74LVC245. Have a close look at your board to be sure the solder joints are all OK.
I'm closing this issue. TRS-IO now requires ESP-IDF 4.2.2. If you have issues with the latest version, please re-open this issue.
I got esp-idf v3.2.2 installed and can load the hello world example successfully.
I ran make in the src folder and was asked a dozen questions I know nothing about. I do know if you select release instead of debug you get compile errors. I stayed with debug and it compiled. I then went to src/esp and did a make menuconfig, set the TTY and then make flash monitor and I get a esp32 program crashing.