• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 188 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.

AWR1843BOOST: AWR1843 objectdetection module customization issue

QHLam
Prodigy 210 points
Part Number: AWR1843BOOST

Hi, 

I am working on customization of DSP processing chain, based on objectdetection.c module. I need only Range/Doppler processing and detection matrix (Range, Doppler bin size = 256, 64) will be sent out over SW LVDS. 

I have use TI demo from sdk 3.5.0.4, then comment out unused processing units (cfar, aoa...). However, I am getting in a trouble the customized processing chain was able to run only once. 

While debugging, I figured out that event of mark end of processing of the frame happened after then new frame started. 

From my understanding, it could not be the case since range/doppler processing should not be longer than inter-frame margin time. My DSS trace attached below. 

I am not sure if something went wrong here, you all please let me know. 

Thanks, 

QHLam

  • 0
    Prodigy 210 points

    Note that I have also commented out the assertion to check if the previous frame processing has completed to avoid the failure of DPC_Objdet_Assert(). .. 

  • 0 in reply to QHLam
    TI__Mastermind 20605 points

    Hi QL,

    More debug info is needed for this problem.

    • Can you please perform timing measurements within the DPC to check if there are any bottlenecks that you could have missed (By running the DPC for 1 frame only)?
    • How does this timing correspond to the frame timing?
    • Do you have a version of your chain that is closes to the SDK and if so, can you try running the same configuration on that version and make sure there are no changes causing this?
    • Can you also make sure that you do not have print logs enabled when debugging? 


    Regards,

    Kaushik

  • 0 in reply to Kaushik Gowda
    Prodigy 210 points

    Thanks Kaushik for your hints. 

    I have executed only 1 frame to check frame timing on DSS side. However, it doesn't seem correct. 

    Based on the raw timestamp, framestart at: 23,630,045,739 and DSS received command 114 at 23,724,768,158 hence duration is (23,724,768,158 - 23,630,045,739) / (600Mhz) = 157.870 ms

    While frame periodicity is only 50ms, that's why I think there is something wrong with this. 

    Please let me know your thoughts. 

    Thanks