Tiny Multi Bootloader+ v0.10.0 works very well with PIC12F1840, PIC16F1825
and PIC16F1938.
As I have migrated so as to aid firmware upgrades.
Have tried to upload PIC firmware over Serial-2-Ethernet [S2E] networks but
it's about 85% successful.
Hope you could provide a number of retry attempts after a bootloader returns
failed CRC 'N' or no response at all to Multi Bootloader+, similar to options
in [COM parameters] as Ethernet cabling, Hub, switch or Routers happens
to drop/undeliver packets to PIC bootloader.
At this point Multi Bootloader+ will attempt to resend a failed memory data
to bootloader without having to start all over.
Kind regards,
Hanspeter.
Last edit: Hanspeter 2016-03-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for reading.
Don't bother, I manage to resolve it in the bootloader with
four lines of code and works well over a Wide Area Network setup.
My nightmares resolved.
Hanspeter.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Edorul
Tiny Multi Bootloader+ v0.10.0 works very well with PIC12F1840, PIC16F1825
and PIC16F1938.
As I have migrated so as to aid firmware upgrades.
Have tried to upload PIC firmware over Serial-2-Ethernet [S2E] networks but
it's about 85% successful.
Hope you could provide a number of retry attempts after a bootloader returns
failed CRC 'N' or no response at all to Multi Bootloader+, similar to options
in [COM parameters] as Ethernet cabling, Hub, switch or Routers happens
to drop/undeliver packets to PIC bootloader.
At this point Multi Bootloader+ will attempt to resend a failed memory data
to bootloader without having to start all over.
Kind regards,
Hanspeter.
Last edit: Hanspeter 2016-03-11
Thanks for reading.
Don't bother, I manage to resolve it in the bootloader with
four lines of code and works well over a Wide Area Network setup.
My nightmares resolved.
Hanspeter.