*Sigh* Trust me and then ignore me. Two minutes after sending this email I managed to get the bloody thing re-programmed !
Thanks for the help, Andy On 13/02/2008, Andy Guest <[EMAIL PROTECTED]> wrote: > > I've been trying to sort my uncommunicative puck without any joy. There > has been a slight change. Now when I try to program with the tiny bootloader > I get an error back immediately "Could not connect to COM5". > > Just to be sure am I trying to do this correctly. Load up tiny > bootloader and get it ready to go. Switch on epuck. Click "Write" in tiny > app and try to hit reset button as soon as possible ? > > A possibly related question. On the main board there is a second button > that looks like the reset button. It's hidden under the board with the > speaker on. The button is almost directly under the bluetooth. What does > this button do ? > > It wouldn't be so bad if I could blame myself for writing a dodgy > controller but its one I downloaded from the e-puck site. I'm a bit confused > as to which one it is, it is one of sercom, advanced sercom, or swiss_demo. > I'd guess at one of the sercoms because none of the other program selections > start up any of the demo programs. > > Andy > > > > On 07/02/2008, Alexandre Campo <[EMAIL PROTECTED]> wrote: > > > > Hi Andy, > > > > This happens indeed when the e-puck is flooding the BT socket. > > To solve this cleanly, you can upload your new controller using an ICD2 > > from Microchip. > > Another solution that I use very often (less nice, but faster) : just > > repeat the operation > > a lot of times. The game is to press reset just when you start sending > > the controller. > > Don't hesitate resetting the robot a lot :-) With some experience I > > manage to send the controller > > in 10 secs. > > > > In the future, when you write a controller, simply put a wait, so that > > the robot > > by default is not sending data through bluetooth, but rather waits for > > your command > > to start his operations. > > > > Cheers, > > alex. > > > > > > On Thu, 7 Feb 2008 12:37:27 +0000 > > "Andy Guest" <[EMAIL PROTECTED]> wrote: > > > > > What I day I'm having with these little things ! > > > > > > One of my e-pucks is behaving oddly now. When I try to use the tiny > > > bootloader to upload a hex file to the it the bootloader seems to > > > automatically connect to the puck without me pressing the reset > > button. The > > > orange light comes on on the e-puck but doesn't flash. If I preset the > > reset > > > button the bootloader fails with a write error, if I don't press the > > reset > > > button the orange led eventually goes off and the bootloader > > eventually > > > stops responding. It seems like the epuck is trying to communicate as > > soon > > > as it is switched on and the bootloader never gets chance to upload > > the > > > code. Powering down, reseting the epuck, removing the battery, even > > trying > > > to choose other programs from the e-puck selector doesn't change > > anything. > > > > > > How do I get the e-puck working again ? > > > > > > > > > Thanks, > > > Andy > > > > > > -- > I reject your reality and substitute one of my own. -- I reject your reality and substitute one of my own.
_______________________________________________ E-puck-user mailing list [email protected] https://mail.gna.org/listinfo/e-puck-user
