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.

DCA1000EVM: Source code of xWR1443 ES3.0 and xWR1642 ES2.0 for mmWave Studio

Part Number: DCA1000EVM
Other Parts Discussed in Thread: AWR1642, AWR1443,

Hello, support team,

Could you please share source code of xWR1443 ES3.0 and xWR1642 ES2.0 for mmWave Studio?
We have some customers who would like to take radio certification in Japan with [mmWave EVM and DCA1000 raw data capture platform]. Frequency range needs to be limited by FW to take certification.

Best Regards,
Katsuhiro

  • Hi Katsuhiro,

    You can use mmwave Studio to configure the device to have the required frequency range for certification.

    For Radio verification device exposes multiple API which you can use here. (like continuous streaming mode). I would request you to go over mmwave studio user guide to find out all the features which are required for certification. 

    And for AWR1443 and AWR1642 also you can use same mmwave Studio and this package provides the firmwares for AWR1443 and AWR1642 device which is required to load to the device in SOP-2 mode (development mode) and then configure the device over SPI.

    Regards,

    Jitendra

  • Hi Jitendra,

    For 77GHz-81GHz certification, we will have to limit the sweep frequency from 77.xGHz to 80.xGHz to keep some margin. mmWave studio has flexibility to set sweep frequency. To take certification, FW for mmWave EVM must limit sweep frequency from 77.xGHz to 80.xGHz even if mmWave studio set sweep frequency outside of the frequency range. This is the reason why I request to share source code.

    Best Regards,

    Katsuhiro

  • Hello Katsuhiro San,

    All the configuration in mmwave studio can be done using lua scripts. You can write your own lua script and in that set a limit to the frequencies.

    Regards,

    Vivek

  • Hello Katsuhiro san,

    By the way, they should be taking the certification with their application and not using mmwave studio. Their final product (including SW) needs to be certified.

    Regards,

    Vivek

  • Hello Vivek,

    Even if limiting frequencies by making own LUA script, mmWave studio still can run arbitrary script. To limit to run specific LUA script, mmWave studio will needs to be modified or original UI will needs to be developed. That cases will probably require more effort and cost than modifying RF FW source code.
    Yes, I agree with you that the customers needs to take the certification with their final product. Because the customers requesting to take the certification is in R&D stage, taking the certification of DCA1000 and mmWave EVM is good choice.
    Can we discuss in private message for RF FW and customers' information?

    Best Regards,
    Katsuhiro

  • Hello Katsuhiro San,

    For  the final product the customer can use their own application. For R&D stage we recommend using the mmwave studio with lua scripts to limit the usage frequency. The test house will use only the lua scripts provided to them.

    We cannot share the mmwave studio source code.

    Regards,

    vivek

  • Hello Vivek,

    I understood that TI cannot share the mmwave studio source code.
    How about sharing masterss source code with us for us to modify the source code to limit the frequency range?

    Best Regards,
    Katsuhiro

  • Hello Katsuhiro San,

    Unfortunately MSS source code also cannot be shared. We have had customers go through the initial certification cycle using the exiting mmwave studio and lua scripts . We believe it should be possible.

    Regards,

    Vivek 

  • Hi Vivek,

    If the test house does not know that other lua script can be run, it will be possible to take certification.

    I feel strange that MSS source code for raw ADC data capture cannot be shared despite that SDK demo FW source code  is open to everybody. Could you explain the reason why MSS source code cannot be shared please?

    Best Regards,
    Katsuhiro

  • Hello Katsuhiro San,

    The SDK is intended for users to develop their application and OOB demo is an example code using the SDK. You could use this source also and modify it to limit the frequency range for your certification purpose.

    Regards,

    vivek

  • Hello Vivek,

    Understood.
    Can OOB demo binary be used by mmWave studio with no modification? If not, please teach me the required change in source code. The modification I wrote is not frequency range limit.

    Best Regards,
    Katsuhiro

  • Hello Katsuhiro San,

    If you use the OOB application you don't need the mmwave studio. You can set the configuration you need y modifying the OOB application and using the demo visualizer for user control. In the end both are ways to configure the AWR device.

    Regards,

    Vivek

  • Hello Vivek,

     [xWR1xxxBOOST===DCA1000EVM===PC(mmWave Studio]
    Is SDK OOB demo binary can be used with this platform?

    Best Regards,
    Katsuhiro

  • Hello Katsuhiro,

    The xWR144sBOOST + DCA1000 + mmwave studio is one way of controlling the awr device which you can use for certification. This is a "blackbox" system and works only with the rfeval firmware provided along with the mmave DFP package. You can use lau scripts to program any configuration you need.

    the mmwave OOB application is an embedded application which runs within the AWr device DSP/R4F can be used on 1443/1642/1843 to configure AWR device and this is used on the standalone  xWR1xxxBOOST boards. It DOES NOT run with mmwave studio. This also can be used for your certification  process.

    Regards,

    Vivek 

  • Hello Vivek,

    Understood.
    Thank you for clarification.

    Best Regards,
    Katsuhiro