[lumi]

Thanks, I should have thought of that.

The blink project worked, so I committed my project’s changes, deleted and cloned it back. Now it’s working again, thank you!

[lumi]

Hi,

Manual running causes the same error. My sdkconfig files are the same (I copied sdkconfig to sdkconfig-debug to be sure). What else should I look at for my environment knowing I cleaned/rebuilt a few times just before enabling the signed app options?

—— Clean started: Project: ProjectName, Configuration: Debug VisualGDB ——
VisualGDB: Run “C:\Users\username\Source\SysGCC\usr\bin\bash.exe –login -c “export IDF_PATH=/esp-idf/v3.2 && export BATCH_BUILD=1 && export PATH=/mingw32/bin:$PATH && export -n PYTHONHOME && export LANG=en_US && cd /C/Users/username/Source/Firmware/ProjectName/ProjectName && make clean BUILD_DIR_BASE=’/C/Users/username/Source/Firmware/ProjectName/ProjectName/Debug’ SDKCONFIG=’/C/Users/username/Source/Firmware/ProjectName/ProjectName/sdkconfig-debug’ V=0″” in directory “” on local computer
/esp-idf/v3.2/make/project.mk:139: SRCDIRS variable is deprecated. These paths can be added to EXTRA_COMPONENT_DIRS or COMPONENT_DIRS instead.
including /esp-idf/v3.2/components/app_update/Makefile.projbuild…
including /esp-idf/v3.2/components/bootloader/Makefile.projbuild…
including /esp-idf/v3.2/components/bootloader_support/Makefile.projbuild…
C:\Users\username\Source\SysGCC\esp-idf\v3.2\components\bootloader_support\Makefile.projbuild(1): error : target pattern contains no ‘%’.  Stop.

[lumi]

Thanks, I had an additional source path mapping entered that referenced my project folder to the cygdrive alternate. Not sure why.  Removing that fixed the problem for me.

[lumi]

Of course just after I post, I find http://gnutoolchains.com/esp32/

[lumi]

Here’s that last step. If I set the Max following/proceeding comment lines to 5000, this fixes the issue (by no longer showing the popups that crash).

Attachments:

You must be logged in to view attached files.

[lumi]

My Setup:

• Intel i7 870
• Radeon HD 4550 with windows update driver, devmgr says version 8.970.100.9001
• dual monitors (each 1920×1200)

[lumi]

So it’s definitely related to the tooltip.  Right after testing I was ok with vTaskDelay and posting, I crashed on xEventGroupSetBits.  I think I’ve been ok so far this week because I wasn’t working near code using the FreeRTOS functions.

The call stack simply was [External Code].  Maybe I’m not setup correctly?  It is debugging in Managed mode.

Edit – VisualGDB build is 2193

• This reply was modified 6 years, 6 months ago by lumi.

[lumi]

There is an issue somewhere.  I was also getting hangups requiring me to use the task manager to end the VS2017 task.  I’m using the same software versions on an ESP32 project (1920×1200 screen though).  I’m not so sure the tooltip is the cause but it may be related. Last week I was at a point where simply opening my solution would cause the crash.  I found that a 2nd 2017 instance didn’t crash, so I ended up working a day with a hung instance in the background.

This week everything has been fine??

If it hangs again I’ll check the call stack.

 

[Author]

Posts