summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* gcc: Separate binutils optionsAlejandro Enedino Hernandez Samaniego2019-12-096-77/+97
| | | | | | binutils options should not be tied to the gcc bbappends Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* gcc-cross-microblazeel: disable multilibAlejandro Enedino Hernandez Samaniego2019-12-091-0/+1
| | | | | | multilib builds are broken on microblaze, disable them Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* toolchain: add cortex-A9 options for gcc and binutilsAlejandro Enedino Hernandez Samaniego2019-12-093-0/+41
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* xilinx-standalone: Reorganize toolchain configure optionsAlejandro Enedino Hernandez Samaniego2019-12-097-161/+194
| | | | | | | | | | | | Previously the GCC configure options per MACHINE were inside the MACHINE.confs, this was wrong since the BSPs are contaminated by the DISTRO options and it should be the other way around. Avoid this contamination by using MACHINE OVERRIDES along with DISTRO OVERRIDES to get the required gcc and binutils configure options by the Xilinx SDK Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* xilinx-standalone: Add staticdev packages for newlib and libgloss to ↵Alejandro Enedino Hernandez Samaniego2019-12-091-0/+3
| | | | | | | | | | | dependencies For the cross canadian toolchain we need to have both the libc.a and libgloss.a. We add them to the LIBC_DEPENDENCIES which are wired in core to be added to the sdk via the TOOLCHAIN_TARGET_TASK variable Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* xilinx-standalone: switch override and appendAlejandro Enedino Hernandez Samaniego2019-12-094-8/+12
| | | | | | Instead of overriding the append, we need to append the override. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Adds MACHINE.conf containing default tune for Cortex A72Alejandro Enedino Hernandez Samaniego2019-12-091-0/+54
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* toolchain: Provide specific configuration for cross(-canadian) gcc and binutilsAlejandro Enedino Hernandez Samaniego2019-12-096-14/+149
| | | | | | | | | | | | | | | Since we need specific configuration for the SDK toolchain, we need to override the configuration coming from oe-core, this configuration needs to be per MACHINE. Use GCC_CONFIGURE_COMMON_XILINX_STANDALONE to define the default config shared amongst MACHINES, and use a GCC_CONFIGURE_<MACHINE> variable to append to this common configuration options on each MACHINE that we want. Use the same procedure for binutils Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Adds MACHINE.conf containing default tune for Cortex A53Alejandro Enedino Hernandez Samaniego2019-12-091-0/+14
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Adds MACHINE.conf containing default tune for Cortex R5Alejandro Enedino Hernandez Samaniego2019-12-091-0/+13
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* gcc-cross: Dont override EXTRA_OECONF unless DISTRO is xilinx-standaloneAlejandro Enedino Hernandez Samaniego2019-12-091-1/+1
| | | | | | | | | For the xilinx-standalone DISTRO, we need to keep some of the configure options that we lose when setting TCLIBC=newlib, although this should only happen when we are selecting xilnx-standalone as the DISTRO, otherwise, we would be overriding the configure options for GCC when this bbappend is parsed Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* qemu-*: Upgrade QEMU version 2.11 -> 4.1.5Sai Hari Chandana Kalluri2019-12-097-180/+15
| | | | | | Upgrade QEMU version from 2.11 -> 4.1.5 for 2020.1 release Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Move recipes to use _%.bb instead of versionSai Hari Chandana Kalluri2019-12-092-0/+0
| | | | | | | The changes in these recipes are version independent. Hence move them to _%.bb Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* tune-versal.inc: Rename include file from arch-armv8 to arch-armv8aSai Hari Chandana Kalluri2019-12-091-1/+1
| | | | | | Rename include file from arch-armv8.inc -> arch-armv8a.inc Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* vck190-versal.conf: Add deploy dir for psm and plm firmwareSai Hari Chandana Kalluri2019-12-091-0/+3
| | | | | | Add deploy dir path for plm and psm to support multiconfig builds. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* versal-mb.conf: Add machine configuration to support standalone buildSai Hari Chandana Kalluri2019-12-091-0/+11
| | | | | | | | for versal components like plm, psm-firmware versal-mb.conf supports versal SOC standalone component builds such as plm, psm-firmware. It provides required configuration to use microblaze toolchain needed for the builds.
* psm-firmware_2019.2.bb: Create psm-firmware recipe for standalone buildSai Hari Chandana Kalluri2019-12-091-0/+71
| | | | | | | | Create psm-firmware recipe for standalone build. PSM is a PS Management unit responsible for controlling the power islands, error processing and other control functions within the PS. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* plm_2019.2.bb: recipe to build plm standaloneSai Hari Chandana Kalluri2019-12-092-0/+74
| | | | | | | | Add recipe to build plm as standalone component. plm is platform loader and manager for versal devices.It performs boot and configuration of the Versal ACAP device. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* u-boot-xlnx: Add the platform init file for zcu216-zynqmpSai Hari Chandana Kalluri2019-12-091-0/+1
| | | | | | | Add u-boot-xlnx platform init file for zcu216-zynqmp machine Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* arm-trusted-firmware_2019.2.bbappend: Update compilation flagSai Hari Chandana Kalluri2019-12-091-0/+1
| | | | | | | | | This patch updates compilation flag for versal silicon. This flag is only needed for s80 device. Signed-off-by: Vineeth Chowdary <vineeth.chowdary@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* tune-versal.inc: Set default SOC_VARIANT = s80Sai Hari Chandana Kalluri2019-12-091-1/+1
| | | | | | Set default SOC_VARIANT for all versal machines as s80. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* vmk180-versal.conf: Add machine configuration for vmk180-versalSai Hari Chandana Kalluri2019-12-091-0/+37
| | | | | | | | | | | | Add machine configuration for vmk180-versal with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* v350-versal.conf: Enforce system.dtb name when using virtual/dtbSai Hari Chandana Kalluri2019-12-091-1/+1
| | | | | | | | Only if user uses virtual/dtb enforce system.dtb name as u-boot looks for system.dtb. Else user can specify a dtb with any name. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* vck-sc-zynqmp: Machine configuration for vck190 system controllerSai Hari Chandana Kalluri2019-12-091-0/+39
| | | | | | | | | | | Add machine configuration vck-sc-zynqmp for vck190 system controller with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* v350-versal.conf:Add versal board configurationMukund PVVN2019-12-091-0/+36
| | | | | | | | Add support to build images for v350-versal board configuration. V350 is a PCIe based card which has s80 Versal part. Signed-off-by: Mukund PVVN <mukundp@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* vc-p-a2197-00-versal.conf:Add versal Tenzing +SE1 board configurationManjukumar Matha2019-12-093-0/+175
| | | | | | | | | | | | | | | | | Add support to build images for vc-p-a2197-00-versal Tenzing board + SE1 board configuration vck190-versal.conf: Rename vc-e-a2197-00-versal to vck190-versal Rename vc-e-a2197-00-versal machine configuration to vck190-versal with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* pynq-ultra96-*: Add Ultra96 specific pynq example demo:Sai Hari Chandana Kalluri2019-12-096-0/+3835
| | | | | | | Add pynq-ultra96-helloworld and pynq-ultra96-bnn examples to demonstrate pynq framework on Ultra96-zynqmp boards Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* linux-xlnx.inc: Add MIPI kernel configuration for Ultra96Sai Hari Chandana Kalluri2019-12-093-0/+133
| | | | | | | Add MIPI kernel configuration for Ultra96 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* ultra96-zynqmp.conf: Include mipi as MACHINE_FEATURESai Hari Chandana Kalluri2019-12-091-1/+1
| | | | | | | | | | Ultra96 provides support for MIPI Interface. To support the interface, additional kernel, device tree modifications are required and must be enabled only when mipi is included as MACHINE_FEATURE Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* linux-firmware_git.bbappend: Add hook for wl18xx and bts fileManjukumar Matha2019-12-092-1/+29
| | | | | | | | | Ultra96 board needs the wl8xx and bts file to enable wireless and bluetooth on the TI part. This recipe uses linux-firmware and modify to include only wl18xx binaries. We also depend on TIInit_11.8.32 bts, add an append to fetch the right bt firmware Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* ultra96-zynqmp.conf: Add support for Ultra96 evaluation boardManjukumar Matha2019-12-091-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Ultra96™ is an Arm-based, Xilinx Zynq UltraScale+™ MPSoC development board based on the Linaro 96Boards specification. The 96Boards’ specifications are open and define a standard board layout for development platforms that can be used by software application, hardware device, kernel, and other system software developers. Ultra96 represents a unique position in the 96Boards community with a wide range of potential peripherals and acceleration engines in the programmable logic that is not available from other offerings More info: http://zedboard.org/product/ultra96 This patch adds machine configuration file for Ultra96 board with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider which will also generate SPL boot.bin While using SPL flow, you may need to provide additional hack to pass the PMU config object. This is similar to all ZU+ boards, due to gap in SPL flow unable to load PMU config object. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zcu216-zynqmp: Add support for zcu216 boardSwagath Gadde2019-12-091-0/+38
| | | | | | | | | | | Add machine configuration for zcu216 RFSoC board With required settings for board specific yocto variables needed for compilation of bootloader kernel and device tree -linux-xlnx is kernel provider -u-boot-xlnx is u-boot provider Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* newlib: export CC_FOR_TARGET as CCAlejandro Enedino Hernandez Samaniego2019-12-091-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Newlibs Makefiles use a variable CC_FOR_TARGET to build libraries for the TARGET machine (as opposed to CC_FOR_BUILD). We pass CC on our compile function, which is normally use to build, although in this case, the configure script is trimming CC and using simply gcc for the target machine, basically taking out the TUNE variables we pass in CC as well, such as march, mfloat-abi and such. This causes errors when building applications since CC will try to use hard floating point for example whereas the libc.a from newlib will contain libraries built with the defaults which could be soft floating point for example. e.g.: $ ${CC} a.c real-ld: error: a.out uses VFP register arguments, /usr/lib/libg.a(lib_a-stdio.o) does not. Analizing the object files we can see that one of them uses soft (library) and the other one uses hard floating point (program): $ readelf -A a.out | grep VFP Tag_ABI_VFP_args: VFP registers $ readelf -A usr/lib/libc.a | grep VFP Hence why the linker complains. Pass CC_FOR_TARGET with the contents of CC to override the trimming from the configure script and build newlib with the correct tune. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* zynqmp-pmu.conf: Update to Microblaze v11.0Alejandro Enedino Hernandez Samaniego2019-12-091-1/+1
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* zynqmp-pmu.conf: Upgrade tune to use Microblaze v10.0Alejandro Enedino Hernandez Samaniego2019-12-091-1/+1
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* image-types-xilinx-qemu.bbclass: Add sector size as 512KManjukumar Matha2019-12-091-3/+3
| | | | | | | Add sector size as 512K for larger SD, this is according to specifications Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* machine-xilinx-default.inc: Adding required dependencies to image_wicJaewon Lee2019-12-091-0/+4
| | | | | | | | | | | | | | | | | Adding base required dependencies to do_image_wic[depends] to make sure the common files required to boot.bin have been deployed in DEPLOYDIR before the do_image_wic task tries to use them. zynqmp/versal will add virtual/kernel, virtual/boot-bin, virtual/bootloader, and virtual/arm-trusted-firmware zynq will add everything but virtual/arm-trusted-firmware If you want to add other files to IMAGE_BOOT_FILES, aside from files deployed from virtual/kernel, virtual/boot-bin, virtual/bootloader, you may need to manually add the dependency to do_image_wic[depends] Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* run-postinsts: Pass the output of the scripts run to kmsgAlejandro Enedino Hernandez Samaniego2019-12-091-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | The run-postinsts scripts are meant to run during the first boot of the device. At boot time, though, some resources are not available(e.g. STDOUT), hence why applications that run at this point need to be correctly daemonized, if, for some reason a script that runs is not able to start as a daemon, proper behavior cannot be guaranteed. For some unknown reason to me at this point, the console behaves differenly on our devices depending on the chosen boot mode, for example, when using sdboot, scripts that echo something during boot show the messages properly on the boot log, but when using jtag as boot mode, this does not happen and the messages are not shown. One of such cases happens with update-alternatives, which expects STDOUT to be present, and if it fails to get a possible output file descriptor it exits ungracefully, causing the run-postinsts script to exit itself. Pass the the kmsg character device as the output for the scripts run by the run-postinsts script, not only to be able to print out the output of such script to the boot log, but also to pass a valid file descriptor to the scripts so they behave properly. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* flashstrip utility: Build and ship flash strip utility needed for qemuJaewon Lee2019-12-092-0/+201
| | | | | | | | | | | | | | | | | | | Building and shipping flash strip utility needed for qemu: flash_strip flash_strip_bw flash_unstrip flash_unstrip_bw From the QEMU flash strip utilities wiki: QSPI Controllers implement byte/bit strip logic. Which mean's when an image is flashed, its stripped bit/byte wise into two flashes. User can use u-boot or Linux apps to flash the image after boot. By using flash strip utilities, we can flash the image without using u-boot. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* bootgen_1.0.bb: Adding initial bootgen recipe to build bootgenJaewon Lee2019-12-091-0/+31
| | | | | | | | | | | | Building and installing bootgen, a tool that lets you stitch binary files together and generate device boot images. native and nativesdk classes are inherited as well to allow native version of bootgen to be built and to allow packaging of bootgen into an sdk if added into the dependency. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* meta-xilinx-pynq: Add layer to support PYNQManjukumar Matha2019-12-0915-0/+409
| | | | | | | | | | | | | | | | | This layer collects Yocto recipes required to build and run PYNQ based examples using jupyter-notebooks on Zynq and ZU+ SoC's. PYNQ is an open-source project from Xilinx that makes it easy to design embedded systems with Zynq All Programmable Systems on Chips (APSoCs). Using the Python language and libraries, designers can exploit the benefits of programmable logic and microprocessors in Zynq to build more capable and exciting embedded systems. See https://github.com/Xilinx/PYNQ for more details and examples Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Peter Ogden <ogden@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zynq-generic.conf: Add qemu wiring to generic confManjukumar Matha2019-12-091-0/+3
| | | | | | Add qemu wiring to generic conf Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zcu1285-zynqmp.conf: Update UBOOT_MACHINEMukund PVVN2019-12-091-1/+1
| | | | | | | | | uboot config file is renamed from "xilinx_zynqmp_zc1275_revB_defconfig" to "xilinx_zynqmp_zcu1275_revB_defconfig", updated UBOOT_MACHINE to reflect the change Signed-off-by: Mukund PVVN <mukundp@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zcu1275-zynqmp.conf: Rename zc1275 to zcu1275Mukund PVVN2019-12-091-4/+4
| | | | | | | | | zc1275 is renamed to zcu1275. All the references to zc1275 is renamed to zcu1275, this patch addresses machine conf name change and other references to zcu1275 Signed-off-by: Mukund PVVN <mukundp@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* machine-xilinx-default.inc: Add qemu-xilinx-helper-native as preferredManjukumar Matha2019-12-091-0/+3
| | | | | | | | | | | provider Python3 package from OE-core depends on qemu-helper-native, to meet this dependency use qemu-xilinx-helper-native as preferred provider. In addition this helps the sstate-cache to be similar across generic machines and evaluation boards. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zynq/zynqmp confs: Adding boot.scr to IMAGE_BOOT_FILESJaewon Lee2019-12-0910-0/+10
| | | | | | | | Adding boot.scr to IMAGE_BOOT_FILES so boot.scr is included in the wic sd card generation, if wic image generation is enabled Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-zynq-scr: Setting sd as default bootmode for versalJaewon Lee2019-12-091-0/+4
| | | | | | | | | Setting sd as default bootmode for versal and adding default boot.scr for versal. NOTE: the difference between zynqmp and versal boot.scr template is versal doesn't have 'earlycon' Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-zynq-scr: reworking boot.scr recipe to work for zynq and zynqmpJaewon Lee2019-12-0916-7/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | Separating out sample boot.cmd file for the three supported arch (zynq, zynqmp, versal), Updating devicetree, kernel, ramdisk load addresses for zynq, and dynamically setting DEVICE_TREE_NAME to either system.dtb or kernel dtb, depending on if dtg is used or not. This u-boot-zynq-scr implementation is put in to set the default boot and boot quicker than having to wait for the distro_bootcmd to cycle to the correct boot medium. For example, zynq arch has boot_targets set to "mmc mmc0 qspi usb0 pxe dhcp xilinx" and it takes about 30 seconds to try the 'xilinx' target which will run the correct bootargs. To use the boot.scr file, zynqmp boards must have BOOT.bin, Image, system.dtb, and boot.scr in the boot partition and a rootfs extracted in the second partition. Zynq boards must have BOOT.bin, uImage, system.dtb, boot.scr, and uramdisk.image.gz in the boot partition. (uramdisk.image.gz is the ${IMAGE}.cpio.gz.u-boot in deploy directory) Adding u-boot-zynq-scr dependency to all zynq and zynqmp machine confs. Conditionally adding system.dtb to IMAGE_BOOT_FILES for zcu102 to support boot.scr in qemu flow. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-zynq-scr: Add pxeboot support in u-boot-scrSwagath Gadde2019-12-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds pxeboot support for versal platform by adding default config file in pxelinux.cfg directory with below minimal mandatory information forbooting. label <name> - begin a label definition. labels continue until a command not recognized as a label command is seen, or EOF is reached. kernel <path> - if this label is chosen, use tftp to retrieve the kernel at <path>. it will be stored at the address indicated in the kernel_addr_r environment variable, and that address will be passed to bootm to boot this kernel. fdt <path> - if this label is chosen, it will load dtb at fdt_addr and that location of a fdt_addr will be passed to bootm when booting a kernel. Generally after u-boot bootup in jtag mode after autoboot time it scans usb and then ethernet and checks for pxelinux.cfg directory with default config file, if found it will load and boot linux. Steps to test: 1.acquire the board 2.in systest point the tftpd <path> 3.open serial terminal and connect com0 4.load the pdi from xsdb 5.stop at uboot promt and set serverip 6.dhcp 7.pxe get 8.pxe boot Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-xlnx_2019.2.bb: Rename zc1275 to zcu1275 board nameSai Hari Chandana Kalluri2019-12-091-2/+2
| | | | | | | | | | The zc1275-zynqmp board name is renamed to zcu1275-zynqmp. All references in u-boot repository have been modified to zcu1275 from zc1275. This patch updates the uboot platform init to use the zcu1275 name change Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-08 16:03:28 +0000