Download
Share
Print this page
  1. Manuals
  2. Brands
  3. Phytec Manuals
  4. Single board computers
  5. i.MX 93
  6. Manual

Phytec i.MX 93 Manual

Bsp pd24.1.1
Hide thumbs

Advertisement

Quick Links

Download this manual
i.MX 93 BSP Manual PD24.1.1
PHYTEC Messtechnik GmbH
Oct 28, 2024

Advertisement

loading
Need help?

Need help?

Do you have a question about the i.MX 93 and is the answer not in the manual?

Questions and answers

Related Manuals for Phytec i.MX 93

Summary of Contents for Phytec i.MX 93

  • Page 1 93 BSP Manual PD24.1.1 PHYTEC Messtechnik GmbH Oct 28, 2024...

  • Page 3: Table Of Contents

    ..........PHYTEC i.MX 93 BSP Device Tree Concept .
  • Page 4 ..........8 i.MX 93 M33 Core Running M33 Core Examples .
  • Page 5 (BSP) and describes how to handle the interfaces for the phyBOARD-Segin i.MX 93 and phyBOARD- Nash i.MX 93 Kit. Furthermore, this document describes how to create BSP images from the source code. This is useful for those who need to change the default image and need a way to implement these changes in a simple and reproducible way.
  • Page 6 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d On top of these standard manuals and guides, PHYTEC will also provide Product Change Notifications, Ap- plication Notes, and Technical Notes. These will be done on a case-by-case basis. Most of the documentation can be found on the https://www.phytec.de/produkte/system-on-modules/phycore-imx-91-93/#downloads...

  • Page 7: Supported Hardware

    Article Number. Now it should show you the necessary Machine Name for your specific hardware. Console examples in this BSP manual only focus on phyBOARD-Segin i.MX 93. Similar commands can also be executed for/on phyBOARD-Nash i.MX 93 1.1 phyBOARD-Segin i.MX 93 Components...
  • Page 8 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Fig. 1: phyBOARD-Segin i.MX 93 Components (top) Supported Hardware...
  • Page 9 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Fig. 2: phyBOARD-Segin i.MX 93 Components (bottom) Fig. 3: phyBOARD-Nash i.MX 93 Components (top) Supported Hardware...
  • Page 10 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Fig. 4: phyBOARD-Nash i.MX 93 Components (bottom) Supported Hardware...

  • Page 11: Getting Started

    The phyBOARD-Segin i.MX 93 and phyBOARD-Nash i.MX 93 Kit is shipped with a pre-flashed SD card. It contains the phytec-qt6demo-image and can be used directly as a boot source. The eMMC is programmed with only a U-Boot by default. You can get all sources from the PHYTEC download server.
  • Page 12 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Selecting the wrong device may result in data loss and e.g. could erase your currently running system on your host PC! 2.2.1 Finding the Correct Device To create your bootable SD card, you must first find the correct device name of your SD card and possible partitions.
  • Page 13 2.2.4 Using After having unmounted all SD card’s partitions, you can create your bootable SD card. Some PHYTEC BSPs produce uncompressed images (with filename-extension *.wic), and some others pro- duce compressed images (with filename-extension *.wic.xz). To flash an uncompressed images (*.wic) use command below: host:~$ sudo dd if=phytec-qt6demo-image-phyboard-segin-imx93-2?(.rootfs).wic of=/dev/<your_...

  • Page 14: First Start-Up

    93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d 2.3 First Start-up • To boot from an SD card, the bootmode switch (S3) needs to be set to the following position: • Insert the SD card • Connect the targets debug console with your host.

  • Page 15: Building The Bsp

    Yocto Reference Manual (mickledore). 3.1 Basic Set-Up If you have never created a Phytec BSP with Yocto on your computer, you should take a closer look at the chapter BSP Workspace Installation in the Yocto Reference Manual (mickledore). 3.2 Get the BSP There are two ways to get the BSP sources.
  • Page 16 • Build your image: host:~/yocto/build$ bitbake phytec-qt6demo-image Note For the first build we suggest starting with our smaller non-graphical image phytec-headless-image to see if everything is working correctly. host:~/yocto/build$ bitbake phytec-headless-image The first compile process takes about 40 minutes on a modern Intel Core i7. All subsequent builds will use the filled caches and should take about 3 minutes.
  • Page 17 – phytec-qt6demo-image-phyboard-*-imx93-*.tar.gz: when bitbake-build was processed for phytec-qt6demo-image – phytec-headless-image-phyboard-*-imx93-*.tar.gz: when bitbake-build was processed for phytec-headless-image • phytec-*.wic.xz: Compressed bootable SD card image of bitbake-image that was built. Includes bootloader, DTBs, Kernel and Root file system. – phytec-qt6demo-image-phyboard-*-imx93-*.wic.xz: when bitbake-build was processed for phytec-qt6demo-image –...
  • Page 18 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Building the BSP...

  • Page 19: Installing The Os

    CHAPTER FOUR INSTALLING THE OS 4.1 Bootmode Switch (S3) Hardware revision baseboard: • phyBOARD-Segin-i.MX 93: 1472.5 • phyBOARD-Nash-i.MX 93: 1616.0 The phyBOARD-Segin/Nash i.MX 93 features a boot switch with four individually switchable ports to select the phyCORE-i.MX 93 default bootsource.
  • Page 20 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Fig. 1: eMMC Fig. 2: Internal Fuses Fig. 3: USB Serial Download Fig. 4: SD Card Installing the OS...

  • Page 21: Flash Emmc

    • The eMMC device can be recognized by the fact that it contains two boot partitions: (mmcblk0boot0; mmcblk0boot1) • Write the image to the phyCORE-i.MX 93 eMMC (/dev/mmcblk0 without partition) using partup: target:~$ partup install phytec-qt6demo-image-phyboard-segin-imx93-2.partup /dev/mmcblk0 Installing the OS...
  • Page 22 4.2.2 Flash eMMC from Network i.MX 93 boards have an Ethernet connector and can be updated over a network. Be sure to set up the development host correctly. The IP needs to be set to 192.168.3.10, the netmask to 255.255.255.0, and a TFTP server needs to be available.
  • Page 23 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Take an uncompressed image on the host and send it with ssh through the network to the eMMC of the target with a one-line command: target:~$ ssh <USER>@192.168.3.10 "dd if=<path_to_file>/phytec-qt6demo-image-phyboard-segin- imx93-2.wic" | dd of=/dev/mmcblk0 bs=1M conv=fsync status=progress →...
  • Page 24 • The eMMC device can be recognized by the fact that it contains two boot partitions: (mmcblk0boot0; mmcblk0boot1) • Write the image to the phyCORE-i.MX 93 eMMC (/dev/mmcblk0 without partition): target:~$ dd if=phytec-qt6demo-image-phyboard-segin-imx93-2.wic of=/dev/mmcblk0 bs=1M␣ conv=fsync status=progress →...

  • Page 25: Rauc

    The RAUC (Robust Auto-Update Controller) mechanism support has been added to meta-ampliphy. It controls the procedure of updating a device with new firmware. This includes updating the Linux kernel, Device Tree, and root filesystem. PHYTEC has written an online manual on how we have intergraded RAUC into our BSPs: L-1006e.A5 RAUC Update &...
  • Page 26 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Installing the OS...

  • Page 27: Development

    -R o+r /srv/tftp • You also need to configure a static IP address for the appropriate interface. The default IP address of the PHYTEC evaluation boards is 192.168.3.11. Setting a host address 192.168.3.10 with netmask 255.255.255.0 is a good choice.
  • Page 28 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Set TFTP_ADDRESS to the host address the server is listening to (set to 0.0.0.0:69 to listen to all local IPs) • Set TFTP_OPTIONS, the following command shows the available options: host:~$ man tftpd •...

  • Page 29: Booting The Kernel From A Network

    93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d (continued from previous page) Warning Be careful when creating subnets as this may interfere with the company network policy. To be on the safe side, use a different network and specify that via the configuration option.

  • Page 30: Working With Uuu-Tool

    93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d 5.2.2 Set the bootenv.txt for Netboot Create a bootenv.txt file in your tftp directory and write the following variables into it. bootfile=Image fdt_file=oftree nfsroot=/srv/nfs overlays=<overlayfilenames> <overlayfilenames> has to be replaced with the devicetree overlay filenames that you want to use. Separate the filenames by spaces.
  • Page 31 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d 5.3.2 Get Images Download imx-boot from server from your Yocto build directory build/deploy/images/phyboard-segin-imx93-2/. For flashing a wic image to eMMC, you will also need phytec-qt6demo-image-phyboard-segin-imx93-2.wic. 5.3.3 Prepare Target Set the bootmode switch (S3) to USB Serial Download.

  • Page 32: Standalone Build Preparation

    • Used Linux kernel repository: git://git.phytec.de/linux-imx • Our i.MX 93 kernel is based on the linux-imx kernel. To find out which u-boot and kernel tags to use for a specific board, have a look at your BSP source folder: meta-phytec/dynamic-layers/freescale-layer/recipes-kernel/linux/linux-imx_*.bb meta-phytec/recipes-bsp/u-boot/u-boot-imx_*.bb...

  • Page 33: U-Boot Standalone Build

    93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d 5.4.3 Install the SDK • Set correct permissions and install the SDK: host:~$ chmod +x phytec-ampliphy-vendor-wayland-glibc-x86_64-phytec-qt6demo-image-cortexa55- toolchain-4.2.3.sh → host:~$ ./phytec-ampliphy-vendor-wayland-glibc-x86_64-phytec-qt6demo-image-cortexa55- toolchain-4.2.3.sh → ============================================================================================================ Enter target directory for SDK (default: /opt/ampliphy-vendor-wayland/4.2.3): You are about to install the SDK to "/opt/ampliphy-vendor-wayland/4.2.3". Proceed [Y/n]? Y Extracting SDK...done...
  • Page 34 • Container image: mx93a1-ahab-container.img If you already built our BSP with Yocto, you can get these files from the directory mentioned here: Images Or you can download the files from the PHYTEC download server (https://download.phytec.de/Software/ Linux/BSP-Yocto-i.MX93/BSP-Yocto-NXP-i.MX93-PD24.1.1/images/ampliphy-vendor-wayland/ phyboard-segin-imx93-2/imx-boot-tools/). You can use the commands below to download all the...
  • Page 35 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d 5.5.3 Build the bootloader • Build u-boot: host:~/u-boot-imx$ make <defconfig> host:~/u-boot-imx$ make host:~/u-boot-imx$ Note command above replace with <defconfig> imx93-phyboard-segin_defconfig , depending on the board you are about to build for. imx93-phyboard-nash_defconfig Build final flash.bin with imx-mkimage...

  • Page 36: Kernel Standalone Build

    93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d E.g. flash SD card: host:~/imx-mkimage$ sudo dd if=./iMX9/flash.bin of=<sd-card> bs=1024 seek=32 conv=sync Note In the command above, replace with your sd-card device name. For more information on how <sd-card> to find the device name, see the section Finding the Correct Device in Getting Started.

  • Page 37: Format Sd-Card

    93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • For (re-)building only Devicetrees and -overlays, it is sufficient to run host:~/linux-imx$ make dtbs Note If you are facing the following build issue: scripts/dtc/yamltree.c:9:10: fatal error: yaml.h: No such file or directory Make sure you installed the package “libyaml-dev”...
  • Page 38 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Expand rootfs Warning Running gparted on host systems which are using resize2fs version 1.46.6 and older (e.g. Ubuntu 22.04) are not able to expand the ext4 partition created with Yocto Mickledore and newer. This is due to a new default option in resize2fs which causes a incompatibility.
  • Page 39 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Drag the slider as far as you like or enter the size manually. Development...
  • Page 40 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Confirm your entry by clicking on the “Change size” button. • To apply your changes, press the green tick. Development...
  • Page 41 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Now you can mount the root partition and copy e.g. the phytec-qt6demo-image-phyboard-segin-imx93- 2.wic image to it. Then unmount it again: host:~$ sudo cp phytec-qt6demo-image-phyboard-segin-imx93-2.wic /mnt/ ; sync host:~$ umount /mnt Create the Third Partition •...
  • Page 42 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Click “Add” • Confirm your changes by pressing the green tick. Development...
  • Page 43 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Now you can mount the new partition and copy e.g. phytec-qt6demo-image-phyboard-segin-imx93- 2.wic image to it. Then unmount it again: host:~$ sudo mount /dev/sde3 /mnt host:~$ sudo cp phytec-qt6demo-image-phyboard-segin-imx93-2.wic /mnt/ ; sync...
  • Page 44 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Development...

  • Page 45: Device Tree (Dt)

    • Module.dtsi - Module includes all devices mounted on the SoM, such as PMIC and RAM. • Board.dts - include the module dtsi file. Devices that come from the i.MX 93 SoC but are just routed down to the carrier board and used there are included in this dts.
  • Page 46 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d (continued from previous page) imx93-phycore-rpmsg.dtbo imx93-phycore-no-emmc.dtbo imx93-phycore-no-eth.dtbo Available overlays for phyboard-nash-imx93-1.conf are: imx93-phyboard-nash-peb-av-010.dtbo imx93-phycore-rpmsg.dtbo imx93-phycore-no-emmc.dtbo imx93-phycore-no-eth.dtbo The usage of overlays can be configured during runtime in Linux or U-Boot. Overlays are applied during the boot process in the bootloader after the boot command is called and before the kernel is loaded.
  • Page 47 MMC device or via TFTP. The main intention of this file is to store the ${overlays} variable. This makes it easy to pre-define the overlays in Yocto depending on the used machine. The content from the file is defined in the Yocto recipe bootenv found in meta-phytec: https://git.phytec.de/ meta-phytec/tree/recipes-bsp/bootenv?h=mickledore Other variables can be set in this file, too.
  • Page 48 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Device Tree (DT)

  • Page 49: Accessing Peripherals

    Device Tree Blob (DTB) (section device tree). Please read section PHYTEC i.MX 93 BSP Device Tree Concept to get an understanding of our i.MX 9 BSP device tree model. The following sections provide an overview of the supported hardware components and their operating system drivers on the i.MX 9 platform.

  • Page 50: Network

    The device tree representation for UART1 pinmuxing: https://git.phytec.de/linux-imx/tree/arch/arm64/ boot/dts/freescale/imx93-phyboard-segin.dts?h=v6.1.55_2.2.0-phy3#n262 7.2 Network phyBOARD-Segin/Nash i.MX 93 provides two ethernet interfaces. • On phyBOARD-Segin we have: – a 100 megabit Ethernet provided by phyCORE-i.MX93 – and 100 megabit Ethernet provided by phyBOARD. • On phyBOARD-Nash we have: –...

  • Page 51: Sd/Mmc Card

    192.168.3.11 netmask 255.255.255.0 up 7.3 SD/MMC Card The i.MX 93 supports a slot for Secure Digital Cards and MultiMedia Cards to be used as general-purpose block devices. These devices can be used in the same way as any other block device.

  • Page 52: Emmc Devices

    7.4 eMMC Devices PHYTEC modules like phyCORE-i.MX 93 is populated with an eMMC memory chip as the main storage. eMMC devices contain raw Multi-Level Cells (MLC) or Triple-Level Cells (TLC) combined with a memory controller that handles ECC and wear leveling. They are connected via an SD/MMC interface to the i.MX 93 and are represented as block devices in the Linux kernel like SD cards, flash drives, or hard disks.
  • Page 53 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d ============================================= Extended CSD rev 1.7 (MMC 5.0) ============================================= Card Supported Command sets [S_CMD_SET: 0x01] [...] 7.4.2 Enabling Background Operations (BKOPS) In contrast to raw NAND Flash, an eMMC device contains a Flash Transfer Layer (FTL) that handles the wear leveling, block management, and ECC of the raw MLC or TLC.
  • Page 54 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • To set the BKOPS_EN bit, execute: target:~$ mmc bkops_en manual /dev/mmcblk0 • To ensure that the new setting is taken over and the kernel triggers BKOPS by itself, shut down the...
  • Page 55 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d (continued from previous page) Dry-run only unless -y or -c is passed. Use -c if more partitioning settings are still to come. NOTE! This is a one-time programmable (unreversible) change. The second Reliable Write option is the configuration bit Reliable Write Request parameter (bit 31) in command CMD23.
  • Page 56 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Resize the filesystem to a new partition size: target:~$ resize2fs /dev/mmcblk0p2 resize2fs 1.46.1 (9-Feb-2021) Filesystem at /dev/mmcblk0p2 is mounted on /; on-line resizing required [ 131.609512] EXT4-fs (mmcblk0p2): resizing filesystem from 454136 to 7367680 blocks old_desc_blocks = 4, new_desc_blocks = 57 [ 131.970278] EXT4-fs (mmcblk0p2): resized filesystem to 7367680...
  • Page 57 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • Now, you can set enhanced attribute for the whole device, e.g. 3719168 KiB, by typing: target:~$ mmc enh_area 0 3719168 /dev/mmcblk0 You will get: Done setting ENH_USR area on /dev/mmcblk0 setting OTP PARTITION_SETTING_COMPLETED! Setting OTP PARTITION_SETTING_COMPLETED on /dev/mmcblk0 SUCCESS Device power cycle needed for settings to take effect.
  • Page 58 The partitions boot1 and boot2 can be used to host the bootloader and are more reliable. Which partition the i.MX 93 uses to load the bootloader is controlled by the boot configuration of the eMMC device. The partition rpmb is a small partition and can only be accessed via a trusted mechanism.
  • Page 59 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Offset User Area Offset Boot Partition eMMC Device Bootloader Filename i.MX 93 32 kiB 0 kiB /dev/mmcblk0 imx-boot After that set the boot partition from user space using the mmc tool: (for ‘boot0’) :...
  • Page 60 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d (continued from previous page) Command (m for help): p Disk /dev/mmcblk0: 7264 MB, 7616856064 bytes, 14876672 sectors 116224 cylinders, 4 heads, 32 sectors/track Units: sectors of 1 * 512 = 512 bytes...

  • Page 61: Gpios

    Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d 7.5 GPIOs The phyBOARD-Segin/Nash i.MX 93 doesn’t have a set of pins especially dedicated for user I/Os since all GPIOs are used by kernel device drivers or used for a specific purpose. The processor has organized its GPIOs into five banks of 32 GPIOs each (GPIO1 –...
  • Page 62 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d (continued from previous page) Set GPIO line values of a GPIO chip Options: -h, --help: display this message and exit -v, --version: display the version and exit -l, --active-low: set the line active state to low...

  • Page 63: Adc

    The i.MX 93 contains several Multimaster fast-mode I²C modules. PHYTEC boards provide plenty of different I²C devices connected to the I²C modules of the i.MX 93. This section describes the basic device usage and its DT representation of some I²C devices integrated into our phyBOARD-Segin/Nash i.MX 93.

  • Page 64: Eeprom

    7.9 EEPROM There are two different I2C EEPROM flashes populated on phyCORE-i.MX93 SoM and on the phyBOARD- Segin/Nash i.MX 93. For now only the one on the phyCORE-i.MX93 is enabled, and it is used for board detection. 7.9.1 I2C EEPROM on phyCORE-i.MX93 The I2C EEPROM on the phyCORE-i.MX93 SoM has its memory divided into two parts.

  • Page 65: Rtc

    The hardware introspection data is pre-written on the EEPROM data spaces. If you have accidentally deleted or overwritten the HW data, you could contact our support! DT representation, e.g. in phyCORE-i.MX 93 file can be found in our PHYTEC git: https://git.phytec.de/ linux-imx/tree/arch/arm64/boot/dts/freescale/imx93-phycore-som.dtsi?h=v6.1.55_2.2.0-phy3#n172...
  • Page 66 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d current date and time (set with the date command) to the RTC using the tool and reboot the target hwclock to check if the changes were applied to the RTC: target:~$ hwclock -w...

  • Page 67: Usb Host Controller

    The OTG port provides an additional pin for over-current protection, which is not used on the phyBOARD- Segin/Nash i.MX 93. Since it’s not used, the driver part is also disabled from within the device tree. In case this pin is used, activate this over-current in the device tree and set the correct polarity (active high/low) according to the device specification.

  • Page 68: Rs232/Rs485

    7.13 CAN FD The phyBOARD-Segin/Nash i.MX 93 has one flexCAN interface supporting CAN FD. They are supported by the Linux standard CAN framework which builds upon the Linux network layer. Using this framework, the CAN interfaces behave like an ordinary Linux network device, with some additional features special to CAN.
  • Page 69 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d • To get information on can0, such as bit rate and error counters, type: target:~$ ip -d -s link show can0 4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group␣...

  • Page 70: Audio On Phyboard-Segin

    7.14 Audio on phyBOARD-Segin On phyBOARD-Segin i.MX 93 the TI TLV320AIC3007 audio codec is used. It uses I2S for data transmission and I2C for codec control. The audio signals available are: • Stereo LINE IN, • Stereo LINE OUT, •...

  • Page 71: Audio On Phyboard-Nash

    7.15 Audio on phyBOARD-Nash Warning Due to HW bug Audio is broken on phyBOARD-Nash i.MX 93 PCB revision: 1616.0 To use audio with phyBOARD-Nash an additional adapter for the Audio/Video connector is needed. The PEB-AV-10 (1531.1 revision) can be bought separately to the Kit. PEB-AV-10 is populated with a TI TLV320AIC3007 audio codec.
  • Page 72 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d target:~$ aplay -L Or type for recording devices: target:~$ arecord -L 7.15.1 Alsamixer To inspect the capabilities of your soundcard, call: target:~$ alsamixer You should see a lot of options as the audio-IC has many features you can experiment with. It might be better to open alsamixer via ssh instead of the serial console, as the console graphical effects are better.
  • Page 73 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d [...] pcm.asymed { type asym playback.pcm "softvol_pebav10" capture.pcm "dsnoop" [...] 7.15.4 Pulseaudio Configuration For applications using Pulseaudio, check for available sinks: target:~$ pactl list short sinks To select the output device, type: target:~$ pactl set-default-sink <sink_number>...

  • Page 74: Video

    Overlay for said display is enabled in by default! BOOT/bootenv.txt The phyBOARD-Nash i.MX 93 needs additional adapter to support 10’’ LVDS display edt,etml1010g3dra with capacitive touchscreen. The PEB-AV-10 (1531.1 revision) can be bought separately to the Kit. Overlay...

  • Page 75: Power Management

    7.18.1 CPU Core Frequency Scaling The CPU in the i.MX 93 SoC is able to scale the clock frequency and the voltage. This is used to save power when the full performance of the CPU is not needed. Unlike i.MX8 M family the i.MX 93 doesn’t support Dynamic Voltage and Frequency Scaling (DVFS), but has the support of basic Voltage and Frequency Scaling (VFS).
  • Page 76 //docs.nxp.com/bundle/AN13917/page/topics/low_power_mode_use_cases.html 7.18.2 CPU Core Management The i.MX 93 SoC can have multiple processor cores on the die. The i.MX 93, for example, has 2 ARM Cores which can be turned on and off individually at runtime. • To see all available cores in the system, execute:...

  • Page 77: Thermal Management

    93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d cpu0/ cpu1/ cpufreq/ [...] Here the system has two processor cores. By default, all available cores in the system are enabled to get maximum performance. • To switch off a single-core, execute:...

  • Page 78: Watchdog

    7.20 Watchdog The PHYTEC i.MX 93 modules include a hardware watchdog that is able to reset the board when the system hangs. The watchdog is started on default in U-Boot with a timeout of 60s. So even during early kernel start, the watchdog is already up and running.

  • Page 79: Bbnsm Power Key

    Triggering a power off with systemd when pushing the ON/OFF button can be configured under and set using: /etc/systemd/logind.conf HandlePowerKey=poweroff 7.22 PXP The i.MX 93 SoC contains an PiXel Pipeline (PXP). The PXP combines the following into a single processing engine: • Scaling • Color Space Conversion (CSC) • Secondary Color Space Conversion (CSC2) •...
  • Page 80 Fuses can only be written once! You can brick your board easily by burning the wrong boot configuration. It cannot be reversed! Which fuse bank/word should be used to program the BOOT_CFGX can be checked in i.MX 93 Applications Processor Reference Manual attached spreadsheet named i.MX93_Fusemap.xlsx.

  • Page 81: Tpm

    • set the eMMC Bus width to 0b01 (8 bit) with BOOT_CFG0[18:17] • set the BT_FUSE_SEL (Boot fuses already programmed) bit with BOOT_CFG0[29] Make sure you set the right bits by reading the Boot Fusemap chapter in i.MX 93 Applications Processor Reference Manual.
  • Page 82 93 BSP Manual PD24.1.1 Documentation Rev.: imx8mp-pd22.1.2-51-ga548be7d Note Do NOT share your private RSA keys if you are going to use these keys for any security purposes. Generate RSA public key and validate its contents: target:~$ openssl rsa -in /tmp/test_key -pubout -out /tmp/pub_key...

  • Page 83: I.mx 93 M33 Core

    I.MX 93 M33 CORE In addition to the Cortex-A55 cores, there is a Cortex-M33 Core as MCU integrated into the i.MX 93 SoC. Our Yocto-Linux-BSP runs on the A55-Cores and the M33 Core can be used as a secondary core for additional tasks using bare-metal firmware.
  • Page 84 The samples found in on the target come from NXP’s Yocto layer meta-imx and are /lib/firmware selected based on compatibility with phyBOARD-Segin/Nash i.MX 93 hardware. Some firmware examples from NXP require additional Linux kernel modules to be loaded. For example, when loading firmware, one requires imx93-11x11-evk_m33_TCM_rpmsg_lite_str_echo_rtos.elf...
  • Page 85 > /dev/ttyRPMSG30 Observing M33 Core debug UART should result in the following output: RPMSG String Echo FreeRTOS RTOS API Demo... Nameservice sent, ready for incoming messages... Get Message From Master Side : "PHYTEC" [len : 6] i.MX 93 M33 Core...

This manual is also suitable for:

Phyboard-segin i.mx 93Phyboard-nash i.mx 93
Save PDF