Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
12748 Discussions

LCD Controller problem

Altera_Forum
Honored Contributor II
‎10-19-2006 05:22 PM
1,177 Views

Hello 

 

I've have been fighting with with LCD controller for some time now. 

I'm using UP3 -EP1C12 demo board an I have a small design with I added LCD controller to it. 

I'm unable to assign FPGA pin# to my LCD controller's DATA pins because on my borad these data pins a shared with SRAM's and CFI flash(LCD opertx-10207). 

I downloaded "sls_tristate_16x2_character" and added it instead of the LCd controller provided by QuartuII, but still have the same problem. Besides I don't have the pin list number for this controller(to which FPGA pins they should be assinged). Does any1 have the pin-list? Or can direct me to som help manual that goes through pin assignments? 

 

For more detail; my design contains: 

1- NiosII/e CPU 

2- JTAG_Uart 

3- sls_tristate_16x2_character_lcd 

4- tristate_bridge 

 

Is something missing and should be added? 

 

I appreciate all kind of help.
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎10-22-2006 08:53 PM
465 Views

Hi 

 

Is there anyone who can help with that problem? I hope it's not impossible to be solved.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.