Skip to main content
Topic: Bus Pirate - Community Firmware 7.0 (Read 88140 times) previous topic - next topic

Re: Bus Pirate - Community Firmware 7.0

Reply #135
Hi guys.
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.
They were obtained by using the compression option "1" of MPLAB so to be in full agreement with the latest recommendations issued about the compilation of the repositories using MPLAB in order to build new firmwares for the Bus Pirate v3 and v4.
Compression option "1" assure right timing that option "s" may not ensure.
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 (the updated version of spi.c is in the compressed archive attached):

https://github.com/BusPirate/Bus_Pirate/issues/122#issuecomment-470428292

From the checks I made Bus Pirate works, flashrom works, avrdude works, all is working, but you use them at your own risk, I do not take any responsibility about the possibility of damaging your Bus Pirate or whatever, expecially talking about of the unsafe version!
About the SAFE and UNSAFE version, please also read this:


http://dangerousprototypes.com/forum/index.php?topic=8760.msg70072#msg70072

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:


http://dangerousprototypes.com/forum/index.php?topic=619.0#p67037

https://github.com/BusPirate/Bus_Pirate/issues/38

https://github.com/BusPirate/Bus_Pirate/issues/58

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)

Please note that the package is a 7z (7zip) archive because the maximum allowed size in the forum is 1 MiB.


Be seeing you.

U.Sb




Re: Bus Pirate - Community Firmware 7.0

Reply #136
Hi guys.
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.
They were obtained by using the compression option "1" of MPLAB so to be in full agreement with the latest recommendations issued about the compilation of the repositories using MPLAB in order to build new firmwares for the Bus Pirate v3 and v4.
Compression option "1" assure right timing that option "s" may not ensure.
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 (the updated version of spi.c is in the compressed archive attached):

https://github.com/BusPirate/Bus_Pirate/issues/122#issuecomment-470428292

From the checks I made Bus Pirate works, flashrom works, avrdude works, all is working, but you use them at your own risk, I do not take any responsibility about the possibility of damaging your Bus Pirate or whatever, expecially talking about of the unsafe version!
About the SAFE and UNSAFE version, please also read this:


http://dangerousprototypes.com/forum/index.php?topic=8760.msg70072#msg70072

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:


http://dangerousprototypes.com/forum/index.php?topic=619.0#p67037

https://github.com/BusPirate/Bus_Pirate/issues/38

https://github.com/BusPirate/Bus_Pirate/issues/58

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)

Please note that the package is a 7z (7zip) archive because the maximum allowed size in the forum is 1 MiB.


Be seeing you.

U.Sb





Thanks USB, you are truly the hero Gotham deserves :D All your effort is much appreciated.

What firmware version are you currently preferring/choosing to use, out of curiosity?

Re: Bus Pirate - Community Firmware 7.0

Reply #137
It would be nice to have a firmware with the JTAG fix from issue 134 in it, as it looks to be breaking reading the ChipID, chain length, etc.

Re: Bus Pirate - Community Firmware 7.0

Reply #138
Thanks for the Wiki update - there's so few willing to contribute as you have noticed.

Re: Bus Pirate - Community Firmware 7.0

Reply #139
Hi
Maybe Someone has a firmware after bpv4_boot4.10_fw7.0_opt0_18092016  for BPv4 which  works with flashrom
I tried to compile&install from the git repo, but not successfully: flashrom cant init bus pirate (hang), but the manual commands work perfectly. 

Re: Bus Pirate - Community Firmware 7.0

Reply #140

Hi to all,

for a nDIY Bus Pirate 4, can I load the latest firmware with my pickit 3 device, without the bootloader, or there are  specific instructions do do that ?
Thanks in advance !

Andrea

Re: Bus Pirate - Community Firmware 7.0

Reply #141
Hi all, I have a v3.6 Bus Pirate I bought a while ago that I'm only now getting started with.  It has a v4.4 bootloader, but only v5.1 firmware.  Are there any precompiled firmware files that I can use or would I need to compile them myself?

Also, I think I saw somewhere there is a v4.5 bootloader.  Would there be any reason for me to update that or should I be fine as I am?

Thanks!

Re: Bus Pirate - Community Firmware 7.0

Reply #142
I do not know if this issue could be related to issue #124 but I had trouble with UART transparent bridge and live monitor so I tried to find the bug.

The trouble
To flash my ESP8266, I need an USB<->TTL converter.
As I had a BusPirate v3b, I tried to use it with the UART Transparent bridge mode.
First, I have flashed the community firmware (09032019_OPT1_UNSAFE.hex) and get the prompt of the ESP8266 (micropython), the UART works.
The command :
m 3 9 enter enter enter 2 W (1)y

Re: Bus Pirate - Community Firmware 7.0

Reply #143
Hi Lucien.

I have a v3.6 Bus Pirate I bought a while ago that I'm only now getting started with.  It has a v4.4 bootloader, but only v5.1 firmware.  Are there any precompiled firmware files that I can use or would I need to compile them myself?

Here in this same thread in some previous posts there are several firmware for the Bus Pirate v3.x, the most updated ones are S_1-29092019.hex and U_1-29092019.hex you can find here:

