• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 4 answers
  • Subscribers 31 subscribers
  • Views 1004 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.

AWR1642BOOST: How to use mmwave SDK 3.2 to capture ADC raw data for the new config file (.cfg) on CCS Ver 9.0.1 ?

A-Kai
Intellectual 310 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: DCA1000EVM, AWR1642

Hi,

 I am a new beginner and used a new CLI config file (.cfg) to work well on mmwave demo visualizer ver 3.2.0 to run  xwr16xx_mmw_mss.xer4f and  xwr16xx_mmw_dss.xe674 on CCS ver 9.0.1 when flash was programming xwr16xx_ccsdebug.bin . I have some questions as follows.

 Q1 : How to capture the ADC raw data on CCS v.9.0.1 by memory browser with mmwave SDK 3.2 If we have no DCA1000EVM or TSW1400 capture board ?

 Q2 :  Follow up the section 5.4.17.3 of user guide of SDK3.2 to run the pre-built mem_capture with xwr16xx_mem_capture_mss.xer4f and xwr16xx_mem_capture_dss.xe674 on CCS and work well.

          2.1 How to change a new config file(.cfg) for the memory capture ?

          2.2 Where is the base address of L3 memory to dump ADC raw data ?

Thanks for your help and support.

  • 0
    TI__Guru 70100 points

    Hi,

    Q1: Please refer these threads, to capture the raw data using DCA100EVM while mmw demo running on the AWR1642

    https://e2e.ti.com/support/sensors/f/1023/t/759979

    https://e2e.ti.com/support/sensors/f/1023/t/791823

    Q2: mem_capture demo dumps single frame worth of raw ADC data to L3 Memory which you can save using CCS (memory browser window) and then do the post processing. Please go over SDK document and search this forum to find more info.

    Q2.1 All the configurations are defined in the mss.c file which you can change and build the application.

    Q2.2 If you are accessing from MSS then L3 address 0x51000000, from DSS 0x20000000.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Intellectual 310 points

    Hi,

      Thanks for your response. 

      We had ordered DCA1000EVM , but not get it now. So I still need to use Q2 method to get the raw ADC data on CCS. 

      About above question Q2 :

         Q 2.1: Build the mem_capture fail for mss and dss. Do you have any example or document to complete to build the  mem_capture ? 

      Thanks for your help.

      Best Regards,

      A-Kai

  • 0 in reply to A-Kai
    Intellectual 310 points

    Hi,

     About  Q 2.1: Build the mem_capture fail for mss and dss. Do you have any example or document to complete to build the  mem_capture ? 

      I follow up the section 4.5.4.1 in SDK 3.2 user guide, It can make the .bin file ok for mss and dss. 

       Let me ask another question, 

         Q 2.1.1 How to build the source code of mem_capture on the CCS environment ? 

      Thanks for your help.

      Best Regards,

      A-Kai

  • 0 in reply to A-Kai
    Intellectual 310 points

    Hi, 

       Based on your user guide of SDK 3.2, it can fixed the issue.

       Thanks for your help.

       Best Regards,

       A-Kai

  • 0 in reply to A-Kai
    Expert 1310 points

    Hi together,

    can anybody elaborate on why you built a .bin-binary, i.e., are there any advantages over just operating the EVM in debug mode and loading the .xer4f and .xe674 into the MSS and DSS, respectively, inside CCS?

    Also, how is it possible to make use of a .cfg profile when using the mem_capture test? I read that the profile information are hard-coded into the mss.c file.

  • 0 in reply to user6096953
    TI__Guru 70100 points

    Hi,

    During the development phase, you need to load the code to the device and may need to check code execution flow/variables etc.

    If you flash you application image to device then you don't have any control to halt the application and check the status.

    So for development (debug mode), SDK provides ccsdebug.bin which can be flashed to device. This .bin file will do the initial device setup and open MSS and DSS for a developer to load *.xer4f and .xe674 images from CCS. Now after loading via CCS you have full control on code execution and look at each debug points.

    Yes, for mem_capture each of configuration is stored in the MSS application which you need to change and re-compile to see the effect.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Expert 1310 points

    Hi Jitendra,

    thanks for clarification! I did indeed flash my board with the ccsdebug.bin. I was just confused because it seems that user A-Kai has manipulated such a binary which makes no sense to me.

    One last question: How exactly does this re-compile step look like, i.e., what do I have to do after editing the mss.c file? Just reloading the *.xer4f and .xe674 images? Or even flash the .bin image again?

  • 0 in reply to user6096953
    TI__Guru 70100 points

    After editing any source file of the application you need to build the application using gmake command (follow SDK user guide).

    And then you can load *.xer4f/*.xe674 via CCS (assuming ccsdebug.bin is already flashed to the device). mem_capture doesn't generate the binary file.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Expert 1310 points

    Thank you Jitendra, your reply was helpful and sufficient.

    Unfortunately, I cannot mark your post as having resolved my issue since I have not started this thread.