• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 701 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.

Regarding TCI6486 simulatore usage on CCSV4 version 4.0.2.01000

ramamohan
Prodigy 30 points

Hi,

I am working on video codec for TCI8486 SOC. We are facing issue for running code on 2 cores simultaneously.

When ever we try to load the code in second core we CCS simulator give below error on console and does not work in expected manner.

"C64+_4: Error: A memory access is pending for greater than 100000 CPU cycles. Check if all the CPU cores are running."

Same code we are able to run on EVM with out any issue.

Please find attached the code we are running along with the command file.

 

Please let us know if we are missing any thing whiele running the code.

 

Thank you,

Best Regards

Rama Mohana Reddy

 

SimulatorIssue.zip
  • 0
    Prodigy 30 points

     

    Correcting Typos,

     

    I am working on video codec for TCI6486 SOC. We are facing issue for running code on 2 cores simultaneously.

    When ever we try to load the code in second core we CCS simulator give below error on console and does not work in expected manner.

    "C64+_4: Error: A memory access is pending for greater than 100000 CPU cycles. Check if all the CPU cores are running."

    Same code we are able to run on EVM C6472 with out any issue.

    Please find attached the code we are running along with the command file.

     

    Please let us know if we are missing any thing whiele running the code.

     

    Thank you,

    Best Regards

    Rama Mohana Reddy

  • 0 in reply to ramamohan
    TI__Intellectual 1380 points

    Hi Rama,

     

    I guess, the application running on Core2 is accessing an internal memory address of an other core, which is not 'running'. And hence, the application running on Core2 times-out. I recommend you to run the simulation in all the relevant cores.

    Regards,

    Nizam

  • 0 in reply to Nizamudheen A
    TI__Guru**** 483141 points

    Rama,

    One thing to consider is that by default, CCS will try to auto run to main on a program load. So when you are doing a program load, it is also try to run to main. Given Nizam's explanation, it makes sense you saw the error on the program load since it is also trying to run when the other cores are not running. When I disabled the autorun to main, I didn't get the error. You can disable the autorun in several places. The global setting is in: 'Windows->Preferences->CCS->Debug->Debugger Options->Generic' and look under 'Auto Run Options'.

    ki