Thanks for the replies. Ok, I CAN connect to OpenOCD with Telnet, it threw me because I expected to see messages like: > *Warning:no telnet port specified, using default port 4444 > Warning:no gdb port specified, using default port 3333 > Warning:no tcl port specified, using default port 6666* But I don't... I guess these messages don't exist any more?
I can connect with telnet to port 4444, and then if i just enter HALT and provided the flyswatter doesn't reset itself it seems to work fine so far. I had a problem with the Flyswatter once before resetting on me all the time and I suspected it was my USB cable. I haven't used it for a while but it seems to be doing it now again, which is why I am getting failed comms. Does anyone else have problems with flyswatters spuriously resetting themselves??? I threw out my suspect USB cable and this is a new one which I thought had solved my problem, but it is as unreliable as ever now. I wonder if it would be possible to harden OpenOCD against flyswatter resets so when it happens the connection to the flyswatter can be re-established without loosing debug state to the target. >> Using a fresh OpenOCD checkout from head (as of an hour ago). The >> problem I get is, after I connect, the flyswatter flashes >> LED2 and LED3 >> alternately for a while and then crashes out. This is my >> first attempt >> at using OpenOCD on PIC32 so I don't know if another version works >> better with it or not. >> >> > > SVN head is working fine for me on PIC32 - using Explorer16. > Most of the important stuff is being detected correctly, first suggestion > would be a full log > openocd -d3 will give lots more info. > > Cheers > Spen > > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
