• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 4 answers
  • Subscribers 98 subscribers
  • Views 2902 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/66AK2L06: RFSDK Demo Setup Problem

ANIL SIRMA
Prodigy 140 points
Part Number: 66AK2L06
Other Parts Discussed in Thread: RFSDK, TCI6630K2L, DAC38J84, , ADC14X250, ADC14X250EVM

Tool/software: Linux

How to find mcsdk ubifs image file named “k2l-evm-ubifs.ubi” for 66ak2l evm.

How to fix the following error ; ( we want to run demo2 for radio configuration 1x1-1xLTE80-HC-JESD121121x-DEMO2 )

root@k2l-evm:~# radio init
Traceback (most recent call last):
File "/usr/bin/radio", line 108, in <module>
command.onecmd(' '.join(sys.argv[1:]))
File "/usr/lib/python2.7/cmd.py", line 221, in onecmd
return func(arg)
File "/usr/lib/python2.7/rfsdk/command.py", line 1068, in do_init
self.radio.radio_init()
File "/usr/lib/python2.7/rfsdk/radio.py", line 262, in radio_init
self.dfe.dfe_reset()
File "/usr/lib/python2.7/rfsdk/platform/TCI6630K2L.py", line 460, in dfe_reset
res = self.rfsdkS.HwExceptionInit(req)
File "/usr/lib/python2.7/rfsdk/service.py", line 289, in HwExceptionInit
raise rfsdk.Error('rfsdkService.HwExceptionInit() API call failed with status %r (%d)' % (status, result,))
rfsdk.Error: rfsdkService.HwExceptionInit() API call failed with status 'RFSDK_API_RESULT_ERROR' (1)

  • 0
    TI__Mastermind 37500 points
    Hello,

    After RFSDK 2.00.06 the files for the 66AK2L06, and 14x250ADC, and DAC38J84 are included with the RFSDK.

    The files for programming the DAC38J84, ADC14x250 are discussed in www.ti.com/.../tidub94a.pdf
    The user guide and tool files are discussed in www.ti.com/.../tidub89.pdf, and www.ti.com/.../tidep0060

    a) 14x250 EVM - JESD ADC
    b) 66aK2L06 EVM - SOC with DFE, JESD, Serdes
    c) K2L HSP - Deterministic Latency Clock and JESD signal routing
    d) DAC38J84 EVM
    e) power splitter, ADC input filter, various cables and test equipment

    The K2L HSP Deterministic Latency Clock and JESD signal routing card - please contact 3rd party provider Azcom International

    Alternately, you can use the
    a) 14x250 EVM - JESD ADC - you need to provide the 245.76Msps ADC clock. The JESD serdes is 4.9152G
    b) 66aK2L06 EVM directly connected to the first JESD 0,1 port. You must have a rev2 or later EVM, or for rev1, there is a hardware modification.

    The ADC must be programmed prior to the RFSDK setup, and must have an active JESD serial output.

    When you run the RFSDK you need to select the option for this use case from the GUI. This preselects the proper Linux setup files.

    Note: There is a JESD loopback example, this does not require the ADC hardware, it can be run from the 66AK2L06 EVM alone.

    Regards,
    Joe Quintal
  • 0 in reply to Radio-Joe
    Prodigy 140 points

    Hello ,

    We have 3 boards , 66AK2L06 EVM ver. 1.0.3.0 , ADC14X250EVM rev B  and DLC board that we produced according the desing files.

    We have no DAC Board, because  we want to use only ADC Board and see any Signal generated by us in RX side RFSDK Demo software.

    Can we do it without a DAC Board ?

    I did everything with the order except DAC according to the document , but I am getting this error below when I write radio init.

    How to fix this problem , Could there be a problem due to not having a DAC Board ?

  • 0 in reply to ANIL SIRMA
    Prodigy 140 points
    The error here ,


    root@k2l-evm:~# radio init
    Traceback (most recent call last):
    File "/usr/bin/radio", line 108, in <module>
    command.onecmd(' '.join(sys.argv[1:]))
    File "/usr/lib/python2.7/cmd.py", line 221, in onecmd
    return func(arg)
    File "/usr/lib/python2.7/rfsdk/command.py", line 1068, in do_init
    self.radio.radio_init()
    File "/usr/lib/python2.7/rfsdk/radio.py", line 262, in radio_init
    self.dfe.dfe_reset()
    File "/usr/lib/python2.7/rfsdk/platform/TCI6630K2L.py", line 460, in dfe_reset
    res = self.rfsdkS.HwExceptionInit(req)
    File "/usr/lib/python2.7/rfsdk/service.py", line 289, in HwExceptionInit
    raise rfsdk.Error('rfsdkService.HwExceptionInit() API call failed with status %r (%d)' % (status, result,))
    rfsdk.Error: rfsdkService.HwExceptionInit() API call failed with status 'RFSDK_API_RESULT_ERROR' (1)



    Thank you
    Regards,

    ANIL S.
  • 0 in reply to ANIL SIRMA
    TI__Mastermind 37500 points

    Hello Anil,

    We have only done the test as described including the DAC board.  I suggest you either order the DAC38J84 EVM for the actual test described, or contact your Local TI Field Application Engineer to see if he has a DAC board you could borrow for a test.

    a) when you first run the RFSDK

         please make sure you select the Appropriate Design #2 adjacent market configuration from the GUI, this configures the RFSDK to know the

         data converters are programmed differently than the Small Cell AFE7500 device (native to RFSDK).

    b) you will need to have the GUI for the Clock DLC, ADC, and DAC an their programming complete, before the RF Init process.

    I will ask the developer if there is an option to have no DAC installed, however we have customers that run the demo with the ADC, DLC, and DAC EVMs attached.

  • 0 in reply to Radio-Joe
    Prodigy 140 points

    Hello Joe ,

    Is there an option to have no DAC installed , Did you ask the developers about this?

    Regards ,

    ANIL S.

  • 0 in reply to ANIL SIRMA
    Prodigy 140 points
    Hi Joe ,

    Other question is ,


    We can not finish updating the UBIFS Image step because cant find “k2l-evm-ubifs.ubi” file.
    How to find mcsdk ubifs image file named “k2l-evm-ubifs.ubi” for 66ak2l evm ?

    Regards ,

    ANIL S.
  • 0 in reply to ANIL SIRMA
    TI__Mastermind 37500 points
    Hello,
    The developer test uses the DAC EVM, with the ADC EVM. I would try your test with the DAC EVM. The test procedure loops back the DAC output to the ADC.
    Regards,
    Joe Quintal
  • 0 in reply to ANIL SIRMA
    TI__Mastermind 37500 points
    Please follow the RFSDK Software Installation Guide in the RFSDK, this comes from the MCSDK.
    note: the version of the MCSDK needs to match the instructions.

    link: processors.wiki.ti.com/.../MCSDK_UG_Chapter_Exploring

    3. Software Installation
    This section covers MCSDK and RFSDK installation and configuration.

    3.1 MCSDK Installation
    3.1.1 Lamarr EVM MCSDK Installation
    First flash Lamarr EVM board with required MCSDK following MCSDK User guide

    Anyway here are steps to follow:

    get MCSDK 3.1.4.7 official release from Texas Instruments web page: MCSDK 3.1.4.7 Release

    from mcsdk3.1.4.7, install the ubi files with commands at UBOOT prompt:

    setenv serverip <customer_serverip>
    setenv gatewayip <customer_gatewayip>
    setenv tftp_root <tftp_root>
    run get_ubi_net
    run burn_ubi
    If the ubi files need to be split (in general, this step is optional):

    dhcp 0x82000000 ${tftp_root}/k2l-evm-ubifs.ubi.part0
    dhcp 0x86000000 ${tftp_root}/k2l-evm-ubifs.ubi.part1
    dhcp 0x8A000000 ${tftp_root}/k2l-evm-ubifs.ubi.part2
    dhcp 0x8E000000 ${tftp_root}/k2l-evm-ubifs.ubi.part3
    dhcp 0x92000000 ${tftp_root}/k2l-evm-ubifs.ubi.part4
    setenv filesize 10180000 # to be verified, updated all the time
    run burn_ubi
    3.1.2 MCSDK3.1.4.7 Customization for RFSDK2
    install uboot patch for RFSDK2 at UBOOT prompt:

    setenv serverip <customer_serverip>
    setenv gatewayip <customer_gatewayip>
    setenv tftp_root <tftp_root>
    setenv name_uboot k2l-evm_u-boot-spi_mcsdk_314_patched.gph
    get_uboot_net
    burn_uboot
    power off/on EVM and get UBOOT prompt then verify your UBOOT parameters:

    env default -f -a
    setenv serverip <customer_serverip>
    setenv netmask <customer_netmask>
    setenv gatewayip <customer_gatewayip>
    setenv ipaddr <board_ipaddr>
    setenv tftp_root <tftp_root>
    setenv boot ubi
    setenv debug_options 1 #to allow CCS connection
    saveenv
    verify version at UBOOT prompt:

    ver command returns: U-Boot 2013.01-00001-g04dcae7 (Oct 13 2015 - 09:25:53)
    boot
    after Linux boot completed add Linux dtb patches:

    mkdir /mnt/boot
    mount -t ubifs ubi0_0 /mnt/boot
    cd /mnt/boot
    tftp -g -r <tftp_server_path>k2l-evm_mcsdk_314_patched.dtb <customer_serverip>
    mv k2l-evm_mcsdk_314_patched.dtb uImage-k2l-evm.dtb
    cd /
    umount /mnt/boot
    reboot the Linux system:

    reboot
    at the linux prompt, verify version of the kernel:

    cat /proc/version command returns:
    Linux version 3.10.72-gca334de (gtbldadm@ubuntu-12) (gcc version 4.7.3 20130226 (prerelease)
    (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 SMP Wed Sep 30 03:51:28 EDT 2015
  • 0 in reply to Radio-Joe
    TI__Mastermind 37500 points
    Hello,
    The weblink to access MCSDK 3.1.4.7 is
    software-dl.ti.com/.../index_FDS.html
    Regards,
    Joe Quintal
  • 0 in reply to Radio-Joe
    Prodigy 140 points

    Hello Joe ,

    We have done all steps in tidub94a document , except below steps;

     * Update the UBIFS Image on the 66AK2L06EVM 

        We skipped this step because we were worried about the error on the link. So we decide to use on board mcsdk version. ( actually we dont know version but we use it )  

         https://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/615477?tisearch=e2e-sitesearch&keymatch=rfsdk%20api%20error

         When we run this board configuration. We get radio init error ( as we said above first ). So we tried to "lamarr-evm-demo2-mcsdk3125" version. then radio init runs with no problem.

    But in now we get the following error when we try radio on over demo gui. 

    Operation failed (Response header: 'rfsdk.error: rfsdkService.Iqn2Start() API call failed with status 'RFSDK_API_RESULT_APISEQ_IQN_INVALID_STATE' (86) '
    So how we get over this problem. Actually we want to read data from JESD / ADC. 

  • 0 in reply to ANIL SIRMA
    TI__Mastermind 37500 points
    Hello,
    In earlier versions of MCSDK and RFSDK, there was a added package for Demo2. The later RFSDK version needs the mcSDK 3147
    this has to do with the peripheral software. The IQN2 software in MCSDK3125 does not seem to be compatible with RFSDK 207

    a) update the board mcSDK version to 3147. following the RFSDK installation guide

    b) or using the demo2 Getting Started Guide, and User Guide, downgrade the mcSDK and RFSDK to the version in this guide, request the demo2 extra files, and configure for use.

    Regards,
    Joe Quintal