I never was able to corrupt the bootloader but I analyzed a corrupted one
from others.

I feel it is not the program that you upload that corrupt the bootloader. It
looks like it is more the process to upload that has an influence, like:

- reset during upload,

- bad BT communication

- low battery,

- multiple resets at the start


to build your self a cable from the ICD2 to e-puck look here:



good luck,




Dr. Gilles Caprari

GCtronic Sagl, Electronics & Mechatronics

web: www.gctronic.com E-mail: g.capr...@ieee.org

Post: Via Cassarinetta 2, CH-6900 Lugano, Switzerland

Tel: +41 91 630 2149 Fax: +41 43 556 8006

Mobile: +41 78 601 1113 skype: gillescaprari


-----Original Message-----
From: Moh'd Zeyad [mailto:crash_0...@hotmail.com] 
Sent: mercoledì, 24. novembre 2010 22:36
To: e-puck-user@gna.org
Subject: [E-puck-user] How to know if the code is buggy ?


we are a group of three students from J.U.S.T university in jordan. We are
working with the two e-puck robots for the graduation project.
before one week, i was wirtting a simple program that controls the motor. i
uploaded the code to the e-puck, and since that i can't upload any other
codes through bluetooth. i gess the e-puck bootloader is corrupted. the
university did not buy the MPLAB ICD2, so we order it, but its going to take
some time (about ten days from this email) until its delivered.
Now,we are afraid to program the other e-puck robot.
So, is there any way to know if my code is buggy and ging to corrupt the
e-puck bootloader.
Sorry for the too much details.
and thank you.

E-puck-user mailing list

Reply via email to