CArduinoPicoTone | ArduinoPicoTone provides static methods for PicoTone |
▼Carduino::HardwareSPI | |
CPicoHardwareSPI | Arduino HardwareSPI interface using the Pico API. We use the following default pins spi0: pinRx = 16; pinTx = 19; pinCS = 17; pinSCK = 18; spi1: pinRx = 12; pinTx = 11; pinCS = 13; pinSCK = 10; On the master miso = pinRx and mosi = pinTx |
CVector< T >::iterator | Iterator for the Vector class |
CMap< K, V > | A simple key value map collection |
CMap< K, V >::MapEntry< KM, VM > | |
CMap< K, V >::MapEntry< K, V > | |
CMuliticoreFifo | The RP2040 contains two FIFOs for passing data, messages or ordered events between the two cores. Each FIFO is 32 bits wide, and 8 entries deep. One of the FIFOs can only be written by core 0, and read by core 1. The other can only be written by core 1, and read by core 0 |
Carduino::Stream::MultiTarget | |
CPicoLogger | |
CPicoPinFunction | |
CPicoPWM | This is an even more powerfull PWM API where we can specify a user defined input range and the cycle frequency in hz |
CPicoPWMNano | |
CPicoTone | We use the TimerAlarmRepeating to generate tones |
CPinInfo | Information about an the status and the Arduino PinMode of an individual pin |
CPIOManager | The PIO subsystem on RP2040 allows you to write small, simple programs for what are called PIO state machines, of which RP2040 has eight split across two PIO instances. A state machine is responsible for setting and reading one or more GPIOs, buffering data to or from the processor (or RP2040’s ultra-fast DMA subsystem), and notifying the processor, via IRQ or polling, when data or attention is needed |
Carduino::PluggableUSB_ | |
Carduino::PluggableUSBModule | |
▼Carduino::Print | |
Carduino::Server | |
▼Carduino::Stream | |
Carduino::Client | |
▼Carduino::HardwareI2C | |
CPicoHardwareI2C | Arduino I2C implementation using the Pico functionality. In Arduino we can read and write individal characters wheresease in Pico the operations have to be done with arrays. We therefore create a read and write buffer to cache the operations |
▼Carduino::HardwareSerial | |
CPicoSerialUART | Serial Stream for a defined UART. By default we use the following pins: UART0 tx/rx = gp0/gp1; UART1 tx/rx = gp4/gp5; |
CPicoSerialUSB | PicoUSBSerial is using the pico USB output. It is mapped to the Arduino Serial variable |
Carduino::UDP | |
▼Carduino::Printable | |
Carduino::IPAddress | |
CQueue< T > | Construct a new Pico Queue object |
CSemaphore | Pico Semaphore which might be useful if you use the 2 processors (e.g. with the Thread class) |
CServo | We provide an alternative Pico implementation for the Servo class which is compatible with the Arduino Server library |
Carduino::SPISettings | |
▼CStream | |
CSoftwareSerial | Software Serial Arduino Stream which uses the Pico PIO |
CThread | Adds support for running code on the second processor core (core1) |
CTimerAlarm | Alarm functions for scheduling future execution |
CTimerAlarmRepeating | Repeating Timer functions for simple scheduling of repeated execution |
CVector< T > | Vector implementation which provides the most important methods as defined by std::vector. This is neither part of Pico nor of the Arduino framwork but nevertheless it is quite handy to have and most of the times quite better then dealing with raw c arrays |
CVector< Map::MapEntry< K, V > > | |