1
Out of the Box2
Embedded Linux
The following section describes the steps to boot the i.MX 8M Plus PEVK.
Development kit contains:
Get started developing your application on the i.MX 8M Plus PEVK with the out-of-the-box video. For more information please visit the i.MX 8M Plus applications processor Documentation.
Figure 1. i.MX 8M Plus Power EVK front
Figure 2. i.MX 8M Plus Power EVK back
The i.MX 8M Plus PEVK is software compatible with the i.MX 8M Plus EVK, but contains additional logic to provide detailed run time power information via a PC-based SW tool.
Something went wrong! Please try again.
Connect the micro-B end of the supplied USB cable into Debug UART port
J23
. Connect the other end of the cable to a host computer.
Four UART connections will appear on the PC, the third port for A53
core and the fourth for M7
core system debugging.
If you are not sure about how to use a terminal application, try one of the following tutorials depending on the operating system of the host machine:
On the command prompt of the Linux host machine, run the following command to determine the port number:
$ ls /dev/ttyUSB*
The smaller number is for Arm® Cortex®-A53 core and the bigger number is for Arm® Cortex ®-M4 core.
Use the following commands to install and run the serial communication program (minicom
as an example):
$ sudo apt-get install minicom
$ sudo minicom /dev/ttyUSB* -s
Figure 3. Minicom Configuration
The FTDI USB-serial chip on i.MX 8M Plus enumerates four serial ports. Assume that the ports are
COM9
,COM10
,COM11
,COM12
, (then Use COM11
). One port is for the serial console communication from Arm® Cortex®-A53 core and the second port is for Arm® Cortex®-M7 core. The
serial-to-USB drivers are available at
http://www.ftdichip.com/Drivers/VCP.htm.
Note: To determine the port number of the i.MX board virtual COM port, open the Windows device manager and find USB serial Port in Ports (COM and LPT)
Is an open source terminal emulation application. This program displays the information sent from the NXP development platform’s virtual serial port.
COM
port number identified earlier) to 115200
baud rate, 8
data bits, no
parity and 1
stop bit. To do this, go to Setup → Serial Port and change the settings.
The FTDI USB-serial chip on i.MX 8M Plus enumerates two serial ports. Assume that the ports are
COM9
,COM10
,COM11
and COM12
. One port is for the serial console communication from Arm® Cortex®-A53 core and the second port is for Arm® Cortex®-M7 core. The serial-to-USB drivers are available
at
http://www.ftdichip.com/Drivers/VCP.htm.
Note: To determine the port number of the i.MX board virtual COM port, open the Windows device manager and find USB serial Port in Ports (COM and LPT)
PuTTY is a popular terminal-emulation application. This program displays the information sent from the NXP development platform’s virtual serial port.
COM
port number that you determined earlier. Also enter the baud rate, in this case
115200
.
COM
port, the terminal window opens. If the configuration is not correct, PuTTY alerts you.Something went wrong! Please try again.
To see the user interface provided with the image binary connect a monitor via the HDMI connector (J17
).
Something went wrong! Please try again.
Click here to see the Boot Switch Setup.
Something went wrong! Please try again.
Use BCU (Board Control Utilities) or PMT(Power Measurement Tool) to monitor real-time power consumption or export the data to Excel for analysis.
Take BCU as example:
Open terminal or command prompt/PowerShell on the PC, change directory to the location of BCU files and then use below command to monitor voltage/current/power for each rail:
For Linux:
$ sudo ./bcu monitor -hz=1 -board=imx8mpevkpwra1
For Windows:
.\bcu.exe monitor -hz=1 -board=imx8mpevkpwra1
A TUI for power monitor can be seen on the screen.
For more info about BCU and PMT, please refer to PEVK Power measurement User’s guide.
Something went wrong! Please try again.
Connect the power supply cable to the power connector (PORT0
).
Power the board by flipping the switch (SW3
).
The processor starts executing from the on-chip ROM code. With the default boot switch setup, the code reads the fuses to define the media where it is expected to have a bootable image. After it finds a bootable image, the U-Boot execution should begin automatically.
Information is printed in the serial console for the Corte ®-A53. If you do not stop the U-Boot process, it continues to boot the kernel.
Something went wrong! Please try again.
As the board boots up, you will see 4 penguins appear in the upper left-hand corner of the monitor, and then you will see the Linux terminal Icon on the top left and timer on right top corner. Congratulations, you are up and running.
Something went wrong! Please try again.
Connect the micro-B end of the supplied USB cable into Debug UART port
J23
. Connect the other end of the cable to a host computer.
Something went wrong! Please try again.
This section is applicable ONLY if attempting to load a Linux operating system on the board.
The i.MX Linux Board Support Package (BSP) is a collection of binary files, source code and support files that are used to boot an Embedded Linux image on a specific i.MX development platform.
Current releases of Linux binary demo files can be found on the i.MX Linux download page. Additional documentation is available in the i.MX Linux documentation bundle under the Linux sections of the i.MX Software and Development Tool.
Before the Linux OS kernel can boot on an i.MX board, the Linux kernel is loaded to a boot device (SD card, eMMC and so on) and the boot switches are set to boot that device.
There are various ways to download the Linux BSP image for different boards and boot devices.
For this getting started guide, only a few methods to transfer the Linux BSP image to an SD card are listed. Experienced Linux developers can explore other options.
The latest pre-built images for the i.MX 8M Plus PEVK are available on the Linux download page under the most current version on Linux.
The pre-built NXP Linux binary demo image provides a typical system and basic set of features for using and evaluating the processor. Without modifying the system, the users can evaluate hardware interfaces, test SoC features and run user space applications.
When more flexibility is desired, an SD card can be loaded with individual components (boot loader, kernel, dtb file and rootfs file) one-by-one or the *wic
image is loaded and the individual parts are overwritten with the specific components.
In addition to the connections from Out of box chapter, connect the PORT1
to the host machine using the proper USB cable.
Turn off the board. Consult Boot switch setup and configure the board to boot on SDP (Serial Download Protocol) mode.
Depending on the OS used in the host machine, the way to transfer the Linux BSP image onto an SD card can vary. Choose an option below for detailed instructions:
Something went wrong! Please try again.
Download the latest stable files from UUU GitHub page. An extensive tutorial for UUU can be found in https://github.com/NXPmicro/mfgtools/wiki.
uuu
libusb1
(via apt-get or any other package manager)The latest pre-built images for the i.MX 8M Plus PEVK are available on the Linux download page under the most current version on Linux.
The pre-built NXP Linux binary demo image provides a typical system and basic set of features for using and evaluating the processor. Without modifying the system, the users can evaluate hardware interfaces, test SoC features and run user space applications.
When more flexibility is desired, an SD card can be loaded with individual components (boot loader, kernel, dtb file and rootfs file) one-by-one or the .sdcard
image is loaded and the individual parts are overwritten with the specific components.
By default, this procedure flashes the image to the emmc flash. Check the UUU GitHub page for reference on how to flash the image to other devices.
Open a terminal application and change directory to the location where uuu
and the latest Linux distribution for i.MX 8M Plus PEVK are located. Add execution permission to the
uuu
file and execute it. Uuu
waits for the USB device to connect
$ chmod a+x uuu sudo ./uuu <release package>.zip
Turn on the board,
uuu
starts to copy the images to the board.
When it finishes, turn off the board and consult
to configure the board to boot from emmc.
Something went wrong! Please try again.
Download the latest stable files from UUU GitHub page. An extensive tutorial for UUU can be found in https://github.com/NXPmicro/mfgtools/wiki.
uuu.exe
By default, this procedure flashes the image to the emmc flash. Check the UUU GitHub page for reference on how to flash the image to other devices.
Open the command prompt application and navigate to the directory where the uuu.exe file and the Linux release for the i.MX 8M Plus PEVK are located.
uuu.exe <kernel_version>_images_<SOC>.zip
Turn on the board,
uuu
starts to copy the images to the board.
When it finishes, turn off the board and consult
to configure the board to boot from emmc.
On the command prompt of the Linux host machine, run the following command to determine the port number:
$ ls /dev/ttyUSB*
The smaller number is for Arm® Cortex®-A53 core and the bigger number is for Arm® Cortex ®-M4 core.
Use the following commands to install and run the serial communication program (minicom
as an example):
$ sudo apt-get install minicom
$ sudo minicom /dev/ttyUSB* -s
Figure 3. Minicom Configuration
The FTDI USB-serial chip on i.MX 8M Plus enumerates four serial ports. Assume that the ports are
COM9
,COM10
,COM11
,COM12
, (then Use COM11
). One port is for the serial console communication from Arm® Cortex®-A53 core and the second port is for Arm® Cortex®-M7 core. The
serial-to-USB drivers are available at
http://www.ftdichip.com/Drivers/VCP.htm.
Note: To determine the port number of the i.MX board virtual COM port, open the Windows device manager and find USB serial Port in Ports (COM and LPT)
Is an open source terminal emulation application. This program displays the information sent from the NXP development platform’s virtual serial port.
COM
port number identified earlier) to 115200
baud rate, 8
data bits, no
parity and 1
stop bit. To do this, go to Setup → Serial Port and change the settings.
The FTDI USB-serial chip on i.MX 8M Plus enumerates two serial ports. Assume that the ports are
COM9
,COM10
,COM11
and COM12
. One port is for the serial console communication from Arm® Cortex®-A53 core and the second port is for Arm® Cortex®-M7 core. The serial-to-USB drivers are available
at
http://www.ftdichip.com/Drivers/VCP.htm.
Note: To determine the port number of the i.MX board virtual COM port, open the Windows device manager and find USB serial Port in Ports (COM and LPT)
PuTTY is a popular terminal-emulation application. This program displays the information sent from the NXP development platform’s virtual serial port.
COM
port number that you determined earlier. Also enter the baud rate, in this case
115200
.
COM
port, the terminal window opens. If the configuration is not correct, PuTTY alerts you.The boot sequence is detailed in the i.MX 8M Plus Reference Manual. In short, the boot modes of the i.MX boards are controlled by the boot configuration switches.
The switches set the boot media (depending on board, i.e. SD card, eMMC, NAND), the serial download protocol mode (SDP) or the value set on eFuses.
The SDP is also the fallback for the boot media, in other words, when the switches are configured to boot from SD card but the SD card slot is empty, or the SD card binary content is not bootable, the boot sequence continues to the SDP boot.
Figure 4. Boot switch setup for i.MX 8M Plus PEVK
The following table lists the boot switch settings on the i.MX 8M Plus PEVK board. The same information can be found on i.MX 8M Plus Reference Manual and on silkscreen on the board near the switches.
Table 1. Boot modes available for i.MX 8M Plus PEVK
Boot Media |
SW1101
[D1-D4]
|
---|---|
Boot from Fuse | 0000 |
Serial Download | 0001 |
eMMC/SDHC3 | 0010 |
MicroSD/SDHC2 | 0011 |
NAND 256 Page | 0100 |
NAND 512 Page | 0101 |
QSPI 3B Read | 0110 |
ECSPI Flash | 1000 |
Infinite Loop | 1110 |
Note: Make sure the boot switch is configured to boot from emmc.
Something went wrong! Please try again.