Thanks for your advice.
In this case it seems esp32 linker has issue with debug build.
Sometimes we still need debug build for further debugging...
Search found 13 matches
- Tue Mar 14, 2017 12:14 pm
- Forum: ESP-IDF
- Topic: Linking errors with BFD assertion fail
- Replies: 8
- Views: 12414
- Mon Mar 06, 2017 9:22 am
- Forum: ESP-IDF
- Topic: Linking errors with BFD assertion fail
- Replies: 8
- Views: 12414
Re: Linking errors with BFD assertion fail
Thank you for the information. In fact, before post this issue, I have tried to build kolban’s jerryscript, but unfortunately still get the same error. Kolban’s code seems to be used for private use, so he did not release the jerryscript parts for public. https://github.com/nkolban/jerryscript-esp32...
- Mon Mar 06, 2017 7:22 am
- Forum: ESP-IDF
- Topic: Linking errors with BFD assertion fail
- Replies: 8
- Views: 12414
Re: Linking errors with BFD assertion fail
Sorry, I updated the attachment again and slightly modified the following steps. Please ignore the previous one and use the new attachment and steps to build the code. 1. Extract the attachment to the template application 2. Get jerryscript from github and copy all files/directories to components/je...
- Mon Mar 06, 2017 6:27 am
- Forum: ESP-IDF
- Topic: Linking errors with BFD assertion fail
- Replies: 8
- Views: 12414
Re: Linking errors with BFD assertion fail
Please check the attachment below. Actually, the purpose is to simply test jerryscript. Here are the steps to build the code: 1. Extract the attached file to the template application 2. Get jerryscript from github and replace it to components/jerryscript https://github.com/jerryscript-project/jerrys...
- Sat Mar 04, 2017 10:35 am
- Forum: ESP-IDF
- Topic: Linking errors with BFD assertion fail
- Replies: 8
- Views: 12414
Linking errors with BFD assertion fail
I tried porting some codes to ESP32, but I encountered a lot of BFD assertions during code linking. This is the only link error, no other error message appears. I also downloaded and checked the source code for binutils-2.25.1, but I can’t see any assertion at line 8316 in elf32-xtensa.c What is the...
- Thu Feb 23, 2017 6:07 am
- Forum: ESP-IDF
- Topic: Cannot correctly jump to next line in some files when debug with openocd/gdb
- Replies: 6
- Views: 10513
Re: Cannot correctly jump to next line in some files when debug with openocd/gdb
Thank BuddyCasino help me reproduce this issue in his debug environment, at least now I am sure this is not the issue only happened to me. In fact, as long as you set the breakpoint in network related files such as sockets.c in this case, even you just set one breakpoint, you still can’t correctly m...
- Wed Feb 22, 2017 4:35 am
- Forum: ESP-IDF
- Topic: Cannot correctly jump to next line in some files when debug with openocd/gdb
- Replies: 6
- Views: 10513
Re: Cannot correctly jump to next line in some files when debug with openocd/gdb
Can someone kindly give me some advice?
Thanks
Thanks
- Mon Feb 20, 2017 6:06 pm
- Forum: ESP-IDF
- Topic: Cannot correctly jump to next line in some files when debug with openocd/gdb
- Replies: 6
- Views: 10513
Cannot correctly jump to next line in some files when debug with openocd/gdb
I used the following example to debug. examples/protocols/http_request I can set the breakpoint to app_main and it indeed stops at this breakpoint. It's also ok to jump to the next line nvs_flash_init() and initialise_wifi(). Breakpoint 1, app_main () at /esp/esp-idf/examples/http_request/main/./htt...
- Fri Jan 06, 2017 8:03 am
- Forum: General Discussion
- Topic: A fatal error occurred: Failed to connect to Espressif device when download app
- Replies: 1
- Views: 7023
A fatal error occurred: Failed to connect to Espressif device when download app
I do a terrible thing that I used a non-stop while loop to print logs without any delay in app_main (before app task created). I try "make flash" or "esptool.py to erase flash" to reflash the app, but it always shows such error: "A fatal error occurred: Failed to connect to Espressif device: Timed o...
- Mon Jan 02, 2017 3:11 pm
- Forum: ESP-IDF
- Topic: xtensa-esp32-elf-gdb stuck on connecting to remote target
- Replies: 2
- Views: 7241
Re: xtensa-esp32-elf-gdb stuck on connecting to remote target
Thanks, tcp_serial_redirect is working good. However, I also found that there is an alternative to use xtensa-esp32-elf-gdb working on a serial port without redirecting it to tcp, that is, using /dev/cu* instead of /dev/tty*. In MAC, /dev/tty* are called "callin devices", are used for incoming traff...