BIOLOID PREMIUM FIRMWARE MESSED UP

[pikaj00]

i was playing with my bioloid premium manager and it said a new firmware update was there so i downloaded it and it failed half way through the install this is the first time that has ever happend iv been useing this bot for over a year with no problems now the thing might aswell be a brick i get nothing but the green power light... is there anything i can do or do i have to send it to bioloid to repair?

[siempre.aprendiendo]

Have you tried to update it again or only one time?

[pikaj00]

yea iv been trying everything for a week now... it comes up saying turn power on and off and doesnt detect anything... cant get past it... iv never had a problem in all this time it really sucks..

[siempre.aprendiendo]

Which Roboplus version do you have installed in the PC?

Have you tried to download to the CM-510 a C program?
If this works then the problem is the download or the firmware.
If this doesn't works then may be there is a problem with the cable, the CM-510,...

[Fritzoid]

You need to use RoboPlus Terminal to get into the bootloader.

After connecting to the serial port at 56KB with RoboPlus Terminal do the following...

Hold down the shift and number sign (#) keys then turn on the CM-510. The CM-510 should respond with the bootloader prompt. If this works then you can use the download command to upgrade the firmware from a .HEX file. (available elsewhere).

If this does not work after a couple of tries then your problem is more serious.

[siempre.aprendiendo]

Fritzoid, I think that since several version of the Bioloid Premium (or from the begining, I'm not sure) there is no "standalone" firmware file, it's embedded in the PC Premium software.

May be, an old firmware version would work with its old version of PC software.

[Fritzoid]

I placed a stand-alone version of the CM-510 firmware (at level 1964) in my files area some time ago. Even if this is not the latest level it should then be upgradeable.

Anyone can create a stand-alone hex file of the current firmware using the bootloader and RoboPlus Terminal. Just use the UPLOAD command, it's easy. The address range you need is from 0 to around 0x17000 (it gets bigger every time).

I'm not sure why the bootloader needs this function, but I'm sure happy that it does. It's like a "hack-me-please" button

And before you start hacking your dynamixels too... the bootloader in the servos dosen't have this feature.

[siempre.aprendiendo]

Very interesting. Thanks, Fritzoid!

[pikaj00]

k im gonna give that a shot it does except c files or atleast it aprears to but i didnt have a firmware file to upload.. i give it a try and report back

[pikaj00]

well no luck the bootloader is whats wrong its completely corrupted so thats it i guess.. i got my robot from robotshop.ca they are contacting robotis on my behalf for further help eg sending it to them for repair.. to bad the warrenty expired lol.. always the way..

[Fritzoid]

Bummer pikaj00,

The bootloader is supposed to be protected from being overwritten by dumb users like you or me. So there's no way that you did anything wrong. The part must have been messed-up at the factory. I'm sure that Robotis will replace it.

[pikaj00]

Yea I was writing the new firmware to the controller when for no reason it failed half way through it was obviously writing to the boot loader section because after that the thing is bricked.. Not my fault and not theirs as I said the robotshop.ca has been great acting as a proxy between me and them trying to resolve the issue but I have been telling them for a week the unit will have to be fixed at the factory I don't mind sending it there and I'm sure they will fix it for free... Thanks for the help guys I'll let everyone know the resolution to this problem when I get it sorted out..

[DM69]

So...? I am having the same issue - what was the resolution?