For easier recognition PHYTEC boards have been prefixed with the SoC name.
As the new hardware model includes the SoC and cpu, this prefixing is not
needed anymore. All PHYTEC eval boards have an individual and unique name
and can be found easily via this name.
Signed-off-by: Jonas Remmert <j.remmert@phytec.de>
It is recommended to disable peripherals used by the M4 core on the Linux host.
@ -111,7 +111,7 @@ The following components are tested and working correctly.
@@ -111,7 +111,7 @@ The following components are tested and working correctly.
UART:
-----
Zephyr is configured to use UART4 on the PhyBoard Polis by default to minimize
Zephyr is configured to use UART4 on the phyBOARD-Polis by default to minimize
problems with the A53-Core because UART4 is only accessible from the M4-Core.
@ -137,7 +137,7 @@ problems with the A53-Core because UART4 is only accessible from the M4-Core.
@@ -137,7 +137,7 @@ problems with the A53-Core because UART4 is only accessible from the M4-Core.
SPI:
----
ECSPI is disabled by default. On phyBOARDPolis, the SoC's ECSPI3 is not
ECSPI is disabled by default. On phyBOARD-Polis, the SoC's ECSPI3 is not
usable.
ECSPI1 is connected to the MCP2518 CAN controller with a chip select.
Another device can be connected via the expansion header (X8):
The following configurations are possible for the flash and sram chosen nodes
@ -308,7 +308,7 @@ on UART4.
@@ -308,7 +308,7 @@ on UART4.
Debugging
=========
The PhyBOARD Polis can be debugged using a JTAG Debugger.
The phyBOARD-Polis can be debugged using a JTAG Debugger.
The easiest way to do that is to use a SEGGER JLink Debugger and Phytec's
``PEB-EVAL-01`` Shield, which can be directly connected to the JLink.
You can find the JLink Software package here: `JLink Software`_
@ -391,7 +391,7 @@ For example: disabling ECSPI1 in Linux to use it on the M4-Core with Zephyr:
@@ -391,7 +391,7 @@ For example: disabling ECSPI1 in Linux to use it on the M4-Core with Zephyr: