• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 1185 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/IWR6843ISK: xdc.runtime.Error.raise: terminating execution

user6187576
Intellectual 385 points

Part Number: IWR6843ISK
Other Parts Discussed in Thread: IWR6843

Tool/software: Code Composer Studio

Hi TI Expert,

I add CAN-FD Tx and Rx into SDK 3303 demo image project, but i'm getting runtime error like this

{module#54}: line 99: error {id:0x10000, args:[0x1c1c8, 0x1c1cc]}
xdc.runtime.Error.raise: terminating execution

-------------------------------------------------------------------------------------------

test step:

1. falsh xwr68xx_ccsdebug.bin (from SDK 3303) into IWR6843;

2. Add CAN-FD Tx and Rx into SDK 3303 demo image project;

3. Test on CCS 8.3.0: when run CANFD_transmitData, getting runtime error like this

{module#54}: line 99: error {id:0x10000, args:[0x1c1c8, 0x1c1cc]}

xdc.runtime.Error.raise: terminating execution

  • 0
    TI__Mastermind 21025 points

    Hi,

    I'm guessing there is something not initialized.  I would suggest running the CANFD example code in the SDK's CANFD driver test folder, just to verify that you can see data on the output pins.  Then, examine how the CANFD module is initialized in the example code and what other objects it depends on that need to be initialized as well (eg. handles to other objects).

      -dave

  • 0 in reply to db_woodall
    Intellectual 385 points

    Hi TI Expert,

    I have test the CANFD example code in the SDK's CANFD driver test folder, and it tesk ok.

    so now I try to add CANFD RX/TX into IWR6843 demo image (refer to "Adding CAN-FD Tx and Rx to an Existing mmWave Project.pdf"), but test failed.

    BRs

  • 0 in reply to db_woodall
    Intellectual 385 points

    Hi TI EXPERT,

    Seems this issue be related with logging function System_printf(). After deleting the logging function System_printf() in canfd code, canfd code work fine.

    Could you please check why System_printf() cause this issue. Both canfd and System_printf() can't work at the same time?

    BRs

  • 0 in reply to user6187576
    TI__Mastermind 21025 points

    There is not a hardware reason why the two cannot work together. The issue is that printf is very slow and will break real time with nearly every usage. 

  • 0 in reply to db_woodall
    Intellectual 385 points

    Hi TI Expert,

    > The issue is that printf is very slow and will break real time with nearly every usage. 

    ==> Could you please check if there is any printf function will not break real time?

    BRs

  • 0 in reply to user6187576
    TI__Mastermind 21025 points

    If you are using system_printf for debugging purposes, there are other ways to catch what is happening, such as keeping a "history buffer" where you add entries into an array to mark that something has happened in your program. You can also add timestamps to log when the events occur. If you are using the printf just for normal output, you will need to use one of the serial I/O peripherals instead.  printfs are only used to log an error condition before shutting down.  This is typical of a realtime embedded system.

     -dave