> For the complete documentation index, see [llms.txt](https://bananapi.gitbook.io/bpi-g1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bananapi.gitbook.io/bpi-g1/zh/someofthefeaturesstm32f103cb.md).

# Some of the features STM32F103CB

* ARM Cortex-M3 core running at 72MHz
* 128K system programmable flash memory
* 20KB RAM
* 2 × 12 bits 1 microsecond A / D 
  1. converter (up to 16 channels)
  2. Conversion range: 0\~3.6 V
  3. Dual sample and hold function
* DMA
  1. 7-channel DMA controller
  2. Supported peripherals: timers, ADC, SPI's, I2C and USART
* 18 general-purpose programmable GPIO
* 7 Timer
  1. 3 16-bit timers, each up to 4 IC / OC / PWM or pulse counter quadrature (incremental)     encoder into
  2. 16-bit motor control PWM timer, dead-time generation and emergency stop
  3. 2 watchdog timers (Independent and windows)
  4. System Timer: 24 downcounter
* 1 I2C interface (SMBus / PMBus)
* 3 USART (ISO7816 interface, LIN, infrared capabilities, modem control)
* 1 SPI interface (18 Mbit / s)
* 1 CAN interface (2.0B Active)
* 1 full-speed USB 2.0 interface


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bananapi.gitbook.io/bpi-g1/zh/someofthefeaturesstm32f103cb.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.