[lisa.tamanti@faacgroup.com]

I tryed to use the Resetting Python Environment  as explained here: https://visualgdb.com/documentation/python/ without solving:

From the message that I reported in my previous comment I see:

IDF_PYTHON_ENV_PATH: C:\Espressif\python_env\\idf5.2_py3.8_env

How can correct this path if I have canceled path from Tools->Options->VisualGDB->General->Python Directory ?

 

[lisa.tamanti@faacgroup.com]

Now I succeded on it but when I create the project I have this error:

— Could not use ‘git describe’ to determine PROJECT_VER.
— Building ESP-IDF components for target esp32
— Checking Python dependencies…
The following Python requirements are not satisfied:
Requirement ‘idf-component-manager~=1.2’ was not met. Installed version: 2.0.2
To install the missing packages, please run “install.bat”
Diagnostic information:
IDF_PYTHON_ENV_PATH: C:\Espressif\python_env\\idf5.2_py3.8_env
Python interpreter used: C:\Espressif\python_env\idf5.2_py3.8_env\Scripts\python.exe
Warning: python interpreter not running from IDF_PYTHON_ENV_PATH
PATH: C:\Program Files\Git\cmd;C:\Espressif\python_env\\idf5.2_py3.8_env\Scripts;C:\Users\bope02\AppData\Local\VisualGDB\Python-3.8.10;C:\SysGCC_R1\tools\xtensa-esp-elf\esp-13.2.0_20230928\xtensa-esp-elf\bin;C:\SysGCC_R1\tools\xtensa-esp-elf\esp-13.2.0_20230928\xtensa-esp-elf\bin;C:\SysGCC_R1\tools\esp32ulp-elf\2.35_20220830\esp32ulp-elf\bin;C:\SysGCC_R1\tools\riscv32-esp-elf\esp-13.2.0_20230928\riscv32-esp-elf\bin;C:\SysGCC_R1\tools\idf-exe\1.0.3;C:\SysGCC_R1\tools\ccache\4.8\ccache-4.8-windows-x86_64;C:\SysGCC_R1\tools\ninja\1.11.1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\Git\cmd;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\dotnet\;C:\Users\bope02\AppData\Local\Microsoft\WindowsApps;
Constraint file: C:\Users\bope02\.espressif\espidf.constraints.v5.2.txt
Requirement files:
– C:\SysGCC_R1\esp-idf\v5.2\tools\requirements\requirements.core.txt
Python being checked: C:\Espressif\python_env\\idf5.2_py3.8_env\Scripts\python.exe
— Configuring incomplete, errors occurred!
CMake Error at C:/SysGCC_R1/esp-idf/v5.2/tools/cmake/build.cmake:368 (message):
Failed to run Python dependency check. Python: python, Error: -1

I reinstalled Python 3.11.5 from Manage VisualGDB Packages (see attached) but without resolving problems…

 

 

 

Attachments:

You must be logged in to view attached files.

[lisa.tamanti@faacgroup.com]

ON your previous message I see different gdb_port and telnet_port  from mine….Have I to  change ? Where I can change them?

 

[lisa.tamanti@faacgroup.com]

This is my initial OpenOCD start command:

C:\Users\bope02\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 54033” -c “telnet_port 54031” -f interface/ftdi/esp32_devkitj_v1.cfg -c “adapter_khz 3000” -f target/esp32.cfg -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2022-05-03)

 

I’m sorry but after added the command line as you indicated  (see attached file VisualGDB_Debug.jpg) when I start DEBUG  immediately I always  have an error “Target not halted”.
Even If I disconnect and then riconnect USB I continue to have this error.
In this case logs are:

C:\Users\bope02\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 54450” -c “telnet_port 54448” -f interface/ftdi/esp32_devkitj_v1.cfg -c “adapter_khz 3000” -f target/esp32.cfg -c “esp appimage_offset 0x20000” -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2022-05-03)
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

DEPRECATED! use ‘adapter speed’ not ‘adapter_khz’
adapter speed: 3000 kHz

Error: Target not halted

Then I tryed to add “init; halt” but without any result but with a different error message:

C:\Users\bope02\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.esp32.core\bin\openocd.exe -c “gdb_port 54502” -c “telnet_port 54500” -f interface/ftdi/esp32_devkitj_v1.cfg -c “adapter_khz 3000” -f target/esp32.cfg “init; halt” -c “esp appimage_offset 0x20000” -c “echo VisualGDB_OpenOCD_Ready”
Open On-Chip Debugger 0.10.0 (2022-05-03)
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Unexpected command line argument: “init;

 

 

 

 

 

[lisa.tamanti@faacgroup.com]

Espressif forum told me that OpenOCD looses offset of my application that is necessary to give this information to OpenOCD with:

