I want to port tiny bootloader+ for android such that PICs can be programmed through USB2serial cables on those tabs/mobiles supporting OTG.
For a start I would like to just update EEPROM locations.
What is the sequence or characters to be transmitted for say updating the first eight EPROM locations to 1,2,3,4,5,6,7,8
In otherwords, is there some documenation on what is being sent to the PIC and what is received for programming the program memory, eeprom memory and configuration.
Regards,
Sunish
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I want to port tiny bootloader+ for android such that PICs can be programmed through USB2serial cables on those tabs/mobiles supporting OTG.
For a start I would like to just update EEPROM locations.
What is the sequence or characters to be transmitted for say updating the first eight EPROM locations to 1,2,3,4,5,6,7,8
In otherwords, is there some documenation on what is being sent to the PIC and what is received for programming the program memory, eeprom memory and configuration.
Regards,
Sunish
Answering my own question,
0xc1 to start boot loader
response will be PIC code byte which is mapped piccodes.ini $15 for 12f1840
followed by "K"
The next sequence is Upper address(byte),Lower address(byte),Number of data bytes,
data 0,data 1,....data n(5),2's complimented CRC
For 12f1840 EEPROM the address is F000 following the above sequence.
If the transfer is successful "K" is sent back from the PIC else "N"
I had issues when the transmission was too fast, on android its okay but in my delphi app I had to insert a 1ms delay bewtween chracters.
Sunish