IWR1443BOOST: TIDEP-0091:level sensing demo: Distance Outputs

Akash,

I have tried uncommenting that line and then rebuilding both demos for IWR1443 and MSP432. After that, I ran the demo and it printed out "measurement timeout" when I tried to take a measurement. But it still doesn't print out the distance data when I have that line uncommented which is weird.

Thanks,
Kyle

Also, this is the output I get when I uncomment the "#define REPORT_IR14_TIME_MEASUREMENTS" line and try to take a measurement.

Hi Kyle,

Can you confirm you've made the correct board modifications described in the getting started guide?


Cheers,
Akash

Hi Akash,

Yes I can. I was looking into the issue and found a few things, and I have a few questions.

1) I never added R164, so I tried adding it. But it is very tough since the resistor is so small. In the getting started guide, it mentions that R164 is optional. So do I need R164 if I don't care about the timing measurements? I am only looking for distance outputs.

2) I have the "#define REPORT_IR14_TIME_MEASUREMENTS" line commented out in the MSP432 code. Is there anywhere else I need to comment it out? The other lines that I found that contain "REPORT_IR14_TIME_MEASUREMENTS" are #ifdef statements, so I wouldn't think those need to be commented out, but I'm not sure.

3) In the guide, it states to add 0 ohm resistor R162. I added this one, and I am able to turn the IWR1443 on and off. However, in the picture on the guide, R9 is also pointed to, but never mentioned. Do I need to add a 0 ohm resistor to R9 as well?

4) When I mated the MSP432 and IWR1443, then removed the MSP432, it pulled off a trace on the IWR1443 on J4. I have included a picture. Will this be a problem with getting the distance outputs? I saw on the schematic that the trace connects to SOP0, so i'm hoping it won't affect the functioning of the level sense demo. 

Thanks & Regards,

Kyle

Hi Kyle,

You should definitely get a new MSP432 Board at once. I cannot predict what kind of problems will occur when you have dislodged the trace of your power connector.

You'll need to add both R162 and R9, both resistors are mandatory.

R164 is not mandatory but is highly recommended. It will be a mandatory requirement in the next revision to this TI-Design which will be released in a few weeks.

The #define REPORT_IR14_TIME_MEASUREMENTS only appears in demo_common.h.


Cheers,
Akash

Hi Akash,

Thanks for the reply. R162 is there and I added R9, but R162 is tiny and very tricky to solder, so I have not added it.

It is on the IWR1443 that the trace came off, but it is still able to take measurements if I just run TIDEP-0091 program using only the IWR1443 and without the MSP432. So I'm not sure how much that is a problem.

So I realized that whenever I run the code and try to take a measurement, the MSP432 gets stuck in the SPI_data_transfer function and essentially is waiting for the IWR1443 to take a measurement and send its data (see the first picture I posted in this thread where MSP432 gets stuck). However, I found out that if I run the IWR1443 code through CCS while the MSP432 is stuck and waiting for the data, it will take a measurement and send data through SPI. So the issue is not with SPI, it is with the MSP432 telling the IWR1443 to take a measurement. See picture, the 2nd set of data.

So I have some more questions

1) Do you have any idea why the MSP432 would get stuck in the SPI_Transfer_data function and not be able to tell the IWR1443 to take a measurement? Especially since now I have R162 and R9 on the board, it seems the program should work.

2) Do you know the specific pins used in the connection between IWR1443 and the MSP432 in this program? So I can check the pins with an oscilloscope.

3) Is there any way to get the IWR1443 to take continuous measurements on its own? I would like to have the IWR1443 take continuous measurements on its own, as soon as it turns on. But I was having trouble figuring out how to do this.

Thanks & Regards,

Kyle

Hi Kyle,

This question is now outside the scope of this thread, if you'd like to continue this discussion then I'd recommend opening up a new one!

Cheers,
Akash