![]() I ask all these questions, as I believe the problem may be related to these debug memory parameters, and not the electrical, connection or power issues. Is there a reset option, or perhaps it does not apply to JTAG programming? I of course have the NodeMCU setting in VisualMicro, but I cannot find a similar setting in VisualGDB. There are apparently 2 reset options: “ct” and “nodemcu”.While on the topic of memory settings – what do the -C1 and -C2 suffixes mean?.What value should I use in VisualGDB? I’ve tried them all. Are the units bits or bytes? The default list all have little “m”s – so is that bits? For VisualMicro I have a setting of 4m (1M SPIFFS) when I program via the UART. There’s a size option in the debug section.How can I confirm the DIO mode is being used once changed in Debug config? (and does this matter to JTAG?) In the Debug Settings: Is “Frequency” the CPU or Flash frequency? For VisualMicro I use 80MHz for CPU and 40MHZ for Flash Frequency.I’ve kept the default of 4096 in all my attempts. In the Debug settings: Is the Sector Size and Erase Block size ever a function of ESP8266 flavor? I’ve use the Arduino / VisualMicro uploaders and have not seen that option.If manually loading these files via something like the NodeMCI Firmeware Programmer, what’s the load address of the largest file? What is the purpose of each of them? Are they actually all supposed to be loaded into the ESP8266? Project-0x20000.binI assume the numbers are meant to be firmware addressed, but the two with numbers are relatively small, and the largest file (project.bin) has no number. There are 3 binary files created in the \VisualGDB\Debug directory:.I have a variety of questions, that perhaps would be good to add to a new “ESP8266” section at (?) □ It is the JTAG issue I’m struggling with. I can definitely program the NodeMCU units via VisualMicro / UART with no problems. I’ve even tried powering the NodeMCU separately with 3.3V, ignoring the on-board UART, leaving it powered off: same results. But I’ve tried two different NodeMCU’s with no success. If I had not had success with the Olimex ESP8266-EVB, I may have given up. ![]() I’m thinking that despite the message “The device has been programmed successfully”, it has not – particularly given the exception “cause:2”. This is the default speed for error messages if not set by target application. Syst?param error, use last saved param!ītw – Feature request: please add the default “74880” speed to dropdown. When running, the program uploaded repeatedly spews reboot because of exception messages:Įts Jan 8 2013,rst cause:2, boot mode:(3,6) ~”Restoring binary file C:/workspace/OMC/VisualGDB/Debug/OMC-0x10000.bin into memory (0x3ffe8008 to 0x3fff75ac)\n” Curiously the raw GDB only mentions one binary file: It does however, seem to go through all the motions and after a brief period claims to have successfully programmed the device. Watchdog feeding during stops is now enabled Interrupt suppression during single-stepping is now enabled Have halted some time after resetting (not Warn : xtensa_deassert_reset: ‘reset halt’ is not supported for Xtensa. Warn : Bypassing JTAG setup events due to errors Info : accepting ‘gdb’ connection on tcp/3333Įrror: JTAG scan chain interrogation failed: all zeroesĮrror: Check JTAG interface, timings, target power, etc.Įrror: Trying to use configured scan chain anyway…Įrror: esp8266.cpu: IR capture error saw 0x00 not 0x01 ![]() However when actually programming, I get the dreaded “all zeros” JTAG message: Info : accepting ‘telnet’ connection on tcp/4444 Info : TAP esp8266.cpu does not have IDCODE Trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srstĮrror: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED When testing the settings, all appears well (in this case with the Olimex ARM-USB-OCD-H_:Ĭ:\SysGCC\esp8266\esp8266-bsp\OpenOCD\bin\openocd.exe -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -f target/esp8266.cfg With that success, I hoped to be able to program the NodeMCU. I’ve had success with the Olimex as described in the sysprogs tutorial, targeting the Olimex ESP8266-EVB. I’m trying to get my JTAG programmer (either an Olimex ARM-USB-OCD-H or Segger J-Link EDU) to program, and ideally step debug the ESP8266.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |