MystikReasons

Forum Replies Created

Viewing 9 posts - 91 through 99 (of 99 total)
  • Author
    Posts
  • in reply to: Keil ARMCC project creation error #23000

    MystikReasons
    Participant

    Hello,

    Sry for my late answer. I tested the new build but I cant find my microcontroller under it.

    Im not finding it under Keil ARMCC neither under Keil ARMClang but still under the normal ARM toolchain.

    My microcontroller: STM32F107VC

    in reply to: V. 5.4 prev. 8 references #22631

    MystikReasons
    Participant

    Update: I found a way for me to reproduce the glitch every time:

    -Start Visual Studio

    -Open up your solution

    -Then watch the references (for me some of them are wrong – see screenshot #1)

    -Change the topic in the reference window to “Code/Data Relations” (for me – see screenshot #2)

    -Then change it back to “References” again: They are now displayed right (see screenshot #3)

    -If you close the solution/close Visual Studio and open up the solution again the glitch is there again.

     

    I think the glitch appears by the first time you start the solution where CodeJumps gathers all the needed data

    Attachments:
    You must be logged in to view attached files.
    in reply to: V. 5.4 prev. 8 references #22629

    MystikReasons
    Participant

    @support I couldn’t reproduce the glitch with the references yet but I found other interesting things.

    If I turn off the “CodeJumps” via a keyboard shortcut (I really love this feature) its still displaying me if I hover for example over a function the reference window with all the other options. Would it be possible that this window would also deactivate if I turn the CodeJumps off (or make an clickbox if you want to toggle/not toggle the reference window too if you toggle the codeJump Annotations)?

    My second thing I found: The reference window is always jumping a bit to the right if you select another topic in it. This is very confusing because sometimes the window jumps so much to the right that the mouse isn’t hovering over it any more and it just disappears and you have to open it again by hovering above the object. If you are lucky you can bring the window completely to the right border of the screen 😉

    Could this be somehow changed?

    in reply to: V. 5.4 prev. 8 references #22592

    MystikReasons
    Participant

    Update: The reference problem is still occuring sometimes on the same objects as mentioned yesterday.

    The weird thing is that its working sometimes and only display 5 references and sometimes its displaying 10 refernces

     

    Update2: I found a way to update the display. If you see the references in detail click on “Calls” and then back again to “References”. After that it loads the right amount of references. But it will change again to a wrong number of references if you write some more code and check it again

    in reply to: V. 5.4 prev. 8 references #22591

    MystikReasons
    Participant

    @support

    Wouldnt it be much easier for the user to have a key combination to turn them off/turn on(dissapear/appear)?

    And what is about my question yesterday about the many references?

    I installed it today on my laptop and now it seems to work like it should, did you make a fix?

    in reply to: Library names aren't being found #22118

    MystikReasons
    Participant

    I added the library project to the solution and referenced it successfully (see screenshot).

    But now I get new errors and I really dont know why:

    I included the necessary header files a few lines above it

    #include “stm32f10x_gpio.h”
    #include “stm32f10x_rcc.h”
    #include “stm32f10x_spi.h”

    Intellisense also finds the functions and nothing is being underlined red.

    Never had this error before

    Attachments:
    You must be logged in to view attached files.
    in reply to: Library names aren't being found #22108

    MystikReasons
    Participant

    Hello

    I could fix the first error about the pthread because I didn’t need it.

    About the second one:

    The linker now finds the TouchP0P1.a but he still complains about not finding libTouchP0P1.a.so which I dont have.

    The only 2 files which VisualGDB created for me when I made the static lib was the “TouchP0P1.a” and the “TouchP0P1.ar.rsp”.

    Why is he searching for libTouchP0P1 instead of just TouchP0P1 which I defined in the settings?

    Is there something wrong with the lib which I created or what can I do to solve this problem?

    In the images down below you will see my settings for creating the lib and the files which the program created.

    • This reply was modified 4 years, 2 months ago by  MystikReasons.
    Attachments:
    You must be logged in to view attached files.
    in reply to: Library names aren't being found #22101

    MystikReasons
    Participant

    I enabled the verbose mode and got this message:

    1>VisualGDB/Debug/stm32f1xx_hal_usart.o
    1>c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/bin/ld.exe: cannot find -lpthread
    1>c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/bin/ld.exe: cannot find -lTouchP0P1.a
    1>collect2.exe : error : ld returned 1 exit status
    1>attempt to open VisualGDB/Debug/stm32f1xx_hal_wwdg.o succeeded
    1>VisualGDB/Debug/stm32f1xx_hal_wwdg.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_adc.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_adc.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_crc.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_crc.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_dac.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_dac.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_dma.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_dma.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_exti.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_exti.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_fsmc.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_fsmc.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_gpio.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_gpio.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_i2c.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_i2c.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_pwr.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_pwr.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_rcc.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_rcc.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_rtc.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_rtc.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_sdmmc.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_sdmmc.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_spi.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_spi.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_tim.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_tim.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_usart.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_usart.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_usb.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_usb.o
    1>attempt to open VisualGDB/Debug/stm32f1xx_ll_utils.o succeeded
    1>VisualGDB/Debug/stm32f1xx_ll_utils.o
    1>attempt to open ../../TouchP0P1.a succeeded
    1>(../../TouchP0P1.a)startup_stm32f107xc.o
    1>attempt to open C:/Elektronik Projekte/05_Bosch-Sensor I2C/06_Software/Visual Studio/libpthread.so failed
    1>attempt to open C:/Elektronik Projekte/05_Bosch-Sensor I2C/06_Software/Visual Studio\libpthread.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/thumb/cortex_m3/libpthread.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/thumb/cortex_m3\libpthread.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib/thumb/cortex_m3/libpthread.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib/thumb/cortex_m3\libpthread.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/libpthread.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0\libpthread.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/libpthread.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc\libpthread.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib/libpthread.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib\libpthread.a failed
    1>attempt to open C:/Elektronik Projekte/05_Bosch-Sensor I2C/06_Software/Visual Studio/libTouchP0P1.a.so failed
    1>attempt to open C:/Elektronik Projekte/05_Bosch-Sensor I2C/06_Software/Visual Studio\libTouchP0P1.a.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/thumb/cortex_m3/libTouchP0P1.a.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/thumb/cortex_m3\libTouchP0P1.a.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib/thumb/cortex_m3/libTouchP0P1.a.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib/thumb/cortex_m3\libTouchP0P1.a.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/libTouchP0P1.a.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0\libTouchP0P1.a.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/libTouchP0P1.a.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc\libTouchP0P1.a.a failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib/libTouchP0P1.a.so failed
    1>attempt to open c:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/7.2.0/../../../../arm-eabi/lib\libTouchP0P1.a.a failed

    Do I need to get the pthread file from somewhere? Nothing has been mentioned about this on this site (https://visualgdb.com/support/linkerinputs/)

    Cant he find the TouchP0P1.a lib because the pthread failed?

    In the images you will see my linker/ c,c++ settings and my files in the directory which I defined

    Attachments:
    You must be logged in to view attached files.
    in reply to: OpenOCD error after changing to newest version of VisualGDB #22099

    MystikReasons
    Participant

    Thank you for the quick answer.

    You were absolutely right!

    Somehow I downloaded the same installer instead of the newer one.

Viewing 9 posts - 91 through 99 (of 99 total)