http://dangerousprototypes.com/forum/index.php?topic=8498.msg70165#msg70165


Also, I think I saw somewhere there is a v4.5 bootloader.  Would there be any reason for me to update that or should I be fine as I am?

That is correct, you saw right.
Latest firmwares require the new bootloader v4.5 in order to be fully functioning.
Without upgrading the bootloader to v4.5 it will not be possible to jump into bootloader from terminal using command $, so that instead it will be necessary to use jumper on PGD and PGC.
If this is not a problem for you, you can very well leave it as it is and just update the firmware, there are no other contraindications than those described above.
However, consider that updating the bootloader is no more complex than the firmware one and that several firmware releases that you find in this same thread in several previous posts incorporate both firmware and bootloader with instructions on how update each of them from Windows, Linux and Apple.

Be seeing you.

U.Sb

Re: Bus Pirate - Community Firmware 7.0

Reply #144
Hi roundcubeeight.
Sorry, I did not quite understand what you are referring to, perhaps that  after giving the commands

m 3 9 enter enter enter 2 W (1)y

by invoking a RESET (command #) is it not possible to restore the Bus Pirate to normal operation?

I do not know if it matches the matter, but do you know this?:

http://dangerousprototypes.com/forum/index.php?topic=9026.0

Be seeing you.

U.Sb

Re: Bus Pirate - Community Firmware 7.0

Reply #145
It would be nice to have a firmware with the JTAG fix from issue 134 in it, as it looks to be breaking reading the ChipID, chain length, etc.

Hi trcm and all.
Here are firmwares busPirate-JTAG_SAFE_1.hex and busPirate_JTAG_UNSAFE_1.hex all of which have the JTAG fix from issue 134 (https://github.com/BusPirate/Bus_Pirate/issues/134) provided by Gabriel Smith as from his commit dated 21 May 2020 here:

https://github.com/BusPirate/Bus_Pirate/commit/dd7fbb0fedd27c08b9c33501ebbe4b28d8085cba

https://github.com/BusPirate/Bus_Pirate/archive/dd7fbb0fedd27c08b9c33501ebbe4b28d8085cba.zip

Starting from https://github.com/BusPirate/Bus_Pirate/archive/dd7fbb0fedd27c08b9c33501ebbe4b28d8085cba.zip, firmwares busPirate-JTAG_SAFE_1.hex and busPirate_JTAG_UNSAFE_1.hex were obtained by using the compression option "1" of MPLAB so to be in full agreement with the latest recommendations issued about the compilation of the repositories using MPLAB in order to build new firmwares for the Bus Pirate v3 and v4.
Compression option "1" assure right timing that option "s" may not ensure.
As far as I can understand the repository already incorporates all the patches introduced up to the current date.
Sadly at this moment I can not verify the functioning of the JTAG part, so I ask the courtesy at trcm or anyone else able to do it to try one of the two firmware and give a response, thanks.

About the SAFE and UNSAFE version, please also read these:

http://dangerousprototypes.com/forum/index.php?topic=8760.msg70072#msg70072
http://dangerousprototypes.com/blog/2009/08/10/bus-pirate-hardware-i2c-added/
http://dangerousprototypes.com/blog/2009/08/07/find-your-bus-pirates-pic-revision/

Attention please!
First to attempt to use busPirate_JTAG_UNSAFE_1.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 Gabriel Smith for the fix he provided!!!

Please note that both busPirate-JTAG_SAFE_1.hex and busPirate_JTAG_UNSAFE_1.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:

http://dangerousprototypes.com/forum/index.php?topic=619.0#p67037

https://github.com/BusPirate/Bus_Pirate/issues/38

https://github.com/BusPirate/Bus_Pirate/issues/58

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)

Please note that the package is a 7z (7zip) archive because the maximum allowed size in the forum is 1 MiB.


Be seeing you.

U.Sb

 

Re: Bus Pirate - Community Firmware 7.0

Reply #146
Hi guys.
The github user gdamjan started github action to make releases on git tags:

https://github.com/BusPirate/Bus_Pirate/pull/152

He provides some test builds, for both Bus Pirate v3 and Bus Pirate v4, here:

https://github.com/gdamjan/Bus_Pirate/releases/tag/v.test

Their output can be seen here:

https://github.com/gdamjan/Bus_Pirate/runs/1157434979?check_suite_focus=true

It is surely possible to use his firmwares in order to do tests.
The one he provides for the Bus Pirate v3 manages the I2C protocol only by firmware, it does not support it by hardware management and has the follow specifications:

Bus Pirate v3.5
Community Firmware v7.1 - goo.gl/gCzQnW [HiZ 1-WIRE UART I2C SPI 2WIRE 3WIRE PIC DIO] Bootloader v4.5
DEVID:0x0447 REVID:0x3046 (24FJ64GA00 2 B8)
http://dangerousprototypes.com

I can not verify the one for the Bus Pirate v4.
Please, pay attention to the fact that the ready to use hexadecimal files kindly provides by gdamjan are in lowercase format and therefore it is need to convert them to uppercase in order to use them with some Bus Pirate firmware update tools.

Thanks very much to gdamjan for the good idea and its brilliant implementation!

Be seeing you.

U.Sb