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: MMWDemoMSS mmWave Configuration failed [Error code -203227134]

Part Number: AWR1642BOOST

Hi,

I tried the following config. The same configuration is running without any error with the demo code provided by TI. 

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 0
profileCfg 0 77 7 7 48.98 0 0 15 1 256 6250 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 16 0 100 1 0
lowPower 0 0
guiMonitor -1 1 1 0 0 0 1
cfarCfg -1 0 0 8 4 4 0 5120
cfarCfg -1 1 0 4 2 3 0 5120
peakGrouping -1 1 1 1 1 255
multiObjBeamForming -1 1 0.5
clutterRemoval -1 1
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 0
bpmCfg -1 0 0 1
lvdsStreamCfg -1 0 0 0
nearFieldCfg -1 0 0 0
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
CQRxSatMonitor 0 3 4 127 0
CQSigImgMonitor 0 127 4
analogMonitor 1 1
sensorStart

I tried to send the data through CAN(used Object Data over CAN Lab provided by TI). With CAN enabled I am able to send data for some profile configurations such as profile_2d (from mmwave sdk).

When I tried some config for longer ranges(50m) such as above config, I am getting configuration error "MMWDemoMSS mmWave Configuration failed [Error code -203227134]" .

Please help me to find the reason for this behavior

Regards,

Shreeroop 

  • Hello Shreeroop,
    If you are using SDK V2.0 you need to use 'lowPower 0 1' CLI command else you will get this error.


    BR,
    Jitendra
  • Hi Jitendra,

    We are using SDK v1.2.

    Regards,
    Shreeroop
  • Hi Shreeroop,

    The "Object Data over CAN " uses the hardcoded configuration and bypasses the CLI based configuration input.

    Have you done the modifications to the Object data over CAN application to receive configuration data over CAN ?

    -Raghu
  • Hello Shreeroop,
    Sampling duration in the chirp to capture 256 samples is at verge of ramp end boundary which is causing this error. If you increase rampEnd time by few usec then it'll not fall in that erroneous condition.

    Further, please use Visualizer Configure TAB or sensingEstimator tool to get valid configuration.


    BR,
    Jitendra
  • Hi Raghu,

    I have made modifications on the code and its taking config from CLI. I tested it with some config files generated using TI demo visualizer. Its working with some configurations, but when I tried to increase the maximum unambiguous range beyond 10m its showing the above error message. Could you please check this demo with config given with the post? We dont have any issues with CAN integration now. We are able to receive messages via CAN.

    Regards,
    Shreeroop
  • Hi Jitendra,

    I ve tried the same config with a small increase in ramp end time (from 48.98 to 50 ,55 and 60). Still I am getting the error. We have separately tried the same config with demo code provided with mmwave sdk. Its working without any error there. When we tried it with TI's object data over CAN demo, its failing. Could you please try the above config with Object Data over CAN demo.

    I ve generated this config using demo visualizer.

    Regards,
    Shreeroop
  • Hello Shreeroop,
    I guess your issue has been resolved as per other duplicate thread
    e2e.ti.com/.../714237


    BR,
    Jitendra
  • Hi Jitendra,

    Both issues are different. That error was  "DSS Frame Processing Deadline Miss Exception" and it got solved by increasing frame periodicity.

    Here we are getting  an error "MMWDemoMSS mmWave Configuration failed [Error code -203227134]" .

    Regards,

    Shreeroop

  • As per your response that issue is not resolved.

    You mentioned that config mentioned above works for SDK demo but not with object-data-over-CAN demo. In CAN demo you need to embed all these config commands in string format [radarCmdString] to cli.c file as this demo doesn't take CLI command over UART but stores internally.
    Connect CCS to MSS core to debug this issue, put breakpoint at 'MmwDemo_CLISensorStart' function and verify & match all the config which are now stored in these global structures 'gCLIMMWaveOpenCfg' & 'gMmwMssMCB.cliCfg'.
    If it works with SDK not with CAN-demo then config parameters are not passed properly to RadarSS as both demo are same only front interface (CLI and CAN) differs.

    And we have tried your configuration with CAN-Demo to be working.

    Error message comes from mss_main.c:mmwDemo_mssDatapathConfig function, try to put a breakpoint inside 'MMwave_config' API to point out where exactly it's falling in error condition.
    Error value what you have mentioned is raised from mmwave.c file with internal error value 'MMWAVE_EINVAL=-3100'


    Regards,
    Jitendra
  • That issue is resolved. Please check the response.
    Object data over CAN demo does take CLI commands over UART if you undef CLI_BYPASS. Please go through my previous replies. I am able to send config through UART.
    And my issue got resolved. The problem was with the commented information in config file generated by demo visualizer. Once I remove this information from config file, I am able to send any config file without any error.


    Regards,
    Shreeroop