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.

AWR1243: Re-configure awr1243p without restart radar failed?

Part Number: AWR1243

We are using awr1243P ES3.0 with dfp 1.2. I'm trying to change awr1243p's parameters (like Tx channels, chirp time,etc) without restart radar. Sometines, re-configuration report fail with error code "RL_RET_CODE_PROTOCOL_ERROR  (-1)", or "RL_RET_CODE_CHIRP_END_INVAL_IN", or "RL_RET_CODE_CHIRP_END_1INVAL_IN", while sometime it works well. And all configuration works after restart.

We store configuration file in flash and using it after radar start or call our re-configure function.

 So how to make sure re-configure successful 100% ?

My re-configure logic is below:

1. stop sensor: stop master radar

2. stop 3 slave radar

2. read new configuration

3. set profile and chirp

4. get chirp and make a comparation

5. start master radar's sensor

6. start 3 slave radar's sensor

  • Hi,

    I assume this is a cascade system. Is this correct?

    When you say "Without restart radar" - you mean without "power up"?

    When it works are you using the same chirp configuration?

    The first step is to make sure that the chirp config being used is valid

    Thank you
    Cesar
  • Yes, it's a cascade system, and without restart means without power-down and power up.

    I download the configuration , if re-configuration  failed, then restart and the same configuration works well. So I think the configuration is correct.

  • hi,
    I also meet a problem that we using continuous mode. And re-configure tx channels, the system did not report error,but the new configuration did not take effect. Then I just restart radar, that configuration works.
    Take a example: At first, we enable master's 3 tx channels, then re-configure radar, close all 3 tx, but the radar did not close, then we restart radar, the 3 tx are closed.
  • This is a known issue needs to be addressed in firmware. Until then, it is recommended to reset the device to change configuration. Look for the issue to be listed amongst the fixed issues in the release notes.
  • Got it. So re-configure without power-down and up has problem. Wait for the new firmware.

    BTW, we use four awr1243 es2.0 with dfp 0.9, its' startup cost two much time, about  2 or 3 minutes. How to reduce the start-up time?

  • On the reconfig issue, just to be sure, you need to make sure that you are sending the Sensor Stop command, then waiting to receive the

    AWR_FRAME_END_AE_SB sync event.

    > How to reduce the start-up time?

    There is no reason for it to take this long.  It will of course include the time for the Host to send configuration commands over the SPI, and will be affected by the SPI transfer rate, but you may want to take a look at the Host code.

     -dave