Ronetix's Wiki - User contributions [en]

SAMA5D3X-CM

2026-09-15T13:58:02Z

Ilko: Note that Buildroot now also builds the SAM-BA host tool automatically

{{#vardefine:HARDWARE_NAME|SAMA5D3X-CM}}
{{#vardefine:CPU|ATSAMA5D3X}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sama5d3x_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with a CORTEX-A5 CPU running at 536MHz

|SAMA5D35-CM_top.png|
https://ronetix.at/product/sama5d3x-cm-cpu-module-with-atmel-sama5d3-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

==== Alternative: Configure and build with GPIO test ====
This requires a special prepared Ronetix's carrier board with shorted pin pairs.
Used for production tests.
$ make sama5d3x_cm_gpio_test_defconfig
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAMA5D3x is maintained by Microchip: https://www.linux4sam.org/bin/view/Linux4SAM/BuildRoot 

Buildroot can build:
* at91bootstrap
* U-BOOT
* Linux Kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ mkdir buildroot-ronetix
$ cd buildroot-ronetix
$ git clone https://github.com/linux4microchip/buildroot-mchp.git
$ git clone https://github.com/ronetix/br2-external-ronetix.git

$ cd buildroot-mchp
$ git switch -c linux4microchip-2026.04 linux4microchip-2026.04

==== Build ====
$ make BR2_EXTERNAL=../br2-external-ronetix sama5d3x_cm_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* u-boot-spl.bin
* zImage
* sama5d31ek.dtb
* sama5d33ek.dtb
* sama5d34ek.dtb
* sama5d35ek.dtb
* sama5d36ek.dtb
* rootfs.ubi
* rootfs.ubifs

The SAM-BA programming tool (used in the "Programming with SAM-BA 3.x" section below) is also built automatically by this defconfig and installed at: 
* ./output/host/bin/sam-ba

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
All images should be programmed with 8-bit ECC.
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap, programmed with header 0xc0304405
|-
| style="padding: 5px;"| 0x00040000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| sama5d35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00F80000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

===== Programming with SAM-BA 3.x =====
$ sam-ba -p usb -b sama5d3-ek -a lowlevel
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c erase
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c writeboot:boot.bin
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:u-boot.bin:0x40000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:sama5d35ek.dtb:0x180000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:zImage:0x200000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:rootfs.ubi:0xF80000

More information about SAM-BA 3.x can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Samba3Subsections

SAMA5D3X-CM

2026-09-15T13:44:23Z

Ilko: Update Buildroot build instructions: use upstream linux4microchip/buildroot-mchp (tag linux4microchip-2026.04) with the new br2-external-ronetix board-support tree, replacing the old ronetix/buildroot-mchp fork

{{#vardefine:HARDWARE_NAME|SAMA5D3X-CM}}
{{#vardefine:CPU|ATSAMA5D3X}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sama5d3x_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with a CORTEX-A5 CPU running at 536MHz

|SAMA5D35-CM_top.png|
https://ronetix.at/product/sama5d3x-cm-cpu-module-with-atmel-sama5d3-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

==== Alternative: Configure and build with GPIO test ====
This requires a special prepared Ronetix's carrier board with shorted pin pairs.
Used for production tests.
$ make sama5d3x_cm_gpio_test_defconfig
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAMA5D3x is maintained by Microchip: https://www.linux4sam.org/bin/view/Linux4SAM/BuildRoot 

Buildroot can build:
* at91bootstrap
* U-BOOT
* Linux Kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ mkdir buildroot-ronetix
$ cd buildroot-ronetix
$ git clone https://github.com/linux4microchip/buildroot-mchp.git
$ git clone https://github.com/ronetix/br2-external-ronetix.git

$ cd buildroot-mchp
$ git switch -c linux4microchip-2026.04 linux4microchip-2026.04

==== Build ====
$ make BR2_EXTERNAL=../br2-external-ronetix sama5d3x_cm_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* u-boot-spl.bin
* zImage
* sama5d31ek.dtb
* sama5d33ek.dtb
* sama5d34ek.dtb
* sama5d35ek.dtb
* sama5d36ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
All images should be programmed with 8-bit ECC.
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap, programmed with header 0xc0304405
|-
| style="padding: 5px;"| 0x00040000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| sama5d35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00F80000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

===== Programming with SAM-BA 3.x =====
$ sam-ba -p usb -b sama5d3-ek -a lowlevel
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c erase
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c writeboot:boot.bin
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:u-boot.bin:0x40000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:sama5d35ek.dtb:0x180000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:zImage:0x200000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:rootfs.ubi:0xF80000

More information about SAM-BA 3.x can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Samba3Subsections

SAM9X5-CM

2026-09-15T13:41:20Z

Ilko: Note that Buildroot now also builds the SAM-BA host tool automatically

{{#vardefine:HARDWARE_NAME|SAM9X5-CM}}
{{#vardefine:CPU|AT91SAM9x5}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sam9x5_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|SAM9-CM_top.png|
https://ronetix.at/product/sam9x5-cm-cpu-module-with-atmel-at91sam9x5-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/LegacySAM9x5Page|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

= Build Results =
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAM9X5 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
The Host build system should be a Linux system with necessary software installed:
http://www.buildroot.net/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ mkdir buildroot-ronetix
$ cd buildroot-ronetix
$ git clone https://github.com/linux4microchip/buildroot-mchp.git
$ git clone https://github.com/ronetix/br2-external-ronetix.git

$ cd buildroot-mchp
$ git switch -c linux4microchip-2026.04 linux4microchip-2026.04

==== Build ====
$ make BR2_EXTERNAL=../br2-external-ronetix sam9x5_cm_defconfig
$ make

==== Build Results ====
Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* at91sam9g15ek.dtb
* at91sam9g25ek.dtb
* at91sam9g35ek.dtb
* at91sam9x25ek.dtb
* at91sam9x35ek.dtb
* rootfs.ubi
* rootfs.ubifs

The SAM-BA programming tool (used in the "Programming with SAM-BA 3.x" section below) is also built automatically by this defconfig and installed at: 
* ./output/host/bin/sam-ba

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| at91sam9x35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

===== Programming with SAM-BA 3.x =====
$ sam-ba -p usb -b sam9xx5-ek -a lowlevel
$ sam-ba -p usb -b sam9xx5-ek -a extram
$ sam-ba -p usb -b sam9xx5-ek -a serialflash -c erase:0:0x10000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c erase
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c writeboot:boot.bin
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:u-boot.bin:0x40000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:at91sam9x35ek.dtb:0x180000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:zImage:0x200000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:rootfs.ubi:0x800000

More information about SAM-BA 3.x can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Samba3Subsections

SAM9X5-CM

2026-09-15T13:35:36Z

{{#vardefine:HARDWARE_NAME|SAM9X5-CM}}
{{#vardefine:CPU|AT91SAM9x5}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sam9x5_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|SAM9-CM_top.png|
https://ronetix.at/product/sam9x5-cm-cpu-module-with-atmel-at91sam9x5-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/LegacySAM9x5Page|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

= Build Results =
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAM9X5 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
The Host build system should be a Linux system with necessary software installed:
http://www.buildroot.net/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ mkdir buildroot-ronetix
$ cd buildroot-ronetix
$ git clone https://github.com/linux4microchip/buildroot-mchp.git
$ git clone https://github.com/ronetix/br2-external-ronetix.git

$ cd buildroot-mchp
$ git switch -c linux4microchip-2026.04 linux4microchip-2026.04

==== Build ====
$ make BR2_EXTERNAL=../br2-external-ronetix sam9x5_cm_defconfig
$ make

==== Build Results ====
Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* at91sam9g15ek.dtb
* at91sam9g25ek.dtb
* at91sam9g35ek.dtb
* at91sam9x25ek.dtb
* at91sam9x35ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| at91sam9x35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

===== Programming with SAM-BA 3.x =====
$ sam-ba -p usb -b sam9xx5-ek -a lowlevel
$ sam-ba -p usb -b sam9xx5-ek -a extram
$ sam-ba -p usb -b sam9xx5-ek -a serialflash -c erase:0:0x10000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c erase
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c writeboot:boot.bin
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:u-boot.bin:0x40000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:at91sam9x35ek.dtb:0x180000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:zImage:0x200000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:rootfs.ubi:0x800000

More information about SAM-BA 3.x can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Samba3Subsections

PM9G45

2026-09-15T13:32:14Z

Ilko: Update Buildroot instructions for br2-external-ronetix / linux4microchip-2026.04

{{#vardefine:HARDWARE_NAME|PM9G45}}
{{#vardefine:CPU|AT91SAM9G45}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_UBOOT_NAME|pm9g45_nf_uboot_defconfig}}
{{#vardefine:DEFCONFIG_LINUX_NAME|pm9g45_nf_linux_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|~/bin/arm-ronetix-eabi-11.1.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|PM9G45-top.png|
https://ronetix.at/product/pm9g45-cpu-module-with-atmel-at91sam9g45

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/GettingStarted#Getting_Started_SAM9
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Install and setup the cross-compiler and CPU architecture ====
$ cd ~
$ mkdir bin
$ wget http://download.ronetix.at/toolchains/crosstool-ng/arm-ronetix-eabi-11.1.0.tar.gz
$ tar xvfz arm-ronetix-eabi-11.1.0.tar.gz --directory bin
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone git@github.com:ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build for booting of U-BOOT ====
$ make {{#var:DEFCONFIG_UBOOT_NAME}}
$ make

==== Configure and build for booting of Linux Kernel ====
$ make {{#var:DEFCONFIG_LINUX_NAME}}
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for AT91SAM9G45 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
The host build system should be a Linux system with necessary software installed:
http://www.buildroot.net/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ mkdir buildroot-ronetix
$ cd buildroot-ronetix
$ git clone https://github.com/linux4microchip/buildroot-mchp.git
$ git clone https://github.com/ronetix/br2-external-ronetix.git

$ cd buildroot-mchp
$ git switch -c linux4microchip-2026.04 linux4microchip-2026.04

==== Build ====
$ make BR2_EXTERNAL=../br2-external-ronetix pm9g45_defconfig
$ make

==== Build Results ====
Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* pm9g45.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| pm9g45.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

RNX-RZG2UL-OSM Yocto Linux

2026-09-14T06:52:29Z

Ilko: Change the templates path in TEMPLATECONF

{{#vardefine:HARDWARE_NAME|RNX-RZG2UL-OSM}}
{{#vardefine:URL_PEEDI|[https://ronetix.at/product/peedi-jtag-swd-bdm-emulator-and-flash-programmer/ PEEDI]}}
[[File:RNX-RZG2UL-OSM_top.png|thumb]]
== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
! Yocto
! Linux Kernel
! U-BOOT
|-
| Poky
| 5.10.184
| 2021.10
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Renesas Verified Linux Package v3.0.5 ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/yocto-renesas
$ cd ~/yocto-renesas

* '''Download the Renesas Verified Linux Package''' 
$ git clone https://github.com/ronetix/rzg_vlp.git
$ cd rzg_vlp

== Setup and build Yocto ==
$ TEMPLATECONF=$PWD/meta-ronetix/conf/templates/default source poky/oe-init-build-env build
$ MACHINE=rnx-rzg2ul-osm bitbake core-image-bsp

== Build Results ==
The resulted images are located in ./tmp/deploy/images/rnx-rzg2ul-osm

== Programming Images ==
* [[RNX-RZG2UL-OSM_Programming_Images|Programming Images]]


{{SeeAlso}}

Ronetix's Wiki:Privacy policy

2026-09-13T11:01:31Z

Ilko: Initial creation

== Privacy Policy ==

Last updated: September 2026

Ronetix Development Tools GmbH ("we," "our," or "us") operates the Ronetix Wiki (the "Service"). This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our wiki and the choices you have associated with that data.

We are committed to protecting your privacy and complying with applicable data protection laws, including the General Data Protection Regulation (GDPR).

== 1. Information We Collect ==

While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ("Personal Data"). This may include, but is not limited to:
* **Account Information:** If you register an account to edit or contribute to the wiki, we collect your username, password (stored in a securely hashed format), and email address.
* **Usage Data:** We may also collect information on how the Service is accessed and used ("Usage Data"). This may include your computer's Internet Protocol address (IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, time spent on those pages, and other diagnostic data.
* **Edit History:** As a standard feature of wiki platforms, any contributions, revisions, or edits you make to wiki pages are publicly linked to your username and stored in the page history logs.

== 2. Use of Cookies ==
We use cookies and similar tracking technologies to track the activity on our Service and hold certain information.
* **Session Cookies:** Used to keep you logged in during your browsing and editing session.
* **Persistent Cookies:** Used to remember your preferences and settings when you return to the wiki.
You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to login or use certain portions of our Service.

== 3. Use of Data ==
Ronetix GmbH uses the collected data for various purposes:
* To provide and maintain the Service (including managing user accounts).
* To notify you about changes to our Service.
* To allow you to participate in interactive features of our Service when you choose to do so.
* To monitor the usage of the Service and prevent vandalism, spam, or security threats.

== 4. Security of Data ==
The security of your data is important to us, but remember that no method of transmission over the Internet or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

== 5. Links to Other Sites ==
Our Service may contain links to other sites that are not operated by us. If you click on a third-party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit. We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.

== 6. Changes to This Privacy Policy ==
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date.

== 7. Contact Us ==
If you have any questions about this Privacy Policy, please contact us:
* By visiting our official website: [https://www.ronetix.at ronetix.at]

Ronetix's Wiki:General disclaimer

2026-09-13T11:00:25Z

Ilko: Initial creation

== General Disclaimer ==

The information provided on the Ronetix Wiki ("we," "our," or "us") is for general informational and technical documentation purposes only. All information on the wiki is provided in good faith; however, we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on this site.

== 1. No Professional or Hardware Warranties ==
The documentation, schematics, application notes, software drivers, and guides provided on this wiki are intended for use by qualified engineers and developers.
* Ronetix Development Tools GmbH does not warrant that hardware designs, code snippets, or configuration examples will be error-free or suitable for any specific commercial or safety-critical application.
* Working with embedded systems, high-voltage circuits, JTAG debuggers, and flashing tools carries inherent risks of hardware damage, data loss, or system instability. You assume full responsibility and risk for all actions taken based on the information found on this wiki.

== 2. Limitation of Liability ==
Under no circumstance shall Ronetix GmbH, its directors, employees, partners, or contributors be held liable for any direct, indirect, incidental, consequential, or punitive damages—including but not limited to loss of profits, data, use, goodwill, or other intangible losses—resulting from:
* Your access to or use of (or inability to access or use) the wiki.
* Any conduct or content of any third party on the wiki.
* Any content obtained from the wiki.
* Unauthorized access, use, or alteration of your transmissions or content, whether based on warranty, contract, tort (including negligence), or any other legal theory.

== 3. External Links Disclaimer ==
The wiki may contain links to external websites or resources that are not provided or maintained by or in any way affiliated with Ronetix. Please note that Ronetix does not guarantee the accuracy, relevance, timeliness, or completeness of any information on these external websites.

== 4. "Use at Your Own Risk" ==
All content, software code, bootloaders, and configuration files are provided **"as is,"** without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and non-infringement.

== 5. Contact Us ==
If you have any questions about this Disclaimer, you can contact us via our official website at [https://www.ronetix.at ronetix.at].

Ronetix's Wiki:About

2026-09-13T10:59:22Z

Ilko: Initial creation

== About Ronetix ==

'''Ronetix GmbH''' is a Vienna, Austria-based company specializing in embedded hardware, founded in 2005. We design and manufacture [[System on Module|System-on-Modules (SOMs)]] and JTAG debugging/flash-programming tools for a wide range of CPU platforms, aiming to give embedded developers a faster and more cost-effective path from prototype to production.

== Products ==

=== System on Modules (SOMs) ===
Compact, production-ready computing modules built around processors from:
* NXP — i.MX95, i.MX93, i.MX8M, and i.MX7 series
* Renesas — RZ/V2N and RZ/G2UL series

Modules are available in several form factors, with matching carrier boards and starter kits for evaluation and development.

=== PEEDI JTAG Emulator ===
A high-speed JTAG debugger and flash programmer supporting ARM Cortex, PowerPC, Power QUICC, and ColdFire architectures, used for on-target debugging and production flash programming.

== Company ==
Ronetix is based in Vienna, Austria, and ships to a worldwide distribution network. The company works closely with semiconductor partners including NXP and Renesas, and is known for direct, responsive customer support and ongoing firmware/BSP updates for its modules.

== Links ==
* Website: [https://www.ronetix.at ronetix.at]

Template:iMX8M-YOCTO

2026-09-13T10:53:57Z

Ilko: Add a new line

= Overview =
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

= Installing required packages =

Please make sure your host PC is running Ubuntu 18.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git \
sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

= Download Yocto based on Freescale Community BSP =

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/bsp-repo -b {{#var:YOCTO_NAME}}

$ repo sync

= Setup and build Yocto =
{{#var:SETUP_BUILD_COMMENT}}

$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fslc-xwayland . setup-environment build_xwayland_{{#var:MACHINE_NAME}}
$ bitbake fsl-image-gui

== Building with Local Sources (externalsrc) ==

To build using local copies of the Linux kernel and U-Boot rather than fetching from remote repositories, append the following lines to 
<code>./build_xwayland_{{#var:MACHINE_NAME}}/conf/local.conf</code>:

<pre>
INHERIT += "externalsrc"
EXTERNALSRC_pn-linux-ronetix = "${HOME}/work/linux-ronetix"
EXTERNALSRC_pn-u-boot-ronetix = "${HOME}/work/u-boot"
</pre>
== Build Results ==
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

== Create a bootable SD card ==
Replace sdX with the right device name.
$ umount /dev/sdX1
$ umount /dev/sdX2
$ sudo bmaptool copy tmp/deploy/images/{{#var:MACHINE_NAME}}/fsl-image-gui-{{#var:MACHINE_NAME}}.wic.gz /dev/sdX

= WiFi Setup =
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

= Audio Test =
List all sound cards:
$ aplay -L

Play a file:
$ aplay Test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

= QSPI NOR Flash test =
$ mtd_debug info /dev/mtd0
$ mtd_debug erase /dev/mtd0 0 0x10000
$ dd if=/dev/urandom of=tmp_write.txt bs=1024 count=64
$ dd if=tmp_write.txt of=/dev/mtd0 bs=1024 count=64
$ dd if=/dev/mtd0 of=tmp_read.txt bs=1024 count=64
$ diff tmp_write.txt tmp_read.txt
$ hexdump -C tmp_read.txt | more

= I2C EEPROM Test =
$ echo "Ronetix GmbH" > /sys/bus/i2c/devices/0-0050/eeprom
$ cat /sys/bus/i2c/devices/0-0050/eeprom > eeprom.bin
$ hexdump -C eeprom.bin

= Camera Test =
$ v4l2-ctl --list-devices
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg

= See also =
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

Template:iMX8M-YOCTO

2026-09-13T08:52:15Z

Ilko: Add comment for building with local sources for Linux Kernel and U-BOOT

= Overview =
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

= Installing required packages =

Please make sure your host PC is running Ubuntu 18.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git \
sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

= Download Yocto based on Freescale Community BSP =

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/bsp-repo -b {{#var:YOCTO_NAME}}

$ repo sync

= Setup and build Yocto =
{{#var:SETUP_BUILD_COMMENT}}

$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fslc-xwayland . setup-environment build_xwayland_{{#var:MACHINE_NAME}}
$ bitbake fsl-image-gui

== Building with Local Sources (externalsrc) ==

To build using local copies of the Linux kernel and U-Boot rather than fetching from remote repositories, append the following lines to <code>./build_xwayland_{{#var:MACHINE_NAME}}/conf/local.conf</code>:

<pre>
INHERIT += "externalsrc"
EXTERNALSRC_pn-linux-ronetix = "${HOME}/work/linux-ronetix"
EXTERNALSRC_pn-u-boot-ronetix = "${HOME}/work/u-boot"
</pre>
== Build Results ==
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

== Create a bootable SD card ==
Replace sdX with the right device name.
$ umount /dev/sdX1
$ umount /dev/sdX2
$ sudo bmaptool copy tmp/deploy/images/{{#var:MACHINE_NAME}}/fsl-image-gui-{{#var:MACHINE_NAME}}.wic.gz /dev/sdX

= WiFi Setup =
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

= Audio Test =
List all sound cards:
$ aplay -L

Play a file:
$ aplay Test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

= QSPI NOR Flash test =
$ mtd_debug info /dev/mtd0
$ mtd_debug erase /dev/mtd0 0 0x10000
$ dd if=/dev/urandom of=tmp_write.txt bs=1024 count=64
$ dd if=tmp_write.txt of=/dev/mtd0 bs=1024 count=64
$ dd if=/dev/mtd0 of=tmp_read.txt bs=1024 count=64
$ diff tmp_write.txt tmp_read.txt
$ hexdump -C tmp_read.txt | more

= I2C EEPROM Test =
$ echo "Ronetix GmbH" > /sys/bus/i2c/devices/0-0050/eeprom
$ cat /sys/bus/i2c/devices/0-0050/eeprom > eeprom.bin
$ hexdump -C eeprom.bin

= Camera Test =
$ v4l2-ctl --list-devices
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg

= See also =
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

iMX8MM-COMPACT-CM Yocto Linux

2026-09-12T14:21:13Z

Ilko: Add comment for building of iMX8MM-COMPACT-2GB-CM, PCB v1.1, LPDDR4 2GB, ETH PHY KSZ9131

{{#vardefine:HARDWARE_NAME|iMX8MM-COMPACT-CM}}
{{#vardefine:MACHINE_NAME|imx8mm-compact-cm}}
{{#vardefine:YOCTO_NAME|dunfell}}
{{#vardefine:KERNEL_VER|5.4.105}}
{{#vardefine:UBOOT_VER|v2020.04}}
{{#vardefine:SETUP_BUILD_COMMENT|For iMX8MM-COMPACT-2GB-CM, replace '''{{#var:MACHINE_NAME}}''' with '''imx8mm-compact-2gb-cm'''}}

[[File:iMX8M-COMPACT-CM-top.png|thumb]]


{{iMX8M-YOCTO}}

Template:iMX8M-YOCTO

2026-09-12T14:13:46Z

Ilko: Add possibility to have a comment in "Setup and build Yocto"

= Overview =
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

= Installing required packages =

Please make sure your host PC is running Ubuntu 18.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git \
sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

= Download Yocto based on Freescale Community BSP =

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/bsp-repo -b {{#var:YOCTO_NAME}}

$ repo sync

= Setup and build Yocto =
{{#var:SETUP_BUILD_COMMENT}}

$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fslc-xwayland . setup-environment build_xwayland_{{#var:MACHINE_NAME}}
$ bitbake fsl-image-gui

== Build Results ==
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

== Create a bootable SD card ==
Replace sdX with the right device name.
$ umount /dev/sdX1
$ umount /dev/sdX2
$ sudo bmaptool copy tmp/deploy/images/{{#var:MACHINE_NAME}}/fsl-image-gui-{{#var:MACHINE_NAME}}.wic.gz /dev/sdX

= WiFi Setup =
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

= Audio Test =
List all sound cards:
$ aplay -L

Play a file:
$ aplay Test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

= QSPI NOR Flash test =
$ mtd_debug info /dev/mtd0
$ mtd_debug erase /dev/mtd0 0 0x10000
$ dd if=/dev/urandom of=tmp_write.txt bs=1024 count=64
$ dd if=tmp_write.txt of=/dev/mtd0 bs=1024 count=64
$ dd if=/dev/mtd0 of=tmp_read.txt bs=1024 count=64
$ diff tmp_write.txt tmp_read.txt
$ hexdump -C tmp_read.txt | more

= I2C EEPROM Test =
$ echo "Ronetix GmbH" > /sys/bus/i2c/devices/0-0050/eeprom
$ cat /sys/bus/i2c/devices/0-0050/eeprom > eeprom.bin
$ hexdump -C eeprom.bin

= Camera Test =
$ v4l2-ctl --list-devices
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg

= See also =
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-OSM Yocto Linux

2026-07-02T09:56:48Z

Ilko:

{{#vardefine:HARDWARE_NAME|RNX-iMX93-OSM}}
{{#vardefine:MACHINE_NAME|rnx-imx93-osm}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-OSM_top.png|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J31:1-2 !! J31:3-4 !! J31:5-6 !! J31:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

{{Note|
If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]}}

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-A (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

{{Note|
If the programming freezes with last message "Failed to configure default pinctrl", then try with another USB cable or USP port on your PC.}}

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,width=640,height=480" ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-SMARC Yocto Linux

2026-07-02T09:56:04Z

Ilko:

{{#vardefine:HARDWARE_NAME|RNX-iMX93-SMARC}}
{{#vardefine:MACHINE_NAME|rnx-imx93-smarc}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-SMARC_top.webp|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J4:1-2 !! J4:3-4 !! J4:5-6 !! J4:7-8
|-
| Cortex-A55 Serial Downloader || '''close''' || open || open || open
|-
| Cortex-A55, eMMC || open || '''close''' || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the first port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<syntaxhighlight lang="console" copyable>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4
</syntaxhighlight>

<syntaxhighlight lang="console" copyable>
$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</syntaxhighlight>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

{{Note|
If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]}}

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-0 (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

{{Note|
If the programming freezes with last message "Failed to configure default pinctrl", then try with another USB cable or USP port on your PC.}}

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
<syntaxhighlight lang="console" copyable>
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0
</syntaxhighlight>

Take a single photo:
<syntaxhighlight lang="console" copyable>
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...
</syntaxhighlight>

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-OSM Yocto Linux

2026-07-02T08:40:19Z

Ilko:

{{#vardefine:HARDWARE_NAME|RNX-iMX93-OSM}}
{{#vardefine:MACHINE_NAME|rnx-imx93-osm}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-OSM_top.png|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J31:1-2 !! J31:3-4 !! J31:5-6 !! J31:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-A (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

{{Note|
If the programming freezes with last message "Failed to configure default pinctrl", then try with another USB cable or USP port on your PC.}}

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,width=640,height=480" ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

Template:Warning

2026-07-02T08:38:21Z

Ilko: Initial creation

<div style="background-color:#f8d7da; border-left:4px solid #dc3545; padding:10px 15px; margin:10px 0;">
'''⚠ Warning:''' {{{1}}}
</div>

Template:Note

2026-07-02T08:37:49Z

Ilko: Initial creation

Template:Info

2026-07-02T08:32:50Z

Ilko:

Template:Info

2026-07-02T08:31:24Z

Ilko:

Template:Info

2026-07-02T08:31:00Z

Ilko: Initial creation

RNX-RZV2N-SMARC Programming Images

2026-05-29T14:01:38Z

Ilko: Fix wrong image name in "bmaptool copy"

{{#vardefine:HARDWARE_NAME|RNX-RZV2N-SMARC}}
{{#vardefine:URL_PEEDI|https://ronetix.at/product/peedi-jtag-swd-bdm-emulator-and-flash-programmer}}
[[File:rzv2n-smarc_top.webp|thumb]]
== Overview ==
For a complete Linux System, the CPU Module {{#var:HARDWARE_NAME}} requires the following images:
* Boot Loader stage 2 (BL2) Trusted Boot Firmware with boot parameters block
* Boot Loader stage 3-1 (BL3-1) EL3 Runtime Firmware
* U-BOOT
* Linux Kernel with Device Tree Blob
* RootFS - root file system

The bootloaders (BL2, BL3 and U-BOOT) and the Linux Kernel can be programmed on the QSPI Flash or on the eMMC. 
The RoorFS can be programmed on the eMMC or on a SD card (J14 on the carrier board).

After successful YOCTO building, all these images are available in tmp/deploy/images/rnx-rzv2n-smarc:
{| class="wikitable"
|-
! Image
! Description
|-
| bl2_bp_spi-rnx-rzv2n-smarc.bin bl2_bp_spi-rnx-rzv2n-smarc.srec
| Boot Loader stage 2 (BL2) + boot parameters block
|-
| fip-rnx-rzv2n-smarc.bin fip-rnx-rzv2n-smarc.srec
| Boot Loader stage 3-1 + U-BOOT
|-
| Image-rnx-rzv2n-smarc.bin
| Linux Kernel
|-
| rnx-rzv2n-smarc.dtb
| Linux Device Tree Blob
|-
| core-image-weston-rnx-rzv2n-smarc.rootfs.ext4
| Root File System
|-
| core-image-weston-rnx-rzv2n-smarc.rootfs.wic.gz
| Partitioned Image containing everything
|}

Alternatively, for development purpose, the images can be built standalone: 
* [[RNX-RZV2N-SMARC_ARM_Trusted_Firmware]]
* [[RNX-RZV2N-SMARC_U-Boot]]
* [[RNX-RZV2N-SMARC_Linux]]

The images can be programmed using the [{{#var:URL_PEEDI}} PEEDI JTAG Flash Programmer].

== Setting Boot mode ==
On the carrier board, set the boot mode to "SCIF Download mode".
{| class="wikitable"
|-
!
! J4, pin 1-2
! J4, pin 3-4
|-
| SCIF Download mode
| open
| open
|-
| QSPI Boot mode
| close
| open
|-
| eMMC Boot mode
| open
| close
|}

== Programming BL2, BL31 and U-BOOT ==

=== Programming QSPI Flash using PEEDI JTAG Flash Programmer ===
PEEDI should be configured to use the '''rzv2n.cfg''' configuration file. 

<pre>
PEEDI - Powerful Embedded Ethernet Debug Interface
Copyright (c) 2005-2025 www.ronetix.at - All rights reserved
Hw:1.2, Fw:25.12.1071, SN: PD-0000-0B6B-301F
------------------------------------------------------------

peedi>
++ info: opening file 'tftp://192.168.3.5/rzv2n.cfg'
++ info: loading file 'tftp://192.168.3.5/rzv2n.cfg'...
++ info: done, loaded 2111 meaningful bytes.
++ info: opening file 'eep:license.txt'
++ info: loading file 'eep:license.txt'...
++ info: done, loaded 534 meaningful bytes.

++ info: Wakeup 20 ms
++ info: Target Vref = 1.72V
++ info: RESET and TRST asserted
++ info: TRST released
++ info: RESET released
++ info: wait 200 ms
++ info: BYPASS check passed, 1 TAP controller(s) detected
++ info: TAP: IDCODE = 0x6BA00477, Cortex-ARMv8

++ info: TAP 0: requesting Debug and System power-up (CDBGPWRUPREQ, CSYSPWRUPREQ)
++ info: core 0: using APB port 0
++ info: core 0: Found VFP and NEON features
++ info: core 0: stopped by user request, PC=0x0000000000005578, CPSR=0x400003CD
++ info: core 0: Cortex-A55, CPUID = 0x412FD050
++ info: core 0: connected
++ info: core 0: initialized
</pre>

* Check the QSPI Flash:
<pre>
rzg2> flash info

++ info: Testing workspace at 0x08000000, size 33024 ... done.

FLASH configuration for core #0:
CPU: RENESAS_RZV
Device: AT25QL128 ID: 1F 42 18 1F
3-BYTE command set, Normal Read
Chip size: 16 MB
Write chunk size: 256 bytes
Erase chunk size: 64 KB

FLASH commands default parameters:
flash read 0x00000000 0x01000000
flash blank 0x00000000 0x01000000
flash erase 0x00000000 0x01000000
flash lock 0x00000000 0x01000000
flash unlock 0x00000000 0x01000000
flash query 0x00000000 0x01000000
flash program bl2_bp-rnx-rzv2n-smarc.bin bin 0x00000000
flash verify bl2_bp-rnx-rzv2n-smarc.bin bin 0x00000000
</pre>

* Erase first two MBs of the QSPI Flash
<pre>
rzg2> flash erase 0 1024*1024*2
erasing at 0x00000000 (block #0)
erasing at 0x00010000 (block #1)
erasing at 0x00020000 (block #2)
erasing at 0x00030000 (block #3)
erasing at 0x00040000 (block #4)
erasing at 0x00050000 (block #5)
erasing at 0x00060000 (block #6)
erasing at 0x00070000 (block #7)
erasing at 0x00080000 (block #8)
erasing at 0x00090000 (block #9)
erasing at 0x000A0000 (block #10)
erasing at 0x000B0000 (block #11)
erasing at 0x000C0000 (block #12)
erasing at 0x000D0000 (block #13)
erasing at 0x000E0000 (block #14)
erasing at 0x000F0000 (block #15)
erasing at 0x00100000 (block #16)
erasing at 0x00110000 (block #17)
erasing at 0x00120000 (block #18)
erasing at 0x00130000 (block #19)
erasing at 0x00140000 (block #20)
erasing at 0x00150000 (block #21)
erasing at 0x00160000 (block #22)
erasing at 0x00170000 (block #23)
erasing at 0x00180000 (block #24)
erasing at 0x00190000 (block #25)
erasing at 0x001A0000 (block #26)
erasing at 0x001B0000 (block #27)
erasing at 0x001C0000 (block #28)
erasing at 0x001D0000 (block #29)
erasing at 0x001E0000 (block #30)
erasing at 0x001F0000 (block #31)
++ info: successfully erased 2 MB in 11.05 sec
</pre>

* Program BL2
<pre>
rzg2> flash program bl2_bp-rnx-rzv2n-smarc.bin 0
++ info: Testing workspace at 0x08000000, size 33024 ... done.
++ info: Programming image file: tftp://192.168.3.5/bl2_bp-rnx-rzv2n-smarc.bin
++ info: Programming using agent, buffer = 29952 bytes
++ info: At absolute address: 0x00000000
programming at 0x00000000
programming at 0x00007500
programming at 0x0000EA00
programming at 0x00015F00
programming at 0x0001D400

++ info: successfully programmed 122.03 KB in 1.81 sec
</pre>

* Program BL31+U-BOOT
<pre>
rzg2> flash program fip-rnx-rzv2n-smarc.bin 0x60000
++ info: Testing workspace at 0x08000000, size 33024 ... done.
++ info: Programming image file: tftp://192.168.3.5/fip-rnx-rzv2n-smarc.bin
++ info: Programming using agent, buffer = 29952 bytes
++ info: At absolute address: 0x00060000
programming at 0x00066600
programming at 0x0006DB00
programming at 0x00075000
programming at 0x0007C500
programming at 0x00083A00
programming at 0x0008AF00
programming at 0x00092400
programming at 0x00099900
programming at 0x000A0E00
programming at 0x000A8300
programming at 0x000AF800
programming at 0x000B6D00
programming at 0x000BE200
programming at 0x000C5700
programming at 0x000CCC00
programming at 0x000D4100
programming at 0x000DB600
programming at 0x000E2B00
programming at 0x000EA000
programming at 0x000F1500
programming at 0x000F8A00
programming at 0x000FFF00
programming at 0x00107400
programming at 0x0010E900
programming at 0x00115E00
programming at 0x00060000
programming at 0x0011D300

++ info: successfully programmed 770.93 KB in 10.72 sec
</pre>

== Write Linux Kernel and RootFS to a uSD card ==
The simplest way to write Linux Kernel and RootFS to a SD card is using the bmaptool: 
$ sudo bmaptool copy tmp/deploy/images/rnx-rzv2n-smarc/copy core-image-weston-rnx-rzv2n-smarc.rootfs.wic.gz /dev/sdX

== Boot log ==
* Select QSPI Boot mode and reset the board:

http://download.ronetix.at/boards/doc/RNX-RZV2N-SMARC/rnx-rzv2n-smarc_bootlog.txt


{{SeeAlso}}

RNX-iMX93-SMARC Yocto Linux

2026-03-23T08:19:58Z

Ilko: Use tag <syntaxhighlight> in some commands

{{#vardefine:HARDWARE_NAME|RNX-iMX93-SMARC}}
{{#vardefine:MACHINE_NAME|rnx-imx93-smarc}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-SMARC_top.webp|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J4:1-2 !! J4:3-4 !! J4:5-6 !! J4:7-8
|-
| Cortex-A55 Serial Downloader || '''close''' || open || open || open
|-
| Cortex-A55, eMMC || open || '''close''' || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the first port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<syntaxhighlight lang="console" copyable>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4
</syntaxhighlight>

<syntaxhighlight lang="console" copyable>
$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</syntaxhighlight>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-0 (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

Note:
* If the programming freezes with last message "Failed to configure default pinctrl", then try with another USB cable or USP port on your PC.

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
<syntaxhighlight lang="console" copyable>
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0
</syntaxhighlight>

Take a single photo:
<syntaxhighlight lang="console" copyable>
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...
</syntaxhighlight>

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-RZV2N-SMARC Programming Images

2026-01-15T13:13:58Z

Ilko: Initial creation

{{#vardefine:HARDWARE_NAME|RNX-RZV2N-SMARC}}
{{#vardefine:URL_PEEDI|https://ronetix.at/product/peedi-jtag-swd-bdm-emulator-and-flash-programmer}}
[[File:rzv2n-smarc_top.webp|thumb]]
== Overview ==
For a complete Linux System, the CPU Module {{#var:HARDWARE_NAME}} requires the following images:
* Boot Loader stage 2 (BL2) Trusted Boot Firmware with boot parameters block
* Boot Loader stage 3-1 (BL3-1) EL3 Runtime Firmware
* U-BOOT
* Linux Kernel with Device Tree Blob
* RootFS - root file system

The bootloaders (BL2, BL3 and U-BOOT) and the Linux Kernel can be programmed on the QSPI Flash or on the eMMC. 
The RoorFS can be programmed on the eMMC or on a SD card (J14 on the carrier board).

After successful YOCTO building, all these images are available in tmp/deploy/images/rnx-rzv2n-smarc:
{| class="wikitable"
|-
! Image
! Description
|-
| bl2_bp_spi-rnx-rzv2n-smarc.bin bl2_bp_spi-rnx-rzv2n-smarc.srec
| Boot Loader stage 2 (BL2) + boot parameters block
|-
| fip-rnx-rzv2n-smarc.bin fip-rnx-rzv2n-smarc.srec
| Boot Loader stage 3-1 + U-BOOT
|-
| Image-rnx-rzv2n-smarc.bin
| Linux Kernel
|-
| rnx-rzv2n-smarc.dtb
| Linux Device Tree Blob
|-
| core-image-weston-rnx-rzv2n-smarc.rootfs.ext4
| Root File System
|-
| core-image-weston-rnx-rzv2n-smarc.rootfs.wic.gz
| Partitioned Image containing everything
|}

Alternatively, for development purpose, the images can be built standalone: 
* [[RNX-RZV2N-SMARC_ARM_Trusted_Firmware]]
* [[RNX-RZV2N-SMARC_U-Boot]]
* [[RNX-RZV2N-SMARC_Linux]]

The images can be programmed using the [{{#var:URL_PEEDI}} PEEDI JTAG Flash Programmer].

== Setting Boot mode ==
On the carrier board, set the boot mode to "SCIF Download mode".
{| class="wikitable"
|-
!
! J4, pin 1-2
! J4, pin 3-4
|-
| SCIF Download mode
| open
| open
|-
| QSPI Boot mode
| close
| open
|-
| eMMC Boot mode
| open
| close
|}

== Programming BL2, BL31 and U-BOOT ==

=== Programming QSPI Flash using PEEDI JTAG Flash Programmer ===
PEEDI should be configured to use the '''rzv2n.cfg''' configuration file. 

<pre>
PEEDI - Powerful Embedded Ethernet Debug Interface
Copyright (c) 2005-2025 www.ronetix.at - All rights reserved
Hw:1.2, Fw:25.12.1071, SN: PD-0000-0B6B-301F
------------------------------------------------------------

peedi>
++ info: opening file 'tftp://192.168.3.5/rzv2n.cfg'
++ info: loading file 'tftp://192.168.3.5/rzv2n.cfg'...
++ info: done, loaded 2111 meaningful bytes.
++ info: opening file 'eep:license.txt'
++ info: loading file 'eep:license.txt'...
++ info: done, loaded 534 meaningful bytes.

++ info: Wakeup 20 ms
++ info: Target Vref = 1.72V
++ info: RESET and TRST asserted
++ info: TRST released
++ info: RESET released
++ info: wait 200 ms
++ info: BYPASS check passed, 1 TAP controller(s) detected
++ info: TAP: IDCODE = 0x6BA00477, Cortex-ARMv8

++ info: TAP 0: requesting Debug and System power-up (CDBGPWRUPREQ, CSYSPWRUPREQ)
++ info: core 0: using APB port 0
++ info: core 0: Found VFP and NEON features
++ info: core 0: stopped by user request, PC=0x0000000000005578, CPSR=0x400003CD
++ info: core 0: Cortex-A55, CPUID = 0x412FD050
++ info: core 0: connected
++ info: core 0: initialized
</pre>

* Check the QSPI Flash:
<pre>
rzg2> flash info

++ info: Testing workspace at 0x08000000, size 33024 ... done.

FLASH configuration for core #0:
CPU: RENESAS_RZV
Device: AT25QL128 ID: 1F 42 18 1F
3-BYTE command set, Normal Read
Chip size: 16 MB
Write chunk size: 256 bytes
Erase chunk size: 64 KB

FLASH commands default parameters:
flash read 0x00000000 0x01000000
flash blank 0x00000000 0x01000000
flash erase 0x00000000 0x01000000
flash lock 0x00000000 0x01000000
flash unlock 0x00000000 0x01000000
flash query 0x00000000 0x01000000
flash program bl2_bp-rnx-rzv2n-smarc.bin bin 0x00000000
flash verify bl2_bp-rnx-rzv2n-smarc.bin bin 0x00000000
</pre>

* Erase first two MBs of the QSPI Flash
<pre>
rzg2> flash erase 0 1024*1024*2
erasing at 0x00000000 (block #0)
erasing at 0x00010000 (block #1)
erasing at 0x00020000 (block #2)
erasing at 0x00030000 (block #3)
erasing at 0x00040000 (block #4)
erasing at 0x00050000 (block #5)
erasing at 0x00060000 (block #6)
erasing at 0x00070000 (block #7)
erasing at 0x00080000 (block #8)
erasing at 0x00090000 (block #9)
erasing at 0x000A0000 (block #10)
erasing at 0x000B0000 (block #11)
erasing at 0x000C0000 (block #12)
erasing at 0x000D0000 (block #13)
erasing at 0x000E0000 (block #14)
erasing at 0x000F0000 (block #15)
erasing at 0x00100000 (block #16)
erasing at 0x00110000 (block #17)
erasing at 0x00120000 (block #18)
erasing at 0x00130000 (block #19)
erasing at 0x00140000 (block #20)
erasing at 0x00150000 (block #21)
erasing at 0x00160000 (block #22)
erasing at 0x00170000 (block #23)
erasing at 0x00180000 (block #24)
erasing at 0x00190000 (block #25)
erasing at 0x001A0000 (block #26)
erasing at 0x001B0000 (block #27)
erasing at 0x001C0000 (block #28)
erasing at 0x001D0000 (block #29)
erasing at 0x001E0000 (block #30)
erasing at 0x001F0000 (block #31)
++ info: successfully erased 2 MB in 11.05 sec
</pre>

* Program BL2
<pre>
rzg2> flash program bl2_bp-rnx-rzv2n-smarc.bin 0
++ info: Testing workspace at 0x08000000, size 33024 ... done.
++ info: Programming image file: tftp://192.168.3.5/bl2_bp-rnx-rzv2n-smarc.bin
++ info: Programming using agent, buffer = 29952 bytes
++ info: At absolute address: 0x00000000
programming at 0x00000000
programming at 0x00007500
programming at 0x0000EA00
programming at 0x00015F00
programming at 0x0001D400

++ info: successfully programmed 122.03 KB in 1.81 sec
</pre>

* Program BL31+U-BOOT
<pre>
rzg2> flash program fip-rnx-rzv2n-smarc.bin 0x60000
++ info: Testing workspace at 0x08000000, size 33024 ... done.
++ info: Programming image file: tftp://192.168.3.5/fip-rnx-rzv2n-smarc.bin
++ info: Programming using agent, buffer = 29952 bytes
++ info: At absolute address: 0x00060000
programming at 0x00066600
programming at 0x0006DB00
programming at 0x00075000
programming at 0x0007C500
programming at 0x00083A00
programming at 0x0008AF00
programming at 0x00092400
programming at 0x00099900
programming at 0x000A0E00
programming at 0x000A8300
programming at 0x000AF800
programming at 0x000B6D00
programming at 0x000BE200
programming at 0x000C5700
programming at 0x000CCC00
programming at 0x000D4100
programming at 0x000DB600
programming at 0x000E2B00
programming at 0x000EA000
programming at 0x000F1500
programming at 0x000F8A00
programming at 0x000FFF00
programming at 0x00107400
programming at 0x0010E900
programming at 0x00115E00
programming at 0x00060000
programming at 0x0011D300

++ info: successfully programmed 770.93 KB in 10.72 sec
</pre>

== Write Linux Kernel and RootFS to a uSD card ==
The simplest way to write Linux Kernel and RootFS to a SD card is using the bmaptool: 
$ sudo bmaptool copy tmp/deploy/images/rnx-rzg2ul-osm/core-image-bsp-rnx-rzg2ul-osm.wic.gz /dev/sdX

== Boot log ==
* Select QSPI Boot mode and reset the board:

http://download.ronetix.at/boards/doc/RNX-RZV2N-SMARC/rnx-rzv2n-smarc_bootlog.txt


{{SeeAlso}}

RNX-RZV2N-SMARC

2026-01-15T12:45:36Z

Ilko: Use template Summary_RZG2 instead of Summary

{{#vardefine:HARDWARE_NAME|RNX-RZV2N-SMARC}}
{{#vardefine:CPU|Renesas RZ/V2N}}

{{Summary_RZG2 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in form factor SMARC 314-pin, 82x50mm format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the {{#var:CPU}} CPU with an advanced ARM Cortex-A55 CPU coupled with a dedicated real-time ARM Cortex-M33 MCU.

{{#var:HARDWARE_NAME}} is provided with Linux Yocto distribution. 
|rzv2n-smarc_top.webp|
https://ronetix.at/product/smarc-som-with-renesas-rz-v2n-high-performance-vision-ai-edge-computing/|
}}

RNX-RZV2N-SMARC Yocto Linux

2026-01-15T11:17:58Z

Ilko: Initial creation

{{#vardefine:HARDWARE_NAME|RNX-RZV2N-SMARC}}
{{#vardefine:URL_PEEDI|[https://ronetix.at/product/peedi-jtag-swd-bdm-emulator-and-flash-programmer/ PEEDI]}}
[[File:rzv2n-smarc_top.webp|thumb]]
== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
! Yocto
! Linux Kernel
! U-BOOT
|-
| Scarthgap
| 6.1.107
| 2024.07
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Installing required packages ==

Please make sure your host PC is running Ubuntu 22.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc build-essential \
chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils \
iputils-ping python3-git python3-jinja2 python3-subunit zstd liblz4-tool file \
locales libacl1 bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Renesas AI SDK v6.20 ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/yocto-renesas
$ cd ~/yocto-renesas

* '''Download the Renesas Verified Linux Package''' 
$ git clone https://github.com/ronetix/rzv_ai_sdk.git
$ cd rzv_ai_sdk

== Setup and build Yocto ==
$ TEMPLATECONF=$PWD/meta-renesas/meta-rz-boards/conf/templates/rz-conf/ source poky/oe-init-build-env build
$ MACHINE=rnx-rzv2n-smarc bitbake core-image-weston

== Build Results ==
The resulted images are located in tmp/deploy/images/rnx-rzv2n-smarc

== Programming Images ==
* [[RNX-RZV2N-SMARC_Programming_Images|Programming Images]]


{{SeeAlso}}

RNX-RZV2N-SMARC

2026-01-15T11:06:55Z

Ilko: Initial creation

{{#vardefine:HARDWARE_NAME|RNX-RZV2N-SMARC}}
{{#vardefine:CPU|Renesas RZ/V2N}}

{{Summary | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in form factor SMARC 314-pin, 82x50mm format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the {{#var:CPU}} CPU with an advanced ARM Cortex-A55 CPU coupled with a dedicated real-time ARM Cortex-M33 MCU.

{{#var:HARDWARE_NAME}} is provided with Linux Yocto distribution. 
|rzv2n-smarc_top.webp|
https://ronetix.at/product/smarc-som-with-renesas-rz-v2n-high-performance-vision-ai-edge-computing/|
}}

Main Page

2026-01-15T11:03:56Z

Ilko: Add SoM RNX-RZV2N-SMARC

__NOTOC__
== Ronetix CPU Modules (System-on-Module) ==

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[RNX-RZV2N-SMARC|RNX-RZV2N-SMARC]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* SMARC 314-pin, 82x50mm
* Renesas RZ/V2N
* Quad-core ARM Cortex-A55 CPU, 1.8GHz
* AI accelerator DRP-AI (AI-MAC+DRP)
* ARM Cortex-M33 200MHz
* Linux (Yocto Scarthgap)
| align="center" | [[File:rzv2n-smarc_top.webp|200px|link=RNX-RZV2N-SMARC]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[RNX-iMX93-SMARC|RNX-iMX93-SMARC]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* SMARC 314-pin, 82x50mm
* NXP i.MX93
* Dual-core ARM Cortex-A55 CPU, 1.7GHz
* Arm® Ethos™ U-65 microNPU, 0.5 TOP/s
* ARM Cortex-M33 250MHz
* Linux (Yocto Micledore)
| align="center" | [[File:RNX-iMX93-SMARC_top.webp|200px|link=RNX-iMX93-SMARC]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[RNX-iMX93-OSM|RNX-iMX93-OSM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* OSM Size-L, LGA 45x45mm
* NXP i.MX93
* Dual-core ARM Cortex-A55 CPU, 1.7GHz
* Arm® Ethos™ U-65 microNPU, 0.5 TOP/s
* ARM Cortex-M33 250MHz
* Linux (Yocto Micledore)
| align="center" | [[File:RNX-iMX93-OSM_top.png|150px|link=RNX-iMX93-OSM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[RNX-RZG2UL-OSM|RNX-RZG2UL-OSM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* Renesas RZ/G2UL or RZ/A3UL or RZ/FIVE
* Single-core ARM Cortex-A55, 1GHz
* ARM Cortex-M33, 200MHz
* Linux (Yocto)
| align="center" | [[File:RNX-RZG2UL-OSM_top.png|150px|link=RNX-RZG2UL-OSM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[iMX8MP-COMPACT-CM|i.MX8MP-COMPACT-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* NXP i.MX8M Plus, 1.8GHz
* Neutral Processing Unit (NPU) 2.3 TOP/s
* Quad-core ARM Cortex-A53
* ARM Cortex-M7, 800MHz
* Linux (Yocto)
| align="center" | [[File:iMX8MP-CM-top.png|200px|link=iMX8MP-COMPACT-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[iMX8M-CM|i.MX8M-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* NXP i.MX8M, 1.5GHz
* Quad-core ARM Cortex-A53
* ARM Cortex-M4, 266MHz
* Linux (Yocto)
| align="center" | [[File:iMX8M-CM-top.png|200px|link=iMX8M-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[iMX8M-MINI-CM|i.MX8M-MINI-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* NXP i.MX8M-MINI, 2.0GHz
* Quad-core ARM Cortex-A53
* ARM Cortex-M4, 400MHz
* Linux (Yocto)
| align="center" | [[File:iMX8M-MINI-CM-top.png|200px|link=iMX8M-MINI-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[iMX8M-NANO-CM|i.MX8M-NANO-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* NXP i.MX8M-NANO, 1.5GHz
* Quad-core ARM Cortex-A53
* ARM Cortex-M7, 750MHz
* Linux (Yocto)
| align="center" | [[File:iMX8M-MINI-CM-top.png|200px|link=iMX8M-NANO-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[iMX8MM-COMPACT-CM|i.MX8MM-COMPACT-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* NXP i.MX8M-MINI, 2.0GHz
* Quad-core ARM Cortex-A53
* ARM Cortex-M4, 400MHz
* Linux (Yocto)
| align="center" | [[File:iMX8M-COMPACT-CM-top.png|130px|link=iMX8MM-COMPACT-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[iMX8MN-COMPACT-CM|i.MX8MN-COMPACT-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* NXP i.MX8M-NANO, 1.5GHz
* Quad-core ARM Cortex-A53
* ARM Cortex-M7, 750MHz
* Linux (Yocto)
| align="center" | [[File:iMX8M-COMPACT-CM-top.png|130px|link=iMX8MN-COMPACT-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[iMX7-CM|i.MX7-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* NXP i.MX7D, 1.0GHz
* Dual-core ARM Cortex-A7
* Linux (Yocto)
| align="center" | [[File:iMX7-CM-top.png|200px|link=iMX7-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[SAMA5D3X-CM|SAMA5D3X-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* Microchip (Atmel) ATSAMA5D3x series
* Cortex-A5 536MHz
* Linux
| align="center" | [[File:SAMA5D35-CM_top.png|200px|link=SAMA5D3X-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[SAM9X5-CM|SAM9X5-CM]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* Microchip (Atmel) AT91SAM9x5 series
* ARM926EJ-S 400MHz
* Linux
| align="center" | [[File:SAM9-CM_top.png|200px|link=SAM9X5-CM]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[PM9G45|PM9G45]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* Atmel AT91SAM9G45
* 400 MHz ARM926EJ-S
* Linux
* Android
| align="center" | [[File:PM9G45-top.png|200px|link=PM9G45]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[PM9263|PM9263]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* Atmel AT91SAM9263
* 240 MHz ARM926EJ-S
| align="center" | [[File:PM9263-top.png|200px|link=PM9263]]
|}
|}

{| width="65%" align="left" cellspacing="3" cellpadding="10"
|- style="line-height: 120%; border-bottom: 1px solid #aaaaaa; font-size: 120%; background-color: #34467F;"
| align="center" | [[PM9261|PM9261]]
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 33%;" |
{| width="100%" align="center" border="0" cellspacing="0"
|- style="font-size: 110%; background-color: #eeeeee;"
| style="width: 60%;" |
* Atmel AT91SAM9261
* 240 MHz ARM926EJ-S
| align="center" | [[File:PM9261-top.png|200px|link=PM9261]]
|}
|}

File:rzv2n-smarc top.webp

2026-01-15T10:38:56Z

Ilko: SoM RNX-RZV2N-SMARC top side

== Summary ==
SoM RNX-RZV2N-SMARC top side

RNX-iMX93-OSM Yocto Linux

2025-10-27T12:49:17Z

Ilko: Add note about failed programming

{{#vardefine:HARDWARE_NAME|RNX-iMX93-OSM}}
{{#vardefine:MACHINE_NAME|rnx-imx93-osm}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-OSM_top.png|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J31:1-2 !! J31:3-4 !! J31:5-6 !! J31:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-A (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

Note:
* If the programming freezes with last message "Failed to configure default pinctrl", then try with another USB cable or USP port on your PC.

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,width=640,height=480" ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-SMARC Yocto Linux

2025-10-27T12:08:12Z

Ilko: Add note about failed programming

{{#vardefine:HARDWARE_NAME|RNX-iMX93-SMARC}}
{{#vardefine:MACHINE_NAME|rnx-imx93-smarc}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-SMARC_top.webp|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J4:1-2 !! J4:3-4 !! J4:5-6 !! J4:7-8
|-
| Cortex-A55 Serial Downloader || '''close''' || open || open || open
|-
| Cortex-A55, eMMC || open || '''close''' || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the first port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-0 (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

Note:
* If the programming freezes with last message "Failed to configure default pinctrl", then try with another USB cable or USP port on your PC.

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-SMARC Yocto Linux

2025-10-27T10:34:16Z

Ilko: Make "close" bold

{{#vardefine:HARDWARE_NAME|RNX-iMX93-SMARC}}
{{#vardefine:MACHINE_NAME|rnx-imx93-smarc}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-SMARC_top.webp|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J4:1-2 !! J4:3-4 !! J4:5-6 !! J4:7-8
|-
| Cortex-A55 Serial Downloader || '''close''' || open || open || open
|-
| Cortex-A55, eMMC || open || '''close''' || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the first port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-0 (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-SMARC U-Boot

2025-09-02T08:42:50Z

Ilko: Add configuration for RNX-iMX93-SMARC v1.0 and v1.1

{{#vardefine:HARDWARE_NAME|RNX-iMX93-SMARC}}
{{#vardefine:UBOOT_BRANCH|lf_v2023.04}}
{{#vardefine:DEFCONFIG_NAME|imx93-rnx_smarc_defconfig}}
{{#vardefine:DEFCONFIG_2GB_NAME|imx93-rnx_smarc_2gb_defconfig}}
[[File:RNX-iMX93-SMARC_top.webp|thumb]]
== Overview ==
The U-Boot bootloader is used for low-level initialization and operating system loading.

== Setting Boot mode ==

{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J4:1-2 !! J4:3-4 !! J4:5-6 !! J4:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.
== Building U-BOOT for {{#var:HARDWARE_NAME}} ==
This U-BOOT is based on https://github.com/nxp-imx/uboot-imx, branch {{#var:UBOOT_BRANCH}}

=== Set up the cross-compiler and CPU architecture ===
$ export ARCH=arm64
$ export CROSS_COMPILE=/opt/cross/aarch64-ronetix-linux-11.1/bin/aarch64-ronetix-linux-gnu-

A cross-compiler can be downloaded from here:
http://download.ronetix.at/toolchains/crosstool-ng

=== Clone the latest revision of the repo ===
$ git clone https://github.com/ronetix/u-boot.git uboot-imx --depth=1 -b {{#var:UBOOT_BRANCH}}
$ cd uboot-imx

=== Configure ===
For RNX-iMX93-SMARC v1.1 with 2GB LPDDR4x:
$ make {{#var:DEFCONFIG_2GB_NAME}}
or for RNX-iMX93-SMARC v1.0 with 1GB LPDDR4x:
$ make {{#var:DEFCONFIG_NAME}}

=== Build ===
$ make

=== Create IMX image ===
Create a new Firmware package '''flash.bin''' that contains SPL, U-Boot, Arm Trusted Firmware, Sentinel
Firmware, DDR PHY Firmware. 
The Sentinel firmware differs on the CPU revision. 
For RNX-iMX93-SMARC v1.1, CPU revision A1:

$ source ./tools/imx_build_firmware.sh imx93

For building image with CPU revision A0 (RNX-iMX93-SMARC v1.0) use:
$ CPU_REV=A0 source ./tools/imx_build_firmware.sh imx93

=== Build Results ===
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| u-boot
| style="padding: 5px;"| U-BOOT ELF image used for JTAG debugging
|-
| style="padding: 5px;"| u-boot-dtb.bin
| style="padding: 5px;"| U-BOOT image with DTB
|-
| style="padding: 5px;"| ./imx-mkimage/iMX9/flash.bin
| style="padding: 5px;"| IMX bootloader
|}

== Programming the IMX image ==
This section describes how to write the bootloader into the eMMC using UUU. 

=== Universal update utility ===
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

==== Downloading UUU ====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

==== Connect USB ports ====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-0 (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

=== Write flash.bin into eMMC ===

$ cd ./imx-mkimage/iMX9
$ wget http://download.ronetix.at/boards/doc/RNX-iMX93-SMARC/tools/u-boot.uuu
$ uuu u-boot.uuu


{{SeeAlso}}

RNX-iMX93-SMARC U-Boot

2025-07-11T14:58:58Z

Ilko: Add option for building of IMX image for CPU revisions A0 and A1

{{#vardefine:HARDWARE_NAME|RNX-iMX93-SMARC}}
{{#vardefine:UBOOT_BRANCH|lf_v2023.04}}
{{#vardefine:DEFCONFIG_NAME|imx93-rnx_smarc_defconfig}}
[[File:RNX-iMX93-SMARC_top.webp|thumb]]
== Overview ==
The U-Boot bootloader is used for low-level initialization and operating system loading.

== Setting Boot mode ==

{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J4:1-2 !! J4:3-4 !! J4:5-6 !! J4:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.
== Building U-BOOT for {{#var:HARDWARE_NAME}} ==
This U-BOOT is based on https://github.com/nxp-imx/uboot-imx, branch {{#var:UBOOT_BRANCH}}

=== Set up the cross-compiler and CPU architecture ===
$ export ARCH=arm64
$ export CROSS_COMPILE=/opt/cross/aarch64-ronetix-linux-11.1/bin/aarch64-ronetix-linux-gnu-

A cross-compiler can be downloaded from here:
http://download.ronetix.at/toolchains/crosstool-ng

=== Clone the latest revision of the repo ===
$ git clone https://github.com/ronetix/u-boot.git uboot-imx --depth=1 -b {{#var:UBOOT_BRANCH}}
$ cd uboot-imx

=== Configure ===
$ make {{#var:DEFCONFIG_NAME}}

=== Build ===
$ make

=== Create IMX image ===
Create a new Firmware package '''flash.bin''' that contains SPL, U-Boot, Arm Trusted Firmware, Sentinel
Firmware, DDR PHY Firmware. 
The Sentinel firmware differs on the CPU revision. By default revision A1 is used:

$ source ./tools/imx_build_firmware.sh imx93

For building image with CPU revision A0 use:
$ CPU_REV=A0 source ./tools/imx_build_firmware.sh imx93

=== Build Results ===
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| u-boot
| style="padding: 5px;"| U-BOOT ELF image used for JTAG debugging
|-
| style="padding: 5px;"| u-boot-dtb.bin
| style="padding: 5px;"| U-BOOT image with DTB
|-
| style="padding: 5px;"| ./imx-mkimage/iMX9/flash.bin
| style="padding: 5px;"| IMX bootloader
|}

== Programming the IMX image ==
This section describes how to write the bootloader into the eMMC using UUU. 

=== Universal update utility ===
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

==== Downloading UUU ====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

==== Connect USB ports ====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-0 (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

=== Write flash.bin into eMMC ===

$ cd ./imx-mkimage/iMX9
$ wget http://download.ronetix.at/boards/doc/RNX-iMX93-SMARC/tools/u-boot.uuu
$ uuu u-boot.uuu


{{SeeAlso}}

RNX-iMX93-SMARC Yocto Linux

2025-03-25T10:34:55Z

Ilko: Fix USB console port

{{#vardefine:HARDWARE_NAME|RNX-iMX93-SMARC}}
{{#vardefine:MACHINE_NAME|rnx-imx93-smarc}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-SMARC_top.webp|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J4:1-2 !! J4:3-4 !! J4:5-6 !! J4:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the first port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-0 (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

SAM9X5-CM

2025-03-13T10:27:47Z

Ilko: Add "Programming with SAM-BA 3.x"

{{#vardefine:HARDWARE_NAME|SAM9X5-CM}}
{{#vardefine:CPU|AT91SAM9x5}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sam9x5_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|SAM9-CM_top.png|
https://ronetix.at/product/sam9x5-cm-cpu-module-with-atmel-at91sam9x5-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/LegacySAM9x5Page|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

= Build Results =
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAM9X5 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
The Host build system should be a Linux system with necessary software installed:
http://www.buildroot.net/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git

$ cd buildroot-mchp
$ git checkout buildroot-at91-linux4microchip-2024.10 -b buildroot-at91-linux4microchip-2024.10

==== Build ====
$ make at91sam9x5ek_defconfig
$ make

==== Build Results ====
Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* at91sam9g15ek.dtb
* at91sam9g25ek.dtb
* at91sam9g35ek.dtb
* at91sam9x25ek.dtb
* at91sam9x35ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| at91sam9x35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

===== Programming with SAM-BA 3.x =====
$ sam-ba -p usb -b sam9xx5-ek -a lowlevel
$ sam-ba -p usb -b sam9xx5-ek -a extram
$ sam-ba -p usb -b sam9xx5-ek -a serialflash -c erase:0:0x10000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c erase
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c writeboot:boot.bin
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:u-boot.bin:0x40000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:at91sam9x35ek.dtb:0x180000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:zImage:0x200000
$ sam-ba -p usb -b sam9xx5-ek -a nandflash -c write:rootfs.ubi:0x800000

More information about SAM-BA 3.x can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Samba3Subsections

SAM9X5-CM

2025-03-13T08:42:35Z

Ilko: Add "Building Buildroot"

{{#vardefine:HARDWARE_NAME|SAM9X5-CM}}
{{#vardefine:CPU|AT91SAM9x5}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sam9x5_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|SAM9-CM_top.png|
https://ronetix.at/product/sam9x5-cm-cpu-module-with-atmel-at91sam9x5-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/LegacySAM9x5Page|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

= Build Results =
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAM9X5 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
The Host build system should be a Linux system with necessary software installed:
http://www.buildroot.net/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git

$ cd buildroot-mchp
$ git checkout buildroot-at91-linux4microchip-2024.10 -b buildroot-at91-linux4microchip-2024.10

==== Build ====
$ make at91sam9x5ek_defconfig
$ make

==== Build Results ====
Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* at91sam9g15ek.dtb
* at91sam9g25ek.dtb
* at91sam9g35ek.dtb
* at91sam9x25ek.dtb
* at91sam9x35ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| at91sam9x35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

PM9G45

2025-03-13T08:41:25Z

Ilko: Change link for the system requirements

{{#vardefine:HARDWARE_NAME|PM9G45}}
{{#vardefine:CPU|AT91SAM9G45}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_UBOOT_NAME|pm9g45_nf_uboot_defconfig}}
{{#vardefine:DEFCONFIG_LINUX_NAME|pm9g45_nf_linux_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|~/bin/arm-ronetix-eabi-11.1.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|PM9G45-top.png|
https://ronetix.at/product/pm9g45-cpu-module-with-atmel-at91sam9g45

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/GettingStarted#Getting_Started_SAM9
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Install and setup the cross-compiler and CPU architecture ====
$ cd ~
$ mkdir bin
$ wget http://download.ronetix.at/toolchains/crosstool-ng/arm-ronetix-eabi-11.1.0.tar.gz
$ tar xvfz arm-ronetix-eabi-11.1.0.tar.gz --directory bin
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone git@github.com:ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build for booting of U-BOOT ====
$ make {{#var:DEFCONFIG_UBOOT_NAME}}
$ make

==== Configure and build for booting of Linux Kernel ====
$ make {{#var:DEFCONFIG_LINUX_NAME}}
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for AT91SAM9G45 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
The host build system should be a Linux system with necessary software installed:
http://www.buildroot.net/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git

$ cd buildroot-mchp
$ git checkout buildroot-at91-linux4microchip-2024.10 -b buildroot-at91-linux4microchip-2024.10

==== Build ====
$ make pm9g45_defconfig
$ make

==== Build Results ====
Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* pm9g45.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| pm9g45.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

SAM9X5-CM

2025-03-10T14:33:23Z

Ilko: Change GitHub protocol

SAMA5D3X-CM

2025-02-25T09:16:10Z

Ilko: Add link for information about SAM-BA 3.x

{{#vardefine:HARDWARE_NAME|SAMA5D3X-CM}}
{{#vardefine:CPU|ATSAMA5D3X}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sama5d3x_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with a CORTEX-A5 CPU running at 536MHz

|SAMA5D35-CM_top.png|
https://ronetix.at/product/sama5d3x-cm-cpu-module-with-atmel-sama5d3-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

==== Alternative: Configure and build with GPIO test ====
This requires a special prepared Ronetix's carrier board with shorted pin pairs.
Used for production tests.
$ make sama5d3x_cm_gpio_test_defconfig
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAMA5D3x is maintained by Microchip: https://www.linux4sam.org/bin/view/Linux4SAM/BuildRoot 

Buildroot can build:
* at91bootstrap
* U-BOOT
* Linux Kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git
$ cd buildroot-mchp

==== Build ====
$ make atmel_sama5d3xek_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* u-boot-spl.bin
* zImage
* sama5d31ek.dtb
* sama5d33ek.dtb
* sama5d34ek.dtb
* sama5d35ek.dtb
* sama5d36ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
All images should be programmed with 8-bit ECC.
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap, programmed with header 0xc0304405
|-
| style="padding: 5px;"| 0x00040000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| sama5d35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00F80000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

===== Programming with SAM-BA 3.x =====
$ sam-ba -p usb -b sama5d3-ek -a lowlevel
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c erase
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c writeboot:boot.bin
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:u-boot.bin:0x40000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:sama5d35ek.dtb:0x180000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:zImage:0x200000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:rootfs.ubi:0xF80000

More information about SAM-BA 3.x can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Samba3Subsections

SAMA5D3X-CM

2025-02-25T08:03:18Z

Ilko: Add "Programming with SAM-BA 3.x"

{{#vardefine:HARDWARE_NAME|SAMA5D3X-CM}}
{{#vardefine:CPU|ATSAMA5D3X}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sama5d3x_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with a CORTEX-A5 CPU running at 536MHz

|SAMA5D35-CM_top.png|
https://ronetix.at/product/sama5d3x-cm-cpu-module-with-atmel-sama5d3-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

==== Alternative: Configure and build with GPIO test ====
This requires a special prepared Ronetix's carrier board with shorted pin pairs.
Used for production tests.
$ make sama5d3x_cm_gpio_test_defconfig
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAMA5D3x is maintained by Microchip: https://www.linux4sam.org/bin/view/Linux4SAM/BuildRoot 

Buildroot can build:
* at91bootstrap
* U-BOOT
* Linux Kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git
$ cd buildroot-mchp

==== Build ====
$ make atmel_sama5d3xek_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* u-boot-spl.bin
* zImage
* sama5d31ek.dtb
* sama5d33ek.dtb
* sama5d34ek.dtb
* sama5d35ek.dtb
* sama5d36ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
All images should be programmed with 8-bit ECC.
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap, programmed with header 0xc0304405
|-
| style="padding: 5px;"| 0x00040000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| sama5d35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00F80000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

===== Programming with SAM-BA 3.x =====
$ sam-ba -p usb -b sama5d3-ek -a lowlevel
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c erase
$ sam-ba -p usb -b sama5d3-ek -a nandflash -c writeboot:boot.bin
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:u-boot.bin:0x40000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:sama5d35ek.dtb:0x180000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:zImage:0x200000
$ sam-ba -p usb -b sama5d3-ek -a nandflash:1:8:0xc0304405 -c write:rootfs.ubi:0xF80000

SAMA5D3X-CM

2025-02-24T11:41:49Z

Ilko: Fix bootstrap header comment

{{#vardefine:HARDWARE_NAME|SAMA5D3X-CM}}
{{#vardefine:CPU|ATSAMA5D3X}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sama5d3x_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with a CORTEX-A5 CPU running at 536MHz

|SAMA5D35-CM_top.png|
https://ronetix.at/product/sama5d3x-cm-cpu-module-with-atmel-sama5d3-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

==== Alternative: Configure and build with GPIO test ====
This requires a special prepared Ronetix's carrier board with shorted pin pairs.
Used for production tests.
$ make sama5d3x_cm_gpio_test_defconfig
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAMA5D3x is maintained by Microchip: https://www.linux4sam.org/bin/view/Linux4SAM/BuildRoot 

Buildroot can build:
* at91bootstrap
* U-BOOT
* Linux Kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git
$ cd buildroot-mchp

==== Build ====
$ make atmel_sama5d3xek_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* u-boot-spl.bin
* zImage
* sama5d31ek.dtb
* sama5d33ek.dtb
* sama5d34ek.dtb
* sama5d35ek.dtb
* sama5d36ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
All images should be programmed with 8-bit ECC.
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap, programmed with header 0xc0304405
|-
| style="padding: 5px;"| 0x00040000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| sama5d35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00F80000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

SAMA5D3X-CM

2025-02-24T11:40:27Z

Ilko: Change to Ronetix's buildroot-mchp.git which uses PMECC 8-bits

{{#vardefine:HARDWARE_NAME|SAMA5D3X-CM}}
{{#vardefine:CPU|ATSAMA5D3X}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sama5d3x_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with a CORTEX-A5 CPU running at 536MHz

|SAMA5D35-CM_top.png|
https://ronetix.at/product/sama5d3x-cm-cpu-module-with-atmel-sama5d3-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

==== Alternative: Configure and build with GPIO test ====
This requires a special prepared Ronetix's carrier board with shorted pin pairs.
Used for production tests.
$ make sama5d3x_cm_gpio_test_defconfig
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAMA5D3x is maintained by Microchip: https://www.linux4sam.org/bin/view/Linux4SAM/BuildRoot 

Buildroot can build:
* at91bootstrap
* U-BOOT
* Linux Kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git
$ cd buildroot-mchp

==== Build ====
$ make atmel_sama5d3xek_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* u-boot-spl.bin
* zImage
* sama5d31ek.dtb
* sama5d33ek.dtb
* sama5d34ek.dtb
* sama5d35ek.dtb
* sama5d36ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
All images should be programmed with 8-bit ECC.
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap, programmed with header 0xc0902405
|-
| style="padding: 5px;"| 0x00040000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| sama5d35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00F80000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

SAMA5D3X-CM

2025-02-24T11:26:23Z

Ilko: Change GitHub path for at91bootstrap

{{#vardefine:HARDWARE_NAME|SAMA5D3X-CM}}
{{#vardefine:CPU|ATSAMA5D3X}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_NAME|sama5d3x_cm_nf_uboot_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|/opt/cross/arm-ronetix-eabi-8.3.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with a CORTEX-A5 CPU running at 536MHz

|SAMA5D35-CM_top.png|
https://ronetix.at/product/sama5d3x-cm-cpu-module-with-atmel-sama5d3-series

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/Sama5d3xekMainPage
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Setup the cross-compiler and CPU architecture ====
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone https://github.com/ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build ====
$ make {{#var:DEFCONFIG_NAME}}
$ make

==== Alternative: Configure and build with GPIO test ====
This requires a special prepared Ronetix's carrier board with shorted pin pairs.
Used for production tests.
$ make sama5d3x_cm_gpio_test_defconfig
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for SAMA5D3x is maintained by Microchip: https://www.linux4sam.org/bin/view/Linux4SAM/BuildRoot 

Buildroot can build:
* at91bootstrap
* u-boot-at91
* linux-at91
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/linux4sam/buildroot-at91.git
$ git clone https://github.com/linux4microchip/buildroot-external-microchip.git

$ cd buildroot-external-microchip/
$ git checkout linux4microchip-2022.10 -b buildroot-external-microchip-linux4microchip-2022.10

$ cd ../buildroot-at91/
$ git checkout linux4sam-2022.10 -b buildroot-at91-linux4sam-2022.10

==== Build ====
$ make atmel_sama5d3xek_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* u-boot-spl.bin
* zImage
* sama5d31ek.dtb
* sama5d33ek.dtb
* sama5d34ek.dtb
* sama5d35ek.dtb
* sama5d36ek.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ BR2_EXTERNAL=../buildroot-external-microchip/ at91bootstrap3-menuconfig

===== U-BOOT =====
$ BR2_EXTERNAL=../buildroot-external-microchip/ make uboot-menuconfig

===== Linux Kernel =====
$ BR2_EXTERNAL=../buildroot-external-microchip/ make linux-menuconfig

===== RootFs =====
$ BR2_EXTERNAL=../buildroot-external-microchip/ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
All images should be programmed with 4-bit ECC.
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap, programmed with header 0xc0902405
|-
| style="padding: 5px;"| 0x00040000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| sama5d35ek.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00F80000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

PM9G45

2025-01-07T14:17:06Z

Ilko: Update paragraph style

{{#vardefine:HARDWARE_NAME|PM9G45}}
{{#vardefine:CPU|AT91SAM9G45}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_UBOOT_NAME|pm9g45_nf_uboot_defconfig}}
{{#vardefine:DEFCONFIG_LINUX_NAME|pm9g45_nf_linux_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|~/bin/arm-ronetix-eabi-11.1.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|PM9G45-top.png|
https://ronetix.at/product/pm9g45-cpu-module-with-atmel-at91sam9g45

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/GettingStarted#Getting_Started_SAM9
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Install and setup the cross-compiler and CPU architecture ====
$ cd ~
$ mkdir bin
$ wget http://download.ronetix.at/toolchains/crosstool-ng/arm-ronetix-eabi-11.1.0.tar.gz
$ tar xvfz arm-ronetix-eabi-11.1.0.tar.gz --directory bin
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone git@github.com:ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build for booting of U-BOOT ====
$ make {{#var:DEFCONFIG_UBOOT_NAME}}
$ make

==== Configure and build for booting of Linux Kernel ====
$ make {{#var:DEFCONFIG_LINUX_NAME}}
$ make

==== Build Results ====
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for AT91SAM9G45 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git

$ cd buildroot-mchp
$ git checkout buildroot-at91-linux4microchip-2024.10 -b buildroot-at91-linux4microchip-2024.10

==== Build ====
$ make pm9g45_defconfig
$ make

==== Build Results ====
Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* pm9g45.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| pm9g45.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

PM9G45

2025-01-07T08:49:16Z

Ilko: Add "Building Buildroot"

{{#vardefine:HARDWARE_NAME|PM9G45}}
{{#vardefine:CPU|AT91SAM9G45}}
{{#vardefine:BRANCH|at91bootstrap-3.10.4_rnx}}
{{#vardefine:DEFCONFIG_UBOOT_NAME|pm9g45_nf_uboot_defconfig}}
{{#vardefine:DEFCONFIG_LINUX_NAME|pm9g45_nf_linux_defconfig}}
{{#vardefine:ARCH|arm}}
{{#vardefine:CROSS_COMPILE|~/bin/arm-ronetix-eabi-11.1.0/bin/arm-ronetix-eabi-}}
{{Summary SAM9 A5 | {{#var:HARDWARE_NAME}} |
{{#var:HARDWARE_NAME}} is a System-on-module (SoM) board in SODIMM204 format designed for embedded applications.

{{#var:HARDWARE_NAME}} is using the Microchip (ATMEL) {{#var:CPU}} CPU with an ARM926EJ CPU running at 400MHz

|PM9G45-top.png|
https://ronetix.at/product/pm9g45-cpu-module-with-atmel-at91sam9g45

Information about at91bootstrap, U-BOOT, Linux can be found here: 
https://www.linux4sam.org/bin/view/Linux4SAM/GettingStarted#Getting_Started_SAM9
|
}}

= Building at91bootstrap - second level bootloader for {{#var:HARDWARE_NAME}} =
This bootloader is based on https://github.com/linux4sam/at91bootstrap, branch at91bootstrap-3.x

==== Install and setup the cross-compiler and CPU architecture ====
$ cd ~
$ mkdir bin
$ wget http://download.ronetix.at/toolchains/crosstool-ng/arm-ronetix-eabi-11.1.0.tar.gz
$ tar xvfz arm-ronetix-eabi-11.1.0.tar.gz --directory bin
$ export ARCH={{#var:ARCH}}
$ export CROSS_COMPILE={{#var:CROSS_COMPILE}}

==== Clone the latest revision of the repo ====
$ git clone git@github.com:ronetix/at91bootstrap.git -b {{#var:BRANCH}}
$ cd at91bootstrap

==== Configure and build for booting of U-BOOT ====
$ make {{#var:DEFCONFIG_UBOOT_NAME}}
$ make

==== Configure and build for booting of Linux Kernel ====
$ make {{#var:DEFCONFIG_LINUX_NAME}}
$ make

= Build Results =
{| class="wikitable"
|-
! scope="col" | File Name
! scope="col" | Description
|-
| style="padding: 5px;"| binaries/at91bootstrap.bin
| style="padding: 5px;"| BIN image, should be programmed at address 0x0
|-
| style="padding: 5px;"| binaries/at91bootstrap.elf
| style="padding: 5px;"| ELF image used for JTAG debugging
|-
|}

= Building Buildroot - a simple Linux System for {{#var:HARDWARE_NAME}} =
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. 
The home page of Buildroot is: https://buildroot.org 
The Buildroot user manual can help you better understand how Buildroot works: http://www.buildroot.net/downloads/manual/manual.html 
The Buildroot for AT91SAM9G45 is maintained by Microchip: https://github.com/linux4microchip/buildroot-mchp 

Buildroot can build:
* at91bootstrap
* U-Boot
* Linux kernel
* A cross-compiler
* Root filesystems of different types

==== Prerequisites ====
Host build system should be a Linux system with necessary software installed: http://buildroot.uclibc.org/downloads/manual/manual.html#requirement 
In addition to these required packages, you should also install libssl-dev:
$ sudo apt-get install libssl1.0-dev
or, depending on your host distribution:
$ sudo apt-get install libssl-dev

==== Get sources ====
$ git clone https://github.com/ronetix/buildroot-mchp.git

$ cd buildroot-mchp
$ git checkout buildroot-at91-linux4microchip-2024.10 -b buildroot-at91-linux4microchip-2024.10

==== Build ====
$ make pm9g45_defconfig
$ make

Once compilation is done, the images have been generated in: ./output/image: 
* at91bootstrap.bin
* rootfs.tar
* u-boot.bin
* zImage
* pm9g45.dtb
* rootfs.ubi
* rootfs.ubifs

==== Customizing Buildroot ====
===== AT91Bootstrap =====
$ make at91bootstrap3-menuconfig

===== U-BOOT =====
$ make uboot-menuconfig

===== Linux Kernel =====
$ make linux-menuconfig

===== RootFs =====
$ make menuconfig

==== NAND Boot: Programming images ====
SAM-BA tool or PEEDI JTAG Flash Programmer can be used for programming the images into the NAND Flash. 
{| class="wikitable"
|-
! scope="col" | Address
! scope="col" | Image
! scope="col" | Note
|-
| style="padding: 5px;"| 0x00000000
| style="padding: 5px;"| boot.bin
| style="padding: 5px;"| at91bootstrap
|-
| style="padding: 5px;"| 0x00020000
| style="padding: 5px;"| u-boot.bin
| style="padding: 5px;"| U-BOOT, third level bootloader
|-
| style="padding: 5px;"| 0x00180000
| style="padding: 5px;"| pm9g45.dtb
| style="padding: 5px;"| Device tree for Linux Kernel
|-
| style="padding: 5px;"| 0x00200000
| style="padding: 5px;"| zImage
| style="padding: 5px;"| Linux Kernel
|-
| style="padding: 5px;"| 0x00800000
| style="padding: 5px;"| rootfs.ubi
| style="padding: 5px;"| Root file system
|-
|}

RNX-iMX93-OSM Yocto Linux

2024-08-28T09:39:45Z

Ilko: Remove the note about CSU resets because a workaround was implemented in U-BOOT

{{#vardefine:HARDWARE_NAME|RNX-iMX93-OSM}}
{{#vardefine:MACHINE_NAME|rnx-imx93-osm}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-OSM_top.png|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J31:1-2 !! J31:3-4 !! J31:5-6 !! J31:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-A (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,width=640,height=480" ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-OSM Yocto Linux

2024-08-12T14:31:38Z

Ilko: Add note about CPU revision

{{#vardefine:HARDWARE_NAME|RNX-iMX93-OSM}}
{{#vardefine:MACHINE_NAME|rnx-imx93-osm}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-OSM_top.png|thumb]]

== Important Note ==

The CPU modules currently available are equipped with the NXP i.MX93 Revision A0 CPU. 
Revision A0 has a bug, which causes unexpected reboots, the u-boot shows "Reset cause: CSU (0x200)" 
Unfortunately, there is no workaround. 
The bug will be fixed in the next Revision A1.


== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J31:1-2 !! J31:3-4 !! J31:5-6 !! J31:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-A (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,width=640,height=480" ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-OSM Yocto Linux

2024-08-12T14:28:45Z

Ilko: Camera test: change image format to 640x480

{{#vardefine:HARDWARE_NAME|RNX-iMX93-OSM}}
{{#vardefine:MACHINE_NAME|rnx-imx93-osm}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-OSM_top.png|thumb]]

== Important Note ==

The current available CPU Modules are assembled with CPU NXP i.MX93 Revision A0. 
Revision A0 has a bug, which causes unexpected reboots, the u-boot shows "Reset cause: CSU (0x200)" 
Unfortunately, there is no workaround. 
The bug will be fixed in the next Revision A1.


== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J31:1-2 !! J31:3-4 !! J31:5-6 !! J31:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-A (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! "video/x-raw,width=640,height=480" ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]

RNX-iMX93-OSM Yocto Linux

2024-06-27T08:09:08Z

Ilko: Fix a typo

{{#vardefine:HARDWARE_NAME|RNX-iMX93-OSM}}
{{#vardefine:MACHINE_NAME|rnx-imx93-osm}}
{{#vardefine:YOCTO_NAME|micledore}}
{{#vardefine:KERNEL_VER|6.1.55}}
{{#vardefine:UBOOT_VER|v2023.04}}
[[File:RNX-iMX93-OSM_top.png|thumb]]

== Overview ==
The Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems for embedded products, regardless of the hardware architecture. 
This article show how to build Yocto Image for {{#var:HARDWARE_NAME}} CPU module using: 
{| class="wikitable"
|-
!
! Linux Kernel
! U-BOOT
|-
| Yocto {{#var:YOCTO_NAME}}
| {{#var:KERNEL_VER}}
| {{#var:UBOOT_VER}}
|}

[https://www.yoctoproject.org/docs/ Learn more about Yocto]

== Setting Boot mode ==
{| class="wikitable"
|+ Boot mode setting on carrier board
|-
! BOOT !! J31:1-2 !! J31:3-4 !! J31:5-6 !! J31:7-8
|-
| Cortex-A55 Serial Downloader || close || open || open || open
|-
| Cortex-A55, eMMC || open || close || open || open
|}

== Terminal Setup ==
The carrier board connects the host PC using the micro-B USB connector (J3). 
Common serial communication programs such as Minicom, HyperTerminal, Tera Term, or PuTTY can be used. 
The {{#var:HARDWARE_NAME}} board uses the second port for the Arm Cortex-A cores console.

== Installing required packages ==

Please make sure your host PC is running Ubuntu 20.04+ 64-bit and install the following packages:
<pre>
$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
xz-utils debianutils iputils-ping libsdl1.2-dev xterm python-is-python3 lz4

$ sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev python-git-doc \
sed cvs subversion coreutils texi2html docbook-utils \
help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev \
mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils pv \
libncurses5 libncurses5-dev libncursesw5-dev libelf-dev zlib1g-dev bmap-tools
</pre>

More details about the Yocto Environment Setup can be found
[https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html on the Yocto official site]

== Download Yocto based on Freescale Community BSP ==

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

$ mkdir ~/bin
$ curl <nowiki>http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo</nowiki>
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH

$ mkdir ~/yocto-ronetix
$ cd ~/yocto-ronetix

* '''Download the Yocto repository''' 
$ repo init -u https://github.com/ronetix/imx-manifest -b imx-linux-mickledore -m imx-6.1.55-2.2.0.xml
$ repo sync

== Setup and build Yocto ==
* Setup first time:
$ MACHINE={{#var:MACHINE_NAME}} DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b build-{{#var:MACHINE_NAME}}

* or setup if already configured:
$ source setup-environment build-{{#var:MACHINE_NAME}}

* Build:
$ bitbake imx-image-core

''If the Ubuntu Terminal is crashed without any notification, see here: [[FAQ - Frequently Asked Questions]]''

=== Build Results ===
The resulted images are located in tmp/deploy/images/{{#var:MACHINE_NAME}}.

=== Booting Linux ===
This section describes how to copy the images (U-Boot, Linux kernel, device tree, and
rootfs) to the eMMC device on the module.

==== Universal update utility ====
The Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used to download images to devices on an i.MX board.

===== Downloading UUU =====
Download UUU version 1.5.21 or later from https://github.com/nxp-imx/mfgtools/releases

===== Write the WIC image into eMMC =====
Follow the instructions below:
* Connect a USB cable from a computer to the J9, port USB-A (Micro-AB) port on the carrier board for download link.
* Connect a USB cable from J3, port UART-DBG (Micro-AB) port to the computer for console output.
* Open a Terminal emulator program
* Set the boot mode to "Cortex-A55 Serial Downloader", see [[#Setting Boot mode]]

$ cd tmp/deploy/images/{{#var:MACHINE_NAME}}
$ uuu -b emmc_all imx-boot-{{#var:MACHINE_NAME}}-sd.bin-flash_singleboot imx-image-core-{{#var:MACHINE_NAME}}.wic.zst

==== Boot Linux ====
* set the boot mode to "Cortex-A55, eMMC", see [[#Setting Boot mode]]
* reset the board

== WiFi Setup ==
Scan for wireless networks:
$ ifconfig wlan0 up
$ iw dev wlan0 scan | grep SSID

Connecting to an Access Point:
$ wpa_passphrase <YourAP> <YourPassword> > /etc/wpa_supplicant.conf
$ wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

wait for:
$ wlcore: Association completed.

Get an IP via DHCP:
$ udhcpc -i wlan0
$ ifconfig

== Audio Test ==
List all sound cards:
$ aplay -L

Play a file:
$ aplay -D "sysdefault:CARD=wm8962audio" test.wav

List all sound controls:
$ amixer controls

Set Speaker Playback volume to max:
$ amixer cset numid=13 127

== Camera Test ==
Connect an OV5640 camera (PCAM 5C) to J21 on the carrier board. 
List capture media devices:
$ v4l2-ctl --list-devices
FSL Capture Media Device (platform:42800000.bus:camera):
/dev/media0

mxc-isi-cap (platform:4ae40000.isi:cap_devic):
/dev/video0

Take a single photo:
$ gst-launch-1.0 v4l2src num-buffers=1 ! jpegenc ! filesink location=test.jpg
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
[ 877.427496] mxc-mipi-csi2.0: format: 0x2008
[ 877.436706] bypass csc
[ 877.439078] input fmt YUV4
[ 877.441775] output fmt YUYV
[ 877.553965] dwc-mipi-csi2-host 4ae00000.csi: enter enable=1
Redistribute latency...
Got EOS from element "pipeline0".
Execution ended after 0:00:02.375455667
Setting pipeline to NULL ...
[ 879.341902] dwc-mipi-csi2-host 4ae00000.csi: enter enable=0
Freeing pipeline ...

== See also ==
* [[{{#var:HARDWARE_NAME}} Yocto Linux | Yocto Linux]]
* [[{{#var:HARDWARE_NAME}} Linux|Building Linux Kernel]]
* [[{{#var:HARDWARE_NAME}} U-Boot|Building U-Boot]]