yenero.blogg.se

Setenv loadaddr 0x89000000 setenv firmware_file am65x-rtu0-prueth-fw.elf run get_firmware_mmc rproc load 11 0x89000000 5676 \ Setenv firmware_file 'am65x-pru0-prueth-fw.elf' run get_firmware_mmc rproc load 10 0x80000000 13040 rproc start 10 \ Setenv init_icssg2 'setenv ethact pruss2_eth setenv autoload no rproc init setenv loadaddr 0x80000000 \ Setenv overlay_files 'k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo' Setenv get_fdt_net 'run start_icssg0 tftp $' Setenv firmware_dir '/lib/firmware/ti-pruss' Setenv stop_icssg0 'rproc stop 2 rproc stop 3' Setenv start_icssg0 'rproc start 2 rproc start 3' User needs to customize the serverip and bootdirĮnv variable to that of the tftp server used in the setup. For more information on using rproc/RemoteProcĪ sample U-Boot env script for AM65x EVM/IDK is shown below for ICSSG0, The firmware is loaded from the rootfs/lib/firmware/ti-pruss/įolder for this purpose. To load and run pru/rtu firmware on ICSSG using env script as shownīelow before doing network operations such as dhcp, tftp over ICSSG First port is marked as Eth0 on base board (ICSSG2),Įth0 (ICSSG0) and Eth2 (ICSSG1) on IDK Application board. Second port instead of first port and rebuild u-boot images using the Second port (MII port 1), user needs to edit the DTS file to enable (MII port 0) of ICSSG0, ICSSG1 and ICSSG2 are enabled. In the release u-boot image, only first port 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,Īnd tftp_root and nfs_root in K2H/K/E/L/G. 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 Requests DMSC to get these services done as shown in the above diagram.ģ.1.1.4.6. Here DMSC acts as master and provides all the critical services. Use the following table to determine what defconfig to use to configure However first configure the build for the board you are working with. Building of both u-boot and SPL is done at the same time.