Bus Pirate - Community Firmware 7.0

Bus Pirate firmware and hardware development.

Re: Bus Pirate - Community Firmware 7.0

Postby USBEprom » Sun Apr 16, 2017 5:54 am

Hi A340.
I know nothing about Ds30 Loader, sorry.
I use pirate-loader on Windows and it works without any problem.
Try it.
As attachment there is a pre configured environment that anyone can use with minimal changes.
Inside the archive are also provided instruction on how to use the whole thing.

Be seeing you.

U.Sb
Attachments
UPGRADE.zip
(130.7 KiB) Downloaded 116 times
USBEprom
Full Member
Full Member
 
Posts: 109
Joined: Wed Mar 14, 2012 4:09 pm

Re: Bus Pirate - Community Firmware 7.0

Postby A340 » Sun Apr 16, 2017 9:21 am

Hi USBEprom,

Thanks for the reply. I followed your instructions, as you wrote,and 7.1 loaded fine. (see Below). Thanks a lot, much appreciated. I will continue to follow this thread, as I move forward learning the Bus Pirate.

Bus Pirate v3.5
Community Firmware v7.1 - goo.gl/gCzQnW [HiZ 1-WIRE UART I2C SPI 2WIRE 3WIRE KEYB LCD PIC DIO] Bootloader v4.4
DEVID:0x0447 REVID:0x3046 (24FJ64GA00 2 B8)
http://dangerousprototypes.com
A340
Newbie
Newbie
 
Posts: 4
Joined: Sat Apr 01, 2017 11:28 pm

Re: Bus Pirate - Community Firmware 7.0

Postby USBEprom » Mon Apr 17, 2017 5:24 am

Hi A340.
That is fine.
Do you mind a question?
For your upgrade have you used the "SAFE" or the "UNSAFE" version?
It would be useful to know what hardware has problems with the "UNSAFE" version and what does not.
For what it is and without any warranty with my Bus Pirate it has not problems.
However by using the "UNSAFE" version anyone must to assume all the responsibility for his action.
Use it at your own risk, I do not take any responsibility about the possibility of damaging your Bus Pirate or whatever!
Just to be clear.
Thanks.

Be seeing you.

U.Sb
USBEprom
Full Member
Full Member
 
Posts: 109
Joined: Wed Mar 14, 2012 4:09 pm

Re: Bus Pirate - Community Firmware 7.0

Postby A340 » Mon Apr 17, 2017 11:25 am

Hi USBEprom,

I used "SAFE" version.

A340
A340
Newbie
Newbie
 
Posts: 4
Joined: Sat Apr 01, 2017 11:28 pm

Re: Bus Pirate - Community Firmware 7.0

Postby marsfan » Wed Apr 19, 2017 7:52 pm

@A340 I was told on the Github issue system that we have to use Pirate Loader, Ds30 is not supported by the community firmware.

@USBEprom, you should post/tag releases on the github page, might be easier than on this support thread.
marsfan
Newbie
Newbie
 
Posts: 4
Joined: Wed Apr 19, 2017 5:44 pm

Re: Bus Pirate - Community Firmware 7.0

Postby USBEprom » Thu Apr 20, 2017 1:19 pm

Hi marsfan.
I agree but, how?, where?
I know nothing about that, sorry.

Be seeing you.

U.Sb
USBEprom
Full Member
Full Member
 
Posts: 109
Joined: Wed Mar 14, 2012 4:09 pm

Re: Bus Pirate - Community Firmware 7.0

Postby marsfan » Mon Apr 24, 2017 9:12 pm

@USBEprom You would need to get the owner of the github repository to mark you as a contributor (not 100% sure how to do that), and then there is a way to create releases containing specific files. I know it can be done, because I have downloaded compiles programs via that before, you would need to talk with @agatti.

Here is a guide on creating releases: https://help.github.com/articles/creating-releases/
These guys use it a lot, and are pretty helpful, they might be able to help out with any questions if you need a person on hand: https://github.com/KSP-CKAN/CKAN.

I know that releases can be given tags. And I also know that you can use 3rd party systems like codeship and travis-ci to confirm builds will work, and they automatically generate new releases.
marsfan
Newbie
Newbie
 
