mattia

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 31 total)
  • Author
    Posts
  • in reply to: IDF_PATH in CMakeList #34537
    mattia
    Participant

    Ok, I just renewed.

    in reply to: SDK config ESP32 #33440
    mattia
    Participant

    Perhaps my suggestion were not very clear, let me be more clear with some images: as you can see in the image attached, the property “Using dynamic TX/RX buffer” is mapped as “CONFIG_MBEDTLS_DYNAMIC_BUFFER” in sdkconfig.

    The filter field search for text in the GUI, but in a lot of example I need to check for the sdkconfig name variable.

    So I would like to know if there is a way to search for name as indicated in sdkconfig.

    Thank you,

    Mattia

    Attachments:
    You must be logged in to view attached files.
    in reply to: Can't compile after moving from VS2019->2022 #33306
    mattia
    Participant

    Just renewed!

    in reply to: ESP32 C3 live watch #32001
    mattia
    Participant

    Great work guys, I will use them ASAP!!

    Mattia

    in reply to: ESP32 C3 Jtag profile #31952
    mattia
    Participant

    Hello,

    forgive me if I have not been clear. What I’d like to tell you is that I have been able to use OpenOCD to debug the ESP32-C3, but I had to put only the child node as WinUSB, not the root node, as you can see in the image attached. Of course VGDB asks to change the root node to WinUSB, but I neglect and I can correctly debug and have the COM available for logging.

    Mattia

    Attachments:
    You must be logged in to view attached files.
    in reply to: ESP32 C3 semihosting #31910
    mattia
    Participant

    Hello,

    I tried to use the ESP-IDF 4.3.1, but I can’t follow your example https://visualgdb.com/tutorials/esp32/apptrace/

    Can you try to reproduce the tutorial on ESP32-C3?

    Thank you,

    Mattia

    in reply to: ESP32 C3 live watch #31896
    mattia
    Participant

    Do you have any tutorials on how to use Visual Watch?

    in reply to: Very small bug on VisualGDB #30994
    mattia
    Participant

    Hello,

    it is correct now. I’ve found another bug, but I’m not sure about it: I would like to use the USB Jtag/serial as console output, but if I try to set it in VisualGDB properties->ESP-IDF Project->Channel o console output->USB CDC and press OK, when I enter in the same menu again the option set is “Default: UART0”. All other options work: Default, Custom UART, None.

    What could it be the cause?

    Thank you,

    Mattia Berton

    in reply to: ESP32 C3 support #30963
    mattia
    Participant

    Hello,

    I have tried to make Jtag work on my board, but I haven’t been able. I can attach to ESP32, ESP32-S2, ESP8266, but with ESP32-C3 I put target/ESP32C3.cfg but I get the classic error as if I didn’t attach the JTAG adapter to the board.

    I checked my project, and I’m sure pin are attached to the correct IOs of ESP32C3. Is there any particular procedure to make JTAG work in ESP32-C3? I’m not using, at this moment, the USB/JTAG, only the classic JTAG.

    Thank you,

    Mattia Berton

    in reply to: Option byte launch #28957
    mattia
    Participant

    Hello,

    I can’t find the gdb trace in STM32CubeIDE. I attached the file called “immagine” to see what I found on STM32CubeIDE. I alsso attached the log I found on VisualGDB.

    How can I write some register before entering in the debug mode? Can you make an example?

    Thank you,

    Mattia

     

    Attachments:
    You must be logged in to view attached files.
    in reply to: Option byte launch #28944
    mattia
    Participant

    Let me explain a little better my problem: I use the STM32G030C8. With CubeIDE no problem, the program executes in normal way using my J-link and loading the CubeMX program. However using VisualGDB it seems as if the option bytes are not correctly handled: at address 0x0000000 there is the System memory, and not the Main memory as it should be. During the startup routine the Stack pointer is loaded wrong, while the Program counter is ok. However, if I press the reset button, the program counter goes to the System memory (and of course it is not correct).

    The only way I found to solve this problem is to load runtime the Option Byte and then perform a reset. In this way, at address 0x0 there is the Main memory as it should be.

    This problems arises only during debug, probably because the Boot0 pin is shared with SWCLK. However, I can’t explain why the CubeIDE works without doing anything.

    Can you help me?

    Thank you,

    Mattia Berton

    in reply to: Difference in compile size #28376
    mattia
    Participant
    1. Isn’t it possible – in your opinion –  that the project compiled for the Atollic discards the unused functions, while the VGDB includes each function? Is there any way to check what setting is used in the two projects (perhaps checking the .proj file)?
    2. Regarding the differences, I will attach the screenshot.
    in reply to: Difference in compile size #28362
    mattia
    Participant

    Thank you,

    the tool is very powerful, and I can find that there are differencies between the two versions. However how could I check the settings between the two projects? Shouldn’t be equal, since are both built with the same CubeMX project?

    Also, one thing about the differential comparison, because from the comparison between the two projects I see something which is not very clear: for each .c file there is the difference between brackets, but it is not the sum of the bytes differences for the functions of that .c file. For example, stm32f0xx_hal_gpio.c has (+952). The two functions called are HAL_GPIO_Init (+384) and HAL_GPIO_WritePin (+46). But 384+46 is not +952. Am I missing something?

    Thank you for your help,

    Mattia

    in reply to: Difference in compile size #28349
    mattia
    Participant

    It seems a great solution. My only question is: how can I import the project created for Truestudio in VisualGDB to compare with the differential view in Memory Explorer? Can I import a single elf file?

    Thank you,

    Mattia Berton

    in reply to: Tab indenting not working #27732
    mattia
    Participant

    Ok, I will try to be more exhaustive:

    I’m starting the debug of a project imported from CubeMX. I attached the project in .gpdsc format.

    I would like to have intelligent indent. I’d expect that when I press backspace to the tab, the cursor goes back to as many spaces as set in the option menu. However, in the main.c file generated (attached, called “Tab not working”), when I press backspace the cursor goes back only one space. I attach the tab option menu.

    I added another .c source file, called app_execute.c (attached, called “Tab working”). This file behaves exactly as expected. I’m attaching the two screenshots of the main.c file and app_execute.c file.

    Can you explain why the two .c files behave in a different way in the tab indenting?

    Thank you,

    Mattia Berton

    Attachments:
    You must be logged in to view attached files.
Viewing 15 posts - 1 through 15 (of 31 total)