-c “init; halt; esp appimage_offset 0x20000”

But where and how  in VisulStudio can I give to OpenOCD this information?

In the past this operation wasn’t necessary….

 

[lisa.tamanti@faacgroup.com]

I restored the previus openOCD but I have the same problem 🙁

Is it possible to understand something from Error log below?

&”mon program_esp \”C:/Progetti_FW/FAAC_IOT_GIT/build/VisualGDB/Debug/bootloader/bootloader.bin\” 0x1000\n”
@”JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n”
@”JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)\n”
@”esp32.cpu0: Debug controller was reset.\n”
@”esp32.cpu0: Core was reset.\n”
@”esp32.cpu0: Target halted, PC=0x500000CF, debug_reason=00000000\n”
@”esp32.cpu0: Core was reset.\n”
@”esp32.cpu0: Target halted, PC=0x40000400, debug_reason=00000000\n”
@”esp32.cpu1: Debug controller was reset.\n”
@”esp32.cpu1: Core was reset.\n”
@”esp32.cpu1: Target halted, PC=0x40000400, debug_reason=00000000\n”
@”timed out while waiting for target halted\n”
@”esp32.cpu0: Target halted, PC=0x4000C2DD, debug_reason=00000000\n”
@”xtensa_wait_algorithm: not halted 0, pc 0x4000c2dd, ps 0x60025\n”
@”Failed to wait algorithm (-302)!\n”
@”Algorithm run failed (-302)!\n”
@”Too many flash mappings 11072892! Must be 2.\n”
@”Failed to get flash mappings (-4)!\n”
@”Target is already running an algorithm\n”
@”Failed to start algorithm (-4)!\n”
@”Failed to get flash size!\n”
@”Target is already running an algorithm\n”
@”Failed to start algorithm (-4)!\n”
@”Failed to get flash size!\n”
@”Failed to probe flash, size 0 KB\n”
@”auto_probe failed\n”
@”Failed to find bank ‘esp32.cpu1.flash’!\n”
@”\n”
^done
-target-disconnect
=thread-group-exited,id=”i1″
^done
-gdb-exit
^exit

[lisa.tamanti@faacgroup.com]

Sorry,  but I continue to have the problem also after to have programmed by USB – COM  bootloader and partition table..

The problem was born after to have updated last Open OCD proposed on VisualStudio ….then I  removed that Open OCD but the problem remained ..

 

[lisa.tamanti@faacgroup.com]

I heve the same problem too!!!!

[lisa.tamanti@faacgroup.com]

I apologize!

Now I succeded in downloading R12 version!!! And the bild process with PSRAM is OK!!!!

 

[lisa.tamanti@faacgroup.com]

I’m sorry but today the situation doesn’t change….the same as yesterday.

It’s not possible for me to update to R12 toolchain….this version isn’t proposed in Manage VisualGBD Packages and from http://gnutoolchains.com/esp32/ link  the installing of R12 creates a Windows error.

I have a collegue that is using Visual Studio Professional instead of Visual Studio Community like me and now he has R12 toolchain proposed in Manage VisualGDB Packages.

We tried to install it (R12)  and he succeded in compiling with PSRAM..so effectively with R12 version is possible to work with external PSRAM.

But I  don’t understand why in my Visual Studio Community 2017 version 15.7.5 it’s not possible to see the new R12 toolchain.

 

[lisa.tamanti@faacgroup.com]

Hi,

I tried to update toolchain from menu Manage VisualGDB Package but it was present only R11 version.

Directly in http://gnutoolchains.com/esp32/   R12 version is available but after launch downloaded exe file  I have a message of “Access is denied” from Windows  so it is impossible for me to use R12 version (on my PC I have Windows 10)

I tried with R11 version and I have the same compilation error:

error: unrecognized command line option ‘-mfix-esp32-psram-cache-issue’.

I attached file with my selections to use module’s PSRAM

On sdkconfig-debug file now I find:

CONFIG_SPIRAM_SUPPORT=y

#
# SPI RAM config
#
CONFIG_SPIRAM_BOOT_INIT=y
CONFIG_SPIRAM_IGNORE_NOTFOUND=
CONFIG_SPIRAM_USE_MEMMAP=y
CONFIG_SPIRAM_USE_CAPS_ALLOC=
CONFIG_SPIRAM_USE_MALLOC=
CONFIG_SPIRAM_TYPE_ESPPSRAM32=y
CONFIG_SPIRAM_SIZE=4194304
CONFIG_SPIRAM_SPEED_40M=y
CONFIG_SPIRAM_MEMTEST=y
CONFIG_SPIRAM_CACHE_WORKAROUND=y

but I don’t succed in compiling withou error

Attachments:

You must be logged in to view attached files.

[Author]

Posts