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.

SRIO in uboot not working in EVMK2H kit

Hi,

       In EVMK2H evaluation kit, we are not able to read srio registers in uboot. when we are trying to access 0x0290b000 address we are getting value as 0 instead of vendor ID. (other register also getting the same value)

Also we are not finding any PCI driver for this processor.

Please help me on this.

P.S: We are using keystone-linux-uboot-2013.01.

Regards,

Sivanantham

  • Hi,

    Please ensure to test with pre-built u-boot binary of Processor SDK or MCSDK and let us know if you have issues. Please provide the log of error message.

    We recommend you to work on latest Processor SDK for development. Please find the download and user guide below my signature.

    Also PCIe driver support is only available in linux (not on u-boot)for this device. Please refer below wiki page for more information,

  • Hi,

    We are using "K2_UBOOT_2013_01_15.07_01" tagged uboot from ti git repository as suggested in wiki page.

    Keystone_rio.c,keystone_rio.h (rio driver) files are not present in latest processor sdk (keystone_serdes.c is present in /drivers/soc/keystone).

    FYI, processor sdk Uboot 2015.07 which is not booting through uart (uboot.uart) or thro ccs (uboot.bin).

    Kindly clarify on this.

    Regards,

    Sivanantham

  • We are using "K2_UBOOT_2013_01_15.07_01" tagged uboot from ti git repository as suggested in wiki page.

    Keystone_rio.c,keystone_rio.h (rio driver) files are not present in latest processor sdk (keystone_serdes.c is present in /drivers/soc/keystone).

    Yes. Your observation is correct. In processor sdk release,  keystone_rio.c and keystone_rio.h files were not available(drivers/rapidio/) as they are not supported by TI however these files were present on MCSDK release u-boot tag "K2_UBOOT_2013_01_15.07_01".  The list of driver support is documented in u-boot section in mcsdk exploring wiki.

  • FYI, processor sdk Uboot 2015.07 which is not booting through uart (uboot.uart) or thro ccs (uboot.bin).

    1. Please confirm whether the pre-built binary (u-boot.bin) of processor sdk works on your EVM or not. 

    2. Please provide the steps followed when the issue occurs(both UART or CCS boot).

    Thank you.

  • Hi,
    
    Please find the steps i have followed in EVMK2H kit.
    
    Uboot compilation
    
    -------------------------
    
    PATH=$PATH:/home/crypto/Desktop/gcc-linaro-4.9-2015.02-3-x86_64_arm-linux-gnueabihf/bin
    
    export ARCH=arm
    
    export CROSS_COMPILE=arm-linux-gnueabihf-
    
    make distclean
    
    make k2hk_evm_defconfig
    
    make
    
    Conversion of u-boot.bin to u-boot.uart (As per ti wiki page)
    
    dd if=/dev/zero of=4k_zeros bs=4096 count=1
    
    cat 4k_zeros u-boot.bin > u-boot.uart
    
    U-boot.uart Loading in Kit
    ------------------------------------
    1.No boot mode is set in Kit thro EVM switches(DSP Noboot mode). then
    
    2.In Hyper terminal bootmode #4 (UART),reboot
    
    3.u-boot.uart is transfered to Kit thro XMODEM setting in Hyper terminal
    
    Loading u-boot.bin thro CCS
    
    ---------------------------------------
    1.Thro Script console,u-boot.bin is loaded in ARM core.The following script is run
    in script console.
    
    loadJSFile
    "E:\TI_PRJ\Datasheets\Processor_TI\mcsdk\mcsdk_linux_3_01_03_06\host-tools\loadlin\loadlin-evm-uboot.js"
    
    SPI Flashing and Load (Single stage loader)
    
    -------------------------------------------------------------
    tftp $addr_uboot $serverip:u-boot.bin
    
    fmtimg spi 0x0c001000 /*After executing the command it ll give fmt_img_size*/
    
    sf probe
    
    sf erase 0 0x60000 /*Nearest value to sizeof(uboot.bin)*/
    
    sf write $addr_uboot 0 0x5ab04 (fmt_img_size)
    
    In EVM Kit
    
    -------------
    1.No boot mode is set in Kit thro EVM switches (DSP No boot mode).
    2.In Hyper terminal bootmode #2 (SPI),reboot
    
    In all the cases "K2_UBOOT_*" uboot image running in the Kit whereas PSDK image is
    not coming up.
    
    Let us know if any issues are there.
    
    Regards,
    
    Sivanantham
    
  • Hi Sivanantham,

    Thank you for the post. I request you to follow below thread for response,

    We recommend you to create new thread for new issues instead of following on old threads or closed threads.

    Thank you.