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++

Problem with addresses

Altera_Forum
Honored Contributor II
1,272 Views

Hi. I have posted some posts around these forums now and asked a lot of different questions. I think I have found out what my problem is now.  

 

I have made a design in SOPC with among other components, the compact flash component. I have also made my own component. The problem is that the address line a[0] to the CF seems to be the same as a[0] to my own component. Is this how it's supposed to be? Is there a way to seperate them? I would very much like to have them seperated. The base addresses are different. They are not connected to the same physical pin.  

 

Ole
0 Kudos
2 Replies
Altera_Forum
Honored Contributor II
555 Views

do you talk about Altera Cyclone Dev. Board ?? 

do you use NIOS1.1 and QUARTUS 4.2 SP1 ? 

 

if yes then from documentation 

 

"The CompactFlash connector shares several Cyclone I/O pins 

with expansion prototype connector PROTO1. See “Expansion 

Prototype Connector (PROTO1)” on page 1–11 for details on 

PROTO1." 

 

Did you started with the standard reference design ? 

if yes, then have a look at the assignement editor, there are pin names for the 

cf card but they are not used in the standard design (marked with ?). 

 

If you want to use PROTO2, the pins on PROTO2 are free, it should work. 

I already worked with PROTO2 connector and had no problems. 

 

I used e.g. the following script to assign the pinnames to the  

proto2 connector, after compilation you should  

check the fitter pinout file !!! 

 

if you make your own component e.g. with "interface to userlogic" and you 

do not mark the "shared" check box at the address signals you will get an extra 

address bus which you connect to your proto2 connector. 

 

hope this helps. 

 

 

sample Script for IO_PROT2  

 

# PINS PROTO2 CONNECTOR 

# Pin & Location Assignments# ========================== 

# ###### J16# ####### RES_n 1 2 GND --- ---# T15 3 4 W15 P2_D\[0\] P2_D\[1]# Y15 5 6 U15 P2_D\[2] P2_D\[3]# V15 7 8 V14 P2_D\[4] P2_D\[5]# U14 9 10 Y14 P2_D\[6] P2_D\[7]# W14 11 12 T14 P2_A\[2\] P2_A\[3]# R14 13 14 V13 P2_A\[4] P2_A\[5]# U13 15 16 W13 P2_A\[6] P2_A\[7]# Y13 17 18 R13 P2_A\[8] P2_A\[9]# GND 19 20 NC # T13 21 22 GND --- ---# V12 23 24 GND --- ---# U12 25 26 GND --- ---# T12 27 28 T11 P2_WR_n P2_RD_n ---# W12 29 30 GND P2_CS_n P2_IRQ_n# Y12 13 32 W8 --- P2_RESET# Y8 13 34 NC P2_MAN_RESET---# U9 13 36 V9 --- ---# T9 13 38 U8 --- ---# R9 13 40 GND --- --- 

# #######J15# ####### GND 1 2 +5V# R11 3 4 Y9 # W9 5 6 T10# U10 7 8 V10# W10 9 10 Y10# V11 11 12 U11# W11 13 14 Y11 

# ###### J17# ####### Vun 1 2 GND# NC 3 4 GND# +3V3 5 6 GND# +3V3 7 8 GND# OSC 9 10 GND# CLKI 11 12 GND# CLKO 13 14 GND# +3V3 15 16 GND# +3V3 17 18 GND# +3V3 19 20 GND 

 

set_location_assignment Pin_T15 -to P2_D\[0\] 

set_location_assignment Pin_W15 -to P2_D\[1\] 

set_location_assignment Pin_Y15 -to P2_D\[2\] 

set_location_assignment Pin_U15 -to P2_D\[3\] 

set_location_assignment Pin_V15 -to P2_D\[4\] 

set_location_assignment Pin_V14 -to P2_D\[5\] 

set_location_assignment Pin_U14 -to P2_D\[6\] 

set_location_assignment Pin_Y14 -to P2_D\[7\] 

 

set_location_assignment Pin_W14 -to P2_A\[2\] 

set_location_assignment Pin_T14 -to P2_A\[3\] 

set_location_assignment Pin_R14 -to P2_A\[4\] 

set_location_assignment Pin_V13 -to P2_A\[5\] 

set_location_assignment Pin_U13 -to P2_A\[6\] 

set_location_assignment Pin_W13 -to P2_A\[7\] 

set_location_assignment Pin_Y13 -to P2_A\[8\] 

set_location_assignment Pin_R13 -to P2_A\[9\] 

 

set_location_assignment Pin_T12 -to P2_WR_n  

set_location_assignment Pin_T11 -to P2_RD_n 

set_location_assignment Pin_W12 -to P2_CS_n 

set_location_assignment Pin_Y12 -to P2_IRQ_n 

set_location_assignment Pin_W8 -to P2_RESET 

set_location_assignment Pin_Y8 -to P2_MAN_RESET
0 Kudos
Altera_Forum
Honored Contributor II
555 Views

There might be a problem with the external component or maybe the software. I'm sorry that I didn't discover this before. There seems to be no problem with the proto2 that I can see. I become confused because the software didn't run everytime I uploaded it. Some times it would run, other times it wouldn't. 

 

Ole
0 Kudos
Reply