Search found 30 matches
- Wed Oct 17, 2018 7:34 am
- Forum: ESP-IDF
- Topic: Debugging Issue: OpenOCD & GDB reporting stack level of -1, crashing Microsoft MI
- Replies: 5
- Views: 6225
Re: Debugging Issue: OpenOCD & GDB reporting stack level of -1, crashing Microsoft MI
Sent! Thanks for your help and prompt replies.
- Wed Oct 17, 2018 7:25 am
- Forum: General Discussion
- Topic: PlatformIO thoughts?
- Replies: 4
- Views: 5497
Re: PlatformIO thoughts?
You're right. I have it downloaded. I'm going to try it myself.
- Tue Oct 16, 2018 1:39 am
- Forum: General Discussion
- Topic: PlatformIO thoughts?
- Replies: 4
- Views: 5497
PlatformIO thoughts?
I was referred to try using PlatformIO with VSCode to debug, but I recall seeing poor reviews of PlatformIO. Does anyone have experience they would like to share regarding using PlatformIO with ESP32?
- Tue Oct 16, 2018 1:37 am
- Forum: ESP-IDF
- Topic: Debugging Issue: OpenOCD & GDB reporting stack level of -1, crashing Microsoft MI
- Replies: 5
- Views: 6225
Re: Debugging Issue: OpenOCD & GDB reporting stack level of -1, crashing Microsoft MI
Yeah I went to look in the settings and I'm have "miDebuggerPath": "/Users/zhe/esp/xtensa-esp32-elf/bin/xtensa-esp32-elf-gdb", in my debug config. So it seems that is not the problem. I found that even when I start GDB on command line mode, my app_main has a stack level of -1, while the documentatio...
- Mon Oct 15, 2018 1:30 am
- Forum: ESP-IDF
- Topic: Debugging Issue: OpenOCD & GDB reporting stack level of -1, crashing Microsoft MI
- Replies: 5
- Views: 6225
Debugging Issue: OpenOCD & GDB reporting stack level of -1, crashing Microsoft MI
#-1 app_main () at /Users/zhe/esp/wifihub/main/main.c:59 Backtrace stopped: Cannot access memory at address 0x400d3bd4 I am getting the above and it seems to be confusing MI Engine. Does anyone know why the stack level would start at -1 instead of 0? Microsoft reported this may happen if the gdb <-...
- Fri Oct 12, 2018 5:48 am
- Forum: General Discussion
- Topic: UART FIFO issue after updating ESP-IDF
- Replies: 4
- Views: 5145
Re: UART FIFO issue after updating ESP-IDF
Sorry about that! I really wanted to delete the post because I felt it was a silly issue.
Issue: UART FIFO getting random pieces of data leftover.
Reason: I was using IO pins that JTAG uses.
Issue: UART FIFO getting random pieces of data leftover.
Reason: I was using IO pins that JTAG uses.
- Thu Sep 20, 2018 4:29 am
- Forum: General Discussion
- Topic: UART FIFO issue after updating ESP-IDF
- Replies: 4
- Views: 5145
- Wed Sep 19, 2018 10:30 am
- Forum: General Discussion
- Topic: UART FIFO issue after updating ESP-IDF
- Replies: 4
- Views: 5145
- Mon Sep 17, 2018 6:51 am
- Forum: General Discussion
- Topic: Problems with WROVER JTAG configuration
- Replies: 0
- Views: 2352
Problems with WROVER JTAG configuration
"https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/configure-wrover.html" I've tried modifying the FTDI driver configuration file as and disabling kext but starting openocd gives me Error: libusb_claim_interface() failed with LIBUSB_ERROR_ACCESS Error: unable to open ft...
- Mon Sep 17, 2018 6:46 am
- Forum: General Discussion
- Topic: Mac power supply insufficient for WROVER Kit?
- Replies: 1
- Views: 2588
Mac power supply insufficient for WROVER Kit?
Has anyone else experienced this? During flashing, I am not receiving the header packet while connected to my WROVER-Kit V4 using an USB. I suspect it is because the power supplied by my Mac's usb port is not sufficient. I've already ordered an externally powered USB adapter but I wanted to check on...