• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 989 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.

AWR1243: async event is missing when stopping a sensor

Ilia K.
Prodigy 250 points
Part Number: AWR1243
Other Parts Discussed in Thread: AWR1642

Hi,

I'm troubleshooting AWR1243 cascading operation using DFP 0.9.1.6.

First setup (works fine):

I configure AWR1243 just like in mmw_example.c, particularly:

- mode Single

- aeDirCfg.aeDirection = 0x05, aeDirCfg.aeControl = 0, i.e. both frame start and frame stop async events are enabled

PC issues sensor start command, waits a second, then issues sensor stop command. After both start and stop commands PC receives async events:

- after start: AWR_RF_ASYNC_EVENT_MSG1 / AWR_AE_RF_FRAME_TRIGGER_RDY_SB

- after stop: AWR_RF_ASYNC_EVENT_MSG1 / AWR_FRAME_END_AE_SB


Second setup (does not work):

exactly the same as first, except mode is Master.

PC issues the same commands like in the first setup. After sensor start command async event is received just like in the first setup.

However, after sensor stop command no async event is received.

I have double checked signals with a logic analyzer. In both first and second setup AWR1243 ACKs the reception of sensor stop (AWR_RF_FRAME_TRIG_MSG / AWR_FRAMESTARTSTOP_CONF_SB). In the first setup it then triggers host interrupt and deliver async event. In the second setup AWR1243 does nothing.

AWR1243 chip under test has SYNC_OUT connected to SYNC_IN.

Is this a BSS bug?

Please assist.

Thanks.

  • 0
    Expert 1095 points

    Hello;

    I have also experienced this issue on the AWR1642 with the latest SDK release. I have completely removed any dependencies upon FRAME END asynchronous events as they were not trustable in deployment mode. The async events appeared to trigger consistently when running through the debugger, but not deployment, so this was a very challenging issue to track down. 

    I'd also like to hear any feedback from TI if this is a known issue.

    Regards,
    Erik

  • 0 in reply to Erik Larsen
    TI__Guru 69960 points
    Hello Erik,
    On AWR1642 I don't see this issue. Please follow these steps to confirm at your end-
    1. download mmw demo application to AWR1642 device.
    2. Open mmWave demo visualizer, connect COM ports
    3. Load config from PC and send.
    4. After getting object plots click sensor STOP button, at this click MSS sends sensorStop command to radarSS.
    5. After sending back response to this command, radarSS sends [RL_RF_ASYNC_EVENT_1_MSG/RL_RF_AE_FRAME_END_SB] async event.
    6. To verify this async event data, connect MSS core from CCS and go to memory browser for BSS-to-MSS mailbox address '0xF0601000' and check for '0xF0601010' value which is SB-ID for sensor_Stop async event. [0x100F]


    Regards,
    Jitendra
  • 0
    TI__Guru 69960 points

    Hello Spring,

    In this experiment you are trying to simulate cascade mode with single AWR1243 device, right?

    In cascade mode SYNC_OUT of master must need to connect back to SYNC_IN line of master itself and further to SYNC_IN of slave as well.

    Please refer figure-1 of cascade appnote - 'swra574.pdf' for more info.

    So in your given experiment, you have only one AWR1243 device which is acting as Master (channelConfig->cascading = 1). As SYNC_OUT is not connected back to SYNC_IN of its own so when on sensor_start command device will not start the frame/chirping. So further when Host sends sensor_stop radarSS returns response but not async event as there is not frame running.

    Regards,

    Jitendra