doc: fix incorrect bullet lists
ReStructuredText bullet lists should be preceded by an empty line Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This commit is contained in:
Benjamin Cabé
Anas Nashif
parent
3c3627b968
commit
a8573a985c
18 changed files with 36 additions and 10 deletions
|
|
@ -15,6 +15,7 @@ with 2MBytes of Flash memory, 1MB RAM, 480 MHz CPU, Art Accelerator, L1 cache, e
|
|||
large set of peripherals, SMPS, and MIPI-DSI.
|
||||
|
||||
Additionally, the board features:
|
||||
|
||||
- USB OTG FS
|
||||
- 3 color user LEDs
|
||||
|
||||
|
|
|
|||
|
|
@ -124,6 +124,7 @@ included during the build process.
|
|||
|
||||
CPU1 does not work without CPU0 enabling it.
|
||||
To enable it, run one of the following samples in ``subsys\ipc``:
|
||||
|
||||
- ``ipm_mcux``
|
||||
- ``openamp``
|
||||
|
||||
|
|
|
|||
|
|
@ -344,6 +344,7 @@ Configuring a Debug Probe
|
|||
A debug probe is used for both flashing and debugging the board. The on-board
|
||||
debugger listed below works with the LinkServer runner by default, or can be
|
||||
reprogrammed with JLink firmware.
|
||||
|
||||
- MIMXRT1170-EVKB: :ref:`mcu-link-cmsis-onboard-debug-probe`
|
||||
- MIMXRT1170-EVK: :ref:`opensda-daplink-onboard-debug-probe`
|
||||
|
||||
|
|
@ -392,10 +393,12 @@ We will use the on-board debugger
|
|||
microcontroller as a usb-to-serial adapter for the serial console. The following
|
||||
jumper settings are default on these boards, and are required to connect the
|
||||
UART signals to the USB bridge circuit:
|
||||
|
||||
- MIMXRT1170-EVKB: JP2 open (default)
|
||||
- MIMXRT1170-EVK: J31 and J32 shorted (default)
|
||||
|
||||
Connect a USB cable from your PC to the on-board debugger USB port:
|
||||
|
||||
- MIMXRT1170-EVKB: J86
|
||||
- MIMXRT1170-EVK: J11
|
||||
|
||||
|
|
|
|||
|
|
@ -177,6 +177,7 @@ To use ethernet on the RD_RW612_BGA board, you first need to make the following
|
|||
modifications to the board hardware:
|
||||
|
||||
Add resistors:
|
||||
|
||||
- R485
|
||||
- R486
|
||||
- R487
|
||||
|
|
@ -184,7 +185,9 @@ Add resistors:
|
|||
- R489
|
||||
- R491
|
||||
- R490
|
||||
|
||||
Remove resistors:
|
||||
|
||||
- R522
|
||||
- R521
|
||||
- R520
|
||||
|
|
|
|||
|
|
@ -194,7 +194,9 @@ Flashing an application to SECO SBC-3.5-PX30
|
|||
|
||||
First, connect the SECO SBC-3.5-PX30 to your host computer using
|
||||
CN56 connector to an ST-Link.
|
||||
|
||||
The pinout is (1-8):
|
||||
|
||||
- VDD
|
||||
- UART1_TX
|
||||
- UART1_RX
|
||||
|
|
|
|||
|
|
@ -112,6 +112,7 @@ features:
|
|||
Other hardware features are not yet supported on this Zephyr port.
|
||||
|
||||
The default configuration can be found in:
|
||||
|
||||
- :zephyr_file:`boards/seeed/lora_e5_dev_board/lora_e5_dev_board_defconfig`
|
||||
- :zephyr_file:`boards/seeed/lora_e5_dev_board/lora_e5_dev_board.dts`
|
||||
|
||||
|
|
|
|||
|
|
@ -42,6 +42,7 @@ More information about the board can be found at the `B-G474E-DPOW1 website`_.
|
|||
|
||||
|
||||
More information about STM32G474RE can be found here:
|
||||
|
||||
- `G474RE on www.st.com`_
|
||||
- `STM32G4 reference manual`_
|
||||
|
||||
|
|
|
|||
|
|
@ -262,7 +262,9 @@ Debugging using STM32CubeIDE
|
|||
----------------------------
|
||||
|
||||
You can debug an application using a STM32WBA compatible version of STM32CubeIDE.
|
||||
|
||||
For that:
|
||||
|
||||
- Create an empty STM32WBA project by going to File > New > STM32 project
|
||||
- Select your MCU, click Next, and select an Empty project.
|
||||
- Right click on your project name, select Debug as > Debug configurations
|
||||
|
|
|
|||
|
|
@ -275,7 +275,9 @@ Debugging using STM32CubeIDE
|
|||
----------------------------
|
||||
|
||||
You can debug an application using a STM32WBA compatible version of STM32CubeIDE.
|
||||
|
||||
For that:
|
||||
|
||||
- Create an empty STM32WBA project by going to File > New > STM32 project
|
||||
- Select your MCU, click Next, and select an Empty project.
|
||||
- Right click on your project name, select Debug as > Debug configurations
|
||||
|
|
|
|||
|
|
@ -51,6 +51,7 @@ More information about the board can be found at the `STM32G071B-DISCO website`_
|
|||
|
||||
|
||||
More information about STM32G071RB can be found here:
|
||||
|
||||
- `G071RB on www.st.com`_
|
||||
- `STM32G071 reference manual`_
|
||||
|
||||
|
|
|
|||
|
|
@ -92,6 +92,7 @@ More information about the board can be found at the `STM32G081B-EVAL website`_.
|
|||
|
||||
|
||||
More information about STM32G081RB can be found here:
|
||||
|
||||
- `G081RB on www.st.com`_
|
||||
- `STM32G081 reference manual`_
|
||||
|
||||
|
|
|
|||
|
|
@ -79,10 +79,12 @@ configuration by altering device tree and Kconfig options. This will be covered
|
|||
in detail in next section.
|
||||
|
||||
Most of Xen-specific features are not supported at the moment. This includes:
|
||||
|
||||
* XenBus (under development)
|
||||
* Xen PV drivers
|
||||
|
||||
Now only following features are supported:
|
||||
|
||||
* Xen Enlighten memory page
|
||||
* Xen event channels
|
||||
* Xen PV console (2 versions: regular ring buffer based for DomU and consoleio for Dom0)
|
||||
|
|
|
|||
|
|
@ -131,6 +131,7 @@ Deviations from the standard
|
|||
****************************
|
||||
|
||||
Certain parts of the protocol are not yet supported in the library.
|
||||
|
||||
* Pre-defined topic IDs
|
||||
* QoS -1 - it's most useful with predefined topics
|
||||
* Gateway discovery using ADVERTISE, SEARCHGW and GWINFO messages.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,8 @@ BQ274XX Sensor Sample
|
|||
Overview
|
||||
********
|
||||
|
||||
This sample application retrieves all the fuel gauge parameters,
|
||||
This sample application retrieves all the fuel gauge parameters:
|
||||
|
||||
- Voltage, in volts
|
||||
- Average current, in amps
|
||||
- Standby current, in amps
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ This sample reads the value of the counter which has been configured in
|
|||
quadrature decoder mode.
|
||||
|
||||
It requires:
|
||||
|
||||
* an external mechanical encoder
|
||||
* pin to be properly configured in the device tree
|
||||
|
||||
|
|
|
|||
|
|
@ -20,12 +20,13 @@ too much resource requirements. The security is not top-notch (AES-128) but it
|
|||
is reasonable enough, given that the alternative is no security at all.
|
||||
|
||||
OSDP Supports the control of the following components on a PD:
|
||||
- LED
|
||||
- Buzzer
|
||||
- Keypad
|
||||
- Output (GPIOs)
|
||||
- Input Control (GPIOs)
|
||||
- Displays
|
||||
- Device status (tamper, power, etc.,)
|
||||
- Card Reader
|
||||
- Fingerprint Reader
|
||||
|
||||
- LED
|
||||
- Buzzer
|
||||
- Keypad
|
||||
- Output (GPIOs)
|
||||
- Input Control (GPIOs)
|
||||
- Displays
|
||||
- Device status (tamper, power, etc.,)
|
||||
- Card Reader
|
||||
- Fingerprint Reader
|
||||
|
|
|
|||
|
|
@ -27,6 +27,7 @@ Testing
|
|||
*******
|
||||
|
||||
Steps to test the sample:
|
||||
|
||||
- Build and flash the sample as described above.
|
||||
- Connect to the HOST.
|
||||
- Chose default Audio IN/OUT.
|
||||
|
|
|
|||
|
|
@ -26,6 +26,7 @@ Testing
|
|||
*******
|
||||
|
||||
Steps to test the sample:
|
||||
|
||||
- Build and flash the sample as described above.
|
||||
- Connect to the HOST.
|
||||
- Chose default Audio IN/OUT.
|
||||
|
|
|
|||
Loading…
Reference in a new issue