support

Forum Replies Created

Viewing 15 posts - 6,466 through 6,480 (of 7,815 total)
  • Author
    Posts
  • in reply to: VisualGDB extremely slow #7776
    support
    Keymaster

    Hi,

    Yes, you can try debugging with a cross-gdb that will run on the Windows machine and connect to your Linux one via gdbserver. Then the symbol handling will be done on the Windows side and the Windows/Linux latencies won’t affect those commands.

    in reply to: Nucleo STM32L476RG Memory Write Failure! #7771
    support
    Keymaster

    OK, the update is out. Please update your BSP via Tools->Embedded Tools Manager.

    in reply to: Nucleo STM32L476RG Memory Write Failure! #7770
    support
    Keymaster

    Hi,

    It looks like an obvious bug in our device definitions, so there is no action needed on your side, we’ll simply release a BSP update fixing this within the next 24 hours.

    in reply to: Create Embeded Project Template #7768
    support
    Keymaster

    Yes, simply use the File->Export VisualGDB Project Template command. We will publish a tutorial on that soon.

    in reply to: Cannot debug after upgrading to JLink software 5.10q #7767
    support
    Keymaster

    Wow, strange. It did not crash on our side. If anyone else can confirm the crash, please send us dump file and we’ll gladly fix it.

    support
    Keymaster

    Hi,

    OK, strange. According to your log file, the breakpoint gets set correctly. Please try modifying your code as follows:

    1. Add a function “void test() {asm(“nop”);}
    2. Change the stringFromJNI() function to return the address of the test() function instead of the counter: sprintf(sz, “test=0x%x”, &test);
    3. Set a breakpoint in ‘test’ by name (Ctrl-B).

    Does the address of ‘test’ reported in the GDB log match the address returned by the stringFromJNI() function? Does the breakpoint still not hit?

    support
    Keymaster

    Hi,

    OK, what is value assigned to APP_ABI in your Application.mk? Does it include arm64-v8a? If not, please add it there:

    APP_ABI := arm64-v8a

    in reply to: Importing new files #7759
    support
    Keymaster

    Hi,

    OK, we have added this to the v5.2 feature list.

    in reply to: About licenses #7758
    support
    Keymaster

    Hi,

    Please find your answers below:

    1. We do allow using a personal license on one additional computer (e.g. a laptop).
    2. The license is perpetual, however the free updates and support will only work for 1 year.
    3. We don’t have any plans for making an Eclipse plugin, as many Eclipse users prefer free tools and may not justify the costs of a plugin like VisualGDB. You can, however, use the free Visual Studio Community edition with VisualGDB if you don’t have a regular Visual Studio license.
    in reply to: C99 support #7757
    support
    Keymaster

    Hi,

    It’s hard to say why these errors are happening if you are using C99. Could you please share the full build log from the Output window? Perhaps you have enabled strict type checking via CFLAGS?

    in reply to: Visual Studio source not updated when debugging #7756
    support
    Keymaster

    Hi,

     

    The Source Cache Manager is used to cache the remote source/header files (e.g. in /usr/src) that are not a part of the project but somehow participated in build, hence they are only transferred one way.

    The sources from the project directory should be normally auto-transferred on each build (see your VisualGDB Project Properties for file transfer settings).

    Sometimes when the target directories are symlinked, gdb reports the path that is different from the one used by VisualGDB and VisualGDB assumes those files are out-of-project files.

    Can you identify one particular file that does not get transferred, check its local path, Linux path reported by GDB (see the GDB Session window) and check if your settings are configured to upload the contents of that directory?

    in reply to: Cannot debug after upgrading to JLink software 5.10q #7755
    support
    Keymaster

    Hi,

    We have just retested it with the latest Segger J-Link v5.10s and could not find any problem.

    We have tested the LEDBlink (BSP) project and tried stepping through the main() function and setting breakpoints – everything worked as expected.

    On the first run the J-Link server prompted to update the firmware and we did that. Could you please verify that the problem still exists with 5.10s and after the firmware update?

    in reply to: Nucleo STM32L476RG Memory Write Failure! #7754
    support
    Keymaster

    Hi,

    Sure. Please see the answer on StackOverflow.

    in reply to: VisualGDB extremely slow #7753
    support
    Keymaster

    Hi,

    Most likely the connection to your server is slow. Please try switching on the timing analysis mode in the GDB Session window (timer icon) and selecting “All GDB interaction” view. This will show how much time each GDB command takes. If this does not explain the slowness, please let us know which commands are the slowest so that we could advise you further.

    support
    Keymaster

    Hi,

    OK, it looks like VisualGDB is somehow using the obj/local/armeabi-v7a directory for symbols instead of obj/local/arm64-v8a.

    Does the arm64-v8a directory exist? What does the VisualGDB Launcher Output say when you try to debug your project?

Viewing 15 posts - 6,466 through 6,480 (of 7,815 total)