• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 255 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWRL1432: How to skip xSemaphoreTake when setting break point

Shawn Li(Radar)
Intellectual 775 points
Part Number: AWRL1432

Hi team,

I find this function in our motion and presence demo. After reading the code, I believe it's related to UART data transfer. I think it's responsible for transmitting the points to computer by UART. But it we set a break point in 4489 line, the program can't run to next line. Can you help look this?

And when I run the out file of motion demo, the output of UART are as follows:

Is it right? I think the COM16 should output some target parameters.

Regards,

Shawn

  • 0 in reply to Shawn Li(Radar)
    TI__Genius 10710 points

    Shawn,

    There was delay due to US Thanksgiving holiday. The team will be getting to you shortly.

    Thanks,

    Angie

  • 0 in reply to Angie Mitchell
    TI__Genius 10476 points

    Hey Shawn,

    Did you start the sensor of the device and verify that the program is still stalling at xSemaphoreTake? If the device sensor isn't running, then the mmwDemo_TransmitProcessedOutputTask won't give the gPowerSem semaphore. Therefore, the powerManagementTask won't be able to take from the gPowerSem semaphore and will stall until data starts to transmit over UART. This demo doesn't switch between power modes until the device sensor is running and collecting data, hence why the powerManagementTask is structured this way.

    Regards,

    Kristien