This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Keystone-rapidio boot messages

Hello,


I am following the instructions http://processors.wiki.ti.com/index.php/MCSDK_HPC_3.x_MPI_over_SRIO#Clone_Linux_Kernel to build and configure a kernel. I've completed the instructions and noticed my console boot messages report failures for initialization of rapidio. Are these errors to be expected?

The EVM is on a desk, not connected to a switch or any other rapidio hardware.

This is a snippet of my console output:

[   78.388691] keystone-netcp 2090000.netcp: Created interface "eth0"
[   78.393746] keystone-netcp 2090000.netcp: dma_chan_name nettx0
[   78.399140] keystone-netcp 2090000.netcp: Created interface "eth1"
[   78.404202] keystone-netcp 2090000.netcp: dma_chan_name nettx1
[   78.409591] keystone-netcp 2090000.netcp: Created interface "eth2"
[   78.414656] keystone-netcp 2090000.netcp: dma_chan_name nettx2
[   78.420045] keystone-netcp 2090000.netcp: Created interface "eth3"
[   78.425109] keystone-netcp 2090000.netcp: dma_chan_name nettx3
[   78.512666] keystone-netcp 2f00000.netcp: Created interface "eth4"
[   78.517721] keystone-netcp 2f00000.netcp: dma_chan_name xgetx0
[   78.522793] keystone-netcp 2f00000.netcp: Created interface "eth5"
[   78.527857] keystone-netcp 2f00000.netcp: dma_chan_name xgetx1
[   78.532706] keystone-netcp 2090000.netcp: could not find interface 2 node in device tree
[   78.539326] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
[   78.546018] keystone-netcp 2090000.netcp: could not find interface 3 node in device tree
[   78.552636] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
[   78.559333] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
[   78.565955] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
[   78.572706] keystone-rapidio 2900000.rapidio: KeyStone RapidIO driver v1.2
[   78.578338] keystone-rapidio 2900000.rapidio: initializing 5.00 Gbps interface with port configuration 15
[   83.755607] keystone-rapidio 2900000.rapidio: initialization of SerDes failed
[   83.761440] keystone-rapidio 2900000.rapidio: initialization of SRIO hardware failed
[   83.767778] keystone-rapidio: probe of 2900000.rapidio failed with error -1
[   83.774303] keystone-dwc3 2690000.dwc: usbss revision 47914300
[   83.779097] keystone-dwc3 2690000.dwc: mapped irq 425 to virq 608

My k2hk-evm.dts is attached (changed extension to txt to attach.) 7624.k2hk-evm.txt

My u-boot env:

U-Boot 2013.01 (Apr 24 2014 - 02:06:05)

