support

Forum Replies Created

Viewing 15 posts - 6,406 through 6,420 (of 7,814 total)
  • Author
    Posts
  • support
    Keymaster

    Hi,

    No problem. If you encounter further problems, don’t hesitate to start another thread.

    support
    Keymaster

    Hi,

    Thanks for reporting this. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.4.674.msi

    in reply to: Newbe looking for instructions #7934
    support
    Keymaster

    Hi,

    Sure, you can do that easily with our VisualGDB product. We have a very detailed tutorial available here: http://visualgdb.com/tutorials/esp8266/openocd/

    in reply to: STM32F042K6 USB CDC Locking Up MCU #7933
    support
    Keymaster

    Hi,

    It’s hard to say what could be wrong without seeing the hardware. Have you copied SystemClock_Config() from a proper example for your board? This function varies slightly between different boards.

    If yes, we would need to first get debugging to work before we could give any further advice. Could you attach the full gdb log and the OpenOCD output so that we could see why the debugging is impossible?

    in reply to: add *.h, *.c and *.cpp to subdirectories #7932
    support
    Keymaster

    The source files need to be physically added to the Solution Explorer. You can add them either one-by-one or altogether via right-click->Add->Import Directory Recursively.

    in reply to: ESP8266 GDB debugging Adafruit Huzzah ESP8266 breakout #7931
    support
    Keymaster

    Hi,

    Good to know it works now. BTW, we have recently released a new toolchain with an updated gdb that should be a bit more stable.

    support
    Keymaster

    Cool. Thanks for sharing this.

    in reply to: Two issues related to SSH Connections #7920
    support
    Keymaster

    Hi,

    We could easily add variables like $(BuildUserName) and $(BuildHostName) and similar ones for deployment machine. Would that be helpful?

    in reply to: Feature Request #7919
    support
    Keymaster

    Hi,

    The problem with raw telnet is that it does not support easy file transfer and has no convenient API for running just one command and seeing when it exited. It could be achieved via various workarounds, but they won’t be very reliable.

    We currently recommend setting up a custom project and simply adding custom pre-debug commands to transfer your files to the device. Similarly, you can use the expect tool to connect to the target via raw telnet and specify it as the local GDB executable so that VisualGDB will simply launch it and send the commands there.

    We will monitor the demand for this feature and consider adding it if the demand grows. In the meanwhile, feel free to try the workaround described above and if it does not work, we will gladly provide more detailed steps.

    in reply to: Feature request: Create empty project #7918
    support
    Keymaster

    Hi,

    You can easily remove all extra files from the project by unreferencing the HAL library in VisualGDB Project Properties -> Embedded Frameworks.

    in reply to: Visual GDB Defualt Code dose Not Work #7916
    support
    Keymaster

    Hi,

    The file you posted is has different _estack and memory size than we suggested. Please double-check that you are using the values we suggested above.

    in reply to: Equivalent of "Link Library Dependencies"? #7915
    support
    Keymaster

    Hi,

    Normally yes. When you add a reference from one Makefile project to another one, VisualGDB will add the outputs of referenced projects to the EXTERNAL_LIBS variable in the Makefile (updated on each build) and the libraries will be linked with.

    in reply to: Install VisualGDB on a virtual machine #7914
    support
    Keymaster

    Hi,

    As long as you don’t have more parallel activations of VisualGDB than your license allows and don’t move the VMs between physical machines too often, you’re fine both legally and technically.

    in reply to: Visual GDB Defualt Code dose Not Work #7909
    support
    Keymaster

    Hi,

    It looks like there is a bug in our LPC1768 linker script that results in incorrect memory size definition.

    Please open VisualGDB Project Properties on the Makefile Settings page, click “Create local copy” near the “Linker Script” field. Then open the linker script added to the project and edit it as follows:

    MEMORY
    {
        FLASH (RX) : ORIGIN = 0x00000000, LENGTH = 512K
        SRAM (RWX) : ORIGIN = 0x10000000, LENGTH = 48K
    }
    
    _estack = 0x1000C000;
    in reply to: STM32F746G Disco – Registers cannot be written to #7897
    support
    Keymaster

    No problem. If you encounter further problems, feel free to create another topic.

Viewing 15 posts - 6,406 through 6,420 (of 7,814 total)