boards: warp7: convert to HWMv2

Convert warp7 board to HWMv2. This board was originally ported
using the iMX7D SOC (despite the fact that board uses an iMX7S
SOC). For HWMv2, this board continues to use the IMX7D SOC port,
since only the M4 core is enabled.

Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com>
This commit is contained in:
Daniel DeGrasse
2024-02-29 19:55:58 +00:00
committed by Jamie
parent ae443d1e3c
commit 84484e6707
12 changed files with 29 additions and 22 deletions

View File

@@ -0,0 +1,10 @@
.. _boards-element-14:
Element 14
##########
.. toctree::
:maxdepth: 1
:glob:
**/*

View File

@@ -3,10 +3,7 @@
# Copyright (c) 2018, Diego Sueiro
# SPDX-License-Identifier: Apache-2.0
if BOARD_WARP7_M4
config BOARD
default "warp7_m4"
if BOARD_WARP7
config FXOS8700_DRDY_INT1
default y
@@ -23,4 +20,4 @@ config FLASH_BASE_ADDRESS
default 0
endif
endif # BOARD_WARP7_M4
endif # BOARD_WARP7

View File

@@ -1,9 +1,7 @@
# WaRP7 iMX7S M4 board
# Copyright (c) 2018, Diego Sueiro
# Copyright 2024 NXP
# SPDX-License-Identifier: Apache-2.0
config BOARD_WARP7_M4
bool "WaRP7 iMX7 Solo"
depends on SOC_SERIES_IMX7_M4
config BOARD_WARP7
select SOC_PART_NUMBER_MCIMX7S3DVK08SA
select SOC_MCIMX7D_M4 if BOARD_WARP7_MCIMX7D_M4

View File

@@ -0,0 +1,5 @@
board:
name: warp7
vendor: element14
socs:
- name: mcimx7d

View File

@@ -1,4 +1,4 @@
.. _warp7_m4:
.. _warp7:
WaRP7 - Next Generation IoT and Wearable Development Platform
#############################################################
@@ -12,7 +12,7 @@ Zephyr was ported to run on the M4 core. In a later release, it will also
communicate with the A7 core (running Linux) via RPmsg.
.. image:: warp7_m4.jpg
.. image:: warp7.jpg
:align: center
:alt: WaRP7-iMX7S
@@ -100,7 +100,7 @@ Cortex M4 Core:
+-----------+------------+-------------------------------------+
The default configuration can be found in the defconfig file:
``boards/arm/warp7_m4/warp7_m4_defconfig``
:zephyr_file:`boards/element14/warp7/warp7_mcimx7d_m4_defconfig`
Other hardware features are not currently supported by the port.
@@ -179,7 +179,7 @@ References
At compilation time you have to choose which RAM will be used. This
configuration is done in the file ``boards/arm/warp7_m4/warp7_m4.dts`` with
configuration is done in the file :zephyr_file:`boards/element14/warp7/warp7_mcimx7d_m4.dts` with
"zephyr,flash" (when CONFIG_XIP=y) and "zephyr,sram" properties. The available
configurations are:
@@ -298,7 +298,7 @@ Issue the following commands inside J-Link commander:
w4 0x00180004 00905020
w4 0x3039000C 0xAA
With these mechanisms, applications for the ``warp7_m4`` board
With these mechanisms, applications for the ``warp7`` board
configuration can be built and debugged in the usual way (see
:ref:`build_an_application` and :ref:`application_run` for more details).

View File

Before

Width:  |  Height:  |  Size: 83 KiB

After

Width:  |  Height:  |  Size: 83 KiB

View File

@@ -7,7 +7,7 @@
/dts-v1/;
#include <nxp/nxp_imx7d_m4.dtsi>
#include "warp7_m4-pinctrl.dtsi"
#include "warp7-pinctrl.dtsi"
#include <zephyr/dt-bindings/input/input-event-codes.h>
/ {

View File

@@ -4,7 +4,7 @@
# SPDX-License-Identifier: Apache-2.0
#
identifier: warp7_m4
identifier: warp7/mcimx7d/m4
name: WaRP7 IMX7S
type: mcu
arch: arm

View File

@@ -4,9 +4,6 @@
# SPDX-License-Identifier: Apache-2.0
#
CONFIG_SOC_SERIES_IMX7_M4=y
CONFIG_SOC_MCIMX7_M4=y
CONFIG_BOARD_WARP7_M4=y
CONFIG_UART_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y

View File

@@ -9,7 +9,7 @@ tests:
platform_allow:
- udoo_neo_full/mcimx6x/m4
- colibri_imx7d/mcimx7d/m4
- warp7_m4
- warp7/mcimx7d/m4
integration_platforms:
- udoo_neo_full/mcimx6x/m4
tags:

View File

@@ -11,7 +11,7 @@ tests:
platform_allow:
- frdm_k64f
- hexiwear/mk64f12
- warp7_m4
- warp7/mcimx7d/m4
- frdm_kw41z
- rv32m1_vega/openisa_rv32m1/ri5cy
- twr_ke18f