• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 638 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

RFSDK: RFSDK error

Gunzung Kim
Prodigy 40 points
Part Number: RFSDK
Other Parts Discussed in Thread: 66AK2L06, ADC12J4000, , DAC38J84

Hi,

I am using an ADC12J4000 EVM connected to the 66AK2L06 EVM via JESD204B interface directly.

There are no additional things connected to 66AK2L06 EVM.

The RFSDK version I'm using is 2.0.6 and the MCSDK version is 3.01.04.07.

To test the RFSDK, I followed the steps described in the RFSDK Installation Guide and selected the Wideband ADC12J4000 and DAC38J84 Demo as a Target board configuration.

I see errors when the RFSDK service launches. I paste the logs underneath:
Traceback (most recent call last):
File "/usr/bin/radio", line 108, in
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 1023, in do_reset
self.radio.radio_reset()
File "/usr/lib/python2.7/rfsdk/radio.py", line 1077, in radio_reset
self.dfe.dfe_reset()
File "/usr/lib/python2.7/rfsdk/platform/TCI6630K2L.py", line 454, 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)

In the target board configuration file - lamarr-evm-demo1-mcsdk3147, there are three UIOs - /dev/uio34, /dev/uio33, and /dev/uio32.

But on my board, the last UIO is /dev/uio32.

Please tell me what can I do to fix the error?

Best regards,

Gunzung Kim

  • 0
    TI__Guru**** 161600 points
    Hi,

    I've notified the RFSDK experts. Their feedback will be posted here.

    Best Regards,
    Yordan
  • 0
    TI__Mastermind 21295 points
    Hello,

    Please check that all the installation instructions in the RFSDK 2.0.6 installation guide were followed including the installation of the RFSDK patched versions of u-boot and the Linux device-tree (dtb) file. Please verify on the EVM that the u-boot and Linux versions match the time/date stamps given in the installation guide. Please also verify that the correct dtb file is being loaded during boot by verifying that the dtb file size is correctly listed in the u-boot/Linux boot trace. For MCSDK 3.1.4.7, the RFSDK-patched dtb file size is 47307 bytes, so the following line should be visible in the boot trace.

    "Loading file 'uImage-k2l-evm.dtb' to addr 0x87000000 with size 47307 (0x0000b8cb)..."

    Regards,
    John
  • 0 in reply to JohnH
    Prodigy 40 points
    Hi John,

    You saved me.
    I missed renaming the k2l-evm_mcsdk_314_patched.dtb file.
    After renaming, It works very well.

    Best regards,
    Gunzung Kim