• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 11 subscribers
  • Views 1138 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 cascading reset

Hao Wang
Prodigy 240 points
Other Parts Discussed in Thread: AWR1243

We use four awr1243 as cascading radar system. We found a problem that we can only reset the master awr1243, when we reset other 3 awr1243 ,they didnot raise irq as response. Only when we configure the master one as cascading master mode, then we reset the 3 slave awr1243 and it raise irq as response. But this is not Consistent with mmwavelink as it will reset the four awr1243 one by one before set radar work mode.

ps: before we set master awr1243's mode into "cascade master", master does not generate clock to slaves, after config master's work mode, it starts to generate clock to slaves.

  • 0
    TI__Guru 70100 points
    Hi,
    Your understanding is corrent for cascade master/slave clocking mechanism.
    So using mmWaveLink you need to use rlDevicePowerOn API only for Master (only one deviceMap for Master SPI line), wait for power-on Async event message from Master, call rlDeviceRfStart (wait for rf-power on Async event) and then call rlSetChannelConfig API set as Master. And all these API need to invoke with deviceMap for Master only.
    Post this only start working on all three slaves, rlDeviceAddDevices (with all three slave deviceMap) - this will now take 3 slaves out of reset. As master device is already up, now all three salves will get clock and raise HostIRQ signal. So after this call you need to wait power-on async event from each slaves.


    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Prodigy 240 points

    hi, the start is ok,both master and slaves powered up ok.But we cannot see SYNC_IN and trigger signal with Oscilloscope no matter we use mipi or lvds. And no data received.

    And if we use sw-trigger in master and set frame count = 0,then how many trigger signal can we see with oscilloscope? 

  • 0 in reply to Hao Wang
    TI__Guru 70100 points
    Hi,
    Make sure you are invoking channelConfig API as [cascading= MULTICHIP_MASTER] while sending it to Master-Device and for remaining 3 slaves this API should be set [cascading= MULTICHIP_SLAVE].
    While calling any API check the return value of those APIs (should be zero). At frame trigger event, Master provides SYNC_OUT to all the slaves connected at SYNC_IN pin. When you set Master as SW-triggered frame and Slaves as HW-triggered frame then at every frame Master will provide SYNC_OUT pulse to all the slaves to trigger the next frame.
    In case you don't see SYNC_OUT signal, then better to check the current/power consumption of Master device while invoking rlSensorStart API (frame-trigger), power inlet should go up at this event. If power is not rising then there is some issue with API call or hardware circuit. Try to run only Master device first to verify if the single device is working fine.

    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Prodigy 240 points

    hi,

    Master's and slave's mode set correctly - master is 0x01,slaves are 0x02,master is sw-trigger,slaves are hw-trigger.And the current become significant larger after call sensorstart.

    We set frame count to zero, then we only call sensor start at the begining. Can we see trigger later without call sensor start again?

    If we set master to multi-chip master,and others to multi-chip slave correctly ,and other configurations are not sure, can master send sync_in to slaves?

  • 0 in reply to Hao Wang
    TI__Guru 70100 points
    Hi,
    I see that you have marked first reply as 'Verify Answer', does that mean this issue is resolved at your end?

    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Prodigy 240 points

    We can see chirp with Spectrum Analyzer, and got adc data. But we still not see SYNC_IN signal,though slave can send frames as long as not stop it.

  • 0 in reply to Hao Wang
    TI__Guru 70100 points
    Hi,
    I assume you have taken care all the Mast-slave configuration (SW/HW trigger) in this scenario. And I understand that Master and slave devices are chirping now.
    If Slave is configured in HW triggered mode then it won't start frame (chirping) till it gets the SYNC_IN signal. In this case SYNC_IN pulse will be very small (min pulse width is 25nsec), oscilloscope might not able to capture that signal.


    Regards,
    Jitendra