This will setup a counter variable which is incremented at every = // Structural coding //= /* reg */ reg counter reg state /* assign */ assign LEDG = state /* always */ always ( posedge CLOCK_50 ) begin counter <= counter + 1 state <= counter // <- data to change end The endmodule tag, to make one of the onboard LEDs blink. We’ll add a small snippet of Verilog at the bottom of this file, just before You’ll see auto-generated ports for all I/O on the board – cool! Project Navigator you’ll see one Verilog file. Of the board preconfigured which avoids a lot of tedious work. A new project will be created with the pinout Click the Add button to add the workspace to your search path.Ĭlick OK to exit this window, and you should see one template populateĬlick Next and then Finish. In the parent window, we will add the workspace directory to the search path.Ĭlick the “…” button to navigate to the workspace where your template par file will be expanded and installed in the workspace.

In the second box, choose the folder you would like to use as your quartus workspace.įor example, I created a folder called quartus in my home directory. In the window that pops up, click the link that says “Install design template”. Name the project whatever you’d like, and select to use a “Project template”:Ĭlick the link that says “add the installation directory to the design template search paths”. I recommend creating a workspace folder for everything related to quartus, and creating a folder In the main window, select “New Project Wizard”. Open quartus by running quartus at the command line, assuming the quartusīinaries have been added to your PATH. Look at the bottom left corner of the underside of the board, as shown below: The C indicates this is a Rev C boardĭownload whichever pinout is appropriate for your board rev. They host pinouts for revisions B and C of the board. Link to baseline pinouts for the DE2i-150. Quartus 16.0.0 rather than the latest version.) Issues with these design files were the motivation for installing Some of the baseline designs that Intel hosts online. Now that the USB Blaster is set up, we can create a simple program Run the following command to load your new udev rule:Īnd run jtagconfig again, which will start jtagd in the background.Ī similar error can occur if you unplug the USB Blaster while running I got quite frustrated at first when my udev rule didn’t appear to be working –Īll because I hadn’t unplugged and replugged, which meant the rule hadn’t yet We don’t want toĪctivate this udev rule while it is plugged in, as this makes troubleshootingĭifficult. IMPORTANT: At this point, unplug your USB blaster.

The rule states that the deviceīe assigned permissions 0666, aka everyone can read and write. The first four lines specify that this rule only applies to USB devices This rule will be executed whenever a new USB device is plugged in. Replace 09fb above with the vendor ID you saw previously,

Altera usb blaster linux