Using E-Blocks With The AVR Programmer
Posted: Sat Jul 07, 2012 10:17 am
Using E-Blocks With the AVR Programmer.
Having just recently bought the AVR programmer, I found the E-Blocks dont always connect as easily as to the PIC systems.
Introduction :
While the E-block system is very versatile, the default configuration (certainly for the more advanced e-blocks) is for the PIC microcontroller.
This is where the patch system comes in.
For example the data lines needed may be PORT C bits 3&4. But on the AVR device the lines may be on PORT D 1&2.
Just being on a different port is not a problem; just plug the e-block into PORT D, but when the data is on different lines it causes problems.
With this article I want to document the configurations I have found to work on my hardware for some of the more advanced e-blocks.
E-blocks such as:
EB004 – LED
EB005 – LCD
EB007 – Switch
EB014 - Keypad
Don’t need to be on specific lines (and don’t implement the batch system anyway), but the more advanced need to use the patch system.
The Patch System :
The patch system allows the data connections of the e-block to be routed to any of the 8 data bits on the microcontroller port.
Next to the 9-Way D-Type connector, is an 8 way SIL header. (Pin 9 is always configured as ground)
Next to this is another SIL header with the e-blocks data lines.
These are connected together by small jumper wires, such as would be used on a prototype board (Breadboard).
Finally the default setup is changed to the patch setup by moving a jumper on the e-block. (See data sheet for which jumper.)
E-Block Configurations :
These are the e-blocks I have tried on my own hardware and found to work.
This may not be the only configuration for the E-Block (or the best), but I hope this information will be of use to other users on the forums.
These were all tested using the ATMEGA 324P Device
EB 051 Zigbee Coordinator
Tested with the co-ordinator, however the End Node/Router is used in exactly the same way.
PORT D – Patch Jumper D & 2
Connections:
RX - PD0 (RX0)
TX - PD1 (TX0)
RTS - PD4
CTS - PD5
Sleep - PD6
RF Board - EB063
PORT B – Patch Jumper C
Connections:
CS - PB0
FSEL - PB1
SCK - PB4
MOSI - PB5
MIOS - PB6
Touch Screen Display EB 076
PORT D – Patch Jumper J7
Connections:
RX - PD0
TX - PD1
Reset - PD4
Card Reader EB 037
Port D Patch Jumper – C
Using software SPI
Connections:
Data Out = PD0
Data In = PD1
CLK = PD4
CS = PD5
gLCD Display EB 057
Port B – Patch Jumper C
Using hardware SPI
Connections:
SCK = PB7
SDI = PB6
SDO = PB5
CS = PB4
The following boards / components worked with the same configuration as on the PIC Microcontroller
Rotary Encoder EB 073 – PORT B
Servo EB 059 – PORT B
The 1-wire Bus was tested using a DS18S20 Temperature Sensor
I will expand this list when I have had the chance to try more hardware.
Having just recently bought the AVR programmer, I found the E-Blocks dont always connect as easily as to the PIC systems.
Introduction :
While the E-block system is very versatile, the default configuration (certainly for the more advanced e-blocks) is for the PIC microcontroller.
This is where the patch system comes in.
For example the data lines needed may be PORT C bits 3&4. But on the AVR device the lines may be on PORT D 1&2.
Just being on a different port is not a problem; just plug the e-block into PORT D, but when the data is on different lines it causes problems.
With this article I want to document the configurations I have found to work on my hardware for some of the more advanced e-blocks.
E-blocks such as:
EB004 – LED
EB005 – LCD
EB007 – Switch
EB014 - Keypad
Don’t need to be on specific lines (and don’t implement the batch system anyway), but the more advanced need to use the patch system.
The Patch System :
The patch system allows the data connections of the e-block to be routed to any of the 8 data bits on the microcontroller port.
Next to the 9-Way D-Type connector, is an 8 way SIL header. (Pin 9 is always configured as ground)
Next to this is another SIL header with the e-blocks data lines.
These are connected together by small jumper wires, such as would be used on a prototype board (Breadboard).
Finally the default setup is changed to the patch setup by moving a jumper on the e-block. (See data sheet for which jumper.)
E-Block Configurations :
These are the e-blocks I have tried on my own hardware and found to work.
This may not be the only configuration for the E-Block (or the best), but I hope this information will be of use to other users on the forums.
These were all tested using the ATMEGA 324P Device
EB 051 Zigbee Coordinator
Tested with the co-ordinator, however the End Node/Router is used in exactly the same way.
PORT D – Patch Jumper D & 2
Connections:
RX - PD0 (RX0)
TX - PD1 (TX0)
RTS - PD4
CTS - PD5
Sleep - PD6
RF Board - EB063
PORT B – Patch Jumper C
Connections:
CS - PB0
FSEL - PB1
SCK - PB4
MOSI - PB5
MIOS - PB6
Touch Screen Display EB 076
PORT D – Patch Jumper J7
Connections:
RX - PD0
TX - PD1
Reset - PD4
Card Reader EB 037
Port D Patch Jumper – C
Using software SPI
Connections:
Data Out = PD0
Data In = PD1
CLK = PD4
CS = PD5
gLCD Display EB 057
Port B – Patch Jumper C
Using hardware SPI
Connections:
SCK = PB7
SDI = PB6
SDO = PB5
CS = PB4
The following boards / components worked with the same configuration as on the PIC Microcontroller
Rotary Encoder EB 073 – PORT B
Servo EB 059 – PORT B
The 1-wire Bus was tested using a DS18S20 Temperature Sensor
I will expand this list when I have had the chance to try more hardware.
