• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 289 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.

IWR6843AOP: understand xdc runtime error messages

RobinSpearhead
Intellectual 395 points
Part Number: IWR6843AOP

Hi mmw team,
 We use a oobdemo lab based firmware in our customised IWR6843aop radar device.

  • mmwave_sdk_03_06_00_00-LTS
  • XDCtool 3.61.2.27

I have added a auto start task to bypass CLI and start the radar sensor. However, I am getting xdc.runtime.error after MmwDemo_startSensor:

MMWave_flushCfg ok [0] 
myconfig initialize ok [0] 
MmwDemo_openSensor ok [0] 
 ========== Memory Stats ==========
                             Size         Used         Free      DPCUsed
    System Heap(TCM)        65536        49792        15744         1024
                  L3       786432        36864       749568
                 TCM        50176        24728        25448
MmwDemo_configSensor ok [0] 
Starting Sensor (issuing MMWave_start)
MmwDemo_startSensor ok [0] 
{module#56}: line 99: error {id:0x10000, args:[0x43d98, 0x43d9c]}
xdc.runtime.Error.raise: terminating execution

I'm just wondering how to interpret the XDC tool error message. For example, how do I know what module #56 is (which file)? So that I can find my firwmare bug it would be good to understand what this means.

 thanks

  • 0
    TI__Genius 17265 points

    Hi,

    Typically, the XDC runtime errors list the .c file which has crashed and on what line, so I am not familiar with this what module this may be referring to offhand. Let's focus on the changes you made for now and debug it together, and then perhaps while we try some things we will get a more helpful error message. For starters, did you ensure that the priority of your new task matches that of the CLI task that existed already? I know that the sensor start process can run into some pre-emption issues with the CLI task when the priority is modified.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 395 points

    Hi Alec,
     yes of course, I will do that: review changes step-by-step and debug.
    But anyway, I was hoping that it could somehow get closer to the bug by finding the module number in, for example, the linker file or the .map file.
    (It must be possible somehow, because after all it won't be a random number, isn't it?)


    best regards

  • 0 in reply to RobinSpearhead
    TI__Genius 17265 points

    Hi,

    Digging around on the forums for a bit, I found this post with a similar error. Could you confirm that you have flashed the CCS Debug binary onto the device, as mentioned in the CCS Debug Guide?

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 395 points

    Hi Alec,
    I have now been able to fix my latest bug. However, I haven't made any progress in understanding the xdc runtime error messages in general (...to know in the future).

    best regards

  • 0 in reply to RobinSpearhead
    TI__Genius 17265 points

    Hi,

    Due to the fact that the CCS debug image was not loaded, the device was not in a "known state" when the XDS110 debugger connected to it. This does not always cause errors and can make it difficult for the debug probe to give accurate device status. I suspect that the errors you see going forward should be more helpful in where they point you.

    Best Regards,
    Alec