I have been having a frustrating day. I have worked with GT16's Coldfires and ARM technology and never before have I had such issues trying to load the sample code. I have now figured out the difference between the debug sda and the file system sda. I have also finally got the serial port and PEmicroopenSDA drivers working. Then I ahve got LED_blink. Whenever I try to program the board it gets to the point of loading the code and then says:
Failed to resume target process
Downloading binary to target
I am at my wits end and about to give up on the whole programming adventure. Please help!
That error message indicates that the debugger is not able to connect to the target or to get control over it. I assume your board and microcontroller is powered (there is typically a jumper on the board to unpower the processor).
And have you plugged in the USB cable on the correct (OpenSDA) USB port?
And you are sure you loaded the P&E *debug* firmware on the board?
Erich
I am using codewarrior 10.6 and the FRDM-K20D50m. I have got the USB cable plugged into the correct place and codewarrior picks up that the connection interface is OpenSDA Embedded Debug and it picks up the port. I have loaded the debug firmware on the board.
It looks like it loads the program but encounters the error on launching it.
I am not sure how to check that the Open SDA connection setting is configured for SWD and not JTAG?
It is here:
Yes that is selected. Interesting test. If I create my own code from scratch then it wqill program - but I cannot get the LED to blink. If I download anyone elses code such as from here:
Or from the freescale LED_Blink with Codewarrior then I get that error
I'm also having this problem. Did you get to solve this problem?
Also I cannot use any pins connected or shared with the JTAG such as the blue LED - which is always on if I manage to get it to program
To use the JTAG/SWD pins as normal input/output pins, you need to reflect this in the Pin Muxing. If you are using Processor Expert, this is very easy: go the the CPU component and disable the JTAG/SWD functionality. But be careful with this: if you do this, this means you will not be able to use it for debugging. So I recommend that you do this with some delay after reset, so you have a chance to connect to your target with a debugger after startup.
Hi
Which FRDM board and which development environment?
Have you checked that the Open SDA connection setting is configured for SWD and not JTAG?
Regards
Mark