TIDEP-01012: TIDEP-01012: mmWave studio error

John Park

Part Number: TIDEP-01012
Other Parts Discussed in Thread: AWR1243

Hello,

I am using TIDEP-01012. It was working fine yesterday but the device is showing some error issue.

here is the log that i got from mmwave studio.

[15:36:58] RstdNet: Port 2777: Client 127.0.0.1:63461 - Connected
[15:37:00] Running script from MATLAB
[15:37:00] Setting up Studio for Cascade started..
[15:37:00] [RadarAPI]: ar1.SelectCaptureDevice("TDA2XX")
[15:37:00] [RadarAPI]: Status: Passed
[15:37:00] [RadarAPI]: TDAStatusCallback Event Registered
[15:37:00] [RadarAPI]: registerTDAStatusCallback Status: Passed
[15:37:00] [RadarAPI]: ar1.ConnectTDA("192.168.33.180", 5001, 15)
[15:37:00] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:00] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_VERSION_INFO Async event recieved() with status 0. TDA Version : REL_VISION_SDK_03_07_01_00 Aug 5 2019 15:04:45[15:37:00] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:01] [RadarAPI]: Device 1 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:01] [RadarAPI]: ConnectTDACaptureCard Status: Passed
[15:37:01] TDA Capture Card Status : CONNECTED!
[15:37:01] ConnectTDA Successful
[15:37:01] [RadarAPI]: ar1.selectCascadeMode(1)
[15:37:01] [RadarAPI]: Status: Passed
[15:37:01] selectCascadeMode Successful
[15:37:01] Setting up Studio for Cascade ended..
[15:37:01] [RadarAPI]: Device 1 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:02] [RadarAPI]: Device 1 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:02] [RadarAPI]: ar1.FullReset(1)
[15:37:02] [RadarAPI]: Status: Passed
[15:37:02] [RadarAPI]: ar1.SOPControl_mult(1,4)
[15:37:02] [RadarAPI]: Status: Passed
[15:37:02] Master : SOP Reset Successful
[15:37:02] [DeviceId-0] MSS power up done async event received!
[15:37:02] [RadarAPI]: ar1.PowerOn_mult(1, 0, 1000, 0,0)
[15:37:02] [RadarAPI]: Status: Passed
[15:37:02] Master : SPI Connection Successful
[15:37:02] [RadarAPI]: ar1.DownloadBssFwOvSPI_mult(1, C:\\ti\\mmwave_dfp_02_02_02_01\\firmware\\xwr22xx_metaImage.bin)
[15:37:05] Master : FW Download Successful
[15:37:06] [RadarAPI]: ar1.SelectChipVersion("AR1243")
[15:37:06] [RadarAPI]: Status: Passed
[15:37:06] [RadarAPI]: ar1.SelectChipVersion("AR1243")
[15:37:06] [RadarAPI]: Status: Passed
[15:37:06] [RadarAPI]: ar1.deviceVariantSelection("XWR2243")
[15:37:06] [RadarAPI]: Status: Passed
[15:37:06] [RadarAPI]: ar1.frequencyBandSelection("77G")
[15:37:06] [RadarAPI]: ar1.SelectChipVersion("XWR2243")
[15:37:06] [RadarAPI]: Status: Passed
[15:37:06] Device Status : XWR2243/ASIL-B/SOP:4/ES:1.1
[15:37:06] [RadarAPI]: ar1.RfEnable_mult(1)
[15:37:07] [DeviceId-0] BSS power up done async event received!
[15:37:07] [RadarAPI]: Status: Passed
[15:37:08] Master : RF Power Up Successful
[15:37:08] [RadarAPI]: ar1.ChanNAdcConfig_mult(1, 1, 1, 1, 1, 1, 1, 1, 2, 1, 0, 1)
[15:37:08] [RadarAPI]: Status: Passed
[15:37:08] Master : Channel & ADC Configuration Successful
[15:37:08] [RadarAPI]: Device 2 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:09] [RadarAPI]: Device 2 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:09] [RadarAPI]: ar1.FullReset(2)
[15:37:09] [RadarAPI]: Status: Passed
[15:37:09] [RadarAPI]: ar1.SOPControl_mult(2,4)
[15:37:09] [RadarAPI]: Status: Passed
[15:37:09] Device 2 : SOP Reset Successful
[15:37:09] [DeviceId-1] MSS power up done async event received!
[15:37:09] [RadarAPI]: ar1.AddDevice(2)
[15:37:09] [RadarAPI]: Status: Passed
[15:37:09] Device 2 : SPI Connection Successful
[15:37:09] [RadarAPI]: Device 4 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:10] [RadarAPI]: Device 4 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:10] [RadarAPI]: ar1.FullReset(4)
[15:37:10] [RadarAPI]: Status: Passed
[15:37:10] [RadarAPI]: ar1.SOPControl_mult(4,4)
[15:37:10] [RadarAPI]: Status: Passed
[15:37:10] Device 3 : SOP Reset Successful
[15:37:10] [DeviceId-2] MSS power up done async event received!
[15:37:10] [RadarAPI]: ar1.AddDevice(4)
[15:37:10] [RadarAPI]: Status: Passed
[15:37:10] Device 3 : SPI Connection Successful
[15:37:10] [RadarAPI]: Device 8 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:11] [RadarAPI]: Device 8 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[15:37:11] [RadarAPI]: ar1.FullReset(8)
[15:37:11] [RadarAPI]: Status: Passed
[15:37:11] [RadarAPI]: ar1.SOPControl_mult(8,4)
[15:37:11] [RadarAPI]: Status: Passed
[15:37:11] Device 4 : SOP Reset Successful
[15:37:42] [RadarAPI]: ar1.AddDevice(8)
[15:37:42] Status: Failed, Error Type: RESP TIMEOUT
[15:37:47] MSS Power Up async event was not received!
[15:37:47] Device 4 : SPI Connection Failed

over 1 year ago

0 James Murdock65 over 1 year ago

TI__Expert 3501 points

1) What do you see in the device manager?

2) Can you check the power supply and try another power supply?

3) Have you changed the FW images selected from your attempts yesterday?

4) Can you try a different EVM board?

0 James Murdock65 over 1 year ago in reply to James Murdock65

TI__Expert 3501 points

It also appears you are selecting AWR1243 in certain selections above. Please verify you have selected the correct device type.

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

1) In the device manager, it has two port like below image

2) I am using power supply of 12V 5A. and I tried other power supply and it is getting same error

3) Yes, I changed FW images and still it has same error

4) Using same lua script, different EVM board is working.

Yesterday, device was sometime working fine but something it gives error. Is there any thing that I should do?

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hello Mr. Park,

You mention that a second board is working. Could you check if there are any differences between the two boards?

Regards,

James

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

I don't think there is a big difference. It was working fine like yesterday, but when I turn it off and reconnect, it doesn't work. Sometimes it works and sometimes it doesn't.

0 John Park over 1 year ago in reply to John Park

Prodigy 90 points

Is the problem with device or is it problem with the mmwave program??
sometimes it is working well and data was saved properly.

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hi John,

Apologies for the delay. It seems you are seeing inconsistent results. Do you by chance have any damaged cables?

Regards,

James

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

I tried changing the cable, but the error continues to appear. If there is a problem with the device, is there a way to fix it?

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hello John,

You mentioned one device is working and the other is not. Could you confirm that they are both marked the same way on the top of the package?

Regards,

James

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

Hello,

Sorry for the late reply, I don't think there is any difference between a working radar and a radar with an operation error.

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hello John,

It is a bit difficult to debug since you have one working part and one non-operational part with no apparent differences. Could you try getting a third part?

Regards,

James

0 James Murdock65 over 1 year ago in reply to James Murdock65

TI__Expert 3501 points

Hello John,

Could you probe the VBGAP pin on the failing device to see if the device is waking up. you should measure ~0.9V.

Regards,

James

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

Currently I own two devices. If there is a problem with the device, is there a way to fix it? And I don't know the details about VBGAP pin. But when i connect to computer i can able to assess ssd using Winscp.

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hi John,

I think we just want to verify that the part boots up correctly. The BGAP pin is available e.g. on several of the caps. You could try to verify what you see on those caps.

Connecting to the computer may just mean you are communicating with the TDA2X host processor.

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

Hi, sorry for late reply.

I don't think the sensor is booting. Can you tell me what to do to make sure it boots up correctly?

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hi John,

No problem! If possible can you try probing the AWR_VBGAP_1?

Regards,

James

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

Hi, thanks for your reply.

I am sorry for keep asking, but i'm no sure what probing the AWR_VBGAP_1 means. Could you tell me how to probe AWR_VBGAP_1??

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hi John,

No problem. Can you use an oscilloscope to see what the voltgae on that cap looks like? cap C2_1 in the image I showed above?

Regards,

James

0 John Park over 1 year ago in reply to James Murdock65

Prodigy 90 points

Hi, sorry for late reply.
I think the device is not waking up when the device is getting error.
and right now almost every time it get connection error.
it seems to be problem with the device. So is there any solution when there is problem with the device??

0 James Murdock65 over 1 year ago in reply to John Park

TI__Expert 3501 points

Hi John,

I do apologize, but it's difficult to give a very good answer. If the device has been damaged there may not be much we can do. Have you been able to try to use an oscilloscope to probe the voltage on C2_1?

If the part was damaged somehow, it's a good idea to review your lab setup. Are there adequate ESD protections in place?

Regards,

James

Sensors

Sensors forum

TIDEP-01012: TIDEP-01012: mmWave studio error