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.

AWRL6432BOOST: AWRL6432BOOST

Part Number: AWRL6432BOOST
Other Parts Discussed in Thread: AWRL6432

Hello,
I encountered anomalies on my AWRL6432BOOST. Then, after flashing the "empty.release.appimage" code, I debug my own code (InCabin/AWRL6432_Capon2D). I get the configuration file from Matlab. I also get a "Done" response to the last "sensorStart" command. But then the data does not arrive. While debugging, the message "Failed to read!" appears on the Console screen as shown in the picture below. Everything was working normally for a long time. I've been encountering this problem since yesterday. I also tried to perform the ATE Calibration process again. But the result did not change.

  • Hi,

    What version of the SDK are you using? Did this change? Has anything else changed from when it was working to now?

    Thanks,

    Clinton

  • I am using "radar_toolbox_1_30_00_05\source\ti\examples\InCabin_Sensing\AWRL6432_Capon2D" as SDK. The code was working in such this for a long time before. There were no problems. But since yesterday it started giving this error. Is it related to memory corruption or is there a hardware problem? I didn't understand if the sensor is broken or not. But I didn't do anything different to cause this distortion. In what situations it gives the message "Failed to read!"?

  • Hi, 
    When I made a detailed review, I saw that the errors (Failed to read!) were given when I entered the "SemaphoreP_pend" function, which I marked in red in the picture.

  • Hi,

    please allow us 24 hours to look into this and we will provide a response here.

    Regards,

    Tim

  • Thanks for the response. Could you check which version of the silicon you have? You can follow the instructions at the link below to find this out:

    https://dev.ti.com/tirex/content/radar_toolbox_2_00_00_06/docs/hardware_guides/determine_silicon_revision.html

    And too confirm - is this where you found the image that you flashed?

    "C:\ti\radar_toolbox_1_30_00_05\source\ti\examples\InCabin_Sensing\AWRL6432_Capon2D\prebuilt_binaries"

    Thanks again,

    Clinton

  • Hi,
    Thanks for your review. I wasn't sure about the silicone version number. You can find pictures of the device and the content of the QR code below.




    I was using code that I had debugged and was working before. I flashed the code "C:\ti\radar_toolbox_1_30_00_05\source\ti\examples\InCabin_Sensing\AWRL6432_Capon2D\prebuilt_binaries". I now encounter the following error while loading the config file.



    I don't know if this error is related to the factoryCalibCfg operation. Because I am flashing, it is not possible to debug.

  • Hi,

    The picture you provided is not of the radar device. The device looks like the rendering at the top of the identification page I sent. You'll see the patch antenna connecting to it on the board. I don't see the silicon rev information in the other references you shared.

    Are you using a modified version of the visualizer? Could you try running the .exe with the original cfg included in the Radar Toolbox for this demo?

    Thanks,

    Clinton

  • Hi,



    I use the original Matlab visualizer (AWRL6432_LifePresenceDetection_visualizer) and the original cfg file in Radar Toolbox.

  • Hi,

    Thanks for the follow up. It looks like you may be using a modified version. I see in the command line output you send that the error is in "AWRL6432_LifePresenceDetection_visualizer_2" The visualizer, as provided, does not have this "_2" naming. Line 49 of 'sendconfiguration' also does not line up with the error reported in the unmodified code in that toolbox version.

    Could you try the .exe provided at the directory listed below?

    C:\ti\radar_toolbox_1_30_00_05\tools\visualizers\InCabin_LifePresenceDetection_GUI

    Thanks,

    Clinton

  • Hi,
    Sorry, my mistake was related to leaving the S1.6 jumper in the wrong position. Thank you for your help.