AWR1843BOOST: 在利用CCS调试时,连接内核C674X_0到dss下的.xe674文件出错

Part Number: AWR1843BOOST

Hi Friend

I'm a novice in radar board development. When reproducing the official automated_paking case of TI
[Reference case webpage:自动泊车 18xx 用户指南
].

When reaching step 4 of Build the Firmware form Source Code, Execute the Compiled Lab, it seems that the kernel C674X_0 cannot be correctly connected to the.xe674 file under dss. Even so, no error message was output in the Debug Output interface. Instead, the data as shown in the figure was output in the VARIABLES section



I'm quite puzzled because I followed the user's instructions in every step. I searched on forums and other possible places but couldn't solve this problem. I hope to get your answers.Thank you very much.

Your most sincere one

Young Louis


Here are some of my configurations (please check them, If you need more information, please let me know) :
The version of CCS is 20.2.0

  • 感谢您对TI产品的关注。
    我们正在核实您的问题,请等待我们的答复。

  • Hi 

    Pls flash your device with CCSdebug binary, then put the SOP state as 001 (functional mode), then reset and connect cores in CCS.

    Let me know if there are still problems after following above procedure.

    Thanks

    Ken 

  • Hi Ken

    Sorry again. It still didn't work.

    I followed your operation. The process screenshot is as follows


    And I re-imported the official project, performed rebuild again, and generated corresponding files for the two projects. Then, after creating the.ccxml file in the debug interface and connecting it to the kernel Cortex_R4_0, I found the following output (it seemed to have a similar output yesterday, but I didn't notice it)



    Then connect the kernel C674X_0, and the output is as shown in the following figure


    I have a question at present. Are these errors related to the location of the ccxml file?
    All my projects are placed in the directory [D:\TI\CCS_Project\test_project]
    The location of the added ccxml is in the directory [C:\Users\Idle\ti\CCSTargetConfigurations]
    Here I post the configuration of the ccxml file for your reference


    Looking forward to your reply again. Thank you very much.

    Young Louis

  • Hi 

    Can you pls help rebuild your project with the SDK and CCS versions listed in demo user guide?

    I noticed you are using theia CCS20 for debug. which is not good support to TI sysbois os.

    Thanks

    Ken

  • Hi,
    Ken, 

    Recently, I'm on summer vacation and haven't been working. I'm sorry for taking so long to reply to you, but I still did the following work during this period.

    I followed your instructions and replaced the CCS with a lower version. According to the user manual provided by the official, the ccs should be version 8.3 or above. So I used versions 9.3.0 and 11.10. During the process, I also encountered another problem, which I will explain to you at the end of my reply.

    First of all, when I first used these two versions, I never encountered the error message I had before. Later, when I tried to use the latest version of CCS20 again, I found that the previous problem completely disappeared. Although this is a good thing, I don't quite understand why this problem occurred.

    Secondly, when I was using these three versions and re-debugging according to the official user manual, new problems emerged:
    C674X_0: Error: DPM Report 4 received with error:-40112 arg0:0x64 arg1:0x814a3c

    C674X_0: xdc.runtime.Main: ".. /dss_main.c", line 256: assertion failure

    C674X_0: xdc.runtime.Error.raise: terminating execution

    Then I was committed to solving this problem. At first, I didn't find the reason, so I was quite confused. But this afternoon, I suddenly found a post:
    AWR1843AOPEVM: Automated Parking Demo in CCS Debug - 传感器论坛 - 传感器 - E2ETm 设计支持

    He encountered the same problem as me, and then I referred to its solution and reduced the value of numLoops to 64, thus solving the problem.


    To sum up:
    Although there are no longer the problems I had at the beginning during the debugging process, I still don't know the reason.
    A new issue emerged later, reporting an error of -40112. However, I managed to solve it by referring to the previous problem post, but I'm still not clear why numLoops needs to be reduced.
    3. The third problem encountered, 9.3. Both version 0 and version 8.3.1 (which I have also downloaded) of CCS cannot access resource exploer within the software. I checked the official guidance method and operated it, but still couldn't solve the problem.


    Although I have successfully resolved the issues related to the import and debugging of the official project routines at present, I still cannot understand the specific reasons. If you are clear about the causes of these problems, I hope you will not hesitate to offer your guidance.

    Thank you

    Young Louis

  • Hi 

    Glad to know this issue is not blocking you any more.

    Num Loops contributes to the total chirp number in a single frame, which require much more compute power and more stringent timing/mem of DSP, 

    The codes in  dss_main.c", line 256 should be a function named as something similar to  DebugP_assert(expression). 

    Pls debug to see why the "expression" is not satisfied any more to get the root cause.

    Thanks

    Ken