I2C:   ready
Detected SO-DIMM [SQR-SD3T-2G1333SED]
DRAM:  2 GiB
NAND:  512 MiB
Net:   TCI6638_EMAC, TCI6638_EMAC1, K2HK_EMAC2, K2HK_EMAC3
Hit any key to stop autoboot:  0 
TCI6638 EVM # printenv
addr_fdt=0x87000000
addr_fs=0x90000000
addr_kern=0x88000000
addr_mon=0x0c5f0000
addr_ubi=0x82000000
addr_uboot=0x87000000
addr_uinitrd=-
args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1 rio-scan.static_enum=1 rio-scan.scan=0
args_net=setenv bootargs ${bootargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp
args_ramfs=setenv bootargs ${bootargs} earlyprintk rdinit=/sbin/init rw root=/dev/ram0 initrd=0x802000000,30M
args_ubi=setenv bootargs ${bootargs} rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048
args_uinitrd=setenv bootargs ${bootargs} earlyprintk rdinit=/sbin/init rw root=/dev/ram0
baudrate=115200
boot=net
bootargs=earlyprintk rdinit=/sbin/init rw root=/dev/ram0 initrd=0x802000000,9M rproc_mem=16M@0xC3000000
bootcmd=run init_${boot} get_fdt_${boot} get_mon_${boot} get_kern_${boot} run_mon run_kern
bootdelay=3
bootfile=uImage-RAP
burn_ubi=nand erase.part ubifs; nand write ${addr_ubi} ubifs ${filesize}
burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}
ethact=TCI6638_EMAC
ethaddr=c4:ed:ba:aa:0a:01
fdt_high=0xffffffff
get_fdt_net=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}
get_fdt_ramfs=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}
get_fdt_ubi=ubifsload ${addr_fdt} ${name_fdt}
get_fdt_uinitrd=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}
get_fs_ramfs=dhcp ${addr_fs} ${tftp_root}/${name_fs}
get_fs_uinitrd=dhcp ${addr_fs} ${tftp_root}/${name_uinitrd}
get_kern_net=dhcp ${addr_kern} ${tftp_root}/${name_kern}
get_kern_ramfs=dhcp ${addr_kern} ${tftp_root}/${name_kern}
get_kern_ubi=ubifsload ${addr_kern} ${name_kern}
get_kern_uinitrd=dhcp ${addr_kern} ${tftp_root}/${name_kern}
get_mon_net=dhcp ${addr_mon} ${tftp_root}/${name_mon}
get_mon_ramfs=dhcp ${addr_mon} ${tftp_root}/${name_mon}
get_mon_ubi=ubifsload ${addr_mon} ${name_mon}
get_mon_uinitrd=dhcp ${addr_mon} ${tftp_root}/${name_mon}
get_ubi_net=dhcp ${addr_ubi} ${tftp_root}/${name_ubi}
get_uboot_net=dhcp ${addr_uboot} ${tftp_root}/${name_uboot}
has_mdio=0
init_net=run set_fs_none args_all args_net
init_ramfs=run set_fs_none args_all args_ramfs get_fs_ramfs
init_ubi=run set_fs_none args_all args_ubi; ubi part ubifs; ubifsmount boot
init_uinitrd=run set_fs_uinitrd args_all args_uinitrd get_fs_uinitrd
initrd_high=0xffffffff
ipaddr=dhcp
mem_lpae=1
mem_reserve=512M
mtdparts=mtdparts=davinci_nand.0:1024k(bootloader)ro,512k(params)ro,129536k(ubifs)
name_fdt=RAP-k2hk-evm.dtb
name_fs=arago-console-image.cpio.gz
name_kern=uImage-RAP
name_mon=skern-keystone-evm.bin
name_ubi=keystone-evm-ubifs.ubi
name_uboot=u-boot-spi-keystone-evm.gph
name_uinitrd=uinitrd.bin
nfs_options=v3,tcp,rsize=4096,wsize=4096
nfs_root=/var/lib/nfsdir/active
no_post=1
run_kern=bootm ${addr_kern} ${addr_uinitrd} ${addr_fdt}
run_mon=mon_install ${addr_mon}
serverip=10.144.186.7
set_fs_none=setenv addr_uinitrd -
set_fs_uinitrd=setenv addr_uinitrd ${addr_fs}
stderr=serial
stdin=serial
stdout=serial
tftp_root=release
ver=U-Boot 2013.01 (Apr 24 2014 - 02:06:05)

Environment size: 3144/262140 bytes

  • Hi, Ralph,

    Let me build it to see if I get the same.

    Rex

  • Hi, Ralph,

    I booted up the EVM using the srio image without any issues. You mentioned that your EVM is not connected to a switch. Do you mean not connected to an Ethernet switch? if that is the case, how does the net boot work to get the kernel image from tftp server and getting the kernel booting up? There are several things I noticed that you have modified in both u-boot environment and dts file. 1) args_net does not indicate how the kernel will get the IP address, not configured for either dhcp or static IP. 2) ipaddr should be an IP address used by uboot. dhcp is not an IP address. 3) dts file has quite a few changes other than what is in the docuement. Could you take the dts file from v3.8/rio-dev-dio and only added those mentioned in the document, then give it a try?

    Rex

  • Hi Rex,
    I've since learned that the srio errors are expected since the EVM is not in a uTCA chassis with a srio switch.
    To answer your questions:
    1)    Args_net does show ip = dhcp, it scrolled off to the right of the screen
    2)    Not sure what’s going on with the ipaddr value. The system does tftp boot with an nfs mounted filesystem.
    3)    That’s what I did.
    Would like to close this question since I’ve learned that the srio errors are due to our hardware setup.