boards: nxp: adopt new zephyr:board directive and role
This updates the documentation of all the NXP boards to use the new `zephyr:board::` directive. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This commit is contained in:
Benjamin Cabé
Carles Cufí
parent
a17d854004
commit
d885957fe8
89 changed files with 143 additions and 483 deletions
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_k22f:
|
.. zephyr:board:: frdm_k22f
|
||||||
|
|
||||||
NXP FRDM-K22F
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -19,10 +16,6 @@ MCUs.
|
||||||
running an open source bootloader, offers options for serial communication,
|
running an open source bootloader, offers options for serial communication,
|
||||||
flash programming, and run-control debugging
|
flash programming, and run-control debugging
|
||||||
|
|
||||||
.. image:: frdm_k22f.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-K22F
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -59,7 +52,7 @@ Supported Features
|
||||||
|
|
||||||
The frdm_k22f board configuration supports the hardware features listed
|
The frdm_k22f board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`frdm_k64f`, which is the superset board in NXP's Kinetis K series.
|
:zephyr:board:`frdm_k64f`, which is the superset board in NXP's Kinetis K series.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the frdm_k64f board may have additional features
|
Zephyr. Therefore, the frdm_k64f board may have additional features
|
||||||
already supported, which can also be re-used on this frdm_k22f board:
|
already supported, which can also be re-used on this frdm_k22f board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_k64f:
|
.. zephyr:board:: frdm_k64f
|
||||||
|
|
||||||
NXP FRDM-K64F
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -19,10 +16,6 @@ K63, and K24 MCUs.
|
||||||
running an open source bootloader, offers options for serial communication,
|
running an open source bootloader, offers options for serial communication,
|
||||||
flash programming, and run-control debugging
|
flash programming, and run-control debugging
|
||||||
|
|
||||||
.. image:: frdm_k64f.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-K64F
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_k82f:
|
.. zephyr:board:: frdm_k82f
|
||||||
|
|
||||||
NXP FRDM-K82F
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -19,10 +16,6 @@ and K82 MCUs.
|
||||||
running an open source bootloader, offers options for serial communication,
|
running an open source bootloader, offers options for serial communication,
|
||||||
flash programming, and run-control debugging
|
flash programming, and run-control debugging
|
||||||
|
|
||||||
.. image:: frdm_k82f.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-K82F
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -60,7 +53,7 @@ Supported Features
|
||||||
|
|
||||||
The frdm_k82f board configuration supports the hardware features listed
|
The frdm_k82f board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`frdm_k64f`, which is the superset board in NXP's Kinetis K series.
|
:zephyr:board:`frdm_k64f`, which is the superset board in NXP's Kinetis K series.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the frdm_k64f board may have additional features
|
Zephyr. Therefore, the frdm_k64f board may have additional features
|
||||||
already supported, which can also be re-used on this frdm_k82f board:
|
already supported, which can also be re-used on this frdm_k82f board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_ke15z:
|
.. zephyr:board:: frdm_ke15z
|
||||||
|
|
||||||
NXP FRDM-KE15Z
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -12,10 +9,6 @@ with up to 50 channels which makes this board highly flexible
|
||||||
for touch keys. Offers options for serial
|
for touch keys. Offers options for serial
|
||||||
communication, flash programming, and run-control debugging.
|
communication, flash programming, and run-control debugging.
|
||||||
|
|
||||||
.. figure:: frdm_ke15z.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-KE15Z
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_ke17z:
|
.. zephyr:board:: frdm_ke17z
|
||||||
|
|
||||||
NXP FRDM-KE17Z
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -12,12 +9,6 @@ with up to 50 channels which makes this board highly flexible
|
||||||
for touch keys. Offers options for serial
|
for touch keys. Offers options for serial
|
||||||
communication, flash programming, and run-control debugging.
|
communication, flash programming, and run-control debugging.
|
||||||
|
|
||||||
.. figure:: frdmke17z.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-KE17Z
|
|
||||||
|
|
||||||
FRDM-KE17Z (Credit: NXP)
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_ke17z512:
|
.. zephyr:board:: frdm_ke17z512
|
||||||
|
|
||||||
NXP FRDM-KE17Z512
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,12 +8,6 @@ MCU-based platforms. The onboard OpenSDAv2 serial and debug adapter,
|
||||||
running an open source bootloader, offers options for serial
|
running an open source bootloader, offers options for serial
|
||||||
communication, flash programming, and run-control debugging.
|
communication, flash programming, and run-control debugging.
|
||||||
|
|
||||||
.. figure:: frdm_ke17z512.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-KE17Z512
|
|
||||||
|
|
||||||
FRDM-KE17Z512 (Credit: NXP)
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_kl25z:
|
.. zephyr:board:: frdm_kl25z
|
||||||
|
|
||||||
NXP FRDM-KL25Z
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -14,11 +11,6 @@ The FRDM-KL25Z features include easy access to MCU I/O, battery-ready,
|
||||||
low-power operation, a standard-based form factor with expansion board
|
low-power operation, a standard-based form factor with expansion board
|
||||||
options and a built-in debug interface for flash programming and run-control.
|
options and a built-in debug interface for flash programming and run-control.
|
||||||
|
|
||||||
|
|
||||||
.. image:: frdm_kl25z.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-KL25Z
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_kw41z:
|
.. zephyr:board:: frdm_kw41z
|
||||||
|
|
||||||
NXP FRDM-KW41Z
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -22,10 +19,6 @@ F-antenna which can be bypassed to test via SMA connection, multiple power
|
||||||
supply options, push/capacitive touch buttons, switches, LEDs and integrated
|
supply options, push/capacitive touch buttons, switches, LEDs and integrated
|
||||||
sensors.
|
sensors.
|
||||||
|
|
||||||
.. image:: frdm_kw41z.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-KW41Z
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_mcxa156:
|
.. zephyr:board:: frdm_mcxa156
|
||||||
|
|
||||||
NXP FRDM-MCXA156
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ an on-board MCU-Link debugger. MCX N Series are high-performance, low-power
|
||||||
microcontrollers with intelligent peripherals and accelerators providing multi-tasking
|
microcontrollers with intelligent peripherals and accelerators providing multi-tasking
|
||||||
capabilities and performance efficiency.
|
capabilities and performance efficiency.
|
||||||
|
|
||||||
.. image:: frdm_mcxa156.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-MCXA156
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_mcxc242:
|
.. zephyr:board:: frdm_mcxc242
|
||||||
|
|
||||||
NXP FRDM-MCXC242
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,11 +10,6 @@ interfaces and on-board MCU-Link debugger.
|
||||||
The MCXC is a general purpose ultra-low-power MCU family,
|
The MCXC is a general purpose ultra-low-power MCU family,
|
||||||
providing additional memory, communications and analog peripheral.
|
providing additional memory, communications and analog peripheral.
|
||||||
|
|
||||||
|
|
||||||
.. image:: frdm_mcxc242.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-MCXC242
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_mcxc444:
|
.. zephyr:board:: frdm_mcxc444
|
||||||
|
|
||||||
NXP FRDM-MCXC444
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,11 +10,6 @@ interfaces and on-board MCU-Link debugger.
|
||||||
The MCXC is a general purpose ultra-low-power MCU family,
|
The MCXC is a general purpose ultra-low-power MCU family,
|
||||||
providing additional memory, communications and analog peripheral.
|
providing additional memory, communications and analog peripheral.
|
||||||
|
|
||||||
|
|
||||||
.. image:: frdm_mcxc444.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-MCXC444
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_mcxn236:
|
.. zephyr:board:: frdm_mcxn236
|
||||||
|
|
||||||
NXP FRDM-MCXN236
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ an on-board MCU-Link debugger. MCX N Series are high-performance, low-power
|
||||||
microcontrollers with intelligent peripherals and accelerators providing multi-tasking
|
microcontrollers with intelligent peripherals and accelerators providing multi-tasking
|
||||||
capabilities and performance efficiency.
|
capabilities and performance efficiency.
|
||||||
|
|
||||||
.. image:: frdm_mcxn236.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-MCXN236
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_mcxn947:
|
.. zephyr:board:: frdm_mcxn947
|
||||||
|
|
||||||
NXP FRDM-MCXN947
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ an on-board MCU-Link debugger. MCX N Series are high-performance, low-power
|
||||||
microcontrollers with intelligent peripherals and accelerators providing multi-tasking
|
microcontrollers with intelligent peripherals and accelerators providing multi-tasking
|
||||||
capabilities and performance efficiency.
|
capabilities and performance efficiency.
|
||||||
|
|
||||||
.. image:: frdm_mcxn947.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-MCXN947
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_mcxw71:
|
.. zephyr:board:: frdm_mcxw71
|
||||||
|
|
||||||
NXP FRDM-MCXW71
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -19,10 +16,6 @@ LE. The independent radio subsystem, with a dedicated core and memory, offloads
|
||||||
the main CPU, preserving it for the primary application and allowing firmware
|
the main CPU, preserving it for the primary application and allowing firmware
|
||||||
updates to support future wireless standards.
|
updates to support future wireless standards.
|
||||||
|
|
||||||
.. image:: frdm_mcxw71.webp
|
|
||||||
:align: center
|
|
||||||
:alt: FRDM-MCXW71
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _frdm_rw612:
|
.. zephyr:board:: frdm_rw612
|
||||||
|
|
||||||
NXP FRDM_RW612
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _imx8mm_evk:
|
.. zephyr:board:: imx8mm_evk
|
||||||
|
|
||||||
NXP i.MX8MM EVK
|
|
||||||
###############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _imx8mn_evk:
|
.. zephyr:board:: imx8mn_evk
|
||||||
|
|
||||||
NXP i.MX8MN EVK (Cortex-A53)
|
|
||||||
############################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _imx8mp_evk:
|
.. zephyr:board:: imx8mp_evk
|
||||||
|
|
||||||
NXP i.MX8MP EVK
|
|
||||||
###############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimx8mq_evk:
|
.. zephyr:board:: imx8mq_evk
|
||||||
|
|
||||||
NXP MIMX8MQ EVK
|
|
||||||
###############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -37,10 +34,6 @@ Zephyr OS is ported to run on the Cortex®-M4 core.
|
||||||
- JTAG 10-pin connector
|
- JTAG 10-pin connector
|
||||||
- MicroUSB for UART debug, two COM ports for A53 and M4
|
- MicroUSB for UART debug, two COM ports for A53 and M4
|
||||||
|
|
||||||
.. image:: img/mimx8mq_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMX8MQ EVK
|
|
||||||
|
|
||||||
More information about the board can be found at the
|
More information about the board can be found at the
|
||||||
`NXP website`_.
|
`NXP website`_.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _imx93_evk:
|
.. zephyr:board:: imx93_evk
|
||||||
|
|
||||||
NXP i.MX93 EVK
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _imx95_evk:
|
.. zephyr:board:: imx95_evk
|
||||||
|
|
||||||
NXP i.MX95 EVK
|
|
||||||
##############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso11u68:
|
.. zephyr:board:: lpcxpresso11u68
|
||||||
|
|
||||||
NXP LPCXpresso11U68
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -9,10 +6,6 @@ Overview
|
||||||
The LPCXpresso11u68 development board uses an NXP LPC11U68 MCU based
|
The LPCXpresso11u68 development board uses an NXP LPC11U68 MCU based
|
||||||
on an ARM Cortex-M0+ core.
|
on an ARM Cortex-M0+ core.
|
||||||
|
|
||||||
.. figure:: lpcxpresso11u68.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXpresso11U68
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso51u68:
|
.. zephyr:board:: lpcxpresso51u68
|
||||||
|
|
||||||
NXP LPCXPRESSO51U68
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -9,10 +6,6 @@ Overview
|
||||||
The LPCXpresso51u68 development board uses an NXP LPC51U68 MCU based
|
The LPCXpresso51u68 development board uses an NXP LPC51U68 MCU based
|
||||||
on an ARM CORTEX-M0+ core.
|
on an ARM CORTEX-M0+ core.
|
||||||
|
|
||||||
.. figure:: lpcxpresso51u68.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXpresso51U68
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso54114:
|
.. zephyr:board:: lpcxpresso54114
|
||||||
|
|
||||||
NXP LPCXPRESSO54114
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ microcontrollers. LPCXpresso is an end-to-end solution enabling embedded
|
||||||
engineers to develop their applications from initial evaluation to final
|
engineers to develop their applications from initial evaluation to final
|
||||||
production.
|
production.
|
||||||
|
|
||||||
.. image:: lpcxpresso54114_m4.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXPRESSO54114
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso55s06:
|
.. zephyr:board:: lpcxpresso55s06
|
||||||
|
|
||||||
NXP LPCXpresso55S06
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ with additional expansion ports around the Arduino footprint, along
|
||||||
with a PMod/host interface port and MikroElektronika Click module
|
with a PMod/host interface port and MikroElektronika Click module
|
||||||
site.
|
site.
|
||||||
|
|
||||||
.. image:: lpcxpress55s06.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXpresso55S06
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -45,7 +38,7 @@ Supported Features
|
||||||
|
|
||||||
The lpcxpresso55s06 board configuration supports the hardware features listed
|
The lpcxpresso55s06 board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`lpcxpresso55s69` , which is the superset board in NXP's LPC55xx series.
|
:zephyr:board:`lpcxpresso55s69` , which is the superset board in NXP's LPC55xx series.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the lpcxpresso55s69 board may have additional features
|
Zephyr. Therefore, the lpcxpresso55s69 board may have additional features
|
||||||
already supported, which can also be re-used on this lpcxpresso55s06 board:
|
already supported, which can also be re-used on this lpcxpresso55s06 board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso55s16:
|
.. zephyr:board:: lpcxpresso55s16
|
||||||
|
|
||||||
NXP LPCXpresso55S16
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ with additional expansion ports around the Arduino footprint, along
|
||||||
with a PMod/host interface port and MikroElektronika Click module
|
with a PMod/host interface port and MikroElektronika Click module
|
||||||
site.
|
site.
|
||||||
|
|
||||||
.. image:: lpcxpresso55S16.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXpresso55S16
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -50,7 +43,7 @@ Supported Features
|
||||||
|
|
||||||
The lpcxpresso55s16 board configuration supports the hardware features listed
|
The lpcxpresso55s16 board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`lpcxpresso55s69` , which is the superset board in NXP's LPC55xx series.
|
:zephyr:board:`lpcxpresso55s69` , which is the superset board in NXP's LPC55xx series.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the lpcxpresso55s69 board may have additional features
|
Zephyr. Therefore, the lpcxpresso55s69 board may have additional features
|
||||||
already supported, which can also be re-used on this lpcxpresso55s16 board:
|
already supported, which can also be re-used on this lpcxpresso55s16 board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso55s28:
|
.. zephyr:board:: lpcxpresso55s28
|
||||||
|
|
||||||
NXP LPCXpresso55S28
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -12,10 +9,6 @@ architecture. The board includes a high-performance onboard debug probe, audio
|
||||||
subsystem and accelerometer, with several options for adding off-the-shelf
|
subsystem and accelerometer, with several options for adding off-the-shelf
|
||||||
add-on boards for networking, sensors, displays, and other interfaces.
|
add-on boards for networking, sensors, displays, and other interfaces.
|
||||||
|
|
||||||
.. image:: LPC55S28-EVK.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXpresso55S28
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -50,7 +43,7 @@ Supported Features
|
||||||
|
|
||||||
The lpcxpresso55s28 board configuration supports the hardware features listed
|
The lpcxpresso55s28 board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`lpcxpresso55s69` , which is the superset board in NXP's LPC55xx series.
|
:zephyr:board:`lpcxpresso55s69` , which is the superset board in NXP's LPC55xx series.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the lpcxpresso55s69 board may have additional features
|
Zephyr. Therefore, the lpcxpresso55s69 board may have additional features
|
||||||
already supported, which can also be re-used on this lpcxpresso55s28 board:
|
already supported, which can also be re-used on this lpcxpresso55s28 board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso55s36:
|
.. zephyr:board:: lpcxpresso55s36
|
||||||
|
|
||||||
NXP LPCXpresso55S36
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ with additional expansion ports around the Arduino footprint, along
|
||||||
with a PMod/host interface port and MikroElektronika Click module
|
with a PMod/host interface port and MikroElektronika Click module
|
||||||
site.
|
site.
|
||||||
|
|
||||||
.. image:: lpcxpresso55S36.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXpresso55S36
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -52,7 +45,7 @@ family of MCUs. This board is a focus for NXP's Full Platform Support for
|
||||||
Zephyr, to better enable the entire LPC55(S)3x family. NXP prioritizes enabling
|
Zephyr, to better enable the entire LPC55(S)3x family. NXP prioritizes enabling
|
||||||
this board with new support for Zephyr features. The lpcxpresso55s36 board
|
this board with new support for Zephyr features. The lpcxpresso55s36 board
|
||||||
configuration supports the hardware features below. Another similar superset
|
configuration supports the hardware features below. Another similar superset
|
||||||
board is the :ref:`lpcxpresso55s69`, and that board may have additional features
|
board is the :zephyr:board:`lpcxpresso55s69`, and that board may have additional features
|
||||||
already supported, which can also be re-used on this lpcxpresso55s36 board:
|
already supported, which can also be re-used on this lpcxpresso55s36 board:
|
||||||
|
|
||||||
+-----------+------------+-------------------------------------+
|
+-----------+------------+-------------------------------------+
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _lpcxpresso55s69:
|
.. zephyr:board:: lpcxpresso55s69
|
||||||
|
|
||||||
NXP LPCXPRESSO55S69
|
|
||||||
###################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -12,10 +9,6 @@ architecture. The board includes a high performance onboard debug probe, audio
|
||||||
subsystem, and accelerometer, with several options for adding off-the-shelf
|
subsystem, and accelerometer, with several options for adding off-the-shelf
|
||||||
add-on boards for networking, sensors, displays, and other interfaces.
|
add-on boards for networking, sensors, displays, and other interfaces.
|
||||||
|
|
||||||
.. image:: lpcxpresso55s69.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: LPCXPRESSO55S69
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _nxp_ls1046ardb:
|
.. zephyr:board:: ls1046ardb
|
||||||
|
|
||||||
NXP LS1046A RDB
|
|
||||||
#################################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1010_evk:
|
.. zephyr:board:: mimxrt1010_evk
|
||||||
|
|
||||||
NXP MIMXRT1010-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ series by providing the lowest-cost LQFP package option, combined with the
|
||||||
high performance and ease-of-use known throughout the entire i.MX RT series.
|
high performance and ease-of-use known throughout the entire i.MX RT series.
|
||||||
This device is fully supported by NXP’s MCUXpresso Software and Tools.
|
This device is fully supported by NXP’s MCUXpresso Software and Tools.
|
||||||
|
|
||||||
.. image:: mimxrt1010_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1010-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -69,7 +62,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1010_evk board configuration supports the hardware features listed
|
The mimxrt1010_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1010_evk board:
|
already supported, which can also be re-used on this mimxrt1010_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1015_evk:
|
.. zephyr:board:: mimxrt1015_evk
|
||||||
|
|
||||||
NXP MIMXRT1015-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ high-performance feature set in low-cost LQFP packages, further simplifying
|
||||||
board design and layout for customers. The i.MX RT1015 runs on the Arm®
|
board design and layout for customers. The i.MX RT1015 runs on the Arm®
|
||||||
Cortex®-M7 core at 500 MHz.
|
Cortex®-M7 core at 500 MHz.
|
||||||
|
|
||||||
.. image:: mimxrt1015_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1015-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -69,7 +62,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1015_evk board configuration supports the hardware features listed
|
The mimxrt1015_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1015_evk board:
|
already supported, which can also be re-used on this mimxrt1015_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1020_evk:
|
.. zephyr:board:: mimxrt1020_evk
|
||||||
|
|
||||||
NXP MIMXRT1020-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ high-performance feature set in low-cost LQFP packages, further simplifying
|
||||||
board design and layout for customers. The i.MX RT1020 runs on the Arm®
|
board design and layout for customers. The i.MX RT1020 runs on the Arm®
|
||||||
Cortex®-M7 core at 500 MHz.
|
Cortex®-M7 core at 500 MHz.
|
||||||
|
|
||||||
.. image:: mimxrt1020_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1020-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -81,7 +74,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1020_evk board configuration supports the hardware features listed
|
The mimxrt1020_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1020_evk board:
|
already supported, which can also be re-used on this mimxrt1020_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1024_evk:
|
.. zephyr:board:: mimxrt1024_evk
|
||||||
|
|
||||||
NXP MIMXRT1024-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ high-performance feature set in low-cost LQFP packages, further simplifying
|
||||||
board design and layout for customers. The i.MX RT1024 runs on the Arm®
|
board design and layout for customers. The i.MX RT1024 runs on the Arm®
|
||||||
Cortex®-M7 core at 500 MHz.
|
Cortex®-M7 core at 500 MHz.
|
||||||
|
|
||||||
.. image:: mimxrt1024_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1024-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -82,7 +75,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1024_evk board configuration supports the hardware features listed
|
The mimxrt1024_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1024_evk board:
|
already supported, which can also be re-used on this mimxrt1024_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1040_evk:
|
.. zephyr:board:: mimxrt1040_evk
|
||||||
|
|
||||||
NXP MIMXRT1040-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -12,10 +9,6 @@ extended temperature range up to 125° C. The i.MX RT1040 MCU has a compact
|
||||||
2-layer PCB design. The i.MX RT1040 MCUs run on the Arm® Cortex®-M7 core at
|
2-layer PCB design. The i.MX RT1040 MCUs run on the Arm® Cortex®-M7 core at
|
||||||
600 MHz.
|
600 MHz.
|
||||||
|
|
||||||
.. image:: mimxrt1040_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1040-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -91,7 +84,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1040_evk board configuration supports the hardware features listed
|
The mimxrt1040_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1040_evk board:
|
already supported, which can also be re-used on this mimxrt1040_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1050_evk:
|
.. zephyr:board:: mimxrt1050_evk
|
||||||
|
|
||||||
NXP MIMXRT1050-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -17,10 +14,6 @@ and camera sensors. As with other i.MX processors, i.MX RT1050 also has rich
|
||||||
audio and video features, including LCD display, basic 2D graphics, camera
|
audio and video features, including LCD display, basic 2D graphics, camera
|
||||||
interface, SPDIF, and I2S audio interface.
|
interface, SPDIF, and I2S audio interface.
|
||||||
|
|
||||||
.. image:: mimxrt1050_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1050-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -104,7 +97,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1050_evk board configuration supports the hardware features listed
|
The mimxrt1050_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1050_evk board:
|
already supported, which can also be re-used on this mimxrt1050_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1060_evk:
|
.. zephyr:board:: mimxrt1060_evk
|
||||||
|
|
||||||
NXP MIMXRT1060-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -15,9 +12,6 @@ ideal for real-time applications such as High-Speed GPIO, CAN FD, and
|
||||||
synchronous parallel NAND/NOR/PSRAM controller. The i.MX RT1060 runs on the
|
synchronous parallel NAND/NOR/PSRAM controller. The i.MX RT1060 runs on the
|
||||||
Arm® Cortex-M7® core up to 600 MHz.
|
Arm® Cortex-M7® core up to 600 MHz.
|
||||||
|
|
||||||
.. image:: mimxrt1060_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1060-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
@ -103,7 +97,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1060_evk board configuration supports the hardware features listed
|
The mimxrt1060_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1060_evk board:
|
already supported, which can also be re-used on this mimxrt1060_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _fmurt6:
|
.. zephyr:board:: mimxrt1062_fmurt6
|
||||||
|
|
||||||
NXP FMURT6
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -15,10 +12,6 @@ ideal for real-time applications such as High-Speed GPIO, CAN FD, and
|
||||||
synchronous parallel NAND/NOR/PSRAM controller. The i.MX RT1062 runs on the
|
synchronous parallel NAND/NOR/PSRAM controller. The i.MX RT1062 runs on the
|
||||||
Arm® Cortex-M7® core up to 600 MHz.
|
Arm® Cortex-M7® core up to 600 MHz.
|
||||||
|
|
||||||
.. image:: mimxrt1062_fmurt6.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1062_FMURT6
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -77,7 +70,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1062_fmurt6 board configuration supports the hardware features listed
|
The mimxrt1062_fmurt6 board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
:zephyr:board:`mimxrt1064_evk` , which is the superset board in NXP's i.MX RT10xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1064_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1060_evk board:
|
already supported, which can also be re-used on this mimxrt1060_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1064_evk:
|
.. zephyr:board:: mimxrt1064_evk
|
||||||
|
|
||||||
NXP MIMXRT1064-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -14,10 +11,6 @@ ideal for real-time applications such as High-Speed GPIO, CAN FD, and
|
||||||
synchronous parallel NAND/NOR/PSRAM controller. The i.MX RT1064 runs on the
|
synchronous parallel NAND/NOR/PSRAM controller. The i.MX RT1064 runs on the
|
||||||
Arm® Cortex-M7® core up to 600 MHz.
|
Arm® Cortex-M7® core up to 600 MHz.
|
||||||
|
|
||||||
.. image:: mimxrt1064_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1064-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1160_evk:
|
.. zephyr:board:: mimxrt1160_evk
|
||||||
|
|
||||||
NXP MIMXRT1160-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ Cortex-M4 at 240 MHz. The i.MX RT1160 MCU offers support over a wide
|
||||||
temperature range and is qualified for consumer, industrial and automotive
|
temperature range and is qualified for consumer, industrial and automotive
|
||||||
markets.
|
markets.
|
||||||
|
|
||||||
.. image:: mimxrt1160_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1160-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -100,7 +93,7 @@ Supported Features
|
||||||
|
|
||||||
The mimxrt1160_evk board configuration supports the hardware features listed
|
The mimxrt1160_evk board configuration supports the hardware features listed
|
||||||
below. For additional features not yet supported, please also refer to the
|
below. For additional features not yet supported, please also refer to the
|
||||||
:ref:`mimxrt1170_evk` , which is the superset board in NXP's i.MX RT11xx family.
|
:zephyr:board:`mimxrt1170_evk` , which is the superset board in NXP's i.MX RT11xx family.
|
||||||
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
NXP prioritizes enabling the superset board with NXP's Full Platform Support for
|
||||||
Zephyr. Therefore, the mimxrt1170_evk board may have additional features
|
Zephyr. Therefore, the mimxrt1170_evk board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt1160_evk board:
|
already supported, which can also be re-used on this mimxrt1160_evk board:
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1170_evk:
|
.. zephyr:board:: mimxrt1170_evk
|
||||||
|
|
||||||
NXP MIMXRT1170-EVK/EVKB
|
|
||||||
#######################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ at 400 MHz. The i.MX RT1170 MCU offers support over a wide temperature range
|
||||||
and is qualified for consumer, industrial and automotive markets. Zephyr
|
and is qualified for consumer, industrial and automotive markets. Zephyr
|
||||||
supports the initial revision of this EVK, as well as rev EVKB.
|
supports the initial revision of this EVK, as well as rev EVKB.
|
||||||
|
|
||||||
.. image:: mimxrt1170_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1170-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt1180_evk:
|
.. zephyr:board:: mimxrt1180_evk
|
||||||
|
|
||||||
NXP MIMXRT1180-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ Cortex-M7 at 792 MHz. The i.MX RT1180 MCU offers support over a wide
|
||||||
temperature range and is qualified for consumer, industrial and automotive
|
temperature range and is qualified for consumer, industrial and automotive
|
||||||
markets.
|
markets.
|
||||||
|
|
||||||
.. image:: mimxrt1180_evk.webp
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT1180-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt595_evk:
|
.. zephyr:board:: mimxrt595_evk
|
||||||
|
|
||||||
NXP MIMXRT595-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -16,9 +13,6 @@ i.MX RT500 MCUs provides up to 5MB of on-chip SRAM and several high-bandwidth in
|
||||||
to access off-chip flash, including an Octal/Quad SPI interface with an on-the-fly
|
to access off-chip flash, including an Octal/Quad SPI interface with an on-the-fly
|
||||||
decryption engine.
|
decryption engine.
|
||||||
|
|
||||||
.. image:: mimxrt595_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT595-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
@ -62,7 +56,7 @@ family of MCUs. This board is a focus for NXP's Full Platform Support for
|
||||||
Zephyr, to better enable the entire RT5xx family. NXP prioritizes enabling
|
Zephyr, to better enable the entire RT5xx family. NXP prioritizes enabling
|
||||||
this board with new support for Zephyr features. The mimxrt595_evk board
|
this board with new support for Zephyr features. The mimxrt595_evk board
|
||||||
configuration supports the hardware features below. Another very similar
|
configuration supports the hardware features below. Another very similar
|
||||||
board is the :ref:`mimxrt685_evk`, and that board may have additional features
|
board is the :zephyr:board:`mimxrt685_evk`, and that board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt595_evk board:
|
already supported, which can also be re-used on this mimxrt595_evk board:
|
||||||
|
|
||||||
+-----------+------------+-------------------------------------+
|
+-----------+------------+-------------------------------------+
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mimxrt685_evk:
|
.. zephyr:board:: mimxrt685_evk
|
||||||
|
|
||||||
NXP MIMXRT685-EVK
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -17,10 +14,6 @@ The i.MX RT600 family provides up to 4.5MB of on-chip SRAM and several
|
||||||
high-bandwidth interfaces to access off-chip flash, including an Octal/Quad SPI
|
high-bandwidth interfaces to access off-chip flash, including an Octal/Quad SPI
|
||||||
interface with an on-the-fly decryption engine.
|
interface with an on-the-fly decryption engine.
|
||||||
|
|
||||||
.. image:: mimxrt685_evk.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: MIMXRT685-EVK
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
@ -59,7 +52,7 @@ family of MCUs. This board is a focus for NXP's Full Platform Support for
|
||||||
Zephyr, to better enable the entire RT6xx family. NXP prioritizes enabling
|
Zephyr, to better enable the entire RT6xx family. NXP prioritizes enabling
|
||||||
this board with new support for Zephyr features. The mimxrt685_evk board
|
this board with new support for Zephyr features. The mimxrt685_evk board
|
||||||
configuration supports the hardware features below. Another very similar
|
configuration supports the hardware features below. Another very similar
|
||||||
board is the :ref:`mimxrt595_evk`, and that board may have additional features
|
board is the :zephyr:board:`mimxrt595_evk`, and that board may have additional features
|
||||||
already supported, which can also be re-used on this mimxrt685_evk board:
|
already supported, which can also be re-used on this mimxrt685_evk board:
|
||||||
|
|
||||||
+-----------+------------+-------------------------------------+
|
+-----------+------------+-------------------------------------+
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _mr_canhubk3:
|
.. zephyr:board:: mr_canhubk3
|
||||||
|
|
||||||
NXP MR-CANHUBK3
|
|
||||||
###############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ as autonomous mobile robots (AMR) and automated guided vehicles (AGV). It
|
||||||
features an `NXP S32K344`_ general-purpose automotive microcontroller based on
|
features an `NXP S32K344`_ general-purpose automotive microcontroller based on
|
||||||
an Arm Cortex-M7 core (Lock-Step).
|
an Arm Cortex-M7 core (Lock-Step).
|
||||||
|
|
||||||
.. image:: img/mr_canhubk3_top.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: NXP MR-CANHUBK3 (TOP)
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _rd_rw612_bga:
|
.. zephyr:board:: rd_rw612_bga
|
||||||
|
|
||||||
NXP RD-RW612-BGA
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _rddrone_fmuk66:
|
.. zephyr:board:: rddrone_fmuk66
|
||||||
|
|
||||||
NXP RDDRONE-FMUK66
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ connectors and a Kinetis K66 on board.
|
||||||
|
|
||||||
- Comes with a J-Link Edu Mini for programming and UART console.
|
- Comes with a J-Link Edu Mini for programming and UART console.
|
||||||
|
|
||||||
.. image:: rddrone_fmuk66.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: RDDRONE-FMUK66
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _s32z2xxdc2:
|
.. zephyr:board:: s32z2xxdc2
|
||||||
|
|
||||||
NXP X-S32Z27X-DC (DC2)
|
|
||||||
######################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _twr_ke18f:
|
.. zephyr:board:: twr_ke18f
|
||||||
|
|
||||||
NXP TWR-KE18F
|
|
||||||
#############
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,12 +8,6 @@ MCU-based platforms. The onboard OpenSDAv2 serial and debug adapter,
|
||||||
running an open source bootloader, offers options for serial
|
running an open source bootloader, offers options for serial
|
||||||
communication, flash programming, and run-control debugging.
|
communication, flash programming, and run-control debugging.
|
||||||
|
|
||||||
.. figure:: TWR-KE18F-DEVICE.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: TWR-KE18F
|
|
||||||
|
|
||||||
TWR-KE18F (Credit: NXP)
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _twr_kv58f220m:
|
.. zephyr:board:: twr_kv58f220m
|
||||||
|
|
||||||
NXP TWR-KV58F220M
|
|
||||||
#################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,12 +8,6 @@ MCU-based platforms. The onboard OpenSDAv2 serial and debug adapter,
|
||||||
running an open source bootloader, offers options for serial
|
running an open source bootloader, offers options for serial
|
||||||
communication, flash programming, and run-control debugging.
|
communication, flash programming, and run-control debugging.
|
||||||
|
|
||||||
.. figure:: twr_kv58f220m.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: TWR-KV58F220M
|
|
||||||
|
|
||||||
TWR-KV58F220M (Credit: NXP)
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _ucans32k1sic:
|
.. zephyr:board:: ucans32k1sic
|
||||||
|
|
||||||
NXP UCANS32K1SIC
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -11,10 +8,6 @@ board designed for both automotive and industrial applications. The UCANS32K1SIC
|
||||||
provides two CAN SIC interfaces and is based on the 32-bit Arm Cortex-M4F
|
provides two CAN SIC interfaces and is based on the 32-bit Arm Cortex-M4F
|
||||||
`NXP S32K146`_ microcontroller.
|
`NXP S32K146`_ microcontroller.
|
||||||
|
|
||||||
.. image:: img/ucans32k1sic_top.webp
|
|
||||||
:align: center
|
|
||||||
:alt: NXP UCANS32K1SIC (TOP)
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _usb_kw24d512:
|
.. zephyr:board:: usb_kw24d512
|
||||||
|
|
||||||
NXP USB-KW24D512
|
|
||||||
################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,4 @@
|
||||||
.. _VMU RT1170:
|
.. zephyr:board:: vmu_rt1170
|
||||||
|
|
||||||
NXP VMU RT1170
|
|
||||||
##################
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
********
|
********
|
||||||
|
|
@ -13,10 +10,6 @@ and is qualified for consumer, industrial and automotive markets.
|
||||||
The VMU RT1170 is the default VMU for CogniPilot's Cerebri, a
|
The VMU RT1170 is the default VMU for CogniPilot's Cerebri, a
|
||||||
Zephyr RTOS based Autopilot.
|
Zephyr RTOS based Autopilot.
|
||||||
|
|
||||||
.. image:: vmu_rt1170.jpg
|
|
||||||
:align: center
|
|
||||||
:alt: VMU RT1170
|
|
||||||
|
|
||||||
Hardware
|
Hardware
|
||||||
********
|
********
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -10,7 +10,7 @@ The Freedom development board platform supports the MCR20A 2.4GHZ wireless
|
||||||
transceiver. The FRDM-CR20A evaluation board is a small, low-power,
|
transceiver. The FRDM-CR20A evaluation board is a small, low-power,
|
||||||
cost-effective reference design for the MCR20A transceiver in a shield form
|
cost-effective reference design for the MCR20A transceiver in a shield form
|
||||||
factor, compatible with existing Freedom development platforms, such as
|
factor, compatible with existing Freedom development platforms, such as
|
||||||
:ref:`frdm_k64f`.
|
:zephyr:board:`frdm_k64f`.
|
||||||
|
|
||||||
.. image:: frdm_cr20a.jpg
|
.. image:: frdm_cr20a.jpg
|
||||||
:align: center
|
:align: center
|
||||||
|
|
|
||||||
|
|
@ -13,7 +13,7 @@ integrated 2.4 GHz transceiver supporting Bluetooth |reg| Smart/Bluetooth
|
||||||
(BLE) v4.2, Generic FSK, IEEE |reg| 802.15.4 and Thread.
|
(BLE) v4.2, Generic FSK, IEEE |reg| 802.15.4 and Thread.
|
||||||
|
|
||||||
The FRDM-KW41Z can be used as a standalone board or as an Arduino shield. This
|
The FRDM-KW41Z can be used as a standalone board or as an Arduino shield. This
|
||||||
document covers usage as a shield; see :ref:`frdm_kw41z` for usage as a
|
document covers usage as a shield; see :zephyr:board:`frdm_kw41z` for usage as a
|
||||||
standalone board.
|
standalone board.
|
||||||
|
|
||||||
Bluetooth Controller
|
Bluetooth Controller
|
||||||
|
|
@ -53,7 +53,7 @@ host controller interface (HCI):
|
||||||
OpenSDA circuit.
|
OpenSDA circuit.
|
||||||
|
|
||||||
#. Attach the FRDM-KW41Z to the Arduino header on your selected main board,
|
#. Attach the FRDM-KW41Z to the Arduino header on your selected main board,
|
||||||
such as :ref:`mimxrt1050_evk` or :ref:`frdm_k64f`.
|
such as :zephyr:board:`mimxrt1050_evk` or :zephyr:board:`frdm_k64f`.
|
||||||
|
|
||||||
#. Set ``--shield frdm_kw41z`` when you invoke ``west build`` in
|
#. Set ``--shield frdm_kw41z`` when you invoke ``west build`` in
|
||||||
your Zephyr bluetooth application. For example,
|
your Zephyr bluetooth application. For example,
|
||||||
|
|
|
||||||
|
|
@ -35,7 +35,7 @@ support must be enabled in ethernet drivers.
|
||||||
|
|
||||||
Boards supported:
|
Boards supported:
|
||||||
|
|
||||||
- :ref:`frdm_k64f`
|
- :zephyr:board:`frdm_k64f`
|
||||||
- :ref:`nucleo_h743zi_board`
|
- :ref:`nucleo_h743zi_board`
|
||||||
- :ref:`nucleo_h745zi_q_board`
|
- :ref:`nucleo_h745zi_q_board`
|
||||||
- :ref:`nucleo_f767zi_board`
|
- :ref:`nucleo_f767zi_board`
|
||||||
|
|
|
||||||
|
|
@ -85,7 +85,7 @@ debug microcontroller SOC:
|
||||||
- LPC4322: :ref:`lpc-link2-onboard-debug-probe`
|
- LPC4322: :ref:`lpc-link2-onboard-debug-probe`
|
||||||
- MK20: :ref:`opensda-onboard-debug-probe`
|
- MK20: :ref:`opensda-onboard-debug-probe`
|
||||||
|
|
||||||
For example, the :ref:`frdm_k64f` board has an MK20 debug microcontroller,
|
For example, the :zephyr:board:`frdm_k64f` board has an MK20 debug microcontroller,
|
||||||
so this board uses the :ref:`opensda-onboard-debug-probe`.
|
so this board uses the :ref:`opensda-onboard-debug-probe`.
|
||||||
|
|
||||||
.. _mcu-link-onboard-debug-probe:
|
.. _mcu-link-onboard-debug-probe:
|
||||||
|
|
|
||||||
|
|
@ -35,7 +35,7 @@ The following :ref:`Kconfig <kconfig>` options enable additional subcommands and
|
||||||
well.
|
well.
|
||||||
* :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE` enables the ``can recover`` subcommand.
|
* :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE` enables the ``can recover`` subcommand.
|
||||||
|
|
||||||
For example, building the :zephyr:code-sample:`hello_world` sample for the :ref:`frdm_k64f` with the CAN shell and
|
For example, building the :zephyr:code-sample:`hello_world` sample for the :zephyr:board:`frdm_k64f` with the CAN shell and
|
||||||
CAN statistics enabled:
|
CAN statistics enabled:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
|
||||||
|
|
@ -95,7 +95,7 @@ the :term:`SoC series` and :term:`SoC family` levels are not always used.
|
||||||
+============================================+==========================+=============+====================+====================+================+======================+
|
+============================================+==========================+=============+====================+====================+================+======================+
|
||||||
| :ref:`nrf52dk <nrf52dk_nrf52832>` | nrf52832 | nRF52832 | nRF52 | Nordic nRF | Arm Cortex-M4 | ARMv7-M |
|
| :ref:`nrf52dk <nrf52dk_nrf52832>` | nrf52832 | nRF52832 | nRF52 | Nordic nRF | Arm Cortex-M4 | ARMv7-M |
|
||||||
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
||||||
| :ref:`frdm_k64f <frdm_k64f>` | mk64f12 | MK64F12 | Kinetis K6x | NXP Kinetis | Arm Cortex-M4 | ARMv7-M |
|
| :zephyr:board:`frdm_k64f <frdm_k64f>` | mk64f12 | MK64F12 | Kinetis K6x | NXP Kinetis | Arm Cortex-M4 | ARMv7-M |
|
||||||
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
||||||
| :ref:`rv32m1_vega <rv32m1_vega>` | openisa_rv32m1/ri5cy | RV32M1 | (Not used) | (Not used) | RI5CY | RISC-V RV32 |
|
| :ref:`rv32m1_vega <rv32m1_vega>` | openisa_rv32m1/ri5cy | RV32M1 | (Not used) | (Not used) | RI5CY | RISC-V RV32 |
|
||||||
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
||||||
|
|
@ -103,7 +103,7 @@ the :term:`SoC series` and :term:`SoC family` levels are not always used.
|
||||||
| +--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
| +--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
||||||
| | nrf5340/cpunet | nRF5340 | nRF53 | Nordic nRF | Arm Cortex-M33 | ARMv8-M |
|
| | nrf5340/cpunet | nRF5340 | nRF53 | Nordic nRF | Arm Cortex-M33 | ARMv8-M |
|
||||||
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
+--------------------------------------------+--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
||||||
| :ref:`mimx8mp_evk <imx8mp_evk>` | mimx8ml8/a53 | i.MX8M Plus | i.MX8M | NXP i.MX | Arm Cortex-A53 | ARMv8-A |
|
| :zephyr:board:`mimx8mp_evk <imx8mp_evk>` | mimx8ml8/a53 | i.MX8M Plus | i.MX8M | NXP i.MX | Arm Cortex-A53 | ARMv8-A |
|
||||||
| +--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
| +--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
||||||
| | mimx8ml8/m7 | i.MX8M Plus | i.MX8M | NXP i.MX | Arm Cortex-M7 | ARMv7-M |
|
| | mimx8ml8/m7 | i.MX8M Plus | i.MX8M | NXP i.MX | Arm Cortex-M7 | ARMv7-M |
|
||||||
| +--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
| +--------------------------+-------------+--------------------+--------------------+----------------+----------------------+
|
||||||
|
|
|
||||||
|
|
@ -14,7 +14,7 @@ The following are some of the boards that can be used with TF-M:
|
||||||
- ``mps3_an547_ns`` (qemu supported)
|
- ``mps3_an547_ns`` (qemu supported)
|
||||||
* - :zephyr:board:`bl5340_dvk`
|
* - :zephyr:board:`bl5340_dvk`
|
||||||
- ``bl5340_dvk/nrf5340/cpuapp/ns``
|
- ``bl5340_dvk/nrf5340/cpuapp/ns``
|
||||||
* - :ref:`lpcxpresso55s69`
|
* - :zephyr:board:`lpcxpresso55s69`
|
||||||
- ``lpcxpresso55s69_ns``
|
- ``lpcxpresso55s69_ns``
|
||||||
* - :ref:`nrf9160dk_nrf9160`
|
* - :ref:`nrf9160dk_nrf9160`
|
||||||
- ``nrf9160dk/nrf9160/ns``
|
- ``nrf9160dk/nrf9160/ns``
|
||||||
|
|
|
||||||
|
|
@ -34,7 +34,7 @@ configured using the ``sw0`` :ref:`devicetree <dt-guide>` alias, usually in the
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
||||||
Example building for :ref:`twr_ke18f`:
|
Example building for :zephyr:board:`twr_ke18f`:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/drivers/can/babbling
|
:zephyr-app: samples/drivers/can/babbling
|
||||||
|
|
|
||||||
|
|
@ -97,7 +97,7 @@ The sample can be built and executed for the
|
||||||
|
|
||||||
Building and Running for NXP TWR-KE18F
|
Building and Running for NXP TWR-KE18F
|
||||||
======================================
|
======================================
|
||||||
The sample can be built and executed for the :ref:`twr_ke18f` as
|
The sample can be built and executed for the :zephyr:board:`twr_ke18f` as
|
||||||
follows:
|
follows:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
@ -111,7 +111,7 @@ connector.
|
||||||
|
|
||||||
Building and Running for NXP FRDM-K64F
|
Building and Running for NXP FRDM-K64F
|
||||||
======================================
|
======================================
|
||||||
The sample can be built and executed for the :ref:`frdm_k64f` as
|
The sample can be built and executed for the :zephyr:board:`frdm_k64f` as
|
||||||
follows:
|
follows:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
@ -211,7 +211,7 @@ also can run for the Longan Nano Lite as follows:
|
||||||
|
|
||||||
Building and Running for NXP LPCXpresso55S36
|
Building and Running for NXP LPCXpresso55S36
|
||||||
============================================
|
============================================
|
||||||
The sample can be built and executed for the :ref:`lpcxpresso55s36` as
|
The sample can be built and executed for the :zephyr:board:`lpcxpresso55s36` as
|
||||||
follows:
|
follows:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
|
||||||
|
|
@ -15,7 +15,7 @@ Requirements
|
||||||
|
|
||||||
This sample requires an I2C peripheral which is capable of acting as a target.
|
This sample requires an I2C peripheral which is capable of acting as a target.
|
||||||
|
|
||||||
This sample has been tested on :ref:`lpcxpresso55s69`.
|
This sample has been tested on :zephyr:board:`lpcxpresso55s69`.
|
||||||
|
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
|
||||||
|
|
@ -15,7 +15,7 @@ Requirements
|
||||||
|
|
||||||
This sample requires an I2C peripheral which is capable of acting as a target.
|
This sample requires an I2C peripheral which is capable of acting as a target.
|
||||||
|
|
||||||
This sample has been tested on :ref:`lpcxpresso55s69`.
|
This sample has been tested on :zephyr:board:`lpcxpresso55s69`.
|
||||||
|
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
|
||||||
|
|
@ -20,7 +20,7 @@ Requirements
|
||||||
The I2S device to be used by the sample is specified by defining
|
The I2S device to be used by the sample is specified by defining
|
||||||
a devicetree alias named ``i2s_tx``
|
a devicetree alias named ``i2s_tx``
|
||||||
|
|
||||||
This sample has been tested on :ref:`mimxrt1060_evk` (mimxrt1060_evkb)
|
This sample has been tested on :zephyr:board:`mimxrt1060_evk` (mimxrt1060_evkb)
|
||||||
|
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
|
||||||
|
|
@ -12,14 +12,14 @@ sample application uses a mailbox to send messages from one
|
||||||
processor core to the other.
|
processor core to the other.
|
||||||
|
|
||||||
This sample applies to the following boards:
|
This sample applies to the following boards:
|
||||||
- :ref:`lpcxpresso54114`, two core processors (Cortex-M4F and Cortex-M0+)
|
- :zephyr:board:`lpcxpresso54114`, two core processors (Cortex-M4F and Cortex-M0+)
|
||||||
- :ref:`lpcxpresso55s69`, two core processors (dual Cortex-M33)
|
- :zephyr:board:`lpcxpresso55s69`, two core processors (dual Cortex-M33)
|
||||||
|
|
||||||
Requirements
|
Requirements
|
||||||
************
|
************
|
||||||
|
|
||||||
- :ref:`lpcxpresso54114` board
|
- :zephyr:board:`lpcxpresso54114` board
|
||||||
- :ref:`lpcxpresso55s69` board
|
- :zephyr:board:`lpcxpresso55s69` board
|
||||||
|
|
||||||
Building the application for lpcxpresso54114/lpc54114/m4
|
Building the application for lpcxpresso54114/lpc54114/m4
|
||||||
********************************************************
|
********************************************************
|
||||||
|
|
|
||||||
|
|
@ -33,7 +33,7 @@ This sample can be built and executed when the devicetree has an I2C device node
|
||||||
with compatible :dtcompatible:`issi,is31fl3216a` enabled, along with the relevant
|
with compatible :dtcompatible:`issi,is31fl3216a` enabled, along with the relevant
|
||||||
bus controller node also being enabled.
|
bus controller node also being enabled.
|
||||||
|
|
||||||
As an example this sample provides a DTS overlay for the :ref:`lpcxpresso55s28`
|
As an example this sample provides a DTS overlay for the :zephyr:board:`lpcxpresso55s28`
|
||||||
board (:file:`boards/lpcxpresso55s28.overlay`). It assumes that a I2C
|
board (:file:`boards/lpcxpresso55s28.overlay`). It assumes that a I2C
|
||||||
_is31fl3216a LED driver (with 16 LEDs wired) is connected to the I2C bus at
|
_is31fl3216a LED driver (with 16 LEDs wired) is connected to the I2C bus at
|
||||||
address 0x74.
|
address 0x74.
|
||||||
|
|
|
||||||
|
|
@ -31,7 +31,7 @@ Building and Running
|
||||||
This sample can be run on any board with an IS31FL3733 LED driver connected via
|
This sample can be run on any board with an IS31FL3733 LED driver connected via
|
||||||
I2C, and a node with the :dtcompatible:`issi,is31fl3733` compatible present in its devicetree.
|
I2C, and a node with the :dtcompatible:`issi,is31fl3733` compatible present in its devicetree.
|
||||||
|
|
||||||
This sample provides a DTS overlay for the :ref:`frdm_k22f` board
|
This sample provides a DTS overlay for the :zephyr:board:`frdm_k22f` board
|
||||||
(:file:`boards/frdm_k22f.overlay`). It assumes that the IS31FL3733 LED
|
(:file:`boards/frdm_k22f.overlay`). It assumes that the IS31FL3733 LED
|
||||||
controller is connected to I2C0, at address 0x50. The SDB GPIO should be
|
controller is connected to I2C0, at address 0x50. The SDB GPIO should be
|
||||||
connected to PTC2 (A3 on the arduino header)
|
connected to PTC2 (A3 on the arduino header)
|
||||||
|
|
|
||||||
|
|
@ -35,7 +35,7 @@ This sample can be built and executed on boards with an I2C LP5009, LP5012,
|
||||||
LP5018, LP5024, LP5030 or LP5036 LED driver connected. A node matching the
|
LP5018, LP5024, LP5030 or LP5036 LED driver connected. A node matching the
|
||||||
the device type binding should be defined in the board DTS files.
|
the device type binding should be defined in the board DTS files.
|
||||||
|
|
||||||
As an example this sample provides a DTS overlay for the :ref:`lpcxpresso11u68`
|
As an example this sample provides a DTS overlay for the :zephyr:board:`lpcxpresso11u68`
|
||||||
board (:file:`boards/lpcxpresso11u68.overlay`). It assumes that a I2C LP5030
|
board (:file:`boards/lpcxpresso11u68.overlay`). It assumes that a I2C LP5030
|
||||||
LED driver (with 10 LEDs wired) is connected to the I2C0 bus at address 0x30.
|
LED driver (with 10 LEDs wired) is connected to the I2C0 bus at address 0x30.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -18,10 +18,10 @@ Supported camera modules on some i.MX RT boards can be found below.
|
||||||
|
|
||||||
- `Camera iMXRT`_
|
- `Camera iMXRT`_
|
||||||
|
|
||||||
- :ref:`mimxrt1064_evk`
|
- :zephyr:board:`mimxrt1064_evk`
|
||||||
- `MT9M114 camera module`_
|
- `MT9M114 camera module`_
|
||||||
|
|
||||||
- :ref:`mimxrt1170_evk`
|
- :zephyr:board:`mimxrt1170_evk`
|
||||||
- `OV5640 camera module`_
|
- `OV5640 camera module`_
|
||||||
|
|
||||||
Also :ref:`arduino_nicla_vision_board` can be used in this sample as capture device, in that case
|
Also :ref:`arduino_nicla_vision_board` can be used in this sample as capture device, in that case
|
||||||
|
|
@ -30,11 +30,11 @@ The user can transfer the captured frames through on board USB.
|
||||||
Wiring
|
Wiring
|
||||||
******
|
******
|
||||||
|
|
||||||
On :ref:`mimxrt1064_evk`, the MT9M114 camera module should be plugged in the
|
On :zephyr:board:`mimxrt1064_evk`, the MT9M114 camera module should be plugged in the
|
||||||
J35 camera connector. A USB cable should be connected from a host to the micro
|
J35 camera connector. A USB cable should be connected from a host to the micro
|
||||||
USB debug connector (J41) in order to get console output via the freelink interface.
|
USB debug connector (J41) in order to get console output via the freelink interface.
|
||||||
|
|
||||||
On :ref:`mimxrt1170_evk`, the OV5640 camera module should be plugged into the
|
On :zephyr:board:`mimxrt1170_evk`, the OV5640 camera module should be plugged into the
|
||||||
J2 camera connector. A USB cable should be connected from a host to the micro
|
J2 camera connector. A USB cable should be connected from a host to the micro
|
||||||
USB debug connector (J11) in order to get console output via the daplink interface.
|
USB debug connector (J11) in order to get console output via the daplink interface.
|
||||||
|
|
||||||
|
|
@ -43,7 +43,7 @@ For :ref:`arduino_nicla_vision_board` there is no extra wiring required.
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
||||||
For :ref:`mimxrt1064_evk`, build this sample application with the following commands:
|
For :zephyr:board:`mimxrt1064_evk`, build this sample application with the following commands:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/drivers/video/capture
|
:zephyr-app: samples/drivers/video/capture
|
||||||
|
|
@ -52,7 +52,7 @@ For :ref:`mimxrt1064_evk`, build this sample application with the following comm
|
||||||
:goals: build
|
:goals: build
|
||||||
:compact:
|
:compact:
|
||||||
|
|
||||||
For :ref:`mimxrt1170_evk`, build this sample application with the following commands:
|
For :zephyr:board:`mimxrt1170_evk`, build this sample application with the following commands:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/drivers/video/capture
|
:zephyr-app: samples/drivers/video/capture
|
||||||
|
|
|
||||||
|
|
@ -15,13 +15,13 @@ Requirements
|
||||||
|
|
||||||
This samples requires a video capture device and network support.
|
This samples requires a video capture device and network support.
|
||||||
|
|
||||||
- :ref:`mimxrt1064_evk`
|
- :zephyr:board:`mimxrt1064_evk`
|
||||||
- `MT9M114 camera module`_
|
- `MT9M114 camera module`_
|
||||||
|
|
||||||
Wiring
|
Wiring
|
||||||
******
|
******
|
||||||
|
|
||||||
On :ref:`mimxrt1064_evk`, The MT9M114 camera module should be plugged in the
|
On :zephyr:board:`mimxrt1064_evk`, The MT9M114 camera module should be plugged in the
|
||||||
J35 camera connector. A USB cable should be connected from a host to the micro
|
J35 camera connector. A USB cable should be connected from a host to the micro
|
||||||
USB debug connector (J41) in order to get console output via the freelink
|
USB debug connector (J41) in order to get console output via the freelink
|
||||||
interface. Ethernet cable must be connected to RJ45 connector.
|
interface. Ethernet cable must be connected to RJ45 connector.
|
||||||
|
|
@ -29,7 +29,7 @@ interface. Ethernet cable must be connected to RJ45 connector.
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
||||||
For :ref:`mimxrt1064_evk`, the sample can be built with the following command.
|
For :zephyr:board:`mimxrt1064_evk`, the sample can be built with the following command.
|
||||||
If a mt9m114 camera shield is missing, video software generator will be used instead.
|
If a mt9m114 camera shield is missing, video software generator will be used instead.
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
|
||||||
|
|
@ -35,7 +35,7 @@ First, ensure the optional CANopenNode module is enabled and available:
|
||||||
|
|
||||||
Building and Running for TWR-KE18F
|
Building and Running for TWR-KE18F
|
||||||
==================================
|
==================================
|
||||||
The :ref:`twr_ke18f` board is equipped with an onboard CAN
|
The :zephyr:board:`twr_ke18f` board is equipped with an onboard CAN
|
||||||
transceiver. This board supports CANopen LED indicators (red and green
|
transceiver. This board supports CANopen LED indicators (red and green
|
||||||
LEDs). The sample can be built and executed for the TWR-KE18F as
|
LEDs). The sample can be built and executed for the TWR-KE18F as
|
||||||
follows:
|
follows:
|
||||||
|
|
@ -51,7 +51,7 @@ counter object at index ``0x2102`` in the object dictionary.
|
||||||
|
|
||||||
Building and Running for FRDM-K64F
|
Building and Running for FRDM-K64F
|
||||||
==================================
|
==================================
|
||||||
The :ref:`frdm_k64f` board does not come with an onboard CAN
|
The :zephyr:board:`frdm_k64f` board does not come with an onboard CAN
|
||||||
transceiver. In order to use the CAN bus on the FRDM-K64F board, an
|
transceiver. In order to use the CAN bus on the FRDM-K64F board, an
|
||||||
external CAN bus transceiver must be connected to ``PTB18``
|
external CAN bus transceiver must be connected to ``PTB18``
|
||||||
(``CAN0_TX``) and ``PTB19`` (``CAN0_RX``). This board supports CANopen
|
(``CAN0_TX``) and ``PTB19`` (``CAN0_RX``). This board supports CANopen
|
||||||
|
|
|
||||||
|
|
@ -31,7 +31,7 @@ Note that other input devices types are not demonstrated in these demos, namely
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
||||||
Example building for :ref:`mimxrt1060_evk`:
|
Example building for :zephyr:board:`mimxrt1060_evk`:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/modules/lvgl/demos
|
:zephyr-app: samples/modules/lvgl/demos
|
||||||
|
|
|
||||||
|
|
@ -44,7 +44,7 @@ Ethernet
|
||||||
|
|
||||||
You can use this application on a supported board with ethernet port. There
|
You can use this application on a supported board with ethernet port. There
|
||||||
are many like :ref:`sam4e_xpro`, :ref:`sam_v71_xplained_ultra`,
|
are many like :ref:`sam4e_xpro`, :ref:`sam_v71_xplained_ultra`,
|
||||||
:ref:`frdm_k64f`, :ref:`nucleo_f767zi_board` etc. Pick one and just build
|
:zephyr:board:`frdm_k64f`, :ref:`nucleo_f767zi_board` etc. Pick one and just build
|
||||||
tagoio-http-client sample application with minimal configuration:
|
tagoio-http-client sample application with minimal configuration:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
|
||||||
|
|
@ -103,10 +103,10 @@ FRDM_K64F
|
||||||
=========
|
=========
|
||||||
|
|
||||||
These are instructions for how to use this sample application running on
|
These are instructions for how to use this sample application running on
|
||||||
:ref:`frdm_k64f` board to negotiate IP address from DHCPv4 server (kea) running
|
:zephyr:board:`frdm_k64f` board to negotiate IP address from DHCPv4 server (kea) running
|
||||||
on Linux host.
|
on Linux host.
|
||||||
|
|
||||||
Connect ethernet cable from :ref:`Freedom-K64F board <frdm_k64f>` to Linux host
|
Connect ethernet cable from :zephyr:board:`Freedom-K64F board <frdm_k64f>` to Linux host
|
||||||
machine and check for new interfaces:
|
machine and check for new interfaces:
|
||||||
|
|
||||||
.. code-block:: console
|
.. code-block:: console
|
||||||
|
|
|
||||||
|
|
@ -41,7 +41,7 @@ Network Configuration
|
||||||
|
|
||||||
Open the project configuration file for your platform, for example:
|
Open the project configuration file for your platform, for example:
|
||||||
:file:`prj_frdm_k64f.conf` is the configuration file for the
|
:file:`prj_frdm_k64f.conf` is the configuration file for the
|
||||||
:ref:`frdm_k64f` board.
|
:zephyr:board:`frdm_k64f` board.
|
||||||
|
|
||||||
In this sample application, both static or DHCPv4 IP addresses are supported.
|
In this sample application, both static or DHCPv4 IP addresses are supported.
|
||||||
Static IP addresses are specified in the project configuration file,
|
Static IP addresses are specified in the project configuration file,
|
||||||
|
|
@ -142,7 +142,7 @@ Open a terminal window and type:
|
||||||
:goals: build flash
|
:goals: build flash
|
||||||
:compact:
|
:compact:
|
||||||
|
|
||||||
See :ref:`Freedom-K64F board documentation <frdm_k64f>` for more information
|
See :zephyr:board:`Freedom-K64F board documentation <frdm_k64f>` for more information
|
||||||
about this board.
|
about this board.
|
||||||
|
|
||||||
Open a terminal window and type:
|
Open a terminal window and type:
|
||||||
|
|
|
||||||
|
|
@ -21,10 +21,10 @@ Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
||||||
These are instructions for how to use this sample application running
|
These are instructions for how to use this sample application running
|
||||||
on a :ref:`frdm_k64f` board to configure a link local IPv4 address and
|
on a :zephyr:board:`frdm_k64f` board to configure a link local IPv4 address and
|
||||||
connect to a Linux host.
|
connect to a Linux host.
|
||||||
|
|
||||||
Connect ethernet cable from a :ref:`Freedom-K64F board <frdm_k64f>` to a Linux
|
Connect ethernet cable from a :zephyr:board:`Freedom-K64F board <frdm_k64f>` to a Linux
|
||||||
host machine and check for new interfaces.
|
host machine and check for new interfaces.
|
||||||
|
|
||||||
Running Avahi client in Linux Host
|
Running Avahi client in Linux Host
|
||||||
|
|
|
||||||
|
|
@ -66,14 +66,14 @@ Freedom-K64F Board
|
||||||
===================
|
===================
|
||||||
|
|
||||||
These are instructions for how to use this sample application running on a
|
These are instructions for how to use this sample application running on a
|
||||||
Freedom-K64F board. Unlike running it on QEMU, :ref:`Freedom-K64F board
|
Freedom-K64F board. Unlike running it on QEMU, :zephyr:board:`Freedom-K64F board
|
||||||
<frdm_k64f>` network configuration for IPv4 will rely on DHCPv4. You cad modify
|
<frdm_k64f>` network configuration for IPv4 will rely on DHCPv4. You cad modify
|
||||||
the :file:`prj_frdm_k64f.conf` to set static IPv4 addresses if it is really needed.
|
the :file:`prj_frdm_k64f.conf` to set static IPv4 addresses if it is really needed.
|
||||||
|
|
||||||
For detailed instructions about building, flashing and using the serial console
|
For detailed instructions about building, flashing and using the serial console
|
||||||
logs, follow the :ref:`Freedom-K64F board <frdm_k64f>` documentation section.
|
logs, follow the :zephyr:board:`Freedom-K64F board <frdm_k64f>` documentation section.
|
||||||
|
|
||||||
Connect ethernet cable from :ref:`Freedom-K64F <frdm_k64f>` board to a
|
Connect ethernet cable from :zephyr:board:`Freedom-K64F <frdm_k64f>` board to a
|
||||||
local network providing IPv4 address configuration via DHCPv4. Creating your own
|
local network providing IPv4 address configuration via DHCPv4. Creating your own
|
||||||
DHCP server on a local network is not in the scope of this README.
|
DHCP server on a local network is not in the scope of this README.
|
||||||
|
|
||||||
|
|
@ -85,7 +85,7 @@ Build Zephyr samples/net/telnet application:
|
||||||
:goals: build
|
:goals: build
|
||||||
:compact:
|
:compact:
|
||||||
|
|
||||||
Flash the resulting Zephyr binary following the :ref:`Freedom-K64F <frdm_k64f>`
|
Flash the resulting Zephyr binary following the :zephyr:board:`Freedom-K64F <frdm_k64f>`
|
||||||
board documentation noted above.
|
board documentation noted above.
|
||||||
|
|
||||||
From your host computer, open a serial console to your board:
|
From your host computer, open a serial console to your board:
|
||||||
|
|
@ -94,7 +94,7 @@ From your host computer, open a serial console to your board:
|
||||||
|
|
||||||
$ sudo screen /dev/ttyACM0 115200
|
$ sudo screen /dev/ttyACM0 115200
|
||||||
|
|
||||||
Plug the Ethernet cable to the :ref:`Freedom-K64F <frdm_k64f>` board.
|
Plug the Ethernet cable to the :zephyr:board:`Freedom-K64F <frdm_k64f>` board.
|
||||||
Reset the board, you should see first on the console:
|
Reset the board, you should see first on the console:
|
||||||
|
|
||||||
.. code-block:: console
|
.. code-block:: console
|
||||||
|
|
|
||||||
|
|
@ -15,9 +15,9 @@ Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
||||||
This project outputs sensor data to the console. FXOS8700
|
This project outputs sensor data to the console. FXOS8700
|
||||||
sensor is present on the :ref:`frdm_k64f`, :ref:`frdm_k22f`,
|
sensor is present on the :zephyr:board:`frdm_k64f`, :zephyr:board:`frdm_k22f`,
|
||||||
:ref:`frdm_kw41z`, :ref:`hexiwear`, and :ref:`twr_ke18f` boards.
|
:zephyr:board:`frdm_kw41z`, :ref:`hexiwear`, and :zephyr:board:`twr_ke18f` boards.
|
||||||
Accelerometer only devices are present on the :ref:`frdm_kl25z`,
|
Accelerometer only devices are present on the :zephyr:board:`frdm_kl25z`,
|
||||||
:zephyr:board:`bbc_microbit`, and :ref:`reel_board` boards. It does not work on
|
:zephyr:board:`bbc_microbit`, and :ref:`reel_board` boards. It does not work on
|
||||||
QEMU.
|
QEMU.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -15,7 +15,7 @@ Requirements
|
||||||
|
|
||||||
This sample uses the LPS22HH sensor controlled using the I3C interface.
|
This sample uses the LPS22HH sensor controlled using the I3C interface.
|
||||||
It has been tested using the LPS22HH on the evaluation board
|
It has been tested using the LPS22HH on the evaluation board
|
||||||
STEVALMKI192-V1 connected to the I3C header on :ref:`mimxrt685_evk`.
|
STEVALMKI192-V1 connected to the I3C header on :zephyr:board:`mimxrt685_evk`.
|
||||||
|
|
||||||
References
|
References
|
||||||
**********
|
**********
|
||||||
|
|
@ -55,7 +55,7 @@ Board Preparations
|
||||||
mimxrt685_evk
|
mimxrt685_evk
|
||||||
------------------
|
------------------
|
||||||
|
|
||||||
On the board :ref:`mimxrt685_evk`, the I3C pins are exposed on the J18
|
On the board :zephyr:board:`mimxrt685_evk`, the I3C pins are exposed on the J18
|
||||||
header, where:
|
header, where:
|
||||||
|
|
||||||
* SCL is on pin 1
|
* SCL is on pin 1
|
||||||
|
|
|
||||||
|
|
@ -17,7 +17,7 @@ Requirements
|
||||||
This sample uses the LSM6DSO sensor controlled using the I2C interface
|
This sample uses the LSM6DSO sensor controlled using the I2C interface
|
||||||
exposed by the I3C controller. It has been tested using the LSM6DSO on
|
exposed by the I3C controller. It has been tested using the LSM6DSO on
|
||||||
the evaluation board STEVAL-MKI196V1 connected to the I3C header
|
the evaluation board STEVAL-MKI196V1 connected to the I3C header
|
||||||
on :ref:`mimxrt685_evk`.
|
on :zephyr:board:`mimxrt685_evk`.
|
||||||
|
|
||||||
References
|
References
|
||||||
**********
|
**********
|
||||||
|
|
@ -46,7 +46,7 @@ Board Preparations
|
||||||
mimxrt685_evk
|
mimxrt685_evk
|
||||||
------------------
|
------------------
|
||||||
|
|
||||||
On the board :ref:`mimxrt685_evk`, the I3C pins are exposed on the J18
|
On the board :zephyr:board:`mimxrt685_evk`, the I3C pins are exposed on the J18
|
||||||
header, where:
|
header, where:
|
||||||
|
|
||||||
* SCL is on pin 1
|
* SCL is on pin 1
|
||||||
|
|
|
||||||
|
|
@ -8,15 +8,15 @@ Overview
|
||||||
********
|
********
|
||||||
|
|
||||||
This sample show how to use the NXP MCUX Analog Comparator (ACMP) driver. The
|
This sample show how to use the NXP MCUX Analog Comparator (ACMP) driver. The
|
||||||
sample supports the :ref:`twr_ke18f`, :ref:`mimxrt1170_evk`, :ref:`frdm_ke17z`
|
sample supports the :zephyr:board:`twr_ke18f`, :zephyr:board:`mimxrt1170_evk`, :zephyr:board:`frdm_ke17z`
|
||||||
, :ref:`frdm_ke17z512` and :ref:`mimxrt1180_evk`.
|
, :zephyr:board:`frdm_ke17z512` and :zephyr:board:`mimxrt1180_evk`.
|
||||||
|
|
||||||
The input voltage for the negative input of the analog comparator is
|
The input voltage for the negative input of the analog comparator is
|
||||||
provided by the ACMP Digital-to-Analog Converter (DAC). The input voltage for
|
provided by the ACMP Digital-to-Analog Converter (DAC). The input voltage for
|
||||||
the positive input can be adjusted by turning the on-board potentiometer for
|
the positive input can be adjusted by turning the on-board potentiometer for
|
||||||
:ref:`twr_ke18f` board, for :ref:`mimxrt1170_evk` the voltage signal is
|
:zephyr:board:`twr_ke18f` board, for :zephyr:board:`mimxrt1170_evk` the voltage signal is
|
||||||
captured on J25-13, the :ref:`frdm_ke17z` and :ref:`frdm_ke17z512` boards are
|
captured on J25-13, the :zephyr:board:`frdm_ke17z` and :zephyr:board:`frdm_ke17z512` boards are
|
||||||
captured in J2-3, the :ref:`mimxrt1180_evk` board are captured in J45-13, need
|
captured in J2-3, the :zephyr:board:`mimxrt1180_evk` board are captured in J45-13, need
|
||||||
change the external voltage signal to check the output.
|
change the external voltage signal to check the output.
|
||||||
|
|
||||||
The output value of the analog comparator is reported on the console.
|
The output value of the analog comparator is reported on the console.
|
||||||
|
|
@ -26,7 +26,7 @@ Building and Running
|
||||||
|
|
||||||
Building and Running for TWR-KE18F
|
Building and Running for TWR-KE18F
|
||||||
==================================
|
==================================
|
||||||
Build the application for the :ref:`twr_ke18f` board, and adjust the
|
Build the application for the :zephyr:board:`twr_ke18f` board, and adjust the
|
||||||
ACMP input voltage by turning the on-board potentiometer.
|
ACMP input voltage by turning the on-board potentiometer.
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
|
||||||
|
|
@ -27,7 +27,7 @@ Building and Running
|
||||||
|
|
||||||
Building and Running for NXP FRDM-MCXN947
|
Building and Running for NXP FRDM-MCXN947
|
||||||
=========================================
|
=========================================
|
||||||
Build the application for the :ref:`frdm_mcxn947` board, and adjust the
|
Build the application for the :zephyr:board:`frdm_mcxn947` board, and adjust the
|
||||||
LPCMP positive input port voltage by changing the voltage input to J2-17.
|
LPCMP positive input port voltage by changing the voltage input to J2-17.
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
@ -38,7 +38,7 @@ LPCMP positive input port voltage by changing the voltage input to J2-17.
|
||||||
|
|
||||||
Building and Running for NXP FRDM-MCXN236
|
Building and Running for NXP FRDM-MCXN236
|
||||||
=========================================
|
=========================================
|
||||||
Build the application for the :ref:`frdm_mcxn236` board, and adjust the
|
Build the application for the :zephyr:board:`frdm_mcxn236` board, and adjust the
|
||||||
LPCMP positive input port voltage by changing the voltage input to J2-8.
|
LPCMP positive input port voltage by changing the voltage input to J2-8.
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
|
|
|
||||||
|
|
@ -18,7 +18,7 @@ devicetree overlay with such a node added.
|
||||||
Building and Running
|
Building and Running
|
||||||
********************
|
********************
|
||||||
|
|
||||||
To build and flash the sample for the :ref:`frdm_k64f`:
|
To build and flash the sample for the :zephyr:board:`frdm_k64f`:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/sensor/tmp112
|
:zephyr-app: samples/sensor/tmp112
|
||||||
|
|
|
||||||
|
|
@ -27,7 +27,7 @@ Building and Running
|
||||||
|
|
||||||
This sample runs with the LMP90100 EVB connected to any development
|
This sample runs with the LMP90100 EVB connected to any development
|
||||||
board with a matching Arduino connector. For this example, we use a
|
board with a matching Arduino connector. For this example, we use a
|
||||||
:ref:`frdm_k64f` board.
|
:zephyr:board:`frdm_k64f` board.
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/shields/lmp90100_evb/rtd
|
:zephyr-app: samples/shields/lmp90100_evb/rtd
|
||||||
|
|
|
||||||
|
|
@ -40,7 +40,7 @@ for corresponding connectors, for example:
|
||||||
|
|
||||||
- :ref:`adafruit_2_8_tft_touch_v2` and :ref:`nrf52840dk_nrf52840`
|
- :ref:`adafruit_2_8_tft_touch_v2` and :ref:`nrf52840dk_nrf52840`
|
||||||
- :ref:`buydisplay_2_8_tft_touch_arduino` and :ref:`nrf52840dk_nrf52840`
|
- :ref:`buydisplay_2_8_tft_touch_arduino` and :ref:`nrf52840dk_nrf52840`
|
||||||
- :ref:`ssd1306_128_shield` and :ref:`frdm_k64f`
|
- :ref:`ssd1306_128_shield` and :zephyr:board:`frdm_k64f`
|
||||||
- :ref:`seeed_xiao_round_display` and :zephyr:board:`xiao_ble`
|
- :ref:`seeed_xiao_round_display` and :zephyr:board:`xiao_ble`
|
||||||
|
|
||||||
or a board with an integrated display:
|
or a board with an integrated display:
|
||||||
|
|
@ -54,12 +54,12 @@ or a simulated display environment in a :ref:`native_sim <native_sim>` applicati
|
||||||
|
|
||||||
or
|
or
|
||||||
|
|
||||||
- :ref:`mimxrt1050_evk`
|
- :zephyr:board:`mimxrt1050_evk`
|
||||||
- `RK043FN02H-CT`_
|
- `RK043FN02H-CT`_
|
||||||
|
|
||||||
or
|
or
|
||||||
|
|
||||||
- :ref:`mimxrt1060_evk`
|
- :zephyr:board:`mimxrt1060_evk`
|
||||||
- `RK043FN02H-CT`_
|
- `RK043FN02H-CT`_
|
||||||
|
|
||||||
Building and Running
|
Building and Running
|
||||||
|
|
|
||||||
|
|
@ -26,7 +26,7 @@ Caveats
|
||||||
*******
|
*******
|
||||||
|
|
||||||
* The Zephyr port of hawkBit is configured to run on a
|
* The Zephyr port of hawkBit is configured to run on a
|
||||||
:ref:`Freedom-K64F <frdm_k64f>` MCU by default. The application should
|
:zephyr:board:`Freedom-K64F <frdm_k64f>` MCU by default. The application should
|
||||||
build and run for other platforms with support internet connection. Some
|
build and run for other platforms with support internet connection. Some
|
||||||
platforms need some modification. Overlay files would be needed to support
|
platforms need some modification. Overlay files would be needed to support
|
||||||
BLE 6lowpan, 802.15.4 or OpenThread configurations as well as the
|
BLE 6lowpan, 802.15.4 or OpenThread configurations as well as the
|
||||||
|
|
@ -78,7 +78,7 @@ the server URL, ``<your-ip-address>:8080``, and logging into the server using
|
||||||
Step 4: Build hawkBit
|
Step 4: Build hawkBit
|
||||||
=====================
|
=====================
|
||||||
|
|
||||||
hawkBit can be built for the :ref:`Freedom-K64F <frdm_k64f>` as follows:
|
hawkBit can be built for the :zephyr:board:`Freedom-K64F <frdm_k64f>` as follows:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/subsys/mgmt/hawkbit
|
:zephyr-app: samples/subsys/mgmt/hawkbit
|
||||||
|
|
@ -260,7 +260,7 @@ Step 9: Build hawkBit HTTPS
|
||||||
* Convert the server.pem file to self_sign.der and place the der file in
|
* Convert the server.pem file to self_sign.der and place the der file in
|
||||||
hawkbit/src directory
|
hawkbit/src directory
|
||||||
|
|
||||||
``hawkBit https`` can be built for the :ref:`Freedom-K64F <frdm_k64f>` as follows:
|
``hawkBit https`` can be built for the :zephyr:board:`Freedom-K64F <frdm_k64f>` as follows:
|
||||||
|
|
||||||
.. zephyr-app-commands::
|
.. zephyr-app-commands::
|
||||||
:zephyr-app: samples/subsys/mgmt/hawkbit
|
:zephyr-app: samples/subsys/mgmt/hawkbit
|
||||||
|
|
|
||||||
|
|
@ -30,7 +30,7 @@ Caveats
|
||||||
*******
|
*******
|
||||||
|
|
||||||
* The Zephyr port of ``UpdateHub`` was initially developed to run on a
|
* The Zephyr port of ``UpdateHub`` was initially developed to run on a
|
||||||
:ref:`Freedom-K64F <frdm_k64f>` kit using the ethernet connectivity. The
|
:zephyr:board:`Freedom-K64F <frdm_k64f>` kit using the ethernet connectivity. The
|
||||||
application should build and run for other platforms with same connectivity.
|
application should build and run for other platforms with same connectivity.
|
||||||
|
|
||||||
* The sample provides overlay files to enable other technologies like WIFI,
|
* The sample provides overlay files to enable other technologies like WIFI,
|
||||||
|
|
@ -453,7 +453,7 @@ The below list of hardware have been used by UpdateHub team.
|
||||||
:widths: 50, 50
|
:widths: 50, 50
|
||||||
:width: 800px
|
:width: 800px
|
||||||
|
|
||||||
:ref:`frdm_k64f`, "1, 2, 3, 4"
|
:zephyr:board:`frdm_k64f`, "1, 2, 3, 4"
|
||||||
:ref:`nrf52840dk_nrf52840`, "2, 3, 4, 5, 6"
|
:ref:`nrf52840dk_nrf52840`, "2, 3, 4, 5, 6"
|
||||||
:ref:`nucleo_f767zi_board`, "1, 2, 3, 4"
|
:ref:`nucleo_f767zi_board`, "1, 2, 3, 4"
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -110,7 +110,7 @@ Next, python-can needs to be configured for the ``can0`` interface. One option i
|
||||||
fd = True
|
fd = True
|
||||||
|
|
||||||
Once the SocketCAN interface has been brought up and configured the test suite can be launched using
|
Once the SocketCAN interface has been brought up and configured the test suite can be launched using
|
||||||
Twister. Below is an example for running on the :ref:`lpcxpresso55s36`:
|
Twister. Below is an example for running on the :zephyr:board:`lpcxpresso55s36`:
|
||||||
|
|
||||||
.. code-block:: shell
|
.. code-block:: shell
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue