Unable to debug

Hello Daram,

DARAM said:

i tried to put some break points

were you successful?

DARAM said:

,now no break point is set but still i was been thrown these errors

CCS will try to automatically reset any breakpoints you set from the last debug session. You have to explicitly clear them if you do not want this to happen. Why the beakpoint setting is failing, I'm not sure. You didn't provide a lot of details. It could be that some target initialization is needed before you can set them.

Thanks

ki

Ki-Soo Lee said:

were you successful?

No this did not help i am really vexed up i am trying from morning some times it allows me to debug,i tried to power off the debugger,CCS and restart everything the same is happening again

Ki-Soo Lee said:

Why the beakpoint setting is failing, I'm not sure. You didn't provide a lot of details. It could be that some target initialization is needed before you can set them.

may i know ,what other details you are expecting from me

DARAM said:

may i know ,what other details you are expecting from me

The details I am looking for is listed in the forum readme:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx

Thanks

ki

 Code Composer Studio Version: 5.2.1.00018

 Operating System:Windows 7

 Emulator under Use:XDS100V1

 my problem occurs when i try to debug

 below are the debug details:

 as soon as i try to load the program to RAM i get an error on console as below

 C55xx: Breakpoint Manager: Retrying with a 55 Hardware breakpoint

C55xx: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x32ad8: (Error -1066 @ 0x32AD8) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.747.0)
C55xx: Breakpoint Manager: Retrying with a 55 Hardware breakpoint
C55xx: Trouble Setting Breakpoint with the Action "Process CIO" at 0x368e3: (Error -1066 @ 0x368E3) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.747.0)
C55xx: Breakpoint Manager: Retrying with a 55 Hardware breakpoint
C55xx: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x376fc: (Error -1066 @ 0x376FC) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.747.0)

 and further i am not able to run the program

DARAM said:

below are the debug details:

 as soon as i try to load the program to RAM i get an error on console as below

Some more information which may help:

Which C55xx device are you using, to be able to check the memory may?

Can you enable Debug Server Logging and attach the log file for when the failure occurs.

Chester Gillon said:

Which C55xx device are you using, to be able to check the memory may?

i am using c5515 DSP,but i am not able to figure out what happened surprisingly the error has gone,now i am successfully able to debub......

my computer has 2 front panel USB ports one is connected with the Emulator i am using .to other another USB ,a another device (not emulator)which is doing some other work,after removing that USB device and connecting it to back panel resolved the problem 

is this a coincidence or what,the situation repeated again when i re connected the USB to the 2nd port

DARAM said:

is this a coincidence or what,the situation repeated again when i re connected the USB to the 2nd port

If the other device uses the same FTDI device as in your c5515 DSP emulator, maybe CCS tries and communicates with the other USB device instead of the emulator.

With the 2nd USB device plugged in:

1) Does the test option on the target configuration still work?

2) Does changing the the target configuration to select the emulator by serial number then allow the debugger to work?

Selection by serial number is supposed to allow more than one emulator to be used - but if there is a conflict with a 2nd USB device maybe selecting by serial number will help - see http://processors.wiki.ti.com/index.php/Multi-Emulator_Debug_with_CCSv5

Chester Gillon said:

With the 2nd USB device plugged in:

1) Does the test option on the target configuration still work?

yes all the tests have succedded 

ok now the problem is  i have removed the other usb so its clear that the problem is not because of any device connected this is just a coincidence but there is some other problem here is  my snap shot of device manager,device details which you may find appropriate