• Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 718 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.

debugger issue

vineet kumar
Intellectual 730 points


Hi 

I am presently working on spectral digital 816x/389x EVM board. I am using code composer studio 5.3.0 version with XDS100V2 jtag emulator. when i am trying to debug hellow world program i am getting error

CortexA8: Trouble Writing Memory Block at 0x40305a28 on Page 0 of Length 0x1a8: (Error -2130 @ 0x40305A28) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.872.0)
CortexA8: GEL: File: C:\Documents and Settings\CMTI\workspace_v5_3\newtry\Debug\newtry.out: Load failed.

the procedure i am following is 

this is the configeration i am doing for the hellow world project. but i am getting the above mentioned error .

please help me out

 

  • TI__Guru**** 474681 points

    vineet kumar said:
    CortexA8: Trouble Writing Memory Block at 0x40305a28 on Page 0 of Length 0x1a8: (Error -2130 @ 0x40305A28) Unable to access device memory

    That is valid memory so you should be able to load your program. What does you actual target configuration ccxml look like? Also provide a screenshot of the debugger.

    I also suggest looking at the below topic:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS_-_Data_Verification_Errors

    Thanks

    ki

  • in reply to Ki
    Intellectual 730 points

    Hi 

    I have went through the link but not able to solve the problem. below are the screen short of how i am configuring my code composure studio

    I am presently in working on spectrum digital 816x/389x board. I simply try to execute the helloworld program but i am unable to figure out where i am doing wrong .

    I am also have doubt which arm ARM3892 or ARM3894 is configured for 816x/389 EVM. There are also two option when you are selecting Davinci 816x the one option is DM816X OR the other option is EVM DM816X which option should be selected.

    please help me out, i am realy finding it diffcult to overcome this problem.

  • in reply to vineet kumar
    TI__Guru**** 474681 points

    Could you zip up and attach here your *.ccxml file and your *.out file?

  • in reply to Ki
    Intellectual 730 points

    hi Ki-soo

    thanks for replying. Below is the zipped file of my .cmd and .out file of my project. 

  • in reply to vineet kumar
    TI__Guru**** 474681 points

    Thanks Vineet. I am able to load your program without any problems on my 816x/389x EVM. Could you attach the ccxml file you are using to debug?

    Thanks

    ki

  • in reply to Ki
    Intellectual 730 points

    hi Ki-Soo

    below is the ccxml file for AM3892.

    6521.AM3892.zip

    one more thing i would like to know that 816x/389x board if i would like to program dm816x then which option should i chose dm816x or EVM DM816X. 

    As i am very much new to the board  i have a confusion that on the 816x/389x spectral digital board can we program both dm816x video processor and ARM389X. there are two processor or they are the same.

    please help me

  • in reply to vineet kumar
    TI__Guru**** 474681 points

    vineet kumar said:
    one more thing i would like to know that 816x/389x board if i would like to program dm816x then which option should i chose dm816x or EVM DM816X. 

    If you have the actual EVM, then I would select it. But your current selection should work too. I just verified it. I used your ccxml file to start a debug session and I was able to successfully load your out file with no problem. This leads me to believe it is some setting on your board. Please make sure all the various settings, switches and jumpers are in the correct position for CCS debug. Also try opening a memory view at address 0x40305a28 and see if you can manually modify memory. If you cannot, it may be some memory initialization/setup issue.

    Thanks

    ki