PetaLinux Tools
TracNav menu
Page contents
List and usage of tools.
petalinux-copy-autoconfig
Usage:
petalinux-copy-autoconfig OPTIONS [projectfile]
Required:
Optional parameters (and default value):
-p platform
The name of the platform. Auto-detect if not specified.
-v vendor
Vendor name for platform. Auto-detect if not specified.
-k kernel_ver (2.4 / 2.6)
Force kernel version to target. Auto-detect if not specified
Not recommended
-noupdateconfig
Don't update kernel configuration settings (not recommended).
projectfile
Filename of the EDK platform studio project (system.xmp).
If .xmp suffix is missing it will be inferred.
If a path prefix is specified, the full path and name of the
XMP file must be specified.
Options -p and -v must be specified together. If either is
missing, then an autodetect is attempted.
petalinux-jtag-boot
Usage : petalinux-jtag-boot [ -p projfile[.xmp] ] -t <target> -a <startaddr> [-c cmdline] -i <imagefile> [-x xmd_connect_args] \
[ -t <target> -a <startaddr> [-c cmdline] -i <imagefile> ] \
[ -t <target> -a <startaddr> [-c cmdline] -i <imagefile> ] ...
Boot a MicroBlaze / Linux system via JTAG (using Xilinx XMD utility)
-p project - specify EDK project file (system.xmp)
-t target - specify target CPU (0 to N-1)
-a startaddr - Load / start address of kernel image
-c cmdline - Kernel command line (use quotes for multiple parameters)
-i imagefile - uClinux-dist type image.bin (or linux.bin)
-x xmd_connect_args - XMD connect argument sting for specific XMD connection options
petalinux-new-app
Usage:
petalinux-new-app [-force] app-name
Required:
app-name The name of the new application
Optional:
-force Force overwriting an existing application directory
petalinux-new-platform
Usage:
petalinux-new-platform [-force] [-k kernelver ] [-v vendor] -p platform
Required:
-p platform The name of the new platform
Optional parameters (and default value):
-v vendor Vendor name for new board (PetaLogix)
-k kernelver Kernel version '2.4' or '2.6' (2.6)
-force Force overwriting an existing platform if required (no).
petalinux-reloc-blob
Usage:
petalinux-reloc-blob [-l default-load-addr] -i payload.elf -o blobname
Description:
Generate a PIC executable blob that copies the payload to its
linked address and executes it. The blob itself may be loaded
to any physical address and executed, provided that
1) The payload's linked address is writeable
2) The blob's and payload's addresses don't overlap
Generates blobname.[srec|elf|bin] files into the working directory
Required:
-i payload[.elf]
the fully relocated ELF file that will be the payload.
-o blobname
basename of the resulting blob files.
Optional:
-l default-load-addr
address at which FS-boot will load the stub+payload
petalinux-remove-platform
Usage:
petalinux-remove-platform [-k kernelver] -v vendor -p platform
Required:
-p platform The name of the platform
-v vendor The vendor name for the platform
Optional:
-k kernelver Specify kernel version (2.4/2.6) (default 2.6)
petalinux-boot-prebuilt
Usage:
petalinux-boot-prebuilt -p platform_name -k kernel_version
[-l boot_level ]
Required:
-p platform_name. Supported platform name:
Xilinx-ML401 - Xilinx ML401 Platform
Xilinx-Spartan3E500-RevC - Xilinx Spartan 3E500 Rev C Platform
Xilinx-Spartan3E1600-RevA - Xilinx Spartan 3E1600 Rev A Platform
-k kernel_version. Supported kernel version [ not required for boot_level 2 and below ]:
2.4 - uClinux 2.4 kernel
2.6 - uClinux 2.6 kernel
Optional parameters (and default value):
-l boot_level [1 to 4].
1 - Boot FS-Boot only
2 - Boot U-Boot only
3 - Boot Linux Kernel only
4 - Boot platform with complete board bring-up. '''Writes data to Flash memory'''
Default is -l 3.
