Hi! I'm using Cyclone I fpga. During reset my IO pins are not stable...their vibrating between '0' to tristate.. Is this normal? if so, I need a solution to keep my IO pins on tristate. can I control them somehow while the program is being read from the epcs? maybe with reset? 10x a lot! Asaf

--- Quote Start --- I need a solution to keep my IO pins on tristate. --- Quote End --- The pin DEV_OE can be used to tri-state all pins. See p331 http://www.altera.com/literature/hb/cyc/cyc_c5v1.pdf Cheers, Dave

thank you so much! do you beleive this is the reason for the unstability I/O pins on the reset? how should I connect it so when the cyclone resets all pins will go tristate and only when the altera has done initialize all pins will go like programmed? 10x again!

--- Quote Start --- The pin DEV_OE can be used to tri-state all pins. --- Quote End --- It's an optional pin function, that takes effect after entering user mode. It's ignored before and during configuration read. --- Quote Start --- During reset my IO pins are not stable...their vibrating between '0' to tristate.. --- Quote End --- The report doesn't seem to describe a regular behaviour. According to the device manual, all I/O pins will act as inputs with weak pull-up for unconfigured device. They change to the configured behaviour when user mode is entered. There's no room for "vibrating between '0' to tristate" before CONFIG_DONE or more exactly INIT_DONE is asserted. You may want to check the state of this pins (INIT_DONE is optional only) when observing the unwanted behaviour. My first assumption would be, that the unwanted behaviour is actually observed in user mode due to incorrect logic program. Can you tell, what's the type of affected pins in your logic?

--- Quote Start --- It's an optional pin function, that takes effect after entering user mode. It's ignored before and during configuration read. --- Quote End --- Hey Frank, thanks for the correction. I was going to recommend he use the IO_PULLUP# option that is present on the Stratix devices to enable the weak pull-ups during configuration, however, the Cyclone device does not have that pin. I incorrectly assumed that DEV_OE performed a similar function (with respect to tri-stating during configuration). However, you're right, the device pins are tri-stated during configuration anyway, so the DEV_OE pin function is not required until after configuration. Cheers, Dave

the current pin is an output from my NIOS processor. I dont think I can make logic errors when sellecting an IO pin in a processor :) Do you have any suggestions?

problem with cyclone POR | Altera Community

11 Replies

Altera_Forum
Honored Contributor
15 years ago
If you do not have enough logic to probe with SignalTap, then build a modelsim simulation. Its possible that the default Modelsim simulation that Quartus will create will be sufficient for you. In SOPC Builder check the box that creates the simulation files, and then click generate to regenerate the SOPC system and the simulation files. For an SOPC system called sopc_system.sopc, the simulation folder will be called sopc_system_sim/. Inside that folder is a setup_sim.do file. Start Modelsim, cd to that directory, then type 'do setup_sim.do' at the Modelsim command line. Read the text instructions that you see, eg., type 's' to synthesize the design files. I think there is another command to add default signals to the wave editor, alternatively type 'add wave *' to add the top-level files. Then type 'run 10 us' to run the simulation for 10 us.

Look at the reset signal and your top-level I/Os that you are having trouble with.

If none of this makes sense, then you need to do some more reading. There is an application note regarding debugging NIOS systems using Modelsim.

http://www.altera.com/literature/an/an351.pdf

Cheers,
Dave

Forum Discussion

problem with cyclone POR

11 Replies

Recent Discussions

Cold Temperature Issue

SDM Monitoring & Thermal Behavior

Need Part EOL status(Active/Obsolete/Discontinued/NRND)

Agilex 7 JTAG Config Fails at 1% on Board #2 (Error 18950 / CONF_DONE Low) - But Board #1 Works

Agilex 3 VCCLSENSE and GNDSENSE