• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 413 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.

CCS/AWR1642: CCS/AWR1642

Claudio ANUCHNIK
Expert 1100 points
Part Number: AWR1642

Tool/software: Code Composer Studio

Hi all,

I am running the 'mmWave Demo image' in its cloud visualizer.

In the 'plots' tab I press the button: 'LOAD CONFIG PC AND SEND'

I open 'profile_calibration.cfg' file and load it. Calibration is done and I see it in the target graph.

How can I do the same in my 'srrdemo' based application when I debug it in CCS_9?

Are the calibration values stored in AWR1642 permanent memory space?

Thanks,

Claudio

  • 0
    TI__Guru*** 148634 points
    Hi,

    The srrdemo was optimized for performance. Part of this optimization was to configure the demo at compile time.
    So, this demo does not support loading the configuration from a profile.cfg file

    thank you
    Cesar
  • 0
    TI__Guru 69960 points
    Hi Claudio,
    What specific feature you are looking in SRR demo?
    If it is for calibration then the device itself does the boot time calibration which is default in all the application (by rf_init API) and this calibration data doesn't get stored to the device permanently. At every power cycle device does this calibration (boot time).


    Regards,
    JG
  • 0 in reply to Jitendra Gupta
    Expert 1100 points
    Hi JG,
    I am not talking about temperature compensation, that I far as I understand: it is made at factory and automatically loaded at boot time.
    We are working with our own AWR1642 cards and there are Rx antennae traces we have to compensate in order to improve the azimuth resolution. I do this with the mmWave Demo visualizer when loading the configuration profile and then manually inserting the results.
    I want, once the new values are got, to store them permanently in the boot flash and not to carry on the calibration procedure each time I power on my system.
    I've seen the CLI functions that work with the configuration routines to write the new cfg parameters obtained at calibration time in RAM. I don't see any problem transferring them to my project.
    At this time I don't know so in deep the AWR1642 architecture and I don't know it has some permanent memory space for calibration data available to rewrite at run time or maybe some API available for this.
    Thank you,
    Claudio
  • 0 in reply to Claudio ANUCHNIK
    TI__Guru*** 148634 points
    Claudio

    It is possible to save calibration coefficients in flash memory.

    I see that you are already discussing this in a different thread. Closing this thread

    e2e.ti.com/.../803183

    Thank you
    Cesar