MBED – IntelliSense problem

Sysprogs forums Forums VisualGDB MBED – IntelliSense problem

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #22820
    maras
    Participant

    I created simple Blinky with 4 platform: NUCLEO_F072, NUCLEO_L433, NUCLEO_L476 and NUCLEO_L452 (this is my platform)
    Code is very simple:

    #include "mbed.h"
    
    DigitalOut led1(LED1);
    Serial ser(PA_2, PA_3, 115200);
    
    // main() runs in its own thread in the OS
    int main() {
        while (true) {
            led1 = !led1;
            wait(0.1);
    	    printf("Hello NUCLEO_L452RE \r\n");
    	    uint32_t someuint = 0;
    	    someuint++;
        }
    }
    

    When chosen platform is NUCLEO_F072 or any other NUCLEO_F4* everything is OK, code looks good and build without errors. But when I choose any of NUCLEO_L4* platform IntelliSense shows error on every types like uint32_t (uint8_t, uint16_t, …) and on printf function. But project builds without errors and works.
    If I try #include “stdint.h” IntelliSense does not suggests anything and marks error on stdint.h file name when platform is NUCLEO_L4* but suggests correct files and does not mark error when chosen platform is NUCLEO_F4*. I see that, when platform is NUCLEO_L4* IntelliSense like not see include subfolder from toolchain folder.

    I don’t know, maybe this is MBED problem, not VisualGDB issue, but I can’t find solution and need some help.

    #22829
    support
    Keymaster

    Hi,

    This could be caused by some leftovers from the previous VisualGDB build that could not compute the IntelliSense settings correctly.

    Please try deleting the VisualGDBCache and CodeDB directories and reopening the project. If it doesn’t help, please check if the problem persists in a freshly created project (we have quickly checked it with NUCLEO_L432KC and could not find any issues).

    #22859
    maras
    Participant

    Deleting this directories works, thanks.

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