• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 210 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.

Compiler/66AK2H14: Running example openMP project hangs processor

Christo Labuschagne1
Intellectual 290 points
Part Number: 66AK2H14

Tool/software: TI C/C++ Compiler

Good day

I'm trying to build and run the openMP project found at this link:

I have attached the project I've created. 

OpenMP_test.zip

It compiles but when I load it on the EVMK2H the DSP hangs.

C66xx_0: Trouble Writing Memory Block at 0xa8000000 on Page 0 of Length 0x57fe: (Error -1202 @ 0xA80057FC) Device core is hung. The debugger will attempt to force the device to a ready state to recover debug control. Your application's state will be corrupt. You should have limited access to memory and registers, but you may need to reset the device to debug further. (Emulation package 9.2.0.00002)

What am I missing with this?

I have 3 warnings when it compiles:

Description	Resource	Path	Location	Type
#10068-D no matching section	linker.cmd	/OpenMP_test/Debug/configPkg	line 118	C/C++ Problem
#10247-D creating output section ".tbss" without a SECTIONS specification	OpenMP_test		 	C/C++ Problem
#10247-D creating output section ".tdata" without a SECTIONS specification	OpenMP_test		 	C/C++ Problem

Could that be related?

Thank you for the feedback

  • 0
    TI__Guru** 116170 points

    Christo,

    BAsed on your error message, I am not sure that the issue occurs due to OpenMP yet. The error message "Trouble writing to memory block 0xa800_0000" could be caused due to DDR issues or permission issues or MPAX setup issues to access higher DDR memory banks. Can you please indicate if you see this error on the EVM or on your custom platform. Are you able to open a memory browser to that address in CCS and do a manual read/write to do sanity check if you can write to the address over JTAG? Do you know what line of code in your test application generates the error.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Intellectual 290 points

    Hi Rahul

    Thank you for the feedback.  I have been able to resolve my issue.  This issue was caused by the fact that I did not run the gel file on connect.  

    Another issue that I ran into was that the same project needs to run on all the cores.

    I have attached the project for if someone ever wants to try the application.

    OMP_test.zip

    Kind regards