Forum Replies Created
-
Posts
-
Hi,
This could be caused by some non-typical data types or rare combinations of settings. If you could describe how exactly you are using the Visual Watch, what do you expect and what actually happens, we should be able to suggest a way to get it to work.
Hi,
We will include it in v5.3 if it proves stable enough. The drawback of the new mechanism is that it unloads the VS project, edits it and then reloads it back, that might cause unforeseen side effects. We will definitely include this in either the first or the second v5.3 preview and decide whether to include it in the final build based on the feedback we get.
Hi,
Strange. Does the regular (non-JTAG) NodeMCU setup work as expected? If not, the module might simply be corrupt. If yes, what happens if you program the firmware via the gdb stub and then change the debug method to JTAG and select “do not program FLASH memory”?
Hi,
Yes, our Kinetis packages are less sophisticated than STM32 and Nordic ones, so the driver .c files need to be added to the project manually. The missing include paths should still be automatically discovered after you open any of the files that tries to include the missing headers.
Hi,
The files should still be generated (the extension is .ihex, not .hex). If not, please check the Embedded Project page of VS project properties (not VisualGDB project properties). The “generate .hex file” should be set to “yes”.
Hi,
This is a known issue. It looks like the KSDK manifest format has recently changed. We are working on a fix for it and will release an update in the next few weeks.
Hi,
This could be caused by incompatible FLASH settings or if VisualGDB had problems resetting the board. Can you confirm that the basic LEDBlink program shown in the tutorial gets programmed and the LED actually blinks after you restart the board manually?
If yes, what happens if you press the reset button while the debug session is active, try resuming it and then set a breakpoint in the blinking loop?
Hi,
This could be our bug. Are you able to reproduce this with a basic “Hello, world” project, or does it only happen for a certain big project?
Hi,
As a part of a workaround to a different VS bug, we have experimented with editing the .vcxproj files directly instead of using the VS APIs. This mechanism seems to work, although it is not 100% stable yet. If you are interested to try it out, we could send you a preliminary build with this feature in the next 1-2 weeks.
Hi,
The connection looks very similar to what we have (unless the individual pins are confused), so the best advice we could give is to double-check each and every connection with a multimeter (also check for accidental short-circuited wires) or try another NodeMCU board.
This could also be caused by some undocumented ESP8266 functionality disabling the JTAG connection, so erasing the FLASH using the serial bootloader might help as well.
Hi,
This still looks like a configuration error. Please try manually checking the <project>\build\sdkconfig file for lines like this:
CONFIG_ESPTOOLPY_PORT="/dev/ttyUSB0" CONFIG_ESPTOOLPY_BAUD_115200B=y
Do the port name and baud rate mentioned there make sense? If yes, please try flashing the ESP32 in verbose mode:
make flash V=1
This should show the command line of esptool.py. Does the port path shown there match the port path shown in the sdkconfig file?
Hi,
Looks like you are missing some source files or libraries. Please try searching the ESP-IDF tree for .c and .a files containing the ‘
emac_send_pause_zero_frame_enable'text and then try adding them to your project.Hi,
Please double-check the serial port name you have specified in the project settings (see step 6 of the tutorial). Most likely it does not match the actual COM port number used by the device.
Hi,
This looks like a JTAG wiring problem. Please double-check the JTAG pins you are using and ensure you have no other hardware connected to them.
