Software: Difference between revisions
From Wiki-DB
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 32: | Line 32: | ||
You have to download the *.jed-File with the programmer to your PLD. | You have to download the *.jed-File with the programmer to your PLD. | ||
In the constraint editor of ispLEVER you can define, which input X_VAR1 is. | In the constraint editor of ispLEVER you can define, which input X_VAR1 is. | ||
In this example GPIO E is defined as X_VAR1. If you define GPIO E as an | In this example GPIO E is defined as X_VAR1. If you define GPIO E as an | ||
output and set GPIO E high, the PLD LED should flash red. | output and set GPIO E high, the PLD LED should flash red. | ||
[[File:VHDL-Code.jpg]] |
Revision as of 11:46, 9 July 2012
GPIOs
Mapping
In the following sheet you can find the GPIOs and their linux-number
Control
How to control a GPIO:
cd /sys/class/gpio echo 44 >export // create new directory cd gpio44 // go into this directory cat direction // show if GPIO is used as an input or an output out echo 1 >value // change output to '1'=high echo in >direction // change GPIO to input cat value // show input value 0 // '0' = low
PLD
Development Software
To write your own VDHL-code you can use the ispLEVER Classic Software from Lattice ([1]
You also need a programmer (e.g. HW-USBN-2A from Lattice) to deploy the VHDL-Code on your PLD.
After installing the software and the drivers for your programmer you can start a new project.
Programming example
You can find a demo-project here:media:PLD-demo.zip
You have to download the *.jed-File with the programmer to your PLD.
In the constraint editor of ispLEVER you can define, which input X_VAR1 is.
In this example GPIO E is defined as X_VAR1. If you define GPIO E as an
output and set GPIO E high, the PLD LED should flash red.