• State Resolved
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 62 views
  • Users 0 members are here
Support feedback
Options
Options
Related

DCA1000EVM: Combination with IWRL6432BOOST

Tom Lackinger
Prodigy 90 points
Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWRL6432, IWRL6432BOOST

Tool/software:

Hello TI Team,

I have one question about a lua script.

At the beginning of the script "IWRL6432_common_device_setup.lua" there is a file namend  atecal_firmware .

-- Change the directory for the firmware file
local firmware_directory_base = [[C:\ti\MMWAVE_L_SDK_05_05_03_00\firmware\mmwave_dfp\]]
local rfeval_firmware = firmware_directory_base .. [[rfevalfirmware\appss\mmwave_plt_rfeval_rprc.bin]]
local rfs_firmware = firmware_directory_base .. [[rfsfirmware\xWRL6432\mmwave_rfs_rprc.bin]]
local atecal_firmware = firmware_directory_base .. [[rfevalfirmware\rfsatecal\xWRL6432\mmwave_rfs_atecal_rprc.bin]]
local rfs_patch_firmware = firmware_directory_base .. [[rfsfirmware\xWRL6432\mmwave_rfs_patch_rprc.bin]]
At the MMWAVE_SDK_05_05_03 this file doesn't exist.
At an older SDK this file exists. I have an IWRL6432BOOST (ES2.0) in combination with the DCA1000.
Do I still have to load this file oder is the atecal_firmware for an older board?
Or for what is this file exactly?
Regards
Tom
  • 0
    TI__Mastermind 23177 points

    Hello Tom,

    With ES1.0 and super early versions of 6432, the ATE calibration was not fused in and had to be provided separately. The script "IWRL6432_common_device_setup.lua" which I imagine was acquired via Radar Toolbox does not actually use the defined "atecal_firmware" anywhere in the script unlike the other variables at the top. You will for example notice that rfs_firmware is the same way where its defined but not used.

    Short answer: you don't need it for any ES2.0 devices

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 90 points

    Thank you for the fast reply!