Look for a directory lib/security under your Java Home directory. However, before you can install it you will need to modify the security settings of your JVM. Once you have installed it, you need the GNU ARM toolkit. You will want the CDT Build of Eclipse NEON Info : esp32.cpu0: Target halted, pc=0x400DBFE8 ($YOUR_HOME)/openocd-esp32/src/openocd -s ($YOUR_HOME)/openocd-esp32/tcl -f ($YOURHOME)/openocd-esp32/esp32.cfg It should be copied to the top level of openocd-esp32. This is the one that openocd uses as a command-line script. You will find one of them in the "Docs" directory of ESP-IDF. You will need two ESP32 config files to make openocd work.Ĭonfusingly, they are both called ESP32.cfg I used the readme.OSX instructions and built and installed it using Brew. You will need to build openocd-esp32 from this github repository: You cannot "see" threads on CPU1 via this setup (They appear on different GDB Ports) SIngle stepping uses these BPs and seems to work fine (if slowly) The other implication of this is that you can only use Hardware Breakpoints of which the ESP32 has two. To do this you'll need to disconnect the debugger from its USB port. So you'll need to "make flash" before doing a debug run. Note that we run from Flash as this version of doesn't not have the ability to run from RAM. There is an Eclipse plugin for ARM which works with the ESP32. I explored the use of the standard OpenOCD/GDB pipe technique, but couldn't get it to work. The JTAG Hardware is a C232HM-DDHSL-0 although any FTDI compatible 3.3V USB->Serial converter should work. Note the need to manually flash the device before debug.įor debug we use the JTAG, OpenOCD and GDB. We use an FTDI Debugger, but they should work with others.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |