• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 32 subscribers
  • Views 1475 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/AWR1443: High Accuracy Visualiser "Error: Incorrect config reported by target. Hint: Change configuration and try again"

Dan12
Prodigy 185 points
Part Number: AWR1443

Tool/software: Code Composer Studio

Device AWR1443

SDK 2.1.0.4

Custom upgraded toolbox 3.1.1 High accuracy lab such that it operated with SDK2.1.0.4 so that i could run this demo on silicon version ES 3.0

I can connect to tthe target in the high accuracy visualiser, but when i try to send it the configuration file i get the following error

"Error: Incorrect config reported by target. Hint: Change configuration and try again"

I'm unsure at this point whether this is an issue with my build or incompatibilitity between sdk2.1.0.4 and the visualizer.

What would produce this error on the visualiser side?

The visualiser as i understand only supports SDK 1.0.0 (in the about section of the visualiser)

Is there anyother way i can view this data?

Regards

Dan

  • 0
    TI__Guru 69990 points
    Hi Dan,
    Have you tried other version of this application with the same device?


    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Prodigy 185 points
    Hi Jitendra,

    Do you mean another version of high accuracy visualiser?

    If thats not what you meant, then I've succesfully ran the standard SDK demo okay on this device.



    Regards
    Dan
  • 0 in reply to Dan12
    Prodigy 185 points
    Jitendra,

    For further information.

    I'm now running the high accuracy code in CCS debug and connecting to the high accuracy visualiser in the normal way. CCS Console output is below

    [Cortex_R4_0] Debug: Launched the Initialization Task
    Debug: HWA has been initialized
    Debug: EDMA instance 0 has been initialized
    Debug: UART Instance @0800aca0 has been opened successfully
    Debug: UART Instance @0800acac has been opened successfully
    Debug: mmWave Control Initialization was successful
    Debug: mmWave Control Synchronization was successful
    Debug: HWA Instance @08000f18 has been opened successfully
    Debug: ADCBUF Instance(0) @0800ad88 has been opened successfully
    Debug: CLI is operational

    However when I try to send config to device through the high accuracy visualizer (config file contents shown below)

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 1 1 0
    adcCfg 2 1
    adcbufCfg 0 1 0 1
    profileCfg 0 77 7 7 212.8 0 0 18.32 1 1024 5000 0 0 40
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 1 0 500 1 0
    calibDcRangeSig 0 -5 5 32
    guiMonitor 1 1 0 0 0 1
    RangeLimitCfg 1 1.0 5.0
    sensorStart

    It brings up this error in the CCS console

    Error: mmWave Open failed -203554190

    I can only find this string in the sensor_mgmt.c file line 283. it attemps to open the mmWave module

    Any ideas how i can rectify this?
  • 0
    TI__Intellectual 2885 points
    Dan,

    What you mean 'Custom upgraded toolbox 3.1.1'?
    Did you try the other chirp profile? (Profile_2db.txt or Profile_2de.txt)
    Have you tried any of the other labs?

    Alex
  • 0 in reply to Alex Rivera
    Prodigy 185 points

    Alex,

    See my previous question:

    Essentially the high accuracy lab is not compatible with ES3.0. I upgraded  the high accuracy lab in order to make it compatible with SDK2.1.0.4 in order that i could use it with the ES3.0. This built succesfully and appears to run, an error occurs when trying to send the config in the high accuracy visualiser, which is where i need to focus on.

    This has now made it seemingly incompatible with the high accuracy visualiser.

    I've tried both profiles yes. Both have the same issue.

    I've ran the demo succesfully, as far as i understand it most of the labs dont support ES3.0. I will look at other labs today and run them, though i think they will fine.

    Regards
    Dan

    Dan

  • 0 in reply to Dan12
    TI__Intellectual 2885 points

    Dan,

    In your chirp try adding the bold line, (lowPower) this was added for ES3 devices.

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 1 1 0
    adcCfg 2 1
    adcbufCfg 0 1 0 1
    lowPower 0 1
    profileCfg 0 77 7 7 212.8 0 0 18.32 1 1024 5000 0 0 40
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 1 0 500 1 0
    calibDcRangeSig 0 -5 5 32
    guiMonitor 1 1 0 0 0 1
    RangeLimitCfg 1 1.0 5.0
    sensorStart

    Alex

  • 0 in reply to Alex Rivera
    Prodigy 185 points

    Hi Alex,

    Thanks for this, it certainly fixes the issue of the error that shows up (that no longer appears with this line added) however there is nothing on the data plot, i've checked both on the high accuracy app as well as tera term serial window.

    Should I start this as a new thread?

    Dan

  • 0 in reply to Dan12
    TI__Intellectual 2885 points
    Dan,

    Yes, please start a new thread, referencing back to this one.
    From Tera Term try to to send a "sensorStop" followed by "sensorStart" and report back with results.

    Alex
  • 0 in reply to Alex Rivera
    Prodigy 185 points
    Hi Alex,
    I've managed to get data out on the UART in the Tera Term and into Matlab. I used the Tera term as you indicated with the sensor stop and sensorstart commands. I also manually entered the config parameters this way. Data out appears to be what is asked for in the guiMonitor cfg sectcion.

    Still struggling with the GUI however, but will start new thread as indicated
    Many thanks for your help here!