> (added PIC tag to be able to read by everyone...)
>
>> Also, on bootloaders, I've started writing them to accept the Intel hex
>> ascii records directly with either DC1/DC3 or RTS/CTS handshaking.
>> Nothing
>> special is then required on the host end, just send the ascii file.
>
> That's exactly what Szilva done - he uses Hyperterm I think to upload the
> HEX file which is parsed by the bootloader. The only catch I remember he
> was
> facing of is that he did not use hw handshaking, and XON/XOFF was not
> sufficient enough. Finally he used a relatively slow bandwidth and double
> buffering as far as I remember so that solved this problem.
>
> Tamas

I think XON/XOFF (DC1/DC3) should be sufficient, but maybe not. Many
terminal programs (including HyperTerminal) allow you to set a delay after
the transmission of each line of data. That can be set long enough to
allow the bootloader to program that section of flash. Another simple
approach I've used (though it pretty much requires a custom application on
the host end) is to not echo a character until I'm done dealing with it.
The host then waits for each character to be echoed.

Harold



-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist