ALP SDK
Drivers and APIs Driver-level discussion: alp_i2c_*, alp_spi_*, alp_gpio_*, alp_uart_*, alp_pwm_*, alp_adc_*, alp_dac_*, alp_counter_*, alp_qenc_*, alp_i2s_*, alp_can_*, alp_rtc_*, alp_wdt_*, plus the v0.3 surfaces (audio, ble, security, mproc, dsp, power, gpu2d, camera, storage). API reference is generated from the headers under include/alp/. Getting Started First-time setup, environment, west, board.yaml, and examples/. Start with docs/firmware-quickstart.md and docs/getting-started.md. Stuck on terminology? docs/glossary.md.
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| About the ALP SDK category |
|
0 | 0 | April 4, 2026 |
| Index — ALP SDK getting-started reading order |
|
0 | 1 | May 14, 2026 |
| ALP SDK Driver API Reference & Discussion |
|
0 | 0 | April 4, 2026 |
| Can I switch hardware vendors without changing my application code? |
|
0 | 3 | April 4, 2026 |
| Which processors are currently supported by ALP SDK? |
|
0 | 4 | April 4, 2026 |
| Can I develop and test without physical hardware? |
|
0 | 1 | April 4, 2026 |
| How do I get started with E1M? |
|
0 | 1 | April 4, 2026 |
| What is ALP SDK and how does it relate to E1M? |
|
0 | 1 | April 4, 2026 |