HyperFlash is supported under MTD framework and U-Boot’s standard MTD commands can be used to access HyperFlash HyperFlash on TI’s J721E EVM is connected to HyperBus Memory Controller that supports memory mapped IO access to flash. But Hyperbus operates at very high frequencies. Since Hyperbus is x8 DDR bus, its equivalent to x16 parallel NOR flash wrt bits per clk. HyperFlash follows CFI AMD/Fujitsu Extended Command Set (0x0002) similar to that of existing parallel NORs. HyperFlash is a NOR flash based device storage over HyperBus. At bus level, it follows a separate protocol described in HyperBus specification. It uses ChipSelect lines to select b/w multiple slaves. Its a 8-bit data bus (DQ) with Read-Write Data Strobe (RWDS) signal and either Single-ended clock(3.0V parts) or Differential clock (1.8V parts). HyperBus is Low Signal Count, High Performance Double Data Rate (DDR) Bus interface between a host system master and one or more slave interfaces. Setenv bootcmd 'run init_mmc run init_icssg2 run get_kern_net run get_fdt_net run get_overlay_net run run_kern' Setenv loadaddr 0x8a000000 setenv firmware_file am65x-rtu0-prueth-fw.elf run get_firmware_mmc rproc load 9 0x8a000000 5676 \ Setenv firmware_file 'am65x-pru0-prueth-fw.elf' run get_firmware_mmc rproc load 8 0x89000000 13040 rproc start 8 \ Setenv init_icssg2 'setenv ethact pruss2_eth setenv autoload no rproc init setenv loadaddr 0x89000000 \ Setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' Setenv get_fdt_net 'run start_icssg2 tftp $' Setenv firmware_dir '/lib/firmware/ti-pruss' Setenv stop_icssg2 'rproc stop 8 rproc stop 9' Setenv start_icssg2 'rproc start 8 rproc start 9' Variable to that of the tftp server used in the setup. User needs to customize the serverip and bootdir env The firmware is loaded from the rootfs/lib/firmware/ User needs to load and run pru/rtu firmware on ICSSG2 to do This port is marked as Eth0 on the AM65xīase board. Only PRU-ICSSG port of the base board (ICSSG2) On AM65x GP and IDK boards, Linux kernel can be booted over PRU-ICSSGĮthernet port as well. Important variables in AM57x/DRA7x are rootpath and nfsopts, and Then in turn printenv other sub-sections of the command. For theĮxact details of each use printenv on the netboot variable and In KS2 EVMs that will automatically load the kernel and boot. There is a boot command called netboot in AM EVMs and boot=net Within the default environment for each board that supports networking If using ISC dhcpd an example host entry would look like this:ģ.1.1.4.6. BoardĭM814x ROM (PG1.0) or AM335x ROM (PG2.0 and later) Spl/u-boot-spl.bin and u-boot.img files to boot. Vendor-class-identifier DHCP field is filled out by the ROM and the In addition, the DHCP server is needed to reply to the target In some cases, a special build of U-Boot may be In some cases we support loading SPL and U-Boot over the network because Use the following table to determine what defconfig to use to configureģ.1.1.4.1. However first configure the build for the board you are working with. Information are provided to show how to use a specific feature, whenįinally, please note that not all boards have all of the interfacesīuilding of both u-boot and SPL is done at the same time. Servers is also outside of the scope of this document, but snippets of Linux Kernel has already been built (or has been provided) as well as anĪppropriate filesystem image. Serial port for the board has been configured. We assume that a GCC-based toolchain has already been installed and the
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |