AWR2243BOOST: Not Able to Restart the Device

Hi Kia,

Have you changed anything in the mmwaveconfig.txt file? If not, can you once try this setup with the mmWave studio and share your log results with us. I see one MSS CPU fault being raised in the screen shot you provided, and we will need to debug this further to get to the cause of this issue. 

Thanks,

Pradipta.

Hi Pradipta, 

I had changed the mmwaveconfig.txt file, and I thought maybe that would be the cause but I tried the original version and still got the same error. I am able to run it with the mmWave Studio with no problem. For mmWave Studio, I put the SOP1 pin back to 1. In mmWave Studio, I use a different lua script with different settings. Here are the messages: 

Thanks again
Kia

Hi,

Can you please send over the mmwaveconfig.txt file which you are using (the original version) so that we can once verify the sequence.

Thanks,

Pradipta.

Hi, 
I used a newer radar, and it works on that one. Nothing was wrong with the mmwaveconfig file. 

Thanks
Kia

Hi Kia,

Can you once confirm which SDK version you are using? Are you able to run any other example code on the kit?

Thanks,

Pradipta.

Hi Pradipta, 

I am using mmwave_dfp_02_02_03_01 for our AWR2243boost. I am able to run other examples on the kit after changing the mmwaveconfig.txt file. However, I am not able to able to enable second or third tx or chips. I am using Dynamic Chirp Test. For chirp configuration in rlChirpCfg_t section, I put the chirpStartIdx and chirpEndIdx both to 0, and for the second rlChirpCfg_t chirpStartIdx and chirpEndIdx are put to 1, the way I have them in my lua script when I use mmWave Studio 3.0.0.14. In the frame configuration, I put chirpStartIdxFCF and chirpEndIdxFCF to 0 and 1 respectively. But when the files are recorded, I only get half the data I expect to get, which I believe is due to only having one tx being enable. 

Is there a way that I can add other chirps as well?

Thanks, 
Kia

Hi Kia,

Can you share the configuration you are applying on the chip. I will need to see if we can reproduce this at our end or not?

Thanks,

Pradipta.

Hi Pradipta,

I cannot share the whoe configuration, but this is what I have for two chirps. I believe with this format only one chirp is being read, not both. Also, when I try to add another chirp with similar format, I encounter error 75. 
"Frame Configuration failed for deviceMap 1 with error 75"

#
#Chirp Configuration parameters, please modify if needed.
#rlChirpCfg_t
#
chirpStartIdx=0;
chirpEndIdx=0;
profileIdCPCFG=0;
startFreqVar=0;
freqSlopeVar=0;
idleTimeVar=0;
adcStartTimeVar=0;
txEnable=1;
#END

#
#Chirp Configuration parameters, please modify if needed.
#rlChirpCfg_t
#
chirpStartIdx=1;
chirpEndIdx=1;
profileIdCPCFG=0;
startFreqVar=0;
freqSlopeVar=0;
idleTimeVar=0;
adcStartTimeVar=0;
txEnable=2;
#END

#
#Frame configuration parameters, please modify if needed.
#rlFrameCfg_t
#
chirpStartIdxFCF=0;
chirpEndIdxFCF=1;


Thanks,
Kia

Hi Kia,

Let me try these config on my bench to see if i can reproduce the issue or not.

Thanks,

Pradipta.

Hi Kia,

Error code 75 represents that the Chirp used in frame is not configured by Chirp config API. Are you configuring both the chirps used in the frame. Can you use the chirp config get API to confirm that both the chirps are being configured by your script. 

Thanks,

Pradipta.

Hi Pradipa,
Can you please help resolve this issue at your earliest convenience? This is a blocking issue for us.

Daniel

Pradipta,

We are getting a mismatch with the chirp get API. 
This is the snippet of the config where we get the error code 75. Can you please check if Idx's are correctly set for 3 chirps? Do you see anything wrong in the config?
Let us know if any other information needed.

#Chirp Configuration 1
#rlChirpCfg_t
#
chirpStartIdx=0;
chirpEndIdx=0;
...
txEnable=1;
#END

#
#Chirp Configuration 2
#rlChirpCfg_t
#
chirpStartIdx=1;
chirpEndIdx=1;
...
txEnable=4;
#END

#
#Chirp Configuration 3
#rlChirpCfg_t
#
chirpStartIdx=2;
chirpEndIdx=2;
...
txEnable=2;
#END

#
#Frame configuration parameters, please modify if needed.
#rlFrameCfg_t
#
chirpStartIdxFCF=0;
chirpEndIdxFCF=2;
...
#END

Hi Daniel,

What is the mismatch you are getting when using the chirp get API. How are you calling the chirp set API. We will need this information to proceed with the debug. 

Thanks,

Pradipta.

Hi Pradipta,

We are not changing the chirp set API but using whatever the default is.

And this is the prints for chirp set API vs chirp get API. As you can see the configuration for the second chirp is mismatching.

profileId: 0, 0
freqSlopeVar: 0.000000, 0.000000
txEnable: 1, 1
startFreqVar: 0, 0
idleTimeVar: 0, 0
adcStartTimeVar: 0, 0
profileId: 0, 0
freqSlopeVar: 0.000000, 0.000000
txEnable: 4, 1
startFreqVar: 0, 0
idleTimeVar: 0, 0
adcStartTimeVar: 0, 0
*** Failed - Parameters are mismatched GetChirpConfig compare to rlSetChirpConfig ***

Hi Daniel,

Without the configuration and screen shots, it will be difficult to debug the issue. As per your previous posting

#Chirp Configuration 1
#rlChirpCfg_t
#
chirpStartIdx=0;
chirpEndIdx=0;
...
txEnable=1;
#END

#
#Chirp Configuration 2
#rlChirpCfg_t
#
chirpStartIdx=1;
chirpEndIdx=1;
...
txEnable=4;
#END

this is your configuration, and the error code was 75. 

Now as per your latest post 

chirp set API vs chirp get API.

profileId: 0, 0
freqSlopeVar: 0.000000, 0.000000
txEnable: 1, 1
startFreqVar: 0, 0
idleTimeVar: 0, 0
adcStartTimeVar: 0, 0

profileId: 0, 0
freqSlopeVar: 0.000000, 0.000000
txEnable: 4, 1
startFreqVar: 0, 0
idleTimeVar: 0, 0
adcStartTimeVar: 0, 0

So, your chirp set in both the cases shared is different. Please clarify your problem statement along with the issue you're facing so that we can try to replicate the issue or suggest a solution.

Thanks,

Pradipta.

Pradipta, I am not sure what "different" you are referring to! We set 1, 4, 2 as the txEnable when configuring three chirps. For the second chirp, get API is obviously returning a wrong value for the txEnable. We believe this is potentially a bug in the sample example code.

Error code 75 will come up later in the code.

Can you clarify your concern first then we can accordingly respond?

Hi Pradipta,

What's the latest update on this? We are blocked!

Hello Daniel,

Can you run "mmWaveLink_SingleChip_Example" present in the DFP package and share the "trace.txt" file that is generated. Also run the example as it is and do not apply any modifications.  

Thanks,

Pradipta.

Yes, we will provide it shortly.

Hi Pradipta, 

2844.trace.txt

This is the trace file without modifications. 

Thanks,
Kia