| /hal_rpi_pico-latest/src/rp2_common/pico_bootrom/ |
| D | bootrom.c | 13 void *rom_func_lookup(uint32_t code) { in rom_func_lookup() argument
14 return rom_func_lookup_inline(code); in rom_func_lookup()
20 void *rom_data_lookup(uint32_t code) { in rom_data_lookup() argument
24 return rom_table_lookup(data_table, code); in rom_data_lookup()
32 return rom_table_lookup(code, RT_FLAG_DATA); in rom_data_lookup()
|
| /hal_rpi_pico-latest/ |
| D | CONTRIBUTING.md | 5 …code, track [issues](https://github.com/raspberrypi/pico-sdk/issues) and feature requests, and to …
9 In order to contribute new or updated code, you must first create a GitHub account and fork the ori…
17 If you are contributing new or updated code please match the existing code style, particularly:
|
| D | .bazelrc | 1 # Silence all C/C++ warnings in external code.
|
| D | README.md | 11 …ing. These libraries should be comprehensive enough that your application code rarely, if at all, …
33 # Example code
35 See [pico-examples](https://github.com/raspberrypi/pico-examples) for example code you can build.
37 # Getting the latest SDK code
146 1. Write your code (see [pico-examples](https://github.com/raspberrypi/pico-examples) or the [Raspb…
|
| /hal_rpi_pico-latest/src/rp2_common/pico_bootrom/include/pico/ |
| D | bootrom.h | 130 void *rom_func_lookup(uint32_t code);
138 void *rom_data_lookup(uint32_t code);
156 typedef void *(*rom_table_lookup_fn)(uint16_t *table, uint32_t code);
158 typedef void *(*rom_table_lookup_fn)(uint32_t code, uint32_t mask);
193 static __force_inline void *rom_func_lookup_inline(uint32_t code) { in rom_func_lookup_inline() argument
197 return rom_table_lookup(func_table, code); in rom_func_lookup_inline()
203 return rom_table_lookup(code, RT_FLAG_FUNC_RISCV); in rom_func_lookup_inline()
209 return rom_table_lookup(code, RT_FLAG_FUNC_ARM_NONSEC); in rom_func_lookup_inline()
211 return rom_table_lookup(code, RT_FLAG_FUNC_ARM_SEC); in rom_func_lookup_inline()
|
| /hal_rpi_pico-latest/docs/ |
| D | CMakeLists.txt | 22 message("Documentation example code will come from ${PICO_EXAMPLES_PATH}")
24 …message(WARNING "Documentation example code configured to come from ${PICO_EXAMPLES_PATH}, but tha…
39 … message("Documentation example code will come from git repo ${GIT_REPOSITORY}, branch ${GIT_TAG}")
|
| D | examples.md | 3 This page links to the various example code fragments in this documentation. For more complete exam…
19 …are released under a 3-Clause BSD licence. Briefly, this means you are free to use the example code
|
| D | mainpage.md | 23 …ludes the entirety of the code needed to run on the device (other than device specific floating-po…
27 …er of example code fragments. An index of these examples can be found [here](@ref examples_page). …
|
| D | weblinks_page.md | 28 All the source code for the Raspberry Pi Pico SDK, examples and other libraries can be found on Git…
34 - [Pico Bootrom source code](https://github.com/raspberrypi/pico-bootrom)
|
| /hal_rpi_pico-latest/test/pico_float_test/llvm/ |
| D | LICENSE.TXT | 25 * Redistributions of source code must retain the above copyright notice,
48 The LLVM software contains code written by third parties. Such software will
51 to that code.
54 applies to all code in the LLVM Distribution, and nothing in any of the
|
| /hal_rpi_pico-latest/src/host/ |
| D | README.md | 5 …tremely useful for testing and debugging higher level application code, or porting code which is n…
|
| /hal_rpi_pico-latest/src/rp2_common/pico_mem_ops/ |
| D | mem_ops_aeabi.S | 29 # NOTE: All code sections are placed in RAM (at the expense of some veneer cost for calls from flas…
30 # otherwise code using basic c division operators will require XIP flash access.
|
| /hal_rpi_pico-latest/src/common/ |
| D | README.md | 1 This directory code that is common to all builds regardless of `PICO_PLATFORM`. It is a mix
|
| /hal_rpi_pico-latest/src/common/pico_binary_info/ |
| D | BUILD.bazel | 18 "include/pico/binary_info/code.h",
|
| /hal_rpi_pico-latest/src/common/pico_bit_ops_headers/ |
| D | BUILD.bazel | 5 # Application code should always use :pico_bit_ops instead.
|
| /hal_rpi_pico-latest/src/rp2_common/pico_platform_panic/ |
| D | BUILD.bazel | 7 # Application code should always use :pico_platform_panic instead.
|
| /hal_rpi_pico-latest/src/rp2_common/hardware_timer/ |
| D | BUILD.bazel | 7 # Application code should always use :hardware_timer instead.
|
| /hal_rpi_pico-latest/src/rp2_common/hardware_sync/ |
| D | BUILD.bazel | 7 # Application code should always use :hardware_sync instead.
|
| /hal_rpi_pico-latest/src/host/hardware_timer/ |
| D | BUILD.bazel | 11 # Application code should always use :hardware_timer instead.
|
| /hal_rpi_pico-latest/src/rp2_common/hardware_clocks/ |
| D | BUILD.bazel | 7 # Application code should always use :hardware_clocks instead.
|
| /hal_rpi_pico-latest/src/rp2_common/pico_crt0/rp2040/ |
| D | memmap_blocked_ram.ld | 2 Defines the following symbols for use by code:
70 …of a hack right now to exclude all floating point and time critical (e.g. memset, memcpy) code from
284 /* todo assert on extra code */
|
| D | memmap_default.ld | 2 Defines the following symbols for use by code:
70 …of a hack right now to exclude all floating point and time critical (e.g. memset, memcpy) code from
284 /* todo assert on extra code */
|
| /hal_rpi_pico-latest/src/rp2_common/pico_stdio/ |
| D | BUILD.bazel | 7 # Application code should always use :pico_stdio instead.
|
| /hal_rpi_pico-latest/src/common/pico_time/ |
| D | BUILD.bazel | 7 # Application code should always use :pico_time instead.
|
| /hal_rpi_pico-latest/src/rp2_common/pico_crt0/rp2350/ |
| D | memmap_default.ld | 2 Defines the following symbols for use by code:
59 …of a hack right now to exclude all floating point and time critical (e.g. memset, memcpy) code from
300 /* todo assert on extra code */
|
