tag:blogger.com,1999:blog-4109066286647243251.post1431179772992003382..comments2024-02-21T00:33:54.667-08:00Comments on GoJimmyPi: JTAG Debugging for ESP32gojimmypihttp://www.blogger.com/profile/14776345152065605589noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-4109066286647243251.post-41897816024101751092018-10-22T11:04:50.298-07:002018-10-22T11:04:50.298-07:00Thanks for the article and pics. I got GDB workin...Thanks for the article and pics. I got GDB working with ESP32 devkit C and J-Link EDU. I am unable to get System View trace working. Not sure if it's a license thing on the J-Link or if I'm doing something wrong. I ordered a FT2232H board to see if that makes a difference.chris miszturhttps://www.blogger.com/profile/09081816083041143049noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-14822679665832800862018-02-24T14:35:51.917-08:002018-02-24T14:35:51.917-08:00Thank you. :) They are called "Dupont Wire Ju...Thank you. :) They are called "Dupont Wire Jumpers" - I got mine from one of my favorite sellers on ebay: http://stores.ebay.com/TxHang-Electronic/_i.html?_nkw=wire+jumper&submit=Search - handy to have M-M, F-M and F-Fgojimmypihttps://www.blogger.com/profile/14776345152065605589noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-32307975985211457992018-02-24T00:54:23.791-08:002018-02-24T00:54:23.791-08:00Hi !
Very interesting article. Can you tell we wh...Hi !<br /><br />Very interesting article. Can you tell we where you found the ribbon cable with separated pins you use on your JLINK ?<br />Anonymoushttps://www.blogger.com/profile/13580155962643965215noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-91290785307436688372017-06-09T15:44:42.712-07:002017-06-09T15:44:42.712-07:00I had a lot of problems using an FT cable as well....I had a lot of problems using an FT cable as well. In the end what helped get things moving was to change the alg_timeout to 10 seconds in the debug-vgbsetting file, which is part of the project. It defaults to 5 seconds which is not long enough for the flash to erase. <br /> <br /> com.sysprogs.esp32.openocd.alg_timeout<br /> 10000<br /> <br /><br />Today I reconnected the J-Link and it was working.<br /><br />Did you change this in your setup?<br />Anonymoushttps://www.blogger.com/profile/11292332201204773180noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-45322228528910131232017-05-19T07:54:10.543-07:002017-05-19T07:54:10.543-07:00Hi Tom - Yes, I had similar comments from the sysp...Hi Tom - Yes, I had similar comments from the sysprogs team regarding JTAG debugging of the ESP devices. I don't recall if I made any other VS settings, but you can see my source files here:<br /><br />https://github.com/gojimmypi/ESP32/tree/master/ESP32-JTAG-VisualGDB<br /><br />It has been a couple of months, and I don't recall if needed for JTAG as well as USB programming... but are you holding down the flash button while powering up the ESP32?gojimmypihttps://www.blogger.com/profile/14776345152065605589noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-54653465250332324132017-05-18T21:42:54.024-07:002017-05-18T21:42:54.024-07:00Did you make any other setting changes in VisualGD...Did you make any other setting changes in VisualGDB to get this working? Here is a reply to my question from Sysprogs:<br /><br />Generally, ESP8266 and ESP32 are much less reliable than ARM-based models and often require experimenting with various options in order to get everything working. If you are looking for a solution that works out-of-the-box, we would recommend CC3200, otherwise feel free to post details on the FLASH programming errors you get and we will try to suggest a solution if this is something known.<br />Anonymoushttps://www.blogger.com/profile/11292332201204773180noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-72095949041436337772017-05-18T20:35:20.220-07:002017-05-18T20:35:20.220-07:00It keeps telling me some GDB command fails to comp...It keeps telling me some GDB command fails to complete when attempting to flash the ESP32. It tries 3 times then gives up. I am powering the ESP32 from the USB cable with a tested cable.Anonymoushttps://www.blogger.com/profile/11292332201204773180noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-53005372760819562532017-05-18T18:16:19.733-07:002017-05-18T18:16:19.733-07:00That's an astute observation! I agree that the...That's an astute observation! I agree that the pin in the Segger is NC, and is likely a leftover during my trial-and-error phase - as when googling "segger j-link pinout" oddly some of the pics will show Pin 2 as TRST. <br /><br />https://www.segger.com/interface-description.html<br /><br />I will recheck my wiring soon and confirm - but in the meantime, I suggest you check out VSCode (no, seriously!). It has amazing debug capabilities - although I did need to run OpenOCD server on an Ubuntu VM. I have another blog that talks about that just this month (May 2017)<br /><br />hmm.. other ideas: I assume you've also tried the usual power cycle of Segger? You are powering the ESP32 separately, too - right - with a known good cable (try a different one)? Be careful of ground loops.gojimmypihttps://www.blogger.com/profile/14776345152065605589noreply@blogger.comtag:blogger.com,1999:blog-4109066286647243251.post-4469160732580946432017-05-18T17:32:42.513-07:002017-05-18T17:32:42.513-07:00Hi, I am trying your setup for debugging an ESP32 ...Hi, I am trying your setup for debugging an ESP32 with a Segger J-link, however it fails to flash the ESP32 with a Not Responding error. The test settings button does indicate all is correct.<br /><br />In your picture of the J-Link connection, you have a brown wire to the ESP32 ground, but on the J-Link connector it looks like it is hooked to pin-2 which is NC.<br /><br />Do you have any thoughts?Anonymoushttps://www.blogger.com/profile/11292332201204773180noreply@blogger.com