Hi All,
I am programming a RF communications protocol to download firmware updates to devices without having them to connect to the USB. The protocol needs to be reliable (as most protocols), handle retransmission, error detection, pairing, discovery, etc. I don't need to worry about error detection, since this is done already by hardware using CRC, what I do need to worry about is retransmission of packets in case of an error.
What I am asking, is if you have any tips or suggestions as to what characteristics the protocol should/must have, it needs to be very light weight, since End Devices don't have a lot of flash space. What is the best way to handle discovery and pairing?, the part attached to the computer can be on throughout the whole process, but the End Devices need to save as much energy as possible.
Is it better to handle the transmission/retransmission packet by packet with acks? or use a window of packets?.
I know there are already a lot of protocols already out there which could meet my criteria, but the application is very specific to my hardware and the protocol needs to be tailored made for this application.
Anyway any tip, suggestion, or examples I can refer to, would be greatly appreciated. BTW. I am programming it in C, in case anyone wants to know.
Thanks,
Julio
I am programming a RF communications protocol to download firmware updates to devices without having them to connect to the USB. The protocol needs to be reliable (as most protocols), handle retransmission, error detection, pairing, discovery, etc. I don't need to worry about error detection, since this is done already by hardware using CRC, what I do need to worry about is retransmission of packets in case of an error.
What I am asking, is if you have any tips or suggestions as to what characteristics the protocol should/must have, it needs to be very light weight, since End Devices don't have a lot of flash space. What is the best way to handle discovery and pairing?, the part attached to the computer can be on throughout the whole process, but the End Devices need to save as much energy as possible.
Is it better to handle the transmission/retransmission packet by packet with acks? or use a window of packets?.
I know there are already a lot of protocols already out there which could meet my criteria, but the application is very specific to my hardware and the protocol needs to be tailored made for this application.
Anyway any tip, suggestion, or examples I can refer to, would be greatly appreciated. BTW. I am programming it in C, in case anyone wants to know.
Thanks,
Julio