Pi Pico extras SDK

Sysprogs forums Forums VisualGDB Pi Pico extras SDK

This topic contains 4 replies, has 2 voices, and was last updated by  support 2 weeks, 1 day ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #30398


    Hi Folks

    I’ve just started using visualGDB – and loving so far.

    Currently I’m trying to add the pico-extras sdk addon to my project so I can use the I2S pio stuff  – no joy so far.

    Anyone know how to do this?






    I read the previous posts on this issue – and tried to import with the wizard a few example extras projects – but just can’t get them to compile.




    If the imported project doesn’t compile, we would advise first getting it to successfully build outside VisualGDB, and then proceeding with import.

    If you are able to build a project outside VisualGDB, but it doesn’t build with VisualGDB, we can help you configure VisualGDB to replicate the manual build results. If the project doesn’t build outside of VisualGDB either, importing it into VisualGDB will not automatically solve the build problems.



    Hello Support!

    My current project – I really really want to import it into visualGDB – but I get errors when importing.

    My project is based around the pio/st7789_lcd example, but I’m also using the extras “audio/i2s” stuff

    here’s my project cmakelists.txt



    pico_generate_pio_header(pio_st7789_lcd ${CMAKE_CURRENT_LIST_DIR}/st7789_lcd.pio)
    #pico_generate_pio_header(pio_st7789_lcd ${CMAKE_CURRENT_LIST_DIR}/spi.pio)

    target_include_directories(pio_st7789_lcd PRIVATE ${CMAKE_CURRENT_LIST_DIR})
    target_sources(pio_st7789_lcd PRIVATE st7789_lcd.cpp lcd565.c payload.s)

    target_link_libraries(pio_st7789_lcd PRIVATE pico_stdlib pico_audio_i2s tinyusb_host tinyusb_board pico_multicore hardware_dma hardware_flash hardware_pll hardware_vreg hardware_clocks hardware_adc hardware_pio hardware_spi hardware_i2c hardware_interp)

    # add url via pico_set_program_url
    #pico_set_float_implementation(pio_st7789_lcd PICO)


    Here’s the error I get after I import my existing project


    CMake Warning (dev) in CMakeLists.txt:
    No project() command is present. The top-level CMakeLists.txt file must
    contain a literal, direct call to the project() command. Add a line of
    code such as


    near the top of the file, but after cmake_minimum_required().

    CMake is pretending there is a “project(Project)” command on the first
    This warning is for project developers. Use -Wno-dev to suppress it.

    CMake Error at CMakeLists.txt:3 (pico_generate_pio_header):
    Unknown CMake command “pico_generate_pio_header”.

    CMake Warning (dev) in CMakeLists.txt:
    No cmake_minimum_required command is present. A line of code such as

    cmake_minimum_required(VERSION 3.15)

    should be added at the top of the file. The version specified may be lower
    if you wish to support older CMake versions for this project. For more
    information run “cmake –help-policy CMP0000”.
    This warning is for project developers. Use -Wno-dev to suppress it.

    — Configuring incomplete, errors occurred!
    See also “D:/TheVault/Pico/Examples/pio/st7789_lcd/build/VisualGDB/Debug/CMakeFiles/CMakeOutput.log”.
    See also “D:/TheVault/Pico/Examples/pio/st7789_lcd/build/VisualGDB/Debug/CMakeFiles/CMakeError.log”.
    System.Exception: CMake exited with code 1
    at z22.n(p a, Object b)

    ========== Project Configuration Summary ==========
    BadACid1 configured in 00:00
    ========== Configuration: 1 Succeeded, 0 Failed, 0 Skipped ==========

    any help getting this to work would be fantastic – I really need to debug it at the moment.

    many thanks



    Please make sure you can build the project outside VisualGDB first. Once you get it to build outside VisualGDB, please try comparing the command line that results in a successful build with the command line used by VisualGDB (you can find it out in the VisualGDB Build window as shown here).

    If you need help locating the settings that will adjust the VisualGDB command line to match the manual build command line, please let us know more details about both command lines and we will be happy to point out the relevant settings.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.