milamber

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 28 total)
  • Author
    Posts
  • milamber
    Participant

    apparently when i execute

    python C:/SysGCC/esp32/esp-idf/v5.2/tools/idf_tools.py check-python-dependencies
    Constraint file: C:\Users\george\.espressif\espidf.constraints.v5.2.txt
    Requirement files:
    - C:\SysGCC\esp32\esp-idf\v5.2\tools\requirements\requirements.core.txt
    Python being checked: C:\Espressif\python_env\idf5.2_py3.8_env\Scripts\python.exe
    Python requirements are satisfied.

    it looks into this file C:\Users\george\.espressif\espidf.constraints.v5.2.txt why is that in 5.2?

    milamber
    Participant

    it seems there is a double \\ after python_env in the batch file

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

    milamber
    Participant

    i did that in my first post . it is the first thing in the post. i found where espressif for vscode installs by default in 5.2 (C:\Users\george\esp\v5.2.1\esp-idf) and copied espidf.constraints.v5.2.txt to where visualgdb expected it (where espressif installed until 5.1 C:\Users\george\.espressif) and the problem was solved.

     

    i understand its a hack but the documentation provided didnt help solve.

    I can delete everything and try again but i have done it a few times already with the same result. it seems that the installation of espressif somehow affects visualgdb although i thought that the 2 were independent.

    I would be happy to troubleshoot if you want me to.

     

     

    milamber
    Participant

    followed the instructions but the problem remains.

    • cleared the  Python installations via Tools->Options->VisualGDB->General->Python Directory. (look at pic)
    • I have deleted the python directories at  %LOCALAPPDATA%\VisualGDB\Python*
    • created a new project (blink) based on esp-idf 5.2 (see attchement)  and clicked on the ‘get python’ button

    this is the created the following directories

    Volume in drive C has no label.
    Volume Serial Number is 1028-E0A7

    Directory of C:\Users\george\AppData\Local\VisualGDB

    03/06/2024 06:24 PM <DIR> .
    02/20/2024 04:15 PM <DIR> ..
    06/03/2023 04:02 PM 490 .clang-format
    03/06/2024 01:14 AM 166 activation.key
    06/03/2023 04:04 PM <DIR> AutoDownloadedSources
    02/09/2024 12:15 AM <DIR> CMake
    10/03/2023 10:03 PM <DIR> CppEngineDumps
    12/03/2023 11:57 PM <DIR> EmbeddedDebugPackages
    06/03/2023 03:26 PM 0 FindBSP.cmake
    06/03/2023 03:26 PM 536 FindBSP.props
    03/06/2024 01:14 AM 1,722 FindComponents.props
    06/03/2023 03:26 PM 292 FindFrameworks.cmake
    06/03/2023 03:26 PM 178 FindRemoteHost.props
    03/06/2024 12:35 AM 1,143 FindToolchain.props
    03/06/2024 02:35 AM 8,793 GUIPreferences.xml
    03/06/2024 01:19 AM 4,110,696 PackageCatalog.xml
    03/06/2024 06:24 PM <DIR> Python-3.8.10
    06/03/2023 03:26 PM <DIR> QemuVMs
    06/04/2023 12:43 AM <DIR> RemoteSourceCache
    03/07/2023 02:00 PM <DIR> SharedFolders
    03/06/2024 01:41 AM <DIR> temp
    10 File(s) 4,124,016 bytes
    11 Dir(s) 182,326,775,808 bytes free

    when i compile i get the same error

    Running CMake: C:\Users\george\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G "Ninja" -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/SysGCC/esp32/tools/ninja/1.11.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0 -DIDF_TARGET=esp32

    — Found Git: C:/Program Files/Git/cmd/git.exe (found version “2.43.0.windows.1”)
    — The C compiler identification is GNU 13.2.0
    — The CXX compiler identification is GNU 13.2.0
    — The ASM compiler identification is GNU
    — Found assembler: C:/SysGCC/esp32/tools/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/xtensa-esp32-elf-gcc.exe
    — Detecting C compiler ABI info
    — Detecting C compiler ABI info – done
    — Check for working C compiler: C:/SysGCC/esp32/tools/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/xtensa-esp32-elf-gcc.exe – skipped
    — Detecting C compile features
    — Detecting C compile features – done
    — Detecting CXX compiler ABI info
    — Detecting CXX compiler ABI info – done
    — Check for working CXX compiler: C:/SysGCC/esp32/tools/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/xtensa-esp32-elf-g++.exe – skipped
    — Detecting CXX compile features
    — Detecting CXX compile features – done
    — git rev-parse returned ‘fatal: not a git repository (or any of the parent directories): .git’
    — Could not use ‘git describe’ to determine PROJECT_VER.
    — Building ESP-IDF components for target esp32
    — Checking Python dependencies… python C:/SysGCC/esp32/esp-idf/v5.2/tools/idf_tools.py check-python-dependencies
    — pythonC:/SysGCC/esp32/esp-idf/v5.2/tools/idf_tools.pycheck-python-dependencies
    No Python at ‘C:\Users\george\AppData\Local\VisualGDB\Python3\python.exe’
    — Configuring incomplete, errors occurred!
    CMake Error at C:/SysGCC/esp32/esp-idf/v5.2/tools/cmake/build.cmake:371 (message):
    Failed to run Python dependency check. Python: python, Error: 103
    Call Stack (most recent call first):
    C:/SysGCC/esp32/esp-idf/v5.2/tools/cmake/build.cmake:505 (__build_check_python)
    C:/SysGCC/esp32/esp-idf/v5.2/tools/cmake/project.cmake:605 (idf_build_process)
    CMakeLists.txt:6 (project)

    System.Exception: CMake exited with code 1
    at a4.b(a a, Object b)

    it is looking  for python C:/SysGCC/esp32/esp-idf/v5.2/tools/idf_tools.py check-python-dependencies

    where obviously there is none. so i copy the  Python-3.8.10 directory into Python3 and the build fails in the same way

     

    Run “C:\Users\george\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/SysGCC/esp32/tools/ninja/1.11.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0 -DIDF_TARGET=esp32″ in directory “C:\d\FS\EmbeddedProject1\EmbeddedProject1/build/VisualGDB/Debug” on local computer
    C:\Users\george\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/SysGCC/esp32/tools/ninja/1.11.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0 -DIDF_TARGET=esp32
    — git rev-parse returned ‘fatal: not a git repository (or any of the parent directories): .git’
    — Could not use ‘git describe’ to determine PROJECT_VER.
    — Building ESP-IDF components for target esp32
    — Checking Python dependencies… python C:/SysGCC/esp32/esp-idf/v5.2/tools/idf_tools.py check-python-dependencies
    — pythonC:/SysGCC/esp32/esp-idf/v5.2/tools/idf_tools.pycheck-python-dependencies
    ERROR: C:\Users\george\.espressif\espidf.constraints.v5.2.txt doesn’t exist. Perhaps you’ve forgotten to run the install scripts. Please check the installation guide for more information.
    — python C:/SysGCC/esp32/esp-idf/v5.2/tools/idf_tools.py check-python-dependencies
    CMake Error at C:/SysGCC/esp32/esp-idf/v5.2/tools/cmake/build.cmake:368 (message):
    Some Python dependencies must be installed. Check above message for
    details.
    Call Stack (most recent call first):
    C:/SysGCC/esp32/esp-idf/v5.2/tools/cmake/build.cmake:505 (__build_check_python)
    C:/SysGCC/esp32/esp-idf/v5.2/tools/cmake/project.cmake:605 (idf_build_process)
    CMakeLists.txt:6 (project)

    — Configuring incomplete, errors occurred!
    ————————————————————-
    Command exited with code 1
    Executable: C:\Users\george\AppData\Local\VisualGDB\CMake\bin\cmake.exe
    Arguments: ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/SysGCC/esp32/tools/ninja/1.11.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0 -DIDF_TARGET=esp32
    Directory: C:\d\FS\EmbeddedProject1\EmbeddedProject1/build/VisualGDB/Debug
    Command-line action failed

    ========== Project Build Summary ==========
    EmbeddedProject1 built in 00:03
    ========== Build: 0 Succeeded, 1 Failed, 0 Skipped ==========

    it is looking to find the C:\Users\george\.espressif\espidf.constraints.v5.2.txt file which doesnt exist, is the the directory where espresiff keeps in vscode installation?

    Attachments:
    You must be logged in to view attached files.
    in reply to: PROBLEM ADDING SECTION TO LINKER SCRIPT #32869
    milamber
    Participant

    The error remains if the variable in not used in a function that is executed.

    • This reply was modified 2 years, 3 months ago by milamber.
    in reply to: PROBLEM ADDING SECTION TO LINKER SCRIPT #32866
    milamber
    Participant

    When i relaunched visual studio and recompiled the project this is the linker report i got

    ------------------- Memory utilization report -------------------
    Used ITCMRAM: 0 bytes out of 64KB (0%)
    Used FLASH: 50KB out of 2048KB (2%) [-2632]
    Used DTCMRAM1: 0 bytes out of 64KB (0%)
    Used DTCMRAM2: 0 bytes out of 64KB (0%)
    Used RAM: 6088 bytes out of 1024KB (0%) [-16]
    Used RAM_CD: 0 bytes out of 128KB (0%) [-320]
    Used RAM_SRD: 0 bytes out of 32KB (0%)

    and this is once I flash the mpu once and recompile

    ------------------- Memory utilization report -------------------
    Used ITCMRAM: 0 bytes out of 64KB (0%)
    Used FLASH: 53KB out of 2048KB (2%) [+2688]
    Used DTCMRAM1: 0 bytes out of 64KB (0%)
    Used DTCMRAM2: 0 bytes out of 64KB (0%)
    Used RAM: 6104 bytes out of 1024KB (0%) [+16]
    Used RAM_CD: 320 bytes out of 128KB (0%) [+320]
    Used RAM_SRD: 0 bytes out of 32KB (0%)

    is this normal behaviour?

    • This reply was modified 2 years, 3 months ago by milamber.
    • This reply was modified 2 years, 3 months ago by milamber.
    in reply to: PROBLEM ADDING SECTION TO LINKER SCRIPT #32865
    milamber
    Participant

    This is a bug of visualdgb.

     

    I flashed the smt32 and once I did that then the linker report and generated map file was updated and showed correct usage. Until I did that the linker memory report was wrong (wasn’t showing the variable in the correct place) and the variable wasn’t in the map file.

    I was expecting to show the correct values and not wrong ones, without any additional step since linker usage and correct map file generation shouldn’t be depended on flashing the mpu.

    in reply to: PROBLEM ADDING SECTION TO LINKER SCRIPT #32863
    milamber
    Participant

    I am not sure I follow. your product claims to be able to parse linker files correctly, yet is fails to do so when different project types are used. why this is a project support request??

    in reply to: live tracing is not #30768
    milamber
    Participant

    any update on this? i was able to reproduce it

    in reply to: live tracing is not #30743
    milamber
    Participant

    when i added an new file to compile (myprintf.c) then the button appeared and the code contained in my file is displayed on live coverage. I would like to see HAL functions covered as well like interrupt handlers

    in reply to: live tracing is not #30741
    milamber
    Participant

    I have started a new project based on smt32cubemx project wizard and enabled code coverage. Now I don’t even get the live coverage window.

    Attachments:
    You must be logged in to view attached files.
    in reply to: live tracing is not #30731
    milamber
    Participant

    i get an exception when i try to add a file to code coverage

    VisualGDB version: 5.6.1.4141
    —————— System.Exception ——————
    System.Exception: ${BSP_ROOT}/Src/main.c is not excluded from code coverage
    at f73.g1_2(w42 b, Boolean a, String c)
    at hr1.a.o_2(da2 a, Object b)
    at wy2.o1.Exec(Guid& a, UInt32 e, UInt32 d, IntPtr b, IntPtr c)
    trace=[f73.g1_2:217, hr1+a.o_2:407, wy2+o1.Exec:350]

    Attachments:
    You must be logged in to view attached files.
    in reply to: live tracing is not #30726
    milamber
    Participant

    it does somewhat. I did follow the code instrumentation tutorial but I dont get the same results are you are showing in your tutorial. In your tutorial one can see function like IRQHandlers and o but when i do it i get something like the attached image

    Attachments:
    You must be logged in to view attached files.
    in reply to: live tracing is not #30719
    milamber
    Participant

    apparently you need J-Trace PRO to have trace information and not a simple j-link. please update the documentation since it is not clear what probe you need to get trace data

    in reply to: live tracing is not #30693
    milamber
    Participant

    I did as you suggested and  it reports 0 data. Please have  in mind  that everything else seems to be working. the jlink flashes the cpu, swv is working

     

    maint packet qSeggerSTRACE:config
    &”maint packet qSeggerSTRACE:config\n”
    sending: “qSeggerSTRACE:config”
    received: “”
    OK
    maint packet qSeggerSTRACE:caps
    &”maint packet qSeggerSTRACE:caps\n”
    sending: “qSeggerSTRACE:caps”
    received: “config;start;stop;read;GetInstStats”
    OK
    maint packet qSeggerSTRACE:start
    &”maint packet qSeggerSTRACE:start\n”
    sending: “qSeggerSTRACE:start”
    received: “00000001”
    OK
    maint packet qSeggerSTRACE:read:4
    &”maint packet qSeggerSTRACE:read:4\n”
    sending: “qSeggerSTRACE:read:4”
    received: “00000000”
    OK

     

     

    C:\Program Files (x86)\SEGGER\JLink\JLinkGDBServerCL.exe -select USB -device STM32H7A3ZI -speed auto -if SWD -port 15971
    SEGGER J-Link GDB Server V7.22a Command Line Version

    JLinkARM.dll V7.22a (DLL compiled Jun 9 2021 16:33:57)

    Command line: -select USB -device STM32H7A3ZI -speed auto -if SWD -port 15971
    —–GDB Server start settings—–
    GDBInit file: none
    GDB Server Listening port: 15971
    SWO raw output listening port: 2332
    Terminal I/O port: 2333
    Accept remote connection: localhost only
    Generate logfile: off
    Verify download: off
    Init regs on start: off
    Silent mode: off
    Single run mode: off
    Target connection timeout: 0 ms
    ——J-Link related settings——
    J-Link Host interface: USB
    J-Link script: none
    J-Link settings file: none
    ——Target related settings——
    Target device: STM32H7A3ZI
    Target interface: SWD
    Target interface speed: auto
    Target endian: little

    Connecting to J-Link…
    J-Link is connected.
    Firmware: J-Link V11 compiled Jun 7 2021 15:48:52
    Hardware: V11.00
    S/N: 261012769
    OEM: SEGGER-EDU
    Feature(s): FlashBP, GDB
    Checking target voltage…
    Target voltage: 3.31 V
    Listening on TCP/IP port 15971
    Connecting to target…
    Connected to target
    Waiting for GDB connection…Connected to 127.0.0.1
    Connected to 127.0.0.1
    Reading all registers
    Read 4 bytes @ address 0x08002F70 (Data = 0x681B4B03)
    Received monitor command: reset
    Resetting target
    Downloading 684 bytes @ address 0x08000000
    Downloading 16032 bytes @ address 0x080002B0
    Downloading 15984 bytes @ address 0x08004150
    Downloading 15920 bytes @ address 0x08007FC0
    Downloading 7044 bytes @ address 0x0800BDF0
    Downloading 428 bytes @ address 0x0800D978
    Downloading 8 bytes @ address 0x0800DB24
    Downloading 8 bytes @ address 0x0800DB2C
    Downloading 4 bytes @ address 0x0800DB34
    Downloading 1092 bytes @ address 0x0800DB38
    Writing register (PC = 0x 8002c2c)
    Read 4 bytes @ address 0x40005024 (Data = 0x00000000)
    Reading register (MSP = 0x20020000)
    Reading register (PSP = 0x 0)
    Reading register (PRIMASK = 0x 0)
    Reading register (BASEPRI = 0x 0)
    Reading register (FAULTMASK = 0x 0)
    Reading register (CONTROL = 0x 0)
    Reading register (FPSCR = 0x 0)
    Reading register (s0 = 0x 0)
    Reading register (s1 = 0x 0)
    Reading register (s2 = 0x 0)
    Reading register (s3 = 0x 0)
    Reading register (s4 = 0x 0)
    Reading register (s5 = 0x 0)
    Reading register (s6 = 0x 0)
    Reading register (s7 = 0x 0)
    Reading register (s8 = 0x 0)
    Reading register (s9 = 0x 0)
    Reading register (s10 = 0x 0)
    Reading register (s11 = 0x 0)
    Reading register (s12 = 0x 0)
    Reading register (s13 = 0x 0)
    Reading register (s14 = 0x 0)
    Reading register (s15 = 0xFFFFFFFF)
    Reading register (s16 = 0x 0)
    Reading register (s17 = 0x 0)
    Reading register (s18 = 0x 0)
    Reading register (s19 = 0x 0)
    Reading register (s20 = 0x 0)
    Reading register (s21 = 0x 0)
    Reading register (s22 = 0x 0)
    Reading register (s23 = 0x 0)
    Reading register (s24 = 0x 0)
    Reading register (s25 = 0x 0)
    Reading register (s26 = 0x 0)
    Reading register (s27 = 0x 0)

Viewing 15 posts - 1 through 15 (of 28 total)