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.

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

Other Parts Discussed in Thread: TCI6638K2K

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,

    This thread has been split from below thread,

    We will get back to with our response. Thank you for your patience.

  • Hi Sivanantham,

    [Note: Please take the pre-built u-boot.bin as your first attempt.You can ignore the MCSDK version here and use processor SDK and follow the steps]

    The following are the steps to get the u-boot prompt on K2H EVM through CCS which is the easiest method.

    I have attached the necessary screenshots for your reference.

    1. Flashing and booting u-boot.bin

    ======================

    The u-boot.bin can be flashed into the EVM through CCS method.

    1.1 HW Set up on K2HK EVM:

    ==================

       In EVMK2hk, rev 3.0 board, you will find two FTDI -USB connectors. The top one is for the emulator (CCS) and

       the bottom one is for opening two channels ( one for displaying the u-boot messages and another one is for BMC commands)

       Connect the USB cables between your host PC where in the CCS is installed and the K2HK EVM. One for Emulation and the other one for receiving the u-boot messages and the BMC commands.

       To flash the u-boot.bin,  EVM dip switches are to be set for no-boot mode

       SWITCH Pin1 Pin2 Pin3 Pin4

       SW1 Off Off Off On

    1.2 CCS set up and u-boot flashing Steps to get u-boot prompt.

    ==================================================

       In CCS, navigate to view--> Target configuration--> create new target configuration file --> and open the file.

       Select the XDS2xx USB emulator as "connection" and "TCI6638K2K" as board/device, save and test connection.

       Now, launch the target configuration file and open -->view scripting console, you will get a console prompt with "js:>"

       You might have already installed the MCSDK at windows and you will find the js file at C:/ti/mcsdk_linux_3_00_03_15/host-tools/loadlin/loadlin-evm-uboot.js

       Connect the coretexA15_1 to the target.

       In the scripting console, use loadJSfile command to load the "loadlin-evm-kern.js" file. Before loading, openup the js file in CCS and modify the

       paths of u-boot, kernel like below

       PATH_LOADLIN = <path of release folder>/host-tools/loadlin

       var pathUboot = PATH_LOADLIN + "/u-boot-keystone-evm.bin";

       var pathSKern = PATH_LOADLIN + "/skern-keystone-evm.bin";

       loadJSFile C:\ti\mcsdk_linux_3_00_03_15\host-tools\loadlin\loadlin-evm-uboot.js

       ----> Observe a progress bar which will complete the loading of images given in the "loadlin-evm-uboot.js"

       ----> Hit the play button in CCS and in the tera term observe the output messages from "u-boot.bin" image ( flashed through CCS just now) and the u-boot prompt like below.

  • Hi,

          I am able to load u-boot.bin of  "K2_UBOOT_2013_01_15.07_01" tagged from ti git repository and it is working fine.

    This uboot.bin is loaded thro CCS (loadjs file in script console) and uboot.uart. But latest PSDK uboot.bin image is not

    coming up. I am not seeing any single print.

    Now I think the topic is deviated because i have asked SRIO is not working in K2_UBOOT_2013_01_15.07_01" tagged uboot. When i was trying to read SRIO register thro uboot i am getting as 0x0.Eg: 0x0290b000 i should get vendor id. But i m getting 0x0

    Please refer the below thread

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/504171/1837533#1837533

    Kindly suggest on this.


    Regards,

    Sivanantham

    K2_UBOOT_2013_01_15.07_01" tagged

  •  Hi,

    I am able to load u-boot.bin of  "K2_UBOOT_2013_01_15.07_01" tagged from ti git repository and it is working fine.

    This uboot.bin is loaded thro

    • CCS (loadjs file in script console)
    • uboot.uart(thro uart by setting bootmode #4 in BMC)
    • SPI boot (setting bootmode #2 in BMC)
    • Nand boot(*.gph).(setting bootmode #0 in BMC

    But latest PSDK uboot.bin image is not coming up in the above said method. I am not seeing any single print.

    Now I think the topic is deviated because i have asked SRIO is not working in K2_UBOOT_2013_01_15.07_01" tagged uboot. When i was trying to read SRIO registers thro uboot (thro md command in uboot) i am getting all registers as 0x0.

    Eg: md 0x0290b000 0x100 i should get vendor id. But i m getting all registers 0x0

    Please refer the below thread

    Sivanantham

  • Dear Sivanantham,
    1) Not able to read SRIO registers
    2) UART u-boot is not working
    Right ?


    Now I think the topic is deviated because i have asked SRIO is not working in K2_UBOOT_2013_01_15.07_01" tagged uboot. When i was trying to read SRIO registers thro uboot (thro md command in uboot) i am getting all registers as 0x0.

    Able to get the vendor ID in CCS memory window for any SRIO example running?

    Will try to run the UART based u-boot binary and update you.
  • Hi,

                 I am able to get the vendor ID as 0x30  at 0x0290b000 thro CCS SRIO loop back example project.

    But not able to read the srio register thro u-boot. FYI, I am using keystone_rio.c file for enabling PSC,Block enable,global block enable.

    My doubt is, any special step is required to read srio registers from ARM core? Since In CCS, DSPs alone is connected.Arm is in doconnected state.

    Kindly help on this.

    Regards,

    Sivanantham

  • Hi,
    1.Now i am able to read SRIO vendor id thro u-boot after modifying the serdes settings as per SRIO loop back example project. For serdes settings i have referred csl_wiz8_sb_refclk156p25MHz_20bit_5Gbps.c file.

    But i am seeing lot of reserved memory (as per user guide spruho3a) is written in csl_wiz8_sb_refclk156p25MHz_20bit_5Gbps.c (in loopback ccs example project).

    Example :Register offsets 0x000C to 0x00E8 is reserved in PHY-A 4 lane memory map but values are written in 0x0060,0x0064 register offsets.

    Can you please clarify on this?

    2.The above said is working in K2_UBOOT_2013_01_15.07_01 tagged uboot.The latest Proc SDK 2.0.2.11 u-boot is not working.

    Kindly comment on this also.

    Regards,
    Sivanantham
  • Hi Sivanantham,

    1. We are glad that you are able to solve the issue. It needs to clarified with design person so we recommend you to start a new thread for this query.

    2. Our comment is that "SRIO is supported in Kernel only, not yet in U-boot. SRIO U-boot support is targeted in Proc SDK 3.0.0."

    Thank you.