L-1017e.A3 i.MX 8M Plus BSP Manual
1.
2.
3.
4.
Building the Firmware
The scripts to build the firmware are located in
<sdk-directory>/phytec-mcux-boards/phyboard-pollux/
<example_category>/<example>/armgcc
. There are scripts for each location the firmware is supposed to run, e.g.
$ ./build_release.sh
to build the firmware for the M7's TCM. The output will be placed under
release/ i
n the
armgcc
directory.
.bin
files
and can be run in U-Boot and
.elf
files within Linux.
Running M7 Core Examples
To receive debug messages start your favorite terminal software (e.g.
Minicom, Tio,
or
Tera Term
) on your host PC
and configure it for 115200 baud, 8 data bits, no parity, and 1 stop bit (8n1) with no handshake.
Once a micro-USB cable is connected to the USB-debug port on the phyBOARD-Pollux, two
ttyUSB
devices are
registered. One prints messages from A53-Core's debug UART and the other one from the M7-Core's debug UART.
Running Examples from U-Boot
To load firmware using the bootloader U-Boot, the
bootaux
command can be used:
Prepare an SD Card with our Yocto-BSP
Copy the generated .bin file to the SD Cards first partition
Stop the autoboot by pressing any key
Type the command depending on the type of firmware:
For firmware built to run in the M7's TCM:
u-boot=> fatload mmc
1
:
1
0x48000000
firmware.bin;cp.b
0x48000000
0x7e0000
20000
;
u-boot=> bootaux
0x7e0000
## Starting auxiliary core stack =
0x20020000
, pc =
0x000004CD
...
For firmware built to run in the DRAM:
u-boot=> fatload mmc
1
:
1
0x80000000
firmware.bin
u-boot=> dcache flush
u-boot=> bootaux
0x80000000
## Starting auxiliary core stack =
0x80400000
, pc =
0x80000539
...
The program's output should appear on the M7's debug UART.
Debugging Using J-Link
The Segger software can be obtained from
https://www.segger.com/downloads/jlink/
Segger software, accessing the i.MX 8M Plus' M7 core requires additional configuration files to be copied into the J-
Link software directory:
