AWR2243BOOST: mmwavelink_example.exe stuck

Somehow image in my previous post can't be shown. I attached them below.

Hi Hank,

If you are running mmwavelink_example from DFP then device needs to be set in functional mode. As per your picture you have set jumpers on SOP-0 and SOP-1 header.

Connect only SOP-0 jumper (other SOP-1 and SOP-2 leave open) to make device in functional mode.

Then try the above example.

NOTE:

- If you are using DevPack with AWR***BOOST then SOP control can be done by the software (application/mmWave Studio). With DevPack, BOOST SOP jumpers can be overridden. 

- But with DCA1000EVM that override is not possible, user needs to manually set the Jumper on BOOST EVM to set device into functional (SOP4) or development mode(SOP2).

Regards,

Jitendra

Thanks Jitendra for the quick response. However, after "Connect only SOP-0 jumper (other SOP-1 and SOP-2 leave open)", still stuck in the same place, no difference. See the Jumper setting below. Look forward to your further debug instructions.

A few things have been done but still stuck at the same place.

1. Check all the power supplies on AWR2243boost EVM board, 1V, 1.2V, 1.8V, 3.3V, PGOOD, all good;

2. Refreshed DCA1000EVM using DCA1000_FPGA_RECORD_V2.8_05JUL2019.bit;

3. Check SPI signals on AWR2243boost board: SPICLK and MOSI are both at 0V, MISO and CS are both at 3.3V.

Please advise how to further proceed.

Hello Hank,

In this kind of scenario, we recommend testing the board with mwmave Studio first.

I don't any obvious reason for you issue. Could you confirm if experiment status with mmwave studio? You need to follow mmwave Studio user guide.

ANd with that you need to do two experiments one in functional and another in development mode.

Regards

Jitendra

Hi Jitendra,

Tried mmwave studio and used it to collect bin file and Post PROC. It works fine. I connected SOP0, SOP1 and left SOP2 open just as the user guide instructed. Could you please advise how to further debug? 

And what you do you mean to do two experiments one in functional and another in development mode?

Thanks

Hank

Hello Hank,

Did you try mmwave studio in functional mode (only SOP-0 jumper)? This way it confirms that it works with mmwave studio in functional mode.

If above experiment works in functional mode then looks like somehow mmwavelink_example is not able to reset the device which application does at the beginning. 

To confirm it is due to example reset- try manually reset when it prints device reset successful.

Regards,

Jitendra

Hi Jitendra,

I tried the two experiments. The results are below.

Experiment #1: mmwave studio in functional mode (only SOP-0 jumper)

Result: I can open the mmwave. But when I click buttons 1,2,3,4, it got stuck in 4th button, which shows "Downloading Firmware to device..." forever; 

Experiment #2:  Run mmwaelink_example.exe, when it gets stuck at "Device reset successfully", press NRST button (at the bottom) at the AWR2243boost EVM board. The button is circled out below in the picture.

Result: it didn't do anything with pressing NRST. Still stuck at "Device reset successfully"


Could you please advise how to proceed?

hello,

In Functional mode with mmwave studio you need to use single metaimage binary (firmware\xwr22xx_metaImage.bin) file from BSS FW text field.

Hi Jitendra,

In functional mode, I changed the binary file in BSS FW text field to firmware\xwr22xx_metaImage.bin and loaded it. Then it got stuck at 0% right there. See below. Please advise.

Hello Hank,

In SOP-4 functional mode, there is slight change in the step.

You need to connect SPI first, then download the firmware (meta image binary).

As mmwave Studio is meant to use in mainly SOP-2 (development mode), so functional mode details are not given in the documentation.

But here I asked to verify if device is working in functional mode or not, as you are facing problem with mmwavelink example which works in functional mode.

So, now coming back to studio in SOP-4 funcitonal mode, steps

1. Reset (Button:1)

2. Don't connect RS232, skip clicking Button-2

3.. Click SPI connect, it should connect without fail

4. Firmware download

5. RF Power up

Above step-3 should confirm that device is able to work in functional mode.

Regards,

Jitendra

Hi Jitendra,

Thank you for the detailed steps. The SOP-4 (functional mode) works fine now. So I guess it means functional mode is good. What can be the problem with the mmwavelink example then? 

If mmwave studio works in functional mode, then mmwavelink_example should also work without any issue.

When you start the application it first reset the device, if it is not able to do that for some reason then try to manually reset the AWR device (by pressing NRST on EVM).

If it also doesn't work then try to include FTDILibrary VS project to mmwavelink_example Visual Studio project, so you can step into all the callbacks and check where exactly it gets stuck (within FTDI-library source).

You can find the this library Visual studio project at this path--

C:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\ReferenceCode\FTDILib\SourceCode\vs\

Regards,

Jitendra

Hi Jitendra,

Interesting. I just tried mmwavelink_example a few times, it runs with no problem. Is it possible the steps you asked me to go through somehow changes the board's status?

Main issue at your end with mmwavelink_example is that it's not able to reset the board and blocked at wait-for-poweron-async-event.

So if you do device reset by mmwave studio then run, so effectively reset happens by studio and further steps is done by example, which makes that work.

I assume that you are unblocked with this issue now.

Regards,

Jitendra