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.

IWR1642: Chirping seems to hang-up when using xdctools_3_51_01_18 or newer

Part Number: IWR1642

Hello,

I have a project based on the SRR demo ported to IWR1642 (Two kind of frames are sent, the DSS processes them and send the resulting point cloud to MSS).

I'm using:

  •     CCS 12.6.0.00008
  •     bios_6_73_01_01
  •     mmwave_sdk_03_06_00_00-LTS.

This project works when I use xdctools_3_50_08_24, but when I use a newer version it hangs up : I have tried : xdctools_3_51_01_18, xdctools_3_60_01_27, xdctools_3_60_02_34 and xdctools_3_62_01_16.

By hang-up, I mean that the MSS doesn't receive the point cloud anymore and that its seems that no frames are generated at the RF level : Scoping the IWR power rail, I don't see the pattern I have habitually, where I can see the two different frames repeating regularly. The current consumption is stable (instead of varying in the working situation) and quite high, like if the RF TX was continuously ON.

In this hangup situation, the two cores are listed as "running" normally in CCS. When I pause the DSS, I see in ROV that the task processing the chirps and frames is "running" and the execution pauses in the clause processing one chirp, but the code execution while stepping from there seems completely erratic (to my eyes).

Do you know what is causing the problem?

What should I do/test/learn to progress on this?

Thank you!

Paul-André

  • My version of xdctools_3_50_08_24 was corrupted: System_vprintf was rendered as good as empty.

    This masked another problem: a call to System_printf just after MMWave_start crashes the system (as detailed in the question). I still have no idea why, but that looks more debuggable to me.

    Sorry and KR,

    PA