File:BPv3-bootloaderv4xtov45-update-vb ENG-g2.7z

Summary

@credits to USBEprom & the team

@source direct: http://dangerousprototypes.com/forum/index.php?action=dlattach;topic=8498.0;attach=15167

@source forum: http://dangerousprototypes.com/forum/index.php?topic=8498.120

@Forum discussion: USBEprom: Reply #135 – September 29, 2019, 06:12:47 pm S_1-29092019.hex and U_1-29092019.hex are exactly the same S_1-28102018.hex and U_1-28102018.hex as before but rebuilt with the agatti fix in spi.c. The only differences with the previous firmware S_1-28102018.hex and U_1-28102018.hex is that the original spi.c was patched with the agatti fix

Attention please! First to attempt to use U_1-29092019.hex (UNSAFE version of the firmware) you have to evaluate what is the silicon revision of the PIC used in your device, paying much attention to the fact that you might damage your device or whatever! By doing it you must to assume all the responsibility for your action, even if actually should be no side effect in activating the Hardware I2C mode without honoring the silicon hardware revision of the PIC, because simply then it would not work. There was a warning message in case the silicon hardware revision of the PIC had not been the expected one, but I do not know if this warning is still present and active in the nowaday new firmwares and I do not have a Bus Pirate wich has one of the buggy silicon revisions of the PIC in order to check it. You use it at your own risk, I do not take any responsibility about the possibility of damaging your Bus Pirate or whatever!

Thanks a lot to agatti for having fixed the repository and freed the HARDWARE mode inside of I2C protocol!

Please note that both S_1-29092019.hex and U_1-29092019.hex were compiled with MPLAB-X IDE v5.00 and the XC-16 v1.35 compiler on Ubuntu 18.04 computer because the latest repositories are not natively compatible with MPLAB-X IDE v4.xx and earlier and both of them require the new bootloader v4.5 in order to work completely (http://dangerousprototypes.com/forum/index.php?topic=8498.0#p67056 and http://dangerousprototypes.com/forum/index.php?topic=8498.0#p67127). Otherwise if do not, enter BOOTLOADER using command "$" will not work (https://github.com/BusPirate/Bus_Pirate/issues/58). Actually it is not really a problem on the firmware side but rather of the bootloader. In order to fix the matter it is need to upgrade the bootloader to the new revision v4.5

With the firmwares was also provided a pre configured environment that anyone can use with minimal changes to simplify the upgrade of the only firmware or together the bootloader and the firmware in a single step. The archive also provides further improved instructions on how to use the whole thing under any operative system (Window, Linux and Apple), simply follow them:

"How to use UPGRADE_TO_BL_v4.5.bat.rtf" (specific instructions for Windows users) "How to update with pirate-loader.rtf" (generic cross-platform instructions for Windows, Linux and Apple users)