FPGA based pixel co...
 
Notifications
Clear all

FPGA based pixel controller

85 Posts
18 Users
0 Reactions
33.6 K Views
Posts: 238
Topic starter
(@ronp5683)
Reputable Member
Joined: 14 years ago

Oh, I was going to post my FPGA utilization for E1.31 receiver plus four output universes.

Family : Cyclone II
Device : EP2C8Q208C8
Timing Models : Final
Total logic elements : 851 / 8,256 ( 10 % )
Total combinational functions : 821 / 8,256 ( 10 % )
Dedicated logic registers : 412 / 8,256 ( 5 % )
Total registers : 415
Total pins : 22 / 138 ( 16 % )
Total virtual pins : 0
Total memory bits : 20,736 / 165,888 ( 13 % )
Embedded Multiplier 9-bit elements : 0 / 36 ( 0 % )
Total PLLs : 0 / 2 ( 0 % )


Reply
Posts: 1249
(@jstjohnz)
Noble Member
Joined: 17 years ago

I'm interested in hearing more about how this works. I am just getting my feet wet with FPGAs, using a Cyclone IV to emulate the upcoming Parallex 2nd generation propeller processor.

I'm assuming that there's a Nios in there somewhere that handles a lot of the work, or is this all done in VHDL? Don't
you need an external non-volatile memory to load the fpga, or is that built into the chip?


Reply
Posts: 238
Topic starter
(@ronp5683)
Reputable Member
Joined: 14 years ago
jstjohnz wrote:I'm interested in hearing more about how this works. I am just getting my feet wet with FPGAs, using a Cyclone IV to emulate the upcoming Parallex 2nd generation propeller processor. I'm assuming that there's a Nios in there somewhere that handles a lot of the work, or is this all done in VHDL?

From my experience, there are two types of FPGA programmers; the software type that use the embedded processors like NIOS, and those that write code. The embedded processors in FPGA's run 'C' code and it is fairly easy for someone not familiar with FPGA's to setup a system. They can code in 'C' and get a project running fairly quickly. The drawback is that it uses a lot of FPGA's resources and the processor is slow for the money. Those that write in code can optimize the resources to get the most bang for the buck. However, writing in code is much different from programming. It has a fairly steep learning curve, and the thought process is different from programming. My design is all in VHDL, no processor.

In hardware designs if you are just moving bits around the FPGA is a better solution. If you are doing a lot of math and logic, then a processor works better. For lighting LED's it is clearly just moving bits.

jstjohnz wrote: Don't you need an external non-volatile memory to load the fpga, or is that built into the chip?

The board I bought from www.wvshare.com has the flash chip on the bottom side for the configuration memory. There is also the power regulators and an oscillator. I would recommend buying one of these boards, and their programmer if you are going to get into FPGA's (~$50)


Reply
Posts: 238
Topic starter
(@ronp5683)
Reputable Member
Joined: 14 years ago
jstjohnz wrote:I'm interested in hearing more about how this works. I am just getting my feet wet with FPGAs, using a Cyclone IV to emulate the upcoming Parallex 2nd generation propeller processor. I'm assuming that there's a Nios in there somewhere that handles a lot of the work, or is this all done in VHDL?

From my experience, there are two types of FPGA programmers; the software type that use the embedded processors like NIOS, and those that write code. The embedded processors in FPGA's run 'C' code and it is fairly easy for someone not familiar with FPGA's to setup a system. They can code in 'C' and get a project running fairly quickly. The drawback is that it uses a lot of FPGA's resources and the processor is slow for the money. Those that write in code can optimize the resources to get the most bang for the buck. However, writing in code is much different from programming. It has a fairly steep learning curve, and the thought process is different from programming. My design is all in VHDL, no processor.

In hardware designs if you are just moving bits around the FPGA is a better solution. If you are doing a lot of math and logic, then a processor works better. For lighting LED's it is clearly just moving bits.

jstjohnz wrote: Don't you need an external non-volatile memory to load the fpga, or is that built into the chip?

The board I bought from www.wvshare.com has the flash chip on the bottom side for the configuration memory. There is also the power regulators and an oscillator. I would recommend buying one of these boards, and their programmer if you are going to get into FPGA's (~$50). Also, the EP2C8 part is better, cause you can run Quartus 9.1. If you buy the EP4C6 or EP4C10, then you have to run a later version. The simulator has a steep learning curve.


Reply
Posts: 238
Topic starter
(@ronp5683)
Reputable Member
Joined: 14 years ago

It sunny and in the 80's and I am typing on my computer?

Updated the firmware to take the first message and ignore subsequent ones until the output is done. (thanks Phil).

Update the firmware to support 2801 LED's. I received in the mail my 5 pixel test string. 🙂

Also, completed pretty much all of the code. I created all 32 universe output state machines. So I am pretty close to done, except for maybe a few my output types (2811 for sure). Below is the usage for the FPGA, and it looks like I have room to add a lot more output types. :-). So do I need to do a video demo to get people's interest? I can do my generic serial to my lights, the five pixels of 2801 and Renard to another computer. Not quite the big display, but at least a demo.

Fitter Status : Successful - Fri Mar 15 17:54:51 2013
Quartus II Version : 9.1 Build 222 10/21/2009 SJ Web Edition
Revision Name : UDP
Top-level Entity Name : UDP
Family : Cyclone II
Device : EP2C8Q208C8
Timing Models : Final
Total logic elements : 5,867 / 8,256 ( 71 % )
Total combinational functions : 5,839 / 8,256 ( 71 % )
Dedicated logic registers : 2,590 / 8,256 ( 31 % )
Total registers : 2593
Total pins : 78 / 138 ( 57 % )
Total virtual pins : 0
Total memory bits : 149,760 / 165,888 ( 90 % )
Embedded Multiplier 9-bit elements : 0 / 36 ( 0 % )
Total PLLs : 0 / 2 ( 0 % )


Reply
Page 9 / 17
Share: