Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 140) sorted by relevance

123456

/hal_rpi_pico-latest/
DChangeLog.zephyr.md1 # The List of changes to fit zephyr.
3 Need to take care to not break these changes when updating pico-sdk.
10 - [#7] pico-sdk: hardware_timer: Don't add irq handler to interrupt vector
12 - [#6] pico-sdk: hardware_timer: Add argument to irq handler to handle userdata
17 - [#5] pico-sdk: Rename is_irq_enabled() to pico_is_irq_enabled()
22 - [#3] pico-sdk: Rename adc_read() to pico_adc_read()
24 - [#2] pico-sdk: Patch occurrences of KHZ/MHZ to PICO_KHZ/PICO_MHZ
DCONTRIBUTING.md1 # Contributing to Raspberry Pi Pico C/C++ SDK
3 ## How to Report a Bug
5 …to host code, track [issues](https://github.com/raspberrypi/pico-sdk/issues) and feature requests,…
7 ## How to Contribute Code
9 …to contribute new or updated code, you must first create a GitHub account and fork the original re…
11 …l automatically CI fail checks and will not be accepted. You will be asked to rebase your PR again…
13 While we are happy to take contributions, big or small, changes in the SDK may have knock-on effect…
25 …he [BSD-3 License](LICENSE.TXT). By contributing content to this repository you are agreeing to pl…
DREADME.md4 necessary to write programs for the RP-series microcontroller-based devices such as the Raspberry P…
7 The SDK is designed to provide an API and programming environment that is familiar both to non-embe…
11 …to access hardware registers directly. However, if you do need or prefer to access the raw hardwar…
13 The SDK can be used to build anything from simple applications, fully-fledged runtime environments …
16 The design goal for entire SDK is to be simple but powerful.
22 …he Raspberry Pi Pico-Series](https://rptl.io/pico-get-started) for information on how to setup your
23 hardware, IDE/environment and how to build and debug software for the Raspberry Pi Pico and other R…
25 See [Connecting to the Internet with Raspberry Pi Pico W](https://rptl.io/picow-connect) to learn m…
26 applications for your Raspberry Pi Pico W that connect to the internet.
28 See [Raspberry Pi Pico-Series C/C++ SDK](https://rptl.io/pico-c-sdk) to learn more about programmin…
[all …]
/hal_rpi_pico-latest/bazel/
DBUILD.bazel12 # to make it show up easier in searches.
14 # Rather than generating lists of headers to match CMake, the Bazel build
15 # opts to have a static header that transitively include two known headers.
17 # to specify an appropriate `cc_library` to replace them.
53 # An empty stub, useful for label_flag flags that need to point to a library,
54 # but for some purposes the library needs to be a no-op.
59 # A library incompatible with everything. Use to mark an invalid configuration.
DREADME.md13 These toolchains tell Bazel how to compile for ARM cores. Add the following
14 to the `MODULE.bazel` for your project:
28 ### Ready to build!
29 You're now ready to start building Pico Projects in Bazel! When building,
30 don't forget to specify `--platforms` so Bazel knows you're targeting the
46 If you have a bespoke board definition, you can configure the Pico SDK to use it
47 by pointing `--@pico-sdk//bazel/config:PICO_CONFIG_HEADER` to a `cc_library`
55 `pico_uf2_aspect` enabled is the easiest way to create a UF2 for every ELF
69 launcher) to build the Pico SDK.
74 You will also need a working compiler configured if you wish to build Picotool
[all …]
/hal_rpi_pico-latest/bazel/config/
DBUILD.bazel5 # PICO_BAZEL_CONFIG: PICO_TOOLCHAIN, The toolchain to use, type=string, default=gcc, group=build
21 # PICO_BAZEL_CONFIG: PICO_BARE_METAL, Flag to exclude anything except base headers from the build, …
33 …O_DEFAULT_BOOT_STAGE2_FILE, Boot stage 2 file to use; this should point to a filegroup with the .S…
39 …DEFAULT_BOOT_STAGE2, Simpler alternative to specifying PICO_DEFAULT_BOOT_STAGE2_FILE where the lat…
45 …AGE2_LINK_IMAGE, [Bazel only] The final boot_stage2 image target to link in. Use this to fully ove…
69 # PICO_BAZEL_CONFIG: PICO_STDIO_UART, Option to globally enable stdio UART for all targets by defau…
81 # PICO_BAZEL_CONFIG: PICO_STDIO_USB, Option to globally enable stdio USB for all targets by default…
87 # PICO_BAZEL_CONFIG: PICO_STDIO_SEMIHOSTING, Option to globally enable stdio semi-hosting for all t…
93 # PICO_BAZEL_CONFIG: PICO_STDIO_RTT, Option to globally enable stdio RTT for all targets by default…
105 # PICO_BAZEL_CONFIG: PICO_DEFAULT_DOUBLE_IMPL, The default implementation for pico_double to link. …
[all …]
/hal_rpi_pico-latest/tools/
DCMakeLists.txt7 # functions to set properties for a given scope.
11 BRIEF_DOCS "OTP File to write"
12 FULL_DOCS "OTP File to write"
35 BRIEF_DOCS "Partition table to embed in output"
36 FULL_DOCS "Partition table to embed in output"
53 BRIEF_DOCS "Address to package UF2 at"
54 FULL_DOCS "Address to package UF2 at"
59 BRIEF_DOCS "UF2 family to use"
60 FULL_DOCS "UF2 family to use"
65 BRIEF_DOCS "Extra arguments to pass to processing"
[all …]
Duf2_aspect.bzl1 # TODO: Default to a list of known compatible rules until the toolchain emits
3 # this can change to ["*"] and another attribute that allows extension-based
4 # filtering can be added to more easily support a wider array of file types.
42 Normally with Bazel, a cc_binary or other rule cannot be "extended" to emit
46 This can be used from a build to produce UF2 files alongside the regular
56 It's also possible to use this aspect within a custom macro (e.g. my_cc_binary)
57 to produce UF2 images alongside ELF files. However, with that method UF2 images
63 doc = "A comma-separated list of rule kinds to apply the UF2 aspect to",
/hal_rpi_pico-latest/bazel/util/
Dtransition.bzl2 """Converts flag values to transition-safe primitives."""
10 A transition in Bazel is a way to force changes to the way the build is
18 Normally, if you set `defines` on a, they couldn't apply to b or c because
19 they are dependencies of a. There's no way for b or c to know about a's
23 that sets --copts=-DFOO=42, we're telling Bazel to build a and all of its
30 you need to do is provide a set of attrs, and then a `flag_overrides`
31 dictionary that tells `declare_transition()` which attrs to pull flag values
32 from. The common `src` attr tells the transition which build rule to apply
33 the transition to.
91 # This could be shared, but we don't in order to make it clearer that
[all …]
/hal_rpi_pico-latest/src/rp2_common/pico_printf/
DLICENSE5 Permission is hereby granted, free of charge, to any person obtaining a copy
6 of this software and associated documentation files (the "Software"), to deal
8 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 copies of the Software, and to permit persons to whom the Software is
10 furnished to do so, subject to the following conditions:
/hal_rpi_pico-latest/src/rp2_common/cmsis/stub/CMSIS/
DLICENSE.txt18 "control" means (i) the power, direct or indirect, to cause the
27 including but not limited to software source code, documentation
32 not limited to compiled object code, generated documentation,
33 and conversions to other media types.
37 copyright notice that is included in or attached to the work
45 separable from, or merely link (or bind by name) to the interfaces of,
50 to that Work or Derivative Works thereof, that is intentionally
51 submitted to Licensor for inclusion in the Work by the copyright owner
52 or by an individual or Legal Entity authorized to submit on behalf of
55 to the Licensor or its representatives, including but not limited to
[all …]
/hal_rpi_pico-latest/external/
Dpico_sdk_import.cmake3 # This can be dropped into an external project to help locate this SDK
4 # It should be include()ed prior to project()
31 set(PICO_SDK_PATH "${PICO_SDK_PATH}" CACHE PATH "Path to the Raspberry Pi Pico SDK")
32 set(PICO_SDK_FETCH_FROM_GIT "${PICO_SDK_FETCH_FROM_GIT}" CACHE BOOL "Set to ON to fetch copy of SDK…
33 set(PICO_SDK_FETCH_FROM_GIT_PATH "${PICO_SDK_FETCH_FROM_GIT_PATH}" CACHE FILEPATH "location to down…
67 …as not specified. Please set PICO_SDK_PATH or set PICO_SDK_FETCH_FROM_GIT to on to fetch from git."
79 …message(FATAL_ERROR "Directory '${PICO_SDK_PATH}' does not appear to contain the Raspberry Pi Pico…
82 set(PICO_SDK_PATH ${PICO_SDK_PATH} CACHE PATH "Path to the Raspberry Pi Pico SDK" FORCE)
/hal_rpi_pico-latest/test/pico_float_test/llvm/
DLICENSE.TXT18 Permission is hereby granted, free of charge, to any person obtaining a copy of
19 this software and associated documentation files (the "Software"), to deal with
20 the Software without restriction, including without limitation the rights to
22 of the Software, and to permit persons to whom the Software is furnished to do
23 so, subject to the following conditions:
33 Urbana-Champaign, nor the names of its contributors may be used to
51 to that code.
54 applies to all code in the LLVM Distribution, and nothing in any of the
55 other licenses gives permission to use the names of the LLVM Team or the
56 University of Illinois to endorse or promote products derived from this
/hal_rpi_pico-latest/src/host/
DREADME.md1 This is a basic set of replacement library implementations sufficient to get simple applications
6 to run on the RP2040 or RP2350 device itself.
8 This base level host library provides a minimal environment to compile programs, but is likely suff…
11 It is possible however to inject additional SDK library implementations/simulations to provide
13 which uses the SDL2 library to add additional library support for pico_multicore, timers/alarms in …
/hal_rpi_pico-latest/cmake/
Dpico_pre_load_toolchain.cmake1 # PICO_CMAKE_CONFIG: PICO_TOOLCHAIN_PATH, Path to search for compiler, type=string, default=none (i…
10 message(STATUS "Defaulting build type to '${default_build_type}' since not specified.")
23 …pico_message("Defaulting compiler (PICO_COMPILER) to '${PICO_DEFAULT_COMPILER}' since not specifie…
28 # PICO_CMAKE_CONFIG: PICO_COMPILER, Specifies the compiler family to use, type=string, group=build,…
29 # If PICO_COMPILER is specified, set toolchain file to ${PICO_COMPILER}.cmake.
67 …message(FATAL_ERROR "CMAKE_TOOLCHAIN_FILE was previously defined to ${PICO_PREVIOUS_CMAKE_TOOLCHAI…
68 is being changed to ${CMAKE_TOOLCHAIN_FILE}. You\
69 need to delete the CMake cache and reconfigure if you want to switch compiler.\
70 … The best practice is to use separate build directories for different platforms or compilers.")
Dpico_pre_load_platform.cmake9 # PICO_CMAKE_CONFIG: PICO_PLATFORM, Platform to build for e.g. rp2040/rp2350/rp2350-arm-s/rp2350-ri…
44 … pico_message("Defaulting platform (PICO_PLATFORM) to '${PICO_PLATFORM}' since not specified.")
51 pico_message("Defaulting target board (PICO_BOARD) to '${PICO_BOARD}' since not specified.")
57 # PICO_CMAKE_CONFIG: PICO_BOARD_CMAKE_DIRS, List of directories to look for <PICO_BOARD>.cmake in. …
75 # PICO_CMAKE_CONFIG: PICO_DEFAULT_RP2350_PLATFORM, Default actual platform to build for if rp2350 i…
87 …message("Auto-converting non-specific PICO_PLATFORM='rp2350' to '${PICO_DEFAULT_RP2350_PLATFORM}'")
96 pico_message("Defaulting platform (PICO_PLATFORM) to '${PICO_PLATFORM}' since not specified.")
100 …pico_message("Defaulting platform (PICO_PLATFORM) to '${PICO_PLATFORM}' based on PICO_BOARD settin…
111 …message(FATAL_ERROR "PICO_PLATFORM is specified to be '${PICO_SAVED_PLATFORM}', but PICO_BOARD='${…
112 …O_PLATFORM}' which is incompatible. You need to delete the CMake cache or build directory and reco…
[all …]
/hal_rpi_pico-latest/docs/
Dmainpage.md3 …to write programs for RP-series microcontroller devices such as the Raspberry Pi Pico in C, C++ or…
7 …io. The SDK can be used to build anything from simple applications, or full-fledged runtime enviro…
9 …sed for each library, but does not provide usage information. Please refer to the Databooks for us…
13 …, runtime vs compile-time configuration) are necessarily much more visible to the developer than t…
15 …ures to just work out of the box, with sensible defaults, but also to give the developer as much c…
19 The SDK uses CMake to manage the build. CMake is widely supported by IDEs (Integrated Development E…
21 Apart from being a widely-used build system for C/C++ development, CMake is fundamental to the way …
23 …able which is bare-metal, i.e. it includes the entirety of the code needed to run on the device (o…
/hal_rpi_pico-latest/src/rp2_common/pico_btstack/
DLICENSE.RP1 “BlueKitchen” shall refer to BlueKitchen GmbH.
2 “Raspberry Pi” shall refer to Raspberry Pi Ltd.
3 “Product” shall refer to Raspberry Pi hardware products Raspberry Pi Pico W or Raspberry Pi Pico WH.
7 Raspberry Pi grants to the Customer a non-exclusive, non-transferable, non-sublicensable, irrevocab…
8 and worldwide licence to use, copy, store, develop, modify, and transmit BTstack in order to use BT…
12 All use of BTstack by the Customer is limited to Products or Customer Products, and the Customer re…
14 regulations, including but not limited to, copyright and other intellectual property laws and priva…
16 BlueKitchen retains all rights, title and interest in, to and associated with BTstack and associate…
/hal_rpi_pico-latest/src/rp2_common/pico_standard_link/
DCMakeLists.txt24 # need this because cmake does not appear to have a way to override an INTERFACE variable
65 …# if PICO_TARGET_BINARY_TYPE is set to foo on the target, otherwise ${CMAKE_CURRENT_LIST_DIR}/memm…
73 …roperty being equal to no_flash if set, otherwise to the value of the PICO_NO_FLASH cmake variable…
76 … being equal to use_blocked_ram if set, otherwise to the value of the PICO_USE_BLOCKED_RAM cmake v…
79 …erty being equal to copy_to_ram if set, otherwise to the value of the PICO_COPY_TO_RAM cmake varia…
89 # -nostartfiles will be added if PICO_NO_FLASH would be defined to 1
91 …# boot_stage2 will be linked if PICO_NO_FLASH would be defined to 0; note if boot_stage2 headers n…
96 …# PICO_CMAKE_CONFIG: PICO_USE_DEFAULT_MAX_PAGE_SIZE, Don't shrink linker max page to 4096, type=bo…
/hal_rpi_pico-latest/src/rp2_common/pico_clib_interface/
DBUILD.bazel5 # This is split between the headers and a link-time requirement to fix issues
27 # TODO: Provide a way to hook up Arm Compiler for Embedded into the automagic
57 # It's hard to properly constrain compatibility since `auto` may select this,
73 # It's hard to properly constrain compatibility since `auto` may select this,
79 # For now, newlib doesn't need to provide any headers.
95 # It's hard to properly constrain compatibility since `auto` may select this,
101 # For now, picolibc doesn't need to provide any headers.
117 # It's hard to properly constrain compatibility since `auto` may select this,
/hal_rpi_pico-latest/src/rp2_common/pico_standard_binary_info/
DBUILD.bazel13 # PICO_BUILD_DEFINE: PICO_CMAKE_BUILD_TYPE, The type of build (e.g. Debug or Release) to embed in b…
22 # With custom_pico_binary_info, it's possible to set binary info globally or
26 # * Set --@pico-sdk//bazel/config:PICO_DEFAULT_BINARY_INFO to point to your
32 # * Add custom_pico_binary_info to each cc_binary individually.
/hal_rpi_pico-latest/src/
DCMakeLists.txt20 # call add_subdirectory(subdir) unless SKIP_SUBDIR evaluates to true
23 # todo add option to disable skip flag
32 # argv1 is the root where the subdir is relative to
61 # note, it would be nice to only add the dependency if it exists, but we do
70 # add a link option to wrap the given function name; i.e. -Wl:wrap=FUNCNAME for gcc
117 # and add include/ relative to the calling directory to the includes.
132 … INTERFACE library that it depends on. The hardware_NAME_headers library add include/ relative to
136 …# Choosing not to add LIB_HARDWARE_ defines to avoid command line bloat pending a need (they aren't
137 …# super interesting except to determine functionality as they are mostly passive accessors, howe…
138 # they could be useful to determine if the header is available.
[all …]
/hal_rpi_pico-latest/cmake/preload/toolchains/util/
Dpico_arm_clang_common.cmake29 # Add target system root to cmake find path.
56 # this is a bit of a hack; to try to autodetect the C library used:
57 …# `picolibc.h` seems to exist on the newer versions of LLVM embedded toolchain for ARM using picol…
60 message("Setting default C library to picolibc as LLVM appears to be using it")
73 message("Setting default C library to llvm_libc as LLVM appears to be using it")
86 # TODO: Move -nostartfiles to the appropriate library.
/hal_rpi_pico-latest/src/cmake/
Drp2_common.cmake5 # PICO_CMAKE_CONFIG: PICO_NO_FLASH, Option to default all binaries to not use flash i.e. run from S…
6 option(PICO_NO_FLASH "Default binaries to not not use flash")
7 # PICO_CMAKE_CONFIG: PICO_COPY_TO_RAM, Option to default all binaries to copy code from flash to SR…
8 option(PICO_COPY_TO_RAM "Default binaries to copy code to RAM when booting from flash")
17 # PICO_CMAKE_CONFIG: PICO_BARE_METAL, Flag to exclude anything except base headers from the build, …
92 # Helper functions to connect to data/functions in the bootrom
/hal_rpi_pico-latest/src/common/pico_binary_info/
DCMakeLists.txt13 …# PICO_BUILD_DEFINE: PICO_PROGRAM_NAME, value passed to pico_set_program_name, type=string, group=…
21 …# PICO_BUILD_DEFINE: PICO_PROGRAM_DESCRIPTION, value passed to pico_set_program_description, type=…
26 …# PICO_BUILD_DEFINE: PICO_PROGRAM_URL, value passed to pico_set_program_url, type=string, group=pi…
31 …# PICO_BUILD_DEFINE: PICO_PROGRAM_VERSION_STRING, value passed to pico_set_program_version, type=s…

123456