AWR1843BOOST: Technical issues, MRR lab

Hi,

Zhonghui Xu said:

Also, SOP0 – ON, SOP1 – ON, SOP2 – OFF is the SOP configuration used.

For functional boot mode in AWR1843, the SOP mode should be SOP0 – ON, SOP1 – OFF, SOP2 – OFF. Could you try with this?

Regards,

Aayush

Hi Aayush,

Thanks for the answers. We have changed the SOP[2:0] from 011 to 001 (functional mode). But now we are getting an error stating, “Break at address 0x802e40 with no debug information available, or outside of program code”. I have attached the screenshot of that error message for your reference.

Please help us solve this error.

Best regards,

Hi Aayush,

Is there any update?

Thanks.

Best regards,

Hi,

Could you ensure that the ccsdebug image is flashed on the device before trying to load code via CCS.

Are you receiving this message as soon as the core is connected, or after loading the image? If it is after core is connected, you can try to reset the core using the reset button at the top bar

Regards,

Aayush

Hi Aayush,

Thanks for your response in respect to our last query. We flashed the ccsdebug image before trying to load the code via CCS. We tried resetting the core and the problem rectified. However, we came across a new issue this time.
We undertook the following steps:
1) Imported MRR_Beamsteering (lab 11) in CCS.
2) Built both mss and dss and got .bin file, .xe674 file, .xer4f file.
3) Flashed ccsdebug.bin in the kit using Uniflash (in Debug mode SOP[2:0] -> 011)
4) Changed to functional mode (SOP[2:0] -> 001)
5) Created target.ccxml file and clicked on Launch Selected Configuration
6) In Debug window, Clicked on Connect Target

7) Then loaded both .xe674 and .xer4f files in their corresponding cores.
8) Grouped the cores and clicked Run.
9) Output console in CCS displayed: “Debug: MMWave has been configured for MRR. Debug: Sensor will start momentarily.”
10) Then opened GUI MRR_viz_1_4 and changed the data port.
11) The GUI fails to show any live data.
In the process, we have loaded the “dss and mss binary files” in the kit. Despite connecting the COM port correctly in the MRR_Viz_1_4 GUI, we are unable to get the live display.

Kindly help us to clear this issue. I am attaching here with the screenshots for your kind reference.

           

Thanks,

Best regards,

Hi,

After the "sensor will start momentarily" prompt, the data should start streaming out. 

I would like to know if any data can be seen on the Auxiliary data COM port via a tool like TeraTerm of PuTTy at a baud rate of 921600. Even if no points are detected, some data is sent out over UART per frame once the lab starts. This would help see that.

Regards,

Aayush

Hi Aayush,

The Auxillary/ Data COM port we use is COM3. We used Tera Term to view the data coming out of COM3. But, we couldn’t see any data in COM3. The Tera Term output window was blank. We tried in PuTTY too, but we got same result.

Please help us in getting to the next step. Expecting your reply soon.

            

Thanks,

Best regards,

Hi Aayush,

Is there any update?

Thanks.

Best regards,

Hi Aayush,

I haven't received your reply. Please follow up.

Thanks.

Best regards,

Hi,

With the steps detailed, you should have observed some output. I will propose the following:

1. If you can share the .xer4f and .xe674 binaries with this thread, I can try to run them on my end and see if I can recreate the issue.

2. Could you share the toolbox version being used, and try running the prebuilt binaries of the lab? This will help rule out possible build issues.

3. Could you try running the prebuilt binaries of the out of box demo in the SDK and see if that is working as intended?

Regards,

Aayush

Hi Aayush,

I get feedback from customers:

1) I have attached the binaries used with this thread.

Binary files.zip
2) The toolbox version used is 3.6.0.
3) Yes, when tried running the demo file of the OOB demo in the SDK, it is working.

Thanks.

Best regards,

Hi Aayush,

Is there any update?

Thanks.

Best regards,

Hi,

I tried out the binaries and was able to see the output on the visualizer.

As you cannot see any output on Teraterm either, one suspicion that I have is if the binaries are executing correctly on the device.

1. You mentioned that for flashing the ccsdebug image the SOP setting used was 011. Could you confirm this? The SOP setting needed for flashing is 101, not 011.

2. Could you post a screenshot of the CCS log that appears when the binaries are run?

3. Could you try flashing the .bin image of the lab directly and see if that seems to work?

Thanks & Regards,

Aayush

Hi Aayush,

At present, I haven't received the updated information from the customer. I'll feed back to you immediately if there is any update.

Thanks.

Best regards,

Hi Aayush,

Sorry for the delay. Here are our response for the questions asked:

1. The SOP setting used is 101 as given in the document.
2. I have attached the screenshot with this thread.

3. When we tried flashing the .bin image of the lab directly, we can observe the output. However, when we try to load the code using CCS we could not see any output.

Thanks.

Best regards,

Hi Aayush,

I would like to give some more clarity on the previous conversation. We found that there are two xwr18xx_mrr_demo.bin files available.
1) One is located in the mmwave_automotive_toolbox_3_6_0\labs\lab0011_mrr_beamsteering\prebuilt_binaries\xwr18xx_mrr_demo.bin folder, which is provided in the automotive toolbox folder. When we tried loading this binary, we could get output in the MRR GUI.
2) The second file is created when we are compiling the lab in CCS and it is located in MRRtest\mrr_18xx_mss\Debug\xwr18xx_mrr_demo.bin folder. When we tried loading this binary using Uniflash, we could not observe any output (same issue as that of trying to load mrr_18xx_dss.xe674, mrr_18xx_mss.xer4f binaries using CCS) in the MRR GUI.
I am also attaching the xwr18xx_mrr_demo.bin that was created in the Debug folder for your reference.

xwr18xx_mrr_demo.zip
I hope this would add some more idea about our issue. I am waiting for your reply.

Thanks.

Best regards,

Hi Cesar,

Thank you for your help.

My customer feedback:

"We actually have built the dss project first and then built the mss project. We have already built the projects in the same order as you mentioned. Still, we face this issue."

Best regards,

Hi Cesar,

Automotive toolbox 2_9_1 is working fine as mentioned by you. Also, the latest version does not work. Thanks so much for your help.

Best regards,