by PedroR » Tue Aug 11, 2009 7:11 pm
by PedroR
Tue Aug 11, 2009 7:11 pm
Hi atwolf
I have also seen that behaviour in my computer as I mentioned.
It appears to be random though. Sometimes it works, sometimes it doesn't.
It may be some synchronization feature or some API call that locks it up.
I'll have a look at it with Robotis.
For Merlin:
I believe Robot Terminal is still the way to roll back the firmware. The bootloader is untouched by the upgrade procedure (you would need an ATMEL programmer to change the bootloader I believe) so if the bootloader is untouched, upgrading the firmware through Robot Terminal should continue to work.
I haven't tested but Robotis also says it's possible to roll back the firmware using other tools (I assume the old Robot Terminal).
With regards to sample files I haven't got any yet as I haven't been able to find the time to make them.
However Roboplus is quite straightforward.
The code you see is not actually "written". You double click on the lines and choose the instructions. They are all shown in a graphical way.
Once you click and double click they appear in the screen, typed but you don't actually write anything so it should be easy to get going with it.
For siempre-aprediendo:
Yes the format is plain text for all files I believe.
HOWEVER I think there is a checksum in the last bytes of the file because I have tried to change the files manually and it doesn't seem to recognize the file once I change it (it says "invalid file").
If you open the file with a nice text editor (not Notepad LOL; something like Notepad++) you will see some bytes at the end of the file which I think are the checksum.
The calculation of the checksum has not been released but I hope some curious mind cracks it

Hi atwolf
I have also seen that behaviour in my computer as I mentioned.
It appears to be random though. Sometimes it works, sometimes it doesn't.
It may be some synchronization feature or some API call that locks it up.
I'll have a look at it with Robotis.
For Merlin:
I believe Robot Terminal is still the way to roll back the firmware. The bootloader is untouched by the upgrade procedure (you would need an ATMEL programmer to change the bootloader I believe) so if the bootloader is untouched, upgrading the firmware through Robot Terminal should continue to work.
I haven't tested but Robotis also says it's possible to roll back the firmware using other tools (I assume the old Robot Terminal).
With regards to sample files I haven't got any yet as I haven't been able to find the time to make them.
However Roboplus is quite straightforward.
The code you see is not actually "written". You double click on the lines and choose the instructions. They are all shown in a graphical way.
Once you click and double click they appear in the screen, typed but you don't actually write anything so it should be easy to get going with it.
For siempre-aprediendo:
Yes the format is plain text for all files I believe.
HOWEVER I think there is a checksum in the last bytes of the file because I have tried to change the files manually and it doesn't seem to recognize the file once I change it (it says "invalid file").
If you open the file with a nice text editor (not Notepad LOL; something like Notepad++) you will see some bytes at the end of the file which I think are the checksum.
The calculation of the checksum has not been released but I hope some curious mind cracks it
