Sysprogs forums › Forums › VisualGDB › Arduino ESP32 memory file not found
- This topic has 4 replies, 2 voices, and was last updated 6 years, 1 month ago by
support.
-
AuthorPosts
-
March 16, 2019 at 19:49 #24297
fastlink30
ParticipantArduino project with esp32 on DOIT ESP32 DEVKIT V1
—— Inizio compilazione: Progetto: HDMI_VGDB, Configurazione: Debug DOIT_ESP32_DEVKIT_V1 ——
Launching Arduino builder…
VisualGDB: Run “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino\arduino-builder.exe -compile -logger=machine -fqbn=espressif:esp32:esp32doit-devkit-v1:FlashFreq=80,UploadSpeed=921600,DebugLevel=none -build-path C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug -unoptimize=sketch -hardware “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/hardware” -hardware C:\Users\rick\Documents/Arduino/hardware -tools “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/tools-builder” -libraries C:\Users\rick\Documents/Arduino/Libraries sketches/HDMI_VGDB.ino” in directory “C:\Arduino\HDMI_VGDB\HDMI_VGDB” on local computer
In file included from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\MasterHeader.h:15:0,
from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\ETFT.c:1:
C:\Users\rick\Documents\Arduino\hardware\espressif\esp32\libraries\SPI\src\SPI.h(28,1): error : unknown type name ‘class’
class SPISettings
^
C:\Users\rick\Documents\Arduino\hardware\espressif\esp32\libraries\SPI\src\SPI.h(29,1): error : expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{‘ token
{
^
C:\Users\rick\Documents\Arduino\hardware\espressif\esp32\libraries\SPI\src\SPI.h(38,1): error : unknown type name ‘class’
class SPIClass
^
C:\Users\rick\Documents\Arduino\hardware\espressif\esp32\libraries\SPI\src\SPI.h(39,1): error : expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{‘ token
{
^
C:\Users\rick\Documents\Arduino\hardware\espressif\esp32\libraries\SPI\src\SPI.h(85,8): error : unknown type name ‘SPIClass’
extern SPIClass SPI;
^
In file included from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\MasterHeader.h:16:0,
C:\Users\rick\Documents\Arduino\hardware\espressif\esp32\libraries\FS\src\FS.h(24,18): error : memory: No such file or directory
compilation terminated.
exit status 1
————————————————————-
Command exited with code 1
Executable: C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino\arduino-builder.exe
Arguments: -compile -logger=machine -fqbn=espressif:esp32:esp32doit-devkit-v1:FlashFreq=80,UploadSpeed=921600,DebugLevel=none -build-path C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug -unoptimize=sketch -hardware “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/hardware” -hardware C:\Users\rick\Documents/Arduino/hardware -tools “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/tools-builder” -libraries C:\Users\rick\Documents/Arduino/Libraries sketches/HDMI_VGDB.ino
Directory: C:\Arduino\HDMI_VGDB\HDMI_VGDB
VisualGDB: Error: Command-line action failed
========== Compilazione: 0 completate, 1 non riuscite, 0 aggiornate, 0 ignorate ==========why <memory> is not found (also SPIClass)? and how to avoid this?
thanks
March 16, 2019 at 20:01 #24298fastlink30
Participantforgot to write:
VisualGDB version 5.4 build 2737
March 16, 2019 at 22:05 #24299support
KeymasterPlease try updating to the latest VisualGDB 5.4R3.
Also, according to our records, it looks like your trial period has expired. In order to get further technical support, please consider purchasing a license.
March 17, 2019 at 08:13 #24302fastlink30
Participanti have installed v5.4r3 (trial) on another pc, with fresh vs2017, problem is the same, created new project on new machine & copy/paste of files project to the new machine
—— Inizio compilazione: Progetto: HDMI_VGDB, Configurazione: Debug DOIT_ESP32_DEVKIT_V1 ——
Launching Arduino builder…
VisualGDB: Run “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino\arduino-builder.exe -compile -logger=machine -fqbn=esp32:esp32:esp32doit-devkit-v1:FlashFreq=80,UploadSpeed=921600,DebugLevel=none -build-path C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug -unoptimize=sketch -hardware “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/hardware” -hardware C:\Users\rick\AppData\Local/Arduino15/packages -tools “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/tools-builder” -tools C:\Users\rick\AppData\Local/Arduino15/packages -libraries C:\Users\rick\Documents/Arduino/Libraries -prefs=runtime.tools.esptool_py.path=C:\Users\rick\AppData\Local\Arduino15\packages\esp32\tools\esptool_py\2.6.0 -prefs=runtime.tools.xtensa-esp32-elf-gcc.path=C:\Users\rick\AppData\Local\Arduino15\packages\esp32\tools\xtensa-esp32-elf-gcc\1.22.0-80-g6c4433a-5.2.0 sketches/HDMI_VGDB.ino” in directory “C:\Arduino\HDMI_VGDB\HDMI_VGDB” on local computer
In file included from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\MasterHeader.h:15:0,
from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\ETFT.c:1:
C:\Users\rick\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.1\libraries\SPI\src\SPI.h(28,1): error : unknown type name ‘class’
class SPISettings
^
C:\Users\rick\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.1\libraries\SPI\src\SPI.h(29,1): error : expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{‘ token
{
^
C:\Users\rick\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.1\libraries\SPI\src\SPI.h(38,1): error : unknown type name ‘class’
class SPIClass
^
C:\Users\rick\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.1\libraries\SPI\src\SPI.h(39,1): error : expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{‘ token
{
^
C:\Users\rick\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.1\libraries\SPI\src\SPI.h(86,8): error : unknown type name ‘SPIClass’
extern SPIClass SPI;
^
In file included from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\MasterHeader.h:16:0,
C:\Users\rick\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.1\libraries\FS\src\FS.h(24,18): error : memory: No such file or directory
compilation terminated.
from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\MQTT.c:1:
class SPISettings
^
{
^
class SPIClass
^
{
^
extern SPIClass SPI;
^
compilation terminated.
from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\WiFi_Util.c:1:
class SPISettings
^
{
^
class SPIClass
^
{
^
extern SPIClass SPI;
^
compilation terminated.
from C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug\sketch\SD.c:1:
class SPISettings
^
{
^
class SPIClass
^
{
^
extern SPIClass SPI;
^
compilation terminated.
exit status 1
————————————————————-
Command exited with code 1
Executable: C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino\arduino-builder.exe
Arguments: -compile -logger=machine -fqbn=esp32:esp32:esp32doit-devkit-v1:FlashFreq=80,UploadSpeed=921600,DebugLevel=none -build-path C:\Arduino\HDMI_VGDB\HDMI_VGDB\Output\DOIT_ESP32_DEVKIT_V1\Debug -unoptimize=sketch -hardware “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/hardware” -hardware C:\Users\rick\AppData\Local/Arduino15/packages -tools “C:\Program Files (x86)\Sysprogs\VisualGDB\Arduino/tools-builder” -tools C:\Users\rick\AppData\Local/Arduino15/packages -libraries C:\Users\rick\Documents/Arduino/Libraries -prefs=runtime.tools.esptool_py.path=C:\Users\rick\AppData\Local\Arduino15\packages\esp32\tools\esptool_py\2.6.0 -prefs=runtime.tools.xtensa-esp32-elf-gcc.path=C:\Users\rick\AppData\Local\Arduino15\packages\esp32\tools\xtensa-esp32-elf-gcc\1.22.0-80-g6c4433a-5.2.0 sketches/HDMI_VGDB.ino
Directory: C:\Arduino\HDMI_VGDB\HDMI_VGDB
VisualGDB: Error: Command-line action failed
========== Compilazione: 0 completate, 1 non riuscite, 0 aggiornate, 0 ignorate ==========March 17, 2019 at 16:32 #24306support
KeymasterAccording to our records, it looks like your trial period has expired. In order to get further technical support, please consider purchasing a license.
Please note that installing VisualGDB on another PC, editing registry to affect the trial counter, or creating further forum accounts does not reset your trial period from the support point of view.
As providing quality technical support for our users requires continuous effort on our side, we do expect our users to play fair and are not able to offer any help once the original trial period expires.
-
AuthorPosts
- You must be logged in to reply to this topic.