On 29.03.2012 11:38, salvador wrote:

>
>  adapter_khz 500

It works now!
The above statement was the problem.
I had to go down to 300kHz to make it work.
At higher frequencies, I get the errors I described before (Error: mini
program did not return to start
Error: timed out while waiting for target halted).

I don't know what's the cause of this.
Ok, it's a prototype board without ground plane, but the wires between
adapter
and PIC are very short, and the PicoTAP is directly plugged to the
board, without any
cable.

Nevertheless, it is not perfectly stable.
When I erase the flash and write it again, sometimes it hangs.
I have then to restart OOCD and do it again.

Also I learned that it isn't a good idea to have a #pragma config DEBUG = ON
statement in the code, because this will permanently lock you out from
JTAG after
flashing.
Can this be circumvented by using a srst at mclr?

Also you should never use #pragma config JTAGEN = OFF, or
mJTAGPortEnable(DEBUG_JTAGPORT_OFF), but this is pretty obvious.

So, many thanks for your help.

My original intention was to support the StickOS project (www.cpustick.com).
Rich Testardy is currently porting it to PIC32MX250F128B, to use it as a
cheap learning
tool for highschool students.

As you have to first flash the OS into the PIC, my idea was to support
beginners
with an easy method to flash a PIC32, without having to buy a PicKIT3.

Therefore I will definitely try it with a direct connection to the
printer port (poor
man's wiggler), and also with a 5$ Byte Blaster.

BTW: Do you think it would be possible to also support the 2-wire
interface of
the PIC32 as a transport? It is in fact nothing else than a JTAG, only
reduced to
2 wires.

Thanks
Uhrheber


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to