MystikReasons

Forum Replies Created

Viewing 15 posts - 61 through 75 (of 99 total)
  • Author
    Posts
  • in reply to: VisualGDB & VAssistX error #24214
    MystikReasons
    Participant

    Update: I updated the visualgdb version to build 3003 from 2978 and now the window is showing again but the class syntax is still being highlighted as an error.

    in reply to: Keil ARMCC features error #24174
    MystikReasons
    Participant

    Additional information: The box in the Keil Components “Automatically manage the RTE_Components.h file” was activated and the two Keil Components which should have been imported were “CMSIS/Core” and “Device/GPIO”.

    And the other errors (from the first post) are still there

    in reply to: Keil ARMCC features error #24169
    MystikReasons
    Participant

    So I found out that I’ve selected an wrong Keil Component (Device/Startup instead of Device/GPIO).

    So I selected the other one and changed the tab to the MSBuild settings and got this message:

    VisualGDB version: 5.4.103.2978
    —————— us1+e ——————
    us1+e: VSProjectWrapper: project object not found
    at us1.w.a1()
    at us1.x.d()
    at VisualGDB.Common_GUI.WPF.Property_pages.MSBuildSettingsPage.ControllerImpl.ImportSettings(Object settingsObject, Object pendingChanges)
    at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.c1.s.Import(s02 a, VisualGDBProjectSettings2 b)
    at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.v.c(Object a, RoutedEventArgs b)

    After that my project was unloaded and I tried to reload it and got an error message (see screenshot#1).

     

    I then deleted the project and tried to setup a new one with the VisualGDB import manager for keil projects.

    The first message of the Clang Intellisense was that it couldn’t find “core_cm3.h” and that no components in the Keil Components window were selected so they haven’t gotten imported.

    See screenshot #2 for the MSBuild settings window and screenshot #3 for the Keil Component window

    Attachments:
    You must be logged in to view attached files.
    in reply to: Keil ARMCC features error #24145
    MystikReasons
    Participant

    Update: I tried to manually recompile every single source file in VisualGDB and I got in two source files errors (P0toP1.c excluded):

    startup_stm32f10x_cl.s:

    1>startup_stm32f10x_cl.s
    1>RTE\Device\startup_stm32f10x_cl.s(159): error : A1854E: Unknown opcode 'BLX', maybe wrong target CPU?
    1> 159 00000002 BLX R0

    system_stm32f10x.c:

    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(129): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regControl
    1>_ASM("control");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(141): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regControl
    1>_ASM("control");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(141): warning : #550-D: variable "__regControl" was set but never used
    1> register uint32_t __regControl __ASM("control");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(153): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regIPSR
    1>_ASM("ipsr");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(177): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regXPSR
    1>_ASM("xpsr");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(189): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regProcessStackPointer
    1>_ASM("psp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(201): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regProcessStackPointer
    1>_ASM("psp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(201): warning : #550-D: variable "__regProcessStackPointer" was set but never used
    1> register uint32_t __regProcessStackPointer __ASM("psp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(213): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regMainStackPointer
    1>_ASM("msp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(225): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regMainStackPointer
    1>_ASM("msp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(225): warning : #550-D: variable "__regMainStackPointer" was set but never used
    1> register uint32_t __regMainStackPointer __ASM("msp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(237): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regPriMask
    1>_ASM("primask");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(249): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regPriMask
    1>_ASM("primask");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(249): warning : #550-D: variable "__regPriMask" was set but never used
    1> register uint32_t __regPriMask __ASM("primask");
    1> ^

    In the STM32F1xx_OPT.s I get no errors (see screenshot#1 for the projects components in VisualGDB)

    Attachments:
    You must be logged in to view attached files.
    in reply to: Keil ARMCC features error #24141
    MystikReasons
    Participant

    The problem is I only have one/two source files in my project and they build without errors (see screenshot#1 for project files).

    See screenshot#2 for the content in my project folder.

    See screenshot#3 for a whole rebuild of the project source files.

    If there are more source files how can I access them/see which of them are being used in my project?

    Attachments:
    You must be logged in to view attached files.
    in reply to: Keil ARMCC features error #24117
    MystikReasons
    Participant

    I’ve tried to remove the “P0toP1.h” file and the .lib file and comment every code in the P0toP1.c which was related to it and I still get some errors (only the while loop was left uncommented):

    But its not the P0toP1.c file because Ctrl+F7 builded it without errors

    1>------ Erstellen gestartet: Projekt: Timer_MCB32, Konfiguration: Debug VisualGDB ------
    1>system_stm32f10x.c
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(129): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regControl
    1>_ASM("control");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(141): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regControl
    1>_ASM("control");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(141): warning : #550-D: variable "__regControl" was set but never used
    1> register uint32_t __regControl __ASM("control");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(153): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regIPSR
    1>_ASM("ipsr");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(177): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regXPSR
    1>_ASM("xpsr");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(189): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regProcessStackPointer
    1>_ASM("psp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(201): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regProcessStackPointer
    1>_ASM("psp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(201): warning : #550-D: variable "__regProcessStackPointer" was set but never used
    1> register uint32_t __regProcessStackPointer __ASM("psp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(213): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regMainStackPointer
    1>_ASM("msp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(225): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regMainStackPointer
    1>_ASM("msp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(225): warning : #550-D: variable "__regMainStackPointer" was set but never used
    1> register uint32_t __regMainStackPointer __ASM("msp");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(237): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regPriMask
    1>_ASM("primask");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(249): error : #1114: this feature not supported on target architecture/processor
    1> register uint32_t __regPriMask
    1>_ASM("primask");
    1> ^
    1>C:\Keil_v5\ARM\pack\ARM\CMSIS\5.2.0\CMSIS\Include\cmsis_armcc.h(249): warning : #550-D: variable "__regPriMask" was set but never used
    1> register uint32_t __regPriMask __ASM("primask");
    1> ^
    1>RTE/Device/system_stm32f10x.c: 4 warnings, 10 errors
    1>Die Erstellung des Projekts "Timer_MCB32.vcxproj" ist abgeschlossen -- FEHLER.

    This is the content of the p0top1._i:

    --c99 -c --cpu Cortex-M3 -D__EVAL -g -O0 --apcs=interwork --split_sections
    -I.\RTE\_Target_1
    -IC:\Keil_v5\ARM\PACK\ARM\CMSIS\5.2.0\CMSIS\Include
    -IC:\Keil_v5\ARM\PACK\Keil\STM32F1xx_DFP\2.2.0\Device\Include
    -IC:\Keil_v5\ARM\PACK\Keil\STM32F1xx_DFP\2.2.0\RTE_Driver
    -D__UVISION_VERSION="524" -D_RTE_ -DSTM32F10X_CL
    -o .\objects\p0top1.o --omf_browse .\objects\p0top1.crf --depend .\objects\p0top1.d "P0toP1.c"

    I’ve sent you both projects (VisualGDB & Keil) with the library via the Support in a .zip file to see if you can find the problem .

    • This reply was modified 5 years, 1 month ago by support. Reason: formatting
    in reply to: Keil ARMCC features error #24099
    MystikReasons
    Participant

    Ok so I created the batch file under uVision and this is the content:

    SET PATH=C:\Keil_v5\ARM\ARMCC\Bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\dotnet\;C:\PROGRA~2\PICC;C:\WINDOWS\System32\OpenSSH\;C:\PRA846~1\CCSCCO~1\PICC;C:\PROGRA~2\MICROC~1\PICC;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Users\jense\AppData\Local\Microsoft\WindowsApps;
    SET ARMCC5_ASMOPT=–diag_suppress=9931
    SET ARMCC5_CCOPT=–diag_suppress=9931
    SET ARMCC5_LINKOPT=–diag_suppress=9931
    SET CPU_TYPE=STM32F107VC
    SET CPU_VENDOR=STMicroelectronics
    SET UV2_TARGET=Target 1
    SET CPU_CLOCK=0x00B71B00
    “C:\Keil_v5\ARM\ARMCC\Bin\ArmCC” –Via “.\objects\p0top1.__i”
    “C:\Keil_v5\ARM\ARMCC\Bin\ArmCC” –Via “.\objects\gpio_stm32f10x.__i”
    “C:\Keil_v5\ARM\ARMCC\Bin\ArmLink” –Via “.\Objects\Timer.lnp”
    “C:\Keil_v5\ARM\ARMCC\Bin\fromelf.exe” “.\Objects\Timer.axf” –i32combined –output “.\Objects\Timer.hex”

     

    And this is the content out of the .gcc.rsp file in VisualGDB:

    -IC:/Users/jense/source/repos/Timer_MCB32/Timer_MCB32 -IC:/Keil_v5/ARM/pack/Keil/STM32F1xx_DFP/2.2.0/Device/Include -IC:/Keil_v5/ARM/ARMCC/../pack/ARM/CMSIS/5.2.0/CMSIS/Include -IC:/Keil_v5/ARM/ARMCC/../pack/Keil/STM32F1xx_DFP/2.2.0/Device/Include -IRTE -IRTE/Device -g -O0 -DSTM32F10X_CL -D_RTE_ -DDEBUG=1 -DDEBUG=1 –split-sections –apcs=interwork –gnu -c “P0toP1.c” -o “VisualGDB/Debug/P0toP1.o” –depend “VisualGDB/Debug/P0toP1.dep”

    in reply to: Clang Intellisense not working #23770
    MystikReasons
    Participant

    I’ve sent you the project via the support but I had to upload it to a website because it was too big for your website (around 30MB).

    in reply to: Clang Intellisense not working #23748
    MystikReasons
    Participant

    Hi

    Thanks for the steps to reproduce it.

    I found where the IntelliSense breaks. If I try to declare the function under my #include “main.h” it wont work but if I place it above the whole IntelliSense came to life again.

    But If I save the file and move the function again under the #include “main.h” the IntelliSense stops working again.

    See my screenshots and the main.c attached in the attachments.

    Attachments:
    You must be logged in to view attached files.
    in reply to: Clang Intellisense not working #23715
    MystikReasons
    Participant

    I resaved the file (main.c) with UTF-8 encoding (see screenshot UTF-8)

    The IntelliSense is still not working correctly (again the same error: The selected location does not refer to a C/C++ entity.)

    But I get now an rather weird warning from the Clang IntelliSense (see screenshot clang intellisense message).

    Do you know how I can save the whole project for UTF-8? I only found the option for single files.

    Attachments:
    You must be logged in to view attached files.
    in reply to: Dynamic Analysis error #23694
    MystikReasons
    Participant

    How can I search after the function located at the address?

    in reply to: Dynamic Analysis error #23676
    MystikReasons
    Participant

    If I try to debug the project I get also errors (see attached screenshots)

    Attachments:
    You must be logged in to view attached files.
    in reply to: Dynamic Analysis error #23674
    MystikReasons
    Participant

    Damnit the max file size is very small on this forum…

    The new image is now smaller.

    Attachments:
    You must be logged in to view attached files.
    in reply to: STM32 connection problem #23636
    MystikReasons
    Participant

    Problem solved.

    I’ve rebuild the whole solution and now it seems to work again.

    • This reply was modified 5 years, 2 months ago by MystikReasons.
    in reply to: STM32 connection problem #23635
    MystikReasons
    Participant

    The problem was I’ve set the i2c frequency in cubemx to 400kHz in Fast Mode but I only got ~50kHz on the SCL line. So I just changed the i2c clock source from PCLK1 to HSI 16. But this destroyed my whole communication and I don’t know why.

Viewing 15 posts - 61 through 75 (of 99 total)