Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
projects:bus-parrot [2014/12/18 10:03] darronprojects:bus-parrot [2017/01/12 22:44] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ==== Bus Parrot Bus Pirate ==== ==== Bus Parrot Bus Pirate ====
 +<wrap right>
 +{{:projects:busparrot.jpg?200}}
 +</wrap>
  
-{{ :projects:busparrot.jpg?300}} +The Bus Parrot is a clone of the Bus Pirate general purpose I/O device for the [[:boards:rpi|Raspberry Pi]].
-The Bus Parrot is a clone of the Bus Pirate general purpose I/O device for the RPi+
  
 In this instance communication is performed via the RPi built-in UART rather than using a USB bridge as in the original. In this instance communication is performed via the RPi built-in UART rather than using a USB bridge as in the original.
  
-==== Credits and Thanks ====+=== Licence === 
 + 
 +Bus Parrot is derived from and uses the same licensing as the original Bus Pirate. 
 +Visit this [[http://dangerousprototypes.com/docs/Bus_Pirate#License|page]] for Bus Pirate licensing information. 
 + 
 +=== Credits and Thanks ===
  
 All the hard work was done by Dangerous Prototypes and it's really worth visiting their site for a proper overview of the Bus Pirate [[http://dangerousprototypes.com/docs/Bus_Pirate|here]] All the hard work was done by Dangerous Prototypes and it's really worth visiting their site for a proper overview of the Bus Pirate [[http://dangerousprototypes.com/docs/Bus_Pirate|here]]
  
-==== Schematic ====+=== Build ===
  
-http://dev.kewl.org/k8048/Src/asm/PIC24FJ64GA002/gEDA/busparrot.png+This layout is almost functionally the same as the original the difference being the the power section.
  
-This layout is a work-in-progress and is almost functionally the same +{{:projects:busparrot.png?200|SCHEMATIC}}
-as the original the difference being the the power section.+
  
-All parts should be available from CPC in the UK including the PICMicro.+All components should be available from CPC in the UK including the PICMicro.
  
-==== Firmware =====+=== Firmware ====
  
-=== k8048 Microchip PIC programmer ===+Install [[:projects:pickle|Pickle Microchip PIC ICSP]].
  
 == Configuration === == Configuration ===
Line 29: Line 35:
 BITRULES=0x1700 BITRULES=0x1700
 VPP=9 VPP=9
-PGM=255+PGM=-1
 PGC=10 PGC=10
 PGD=11 PGD=11
 </code> </code>
  
-== Detect PIC24FJ64GA002 ==+== Detect Chip ==
 <code> <code>
-k24 lvp id+p24 lvp id
 [000000] [PROGRAM]  5600 WORDS [000000] [PROGRAM]  5600 WORDS
 [00ABFC] [CONFIG2]  F9DF [00ABFC] [CONFIG2]  F9DF
Line 54: Line 60:
 == Program firmware == == Program firmware ==
 <code> <code>
-k24 lvp program BPv3-Firmware_v6.3-beta1_r2151__Bootloader_v4.4.hex +hg clone http://hg.kewl.org/pub/bus-parrot 
 +cd BPv3 
 +p24 lvp program BPv3-Firmware_v6.3-beta1_r2151__Bootloader_v4.4.hex 
 Total: 18436 Total: 18436
 Time: 0:03.97s Time: 0:03.97s
Line 61: Line 69:
 == Verify firmware == == Verify firmware ==
 <code> <code>
-k24 lvp verify BPv3-Firmware_v6.3-beta1_r2151__Bootloader_v4.4.hex+p24 lvp verify BPv3-Firmware_v6.3-beta1_r2151__Bootloader_v4.4.hex
 Total: 18436 Pass: 18436 Fail: 0 Total: 18436 Pass: 18436 Fail: 0
 Time: 0:04.58s Time: 0:04.58s
 </code> </code>
  
 +=== Communications ===
  
-==== Communications ====+To communicate we will use `kermit' but any other comms. program will do such as picocom or even screen.
  
-=== Kermit === 
 == Install == == Install ==
 <code> <code>
Line 102: Line 110:
 to the UNIX shell. to the UNIX shell.
  
-==== I2C EEPROM demonstration ====+=== Demonstration ===
  
-[[http://dangerousprototypes.com/docs/3EEPROM_explorer_board#24AA_I2C_EEPROM|http://dangerousprototypes.com/]]+We will follow the I2C EEPROM demo from the  
 +[[http://dangerousprototypes.com/docs/3EEPROM_explorer_board#24AA_I2C_EEPROM|original]] site using our bus-parrot.
  
 <code> <code>