RoboSavvy Forum

Thank you Hivemind,

2007-05-29T04:12:26+01:00

Hi from Will, you might remember from a Newbee's Tail.
Big Thanks to Hivemind who's post here has got my bioloid to perform the demo.
Thank you, bye for now and be well from Will.

Statistics: Posted by Will — Tue May 29, 2007 4:12 am

Behavior Control Prog can't connect to CM-5, Terminal can...

2007-05-28T02:07:44+01:00

ah, that explains it. I didn't realize I had to type the command to put it in download mode AND launch the download manually. Thanks!

Statistics: Posted by Miamicanes — Mon May 28, 2007 2:07 am

Behavior Control Prog can't connect to CM-5, Terminal can...

2007-05-28T01:53:14+01:00

Enter the bootloader, type "load" and press enter. It will wait for a file, under "Files", select "transfer file" and then select the file of your choice.

Statistics: Posted by hivemind — Mon May 28, 2007 1:53 am

Behavior Control Prog can't connect to CM-5, Terminal can...

2007-05-28T01:43:10+01:00

do you know what the syntax is (assuming it's something besides load foo.hex)?

Statistics: Posted by Miamicanes — Mon May 28, 2007 1:43 am

Behavior Control Prog can't connect to CM-5, Terminal can...

2007-05-28T00:56:08+01:00

The original firmware hex file is laying around in one of the directories. You can try uploading that.

Statistics: Posted by billyzelsnack — Mon May 28, 2007 12:56 am

Behavior Control Prog can't connect to CM-5, Terminal can...

2007-05-28T00:17:54+01:00

I recently tried to compile and upload the example C program supplied on the CD using robot terminal using the 'load' command. It didn't appear to work. Now, when I turn on the CM-5, only the power light comes on, and the buttons don't seem to do anything. Worse, when I try to connect using the Behavior Control Programmer to update the CM-5's firmware (or, more precisely, reflash it to what it presumably was before it somehow got corrupted), it replies, "Cannot Connect CM-5! Please check the condition of connection". However, if I exit the behavior control program and load Robot Terminal, then turn on the CM-5 while holding down the "#" key, it enters the bootloader.

I suspect that there's something I need to do from within Robot Terminal to get the CM-5 back into a state where the BCP can communicate with it... but what?

Statistics: Posted by Miamicanes — Mon May 28, 2007 12:17 am