Issue in MbedProject on STM32U5 board

Sysprogs forums Forums VisualGDB Issue in MbedProject on STM32U5 board

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #35760
    mgraceltis
    Participant

    Hello,

    I started a mbed project on NUCLEO_U575ZI_Q board, and i have some issues with clang intellisense (I think)

    Here is a dummy source code for exemple :

    #include “mbed.h”

    Ticker ticker;
    bool ledSwitch = false;

    int main()
    {
    DigitalOut led(LED1);

    ticker.attach(callback([](){
    ledSwitch = true;
    }), 1000ms);

    while (true) {
    if (ledSwitch)
    {
    led = !led;
    ledSwitch = false;
    }
    ThisThread::sleep_for(1ms);
    }
    }

    In this exemple, clang intellisense make an error on “ticker.attach” : [Clang IntelliSense] Error : no matching member function for call to ‘attach’ test C : \Users\maxime\Desktop\test\test\main.cpp 10
    I have this error too : [Clang IntelliSense] Error : “Unknown ARM architecture for exclusive access” test C : \Users\maxime\Desktop\test\test\mbed – os\platform\include\platform\mbed_atomic.h 95
    However, the code compiles and runs correctly on the boards.

    I tried with another board (NUCLEO_L496ZG) and everything works perfeclty with no error from intellisense.

    Setup :
    Windows 11
    Visual Studio 2022 17.8.11
    VisualGDB 6.0R3 build 5191
    GCC 9.3.1

    Thank you

    • This topic was modified 2 weeks, 6 days ago by mgraceltis.
    • This topic was modified 2 weeks, 6 days ago by mgraceltis.
    #35767
    support
    Keymaster

    Hi,

    Thanks, looks like the U5 port is using a couple of built-in functions that are not known to Clang and somehow trigger strange behavior.

    We have added a workaround on the VisualGDB side. Please try this build: VisualGDB-6.0.103.5197.msi

    #35769
    mgraceltis
    Participant

    Hi,

    I tried the new build and the issues seem to be resolved.

    Thank you very much for your help !

     

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.