Skip to content
campbellsan edited this page Jan 29, 2015 · 34 revisions

If you do not see a suitable core below, please raise a 'new core request' issue with a description of your requirement in the body of the issue. To do this, click the Issues button on the right (it's the one with an exclamation in a circle) and click on 'New Issue' to get started.

For each available core, there are two links. 'fitter report' links to a report on what resources were used, and what the pinouts are. Near the end of the report is an ascii art rendering of the chip with a legend showing which signals are assigned where. Unused pins are labeled 'KPR' (for 'Keeper'). However, a Guzunty user is more interested in the 'Loc' column in the Outputs and Inputs tables. These id codes match with the labels on the Guzunty PCB.

The 'wave' link shows you a waveform view, a logic analyser like view of the signals as they change over time under control of the test bench (every core has a test bench). Each waveform is accompanied by some comments explaining what is going on.

Output heavy

Input heavy

Pulse Width Modulation

LEGEND: o = output, i = input, p = pwm, s = servo - Upper case means direct IO not via SPI

Specialised cores

  • gz_led_driver.xsvf - 4 digit, 7 segment led display driver - fitter report - wave
  • gz_test.xsvf - Simple clock divider test pattern - fitter report - wave
  • gz_arduino.xsvf - Enables 5v Arduino programming and interfacing - fitter report - wave
  • gz_lcd_driver.xsvf - Drives popular LCD touch screens while leaving GPIOs to spare. Flexible build configuration recommended for this one. - fitter report - wave
  • gz_ppm.xsvf - One for Radio Control fans. Reads a common PPM signal from an RC receiver and provides decoded values for the Pi to read on the SPI bus. - fitter report - wave