Posts: 4
Joined: Wed Apr 19, 2017 5:44 pm

Re: Bus Pirate - Community Firmware 7.0

Postby USBEprom » Mon May 15, 2017 1:23 pm

Hi marsfan.
Sorry.
I do not understand a single word, too hard for me.
I give up, I will continue to put the new firmwares here.
I can not do anything else, sorry again.

Be seeing you.

U.Sb
USBEprom
Full Member
Full Member
 
Posts: 109
Joined: Wed Mar 14, 2012 4:09 pm

Re: Bus Pirate - Community Firmware 7.0

Postby marsfan » Sat Jun 24, 2017 6:43 pm

@ USBEprom

I understand, maybe in the future you could get with agatti or someone else who runs the repo and work together on it.
marsfan
Newbie
Newbie
 
Posts: 4
Joined: Wed Apr 19, 2017 5:44 pm

Re: Bus Pirate - Community Firmware 7.0

Postby USBEprom » Sun Jul 16, 2017 12:19 pm

Hi guys.
agatti has recently upgraded some things inside firmware v7.1.
So I was able to build new firmwares v7.1 for the Bus Pirate revision 3 using the new repository (https://github.com/BusPirate/Bus_Pirate ... master.zip), also because I wanted to test some modifications made by agatti on the I2C protocol.
I made two versions that i named SAFE_16072017 and UNSAFE_16072017.
Both of them have all the features enabled, BASIC too, the command line allows up 256 characters.
The first one (SAFE_16072017) is built on the configuration.h file which is in the specific folder.
So into configuration.h I changed lines from 316 to 331 in order to enable all the features available, BASIC too.

#ifdef BUSPIRATEV3
#define BP_ENABLE_1WIRE_SUPPORT
#define BP_ENABLE_BASIC_SUPPORT
#define BP_ENABLE_DIO_SUPPORT
#define BP_ENABLE_HD44780_SUPPORT
#define BP_ENABLE_I2C_SUPPORT
#define BP_ENABLE_JTAG_SUPPORT
#define BP_ENABLE_PIC_SUPPORT
#define BP_ENABLE_PC_AT_KEYBOARD_SUPPORT
#define BP_ENABLE_RAW_2WIRE_SUPPORT
#define BP_ENABLE_RAW_3WIRE_SUPPORT
#define BP_ENABLE_SMPS_SUPPORT
#define BP_ENABLE_SPI_SUPPORT
#define BP_ENABLE_SUMP_SUPPORT
#define BP_ENABLE_UART_SUPPORT
#endif /* BUSPIRATEV3 */


Then I changed the line 417 too in this way in order to make room for BASIC scripting:

#define BP_BASIC_PROGRAM_SPACE 512

Finally I had to set line 535 for up 256 characters into the command line by changing it in this way:

/**
* How big the serial command buffer can be, in bytes.
*
* @warning This must be set to a power of two, ie. 256, 128, 64, 32, etc.
*/
#ifdef BUSPIRATEV3
#define BP_COMMAND_BUFFER_SIZE 256
#else
#define BP_COMMAND_BUFFER_SIZE 256
#endif /* BUSPIRATEV3 */


The result that I have achieved I have called it SAFE_16072017_1.hex and SAFE_16072017_s.hex.
SAFE_16072017_1.hex was obtained by using the compression option "1" of MPLAB, while instead for SAFE_16072017_s.hex I used compression option "s".
Compression option "1" assure right timing that option "s" may not ensure.
So the firmware to use is SAFE_16072017_1.hex, SAFE_16072017_s.hex was built only for test.
For me it works great.
Thanks a lot to agatti for having upgraded the repository!

---------------------------------------------------------
---------------------------------------------------------

The second one (UNSAFE_16072017) is the same as SAFE_16072017 but also it has the HARDWARE mode unlocked for the I2C protocol..
Indeed in the recent past agatti taught how to free the HARDWARE mode inside I2C protocol (https://github.com/BusPirate/Bus_Pirate/issues/39).
Please read the above link carefully!
As agatti wrote:
"Dangerous Prototypes' original firmware did not use hardware I2C due to hardware bugs in PIC24FJ64GA004 chips with revision A3 or A4.
Now that hardware I2C is enabled again and the appropriate workarounds detailed here (http://ww1.microchip.com/downloads/en/D ... 00470j.pdf) have been applied, we need to test those on real hardware.

The catch: the code is experimental and it may or may not mess up with your hardware, just in case."
UNSAFE_16072017 is built on the configuration.h file which is in the specific folder.
In order to build it into configuration.h I changed lines from 316 to 331 in order to enable all the features available, BASIC too.

#ifdef BUSPIRATEV3
#define BP_ENABLE_1WIRE_SUPPORT
#define BP_ENABLE_BASIC_SUPPORT
#define BP_ENABLE_DIO_SUPPORT
#define BP_ENABLE_HD44780_SUPPORT
#define BP_ENABLE_I2C_SUPPORT
#define BP_ENABLE_JTAG_SUPPORT
#define BP_ENABLE_PIC_SUPPORT
#define BP_ENABLE_PC_AT_KEYBOARD_SUPPORT
#define BP_ENABLE_RAW_2WIRE_SUPPORT
#define BP_ENABLE_RAW_3WIRE_SUPPORT
#define BP_ENABLE_SMPS_SUPPORT
#define BP_ENABLE_SPI_SUPPORT
#define BP_ENABLE_SUMP_SUPPORT
#define BP_ENABLE_UART_SUPPORT
#endif /* BUSPIRATEV3 */


Then I changed the line 417 too in this way in order to make room for BASIC scripting:

#define BP_BASIC_PROGRAM_SPACE 512

And then I had to set line 535 for up 256 characters into the command line by changing it in this way:

/**
* How big the serial command buffer can be, in bytes.
*
* @warning This must be set to a power of two, ie. 256, 128, 64, 32, etc.
*/
#ifdef BUSPIRATEV3
#define BP_COMMAND_BUFFER_SIZE 256
#else
#define BP_COMMAND_BUFFER_SIZE 256
#endif /* BUSPIRATEV3 */


Finally I had to put a remark sign ("//") inside line 382 and 391 in order to unlock the HARDWARE mode for the I2C protocol:

382 // #ifdef BUSPIRATEV4

391 // #endif /* BUSPIRATEV4 */

The result that I have achieved I have called it UNSAFE_16072017_1.hex and UNSAFE_16072017_s.hex.
UNSAFE_16072017_1.hex was obtained by using the compression option "1" of MPLAB, while instead for UNSAFE_16072017_s.hex I used compression option "s".
Compression option "1" assure right timing that option "s" may not ensure.
So the firmware to use is UNSAFE_16072017_1.hex, UNSAFE_16072017_s.hex was built only for test.

For me it works but you use it at your own risk, I do not take any responsibility about the possibility of damaging your Bus Pirate or whatever!
Attention please!
First to attempt to use this 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!
For this reason the archive which contains this unsafe version of the firmware v7.1 is password protected.
The password is:


UNSAFE_FW

all uppercase.
You have to insert it in order to unpack the firmware.
By doing it you must to assume all the responsibility for your action.
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 upgraded the repository and freed the HARDWARE mode inside of I2C protocol!

With the firmwares I also provide a pre configured environment that anyone can use with minimal changes to simplify the upgrade.
Inside the archive are also provided instructions on how to use the whole thing.

A T T E N T I O N ! ! !

July 20, 2017 I noticed that SAFE_16072017 and UNSAFE_16072017 are not fully functioning, because enter BOOTLOADER using command "$" does not work (https://github.com/BusPirate/Bus_Pirate/issues/58).
So please, instead of them use SAFE_13042017 or UNSAFE_13042017 from here:

viewtopic.php?f=28&t=8498&start=45#p66033

Anyway I leave SAFE_16072017 and UNSAFE_16072017 as test, I do not remove them, so anyone who wants to use them can do it for that purpose.

I apologize for the mistake, I am sorry.

Be seeing you.

U.Sb
Attachments
UNSAFE_16072017.zip
(119.63 KiB) Downloaded 4 times
SAFE_16072017.zip
(132.56 KiB) Downloaded 12 times
UPGRADE.zip
(130.71 KiB) Downloaded 12 times
USBEprom
Full Member
Full Member
 
Posts: 109
Joined: Wed Mar 14, 2012 4:09 pm

Previous

Return to Bus Pirate Development