Quantcast
Channel: Altera Forums
Viewing all 19390 articles
Browse latest View live

Nios 2 Camera interface

$
0
0
Hello All,

I am interfacing OV2640 camera to nios2 design on De2 115. I have a custom parallel port component which is connected to 8 data lines of camera. There are 3 control signals VSYNC, HREF and PCLK. I am supposed to latch the data into memory during each PCLK period. I was thinking may be it will be a better idea to get this thing going on in hardware (May be a hardware triggered DMA?) or something rather than trying to read the port on each PCLK in software. Can anyone give some recommendation please?

Thanks so much!
Best regards,

5CEBA2F 256-FPGA pinout not available

$
0
0
We're looking at using a Cyclone V in our next project, and want to use this part: 5CEBA2F1C8N, which Digikey/Altera buy-now website says is a 256 pin FPGA, but the Altera website documentation for this part shows only the 324 BGA pin-out.

Can anyone help point me to the correct doumentation?

TIA.

why the NiosII program don't run in 13.1

$
0
0
when i use NiosII 13.1 , the program don't run when i checked the "reset the selected system" in "run config" tab.the same problem, when I programmed the sof and elf to the epcs with "NiosII flash programmer", the program will not run when power on,but the logic is running.
who can tell me why?
the same project is ok in 12.1.

Error: Can't simulate mismatched node types

$
0
0
Good day, I design ALU (arithmetic and logic unit) in the language of Verilog HDL. When I try to simulate the circuit though I get these errors:
Quote:

Warning: Wrong node type for node "result[0]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "result[1]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "result[2]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "result[3]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "result[4]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "result[5]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "result[6]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "result[7]" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "flagZ" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "flagO" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Warning: Wrong node type for node "flagN" in vector source file. Design node is of type Output, but signal in vector source file is of type Input.
Error: Can't simulate mismatched node types
Error: Quartus II 64-Bit Simulator was unsuccessful. 11 errors, 11 warnings
What am I doing wrong here?

P.S.
I live in Russia, and does not know very well English. Forgive my ignorance.
Attached Files

meeting timing requirement in quartus without hard ip license for quartus synthesis

$
0
0
For a project we required ip of spi4.2. but before buying it from altera we created some interface for it and tried to synthesize it with the sdc we have made. my question is is it possible that due to non availability of licese of that ip their is some timing requirement no meeting in that interface block of spi...kindly help

toggle report in Modelsim

$
0
0
I want to toggle report (count number of the transitions) in modelsim every 10 ns from a simulation that lasts in 1000 ns. Anybody knows that how i can do this?

Question about editing components in qsys

$
0
0
Hi,

I've got a custom component in a qsys project. I'm wondering every time when I modify the source file, do I have to delete the component from the 'system contents', edit the component, save and re-add the component back to the 'system contents'? Is there anyway I can refresh/update the component already connected in the 'system content'?

Thank you guys.

Qsys - Quartus II

$
0
0
Hello,

I would like to know if QSYS is on the 9.1 sp2 version of Quartus II because i try to search it but i never found. I found only SOPC that according me has not all function that QSYS have. But for my project i need to use the version 9.1 sp2....there is the possibility to install QSYS on version 9.1?

Best Regards

Michele

Fan-out too weak to trigger SignalTap II ??

$
0
0
I set up two instances in signaltap, one instance contained a signal that would trigger acquisition at rising edge, the other instance contained the same signal but would be triggered by something else. The problem is the former instance wasn't triggered at all during the runtime while several rising edges on that signal was recorded in the latter instance. The signal was a combinatorial bus, so is it possible to have a situation where the combinatorial fan-out is too weak to trigger the signaltap? If this is not supposed to happen, what could be the reason for this?

Thanks!

Enable open drain on CRC_ERROR pin

$
0
0
I try to use the CRC_ERROR pin on a Cyclone IV device.
The functionality is however not clear.
According to the documentation this pin is open drain.
According to Quartus the open drain is selectable.

Question:
Does the selection:1/ Enable Error Detection CRC also enable the CRC_ERROR pin?
Or does the selection:2/ Enable open drain on CRC_ERROR pin enable this pin?

If selection 2/ is correct, then the text should read: Enable CRC_ERROR pin (open drain)

Thanks for any answer.

Timing the OpenCL kernel execution

$
0
0
Hi

I am interested to measure the amount of time each of the kernels take to execute (including the memory transfers) in my Multikernel application.

Any suggestions on what timer to use in the host application for precisely timing the kernels?

A shared custom Instruction between Nios II processors

$
0
0
Hello everybody,

I want to
Implement a shared Custom Instruction Hardware(a shared Accelerator) which connects directly to the Nios II arithmetic logic unit (ALU).
In fact, I want to know how to add this shared custom instruction between two NiosII processors.
Thanks in advance.

Trying to compile linux for Cyclone V Soc dev board - errors

$
0
0
I all, I get the following errors when I am following the steps on http://www.rocketboards.org/foswiki/...GettingStarted

ERROR: Failed to obtain external Linaro toolchain version: Execution of '/opt/altera-linux/linaro/gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux/bin/arm-linux-gnueabihf-gcc -v' failed: command not found
ERROR: Failed to obtain external Linaro toolchain version: Execution of '/opt/altera-linux/linaro/gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux/bin/arm-linux-gnueabihf-gcc -v' failed: command not found
ERROR: Execution of event handler 'external_linaro_toolchain_version_handler' failed
Traceback (most recent call last):
File "external_linaro_toolchain_version_handler(e)" , line 12, in external_linaro_toolchain_version_handler(e=<bb.ev ent.ConfigParsed object at 0x3b5ee50>)
File "external-linaro-toolchain-versions.inc", line 4, in elt_get_gdb_version(d=<bb.data_smart.DataSmart object at 0x2aed510>)
NameError: global name 'CmdError' is not defined


WARNING: Host distribution "Ubuntu 12.04.3 LTS" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.


As far as I can tell, the paths it says it cannot find do exist. When I am in the correct directory, and run any files here, it tells me the file doesnt exist - odd that given its in the file list...

I have Ubuntu running on a VM inside windows.

Newbie project - DSO with high speed ADC, FPGA, DDR2 (3) and MCU

$
0
0
Hi everyone,

I have been working with AVRs and C/C++ for quite a few years and everything looked pretty much straightforward as i used CodeVisionAVR and did not have to dig in the manual of every uC i worked with. Recently i started a project (http://www.youtube.com/watch?v=73ygBq9Wq_M) with a STM32F4 discovery board aiming to build a DSO with high speed ADC 16bits (100-250Msps) and a few (tenths) megabytes of memory to store the captured values. As i finally concluded, after googling a lot and asking for help in chat rooms, the most obvious solution was to use an ADC, connect it to a FPGA, connect a RAM chip to the FPGA and optionally also connect a uC such as the STM32F4 to the FPGA or just use Nios II as uC (depending on the CPU power needs of the app). In order to get to know a little bit about FPGAs, i bought a DE0-nano which was perfect for my case as it carries an ADC, a Cyclone IV, 32Mbytes of SDRAM and some sensors, leds, buttons etc. I was able to play a little bit with the leds and buttons based on a Nios II configuration but that was pretty much all i did. So, as i am not experienced at all with FPGAs and don't have a clue about coding in Verilog / VHDL or even thinking in terms of parallel processing, i would like to ask for your suggestions as far as my project is concerned.

My thinking is that an ADC 16bit 250MSps connected to a FPGA and a DDR2 or 3 will do the trick. The thing is that i have no idea where to start from. I know that a FPGA does have a huge advantages package that includes interfacing different types of levels such as LVDS (ADC), TTL/CMOS (uC) and memory chips at the same time which is fantastic. However, even though i used the Quarus 13 software not for writing my own HDL but using the MegaWizard, i have no clue which IPs to use and how in order to interconnect the ADC, DDR mem and probably an ARM uC such as a STM32F4. As far as i know the speed of 250Msps plays a huge role of whether selecting a Cyclone FPGA or a faster one. There will also be issues with the timing of the memory while capturing at 250Msps and so on. As i read, simulation must be done before proceeding with anything but of course after writing the HDL that will bring all these parts together.

- The ADC will be dual at 16bits 250Msps. The output of the ADC will be LVDS parallel (not serial). That would propably be the important key when considering which FPGA to use. Which do you think suits this project?
- I was thinking about using a memory chip close to 64Mbytes so that i can always run the ADC at max rate and still be able to show on my LCD low frequency signals by compressing time axis as well as doing other things that only very expensive DSOs do. Is there a memory like that when it comes to DDR2/3?
- Will a Nios II CPU be able to process fast enough the data from the memory? Not the whole 64Mbytes. For example, the RMS value of a signal would require (assumption) 10K samples to be calculated with a decent accuracy. Would such a CPU be able to draw fast enough on a 800x480 16bit TFT LCD via DMA?
- What should i be reading right now? Verilog?


I know that specific answers require specific questions but the point where i am right now is anything but guess-safe.

Thanks for reading.

Any suggestions are welcome.

Manos

HTM Help files not loading

$
0
0
I just installed Quartus 13.0.1 SP1 and it seems to be running OK except for the help files. Whenever I select a HELP menu item that tries to load a .htm from file:\\..., I get a flashing blue banner at the top of my browser screen (Chrome) and it seems to go into an endless loop trying to load the .htm fie.

Is this solved in 13.1 ?

toggle report in Modelsim

$
0
0
I want to toggle report (count number of the transitions) in modelsim every 10 ns from a simulation that lasts in 1000 ns. Anybody knows that how i can do this?

Using CVO for NTSC output

$
0
0
Hi All,
I have a question that I have been battling for a couple of days. I am trying to use Altera's CVO IP to output NTSC video. I have tried to use the NTSC setting on the CVO but it automatically selects the Embedded sync options, but I need the sync signals on separate wires because my Video DAC requires the sync signals. This is the setup that I have: TPG -> CVO. I am using Quartus 13.0. Here are the settings that I am using for the TPG and the CVO. The pixel clock frequency I am using is 27Mhz.


TPG settings:
image width: 720
image height: 488
Bits per pixel per color plane: 8
Color space: RGB
Output format: 4:4:4
Color plane configuration: Parallel
interlacing: interlace output (F0 first)
pattern: Color bars

CVO settings:
image width: 720
image height: 487
Bits per pixel per color plane: 8
Number of color planes: 3
Color plane format: parallel
Interlaced video: checked
Syncs signals: On separate wires

Active picture line: 20

Field 1
Horizontal sync: 138
hfp: 0
hbp: 0
Vertical sync: 19
vfp: 0
vbp: 0

Field 0
F rising edge line: 266
F falling edge line: 4
Vertical blanking rising edge line: 264

Vertical sync: 19
vfp: 0
vbp: 0

pixel fifo size: 720
Fifo level : 719

I am not getting anything out on the screen with this setup. Can you guys shed some light on what I am doing wrong. Thank you for your help.

Linker problem with SDK 13.1

$
0
0
Hi people,

I have some linker error happening with the SDK 13.1. To diagnose a bit, I tried running the examples from 13.0 found in "$(ALTERAOCLSDKROOT)/designs/", which are not provided anymore with 13.1 from what I have seen, and I get the same errors as in my own project. Here they are:

1>alteracl.lib(acl_program.obj) : error LNK2001: unresolved external symbol load_autodiscovery_xml
1>alteracl.lib(acl_program.obj) : error LNK2001: unresolved external symbol load_board_spec_xml

You will guess this is using Visual Studio. My board is a Nallatech PCIe-385N and the computer is running Windows 7.

Does anybody have an idea where the problem might be?

Thanks a bunch,

Smith

ALTFP_SINCOS's Latency

$
0
0
I tried to generate ALTFP_SINCOS for sin with qmegawiz. I set the PIPELINE parameter to 36 according to the document

http://www.google.com/url?sa=t&rct=j...,d.eW0&cad=rja

but received an error: Error: The specified megafunction or wizard is not supported in command line mode
Parameter PIPELINE has been assigned the value 36 which is incompatible with the current settings of WIDTH_MAN(23). The legal value is 35

It happened to 13.1, 13.0sp1 and some earlier versions. It worked when I set it to 35. Is it an mistake of document, a bug in the tool, or something I missed?

Thanks

How to set Virtual Memory Address for excalibur with mmu?

$
0
0
Hello everyone.
The NiosII MMU boot mechanism puzzle me for several days.
Without MMU,Germs can boot well from the uart.But when I add the onchip_memory_0 with the MMU model,there's no response from the uart.
The physical address of the excalibur.s and excalibur.mk are set as below.
Code:

    GEQU na_sdram                                    , 0x18000000 # altera_avalon_new_sdram_controller
    GEQU na_sdram_end                                , 0x1c000000
    GEQU na_sdram_size                                , 0x04000000
    GEQU na_cpu0                                      , 0x00000000 # altera_nios2
    GEQU na_uart                                      , 0x08000060 # altera_avalon_uart
    GEQU na_uart_irq                                  , 2
    GEQU na_cpu0_jtag_debug_module                    , 0x11000000 # altera_nios2
    GEQU na_memory_monitor                            , 0x00004000 # altera_avalon_onchip_memory
    GEQU na_memory_monitor_end                        , 0x00004800
    GEQU na_memory_monitor_size                      , 0x00000800
        GEQU na_onchip_memory_0_s1                        , 0x00005000 # altera_avalon_onchip_memory2
    GEQU na_onchip_memory_0_s1_end                    , 0x00006000
    GEQU na_onchip_memory_0_s1_size                  , 0x00001000
    GEQU na_sys_clk_timer                            , 0x10000800 # altera_avalon_timer
    GEQU na_sys_clk_timer_irq                        , 0
    GEQU na_jtag_uart                                , 0x10000840 # altera_avalon_jtag_uart
    GEQU na_jtag_uart_end                            , 0x10000848
    GEQU na_jtag_uart_size                            , 0x00000008
    GEQU na_jtag_uart_irq                            , 1
    GEQU na_ext_flash                                , 0x08000000 # altera_avalon_cfi_flash
    GEQU na_ext_flash_end                            , 0x10000000
    GEQU na_ext_flash_size                            , 0x08000000
 
    GEQU na_null                        , 0
    GEQU nasys_timer_count              , 1
    GEQU nasys_timer_0                  , na_sys_clk_timer
    GEQU nasys_uart_count                , 1
    GEQU nasys_uart_0                    , na_uart
    GEQU nasys_uart_0_irq                , 2
    GEQU nasys_reset_address            , 0x00004000
    GEQU nasys_exception_address        , 0x18000020
    GEQU nasys_break_address            , 0x11000020
    GEQU nasys_fast_tlb_miss_exc_address , 0x00005100
    GEQU nasys_clock_freq                , 50000000
    GEQU nasys_clock_freq_1000          , 50000
    GEQU nasys_debug_core                , 0
    GEQU nasys_printf_uart              , na_uart
    GEQU nasys_printf_uart_irq          , na_uart_irq
    GEQU nasys_main_flash                , 0x08000000
    GEQU nasys_main_flash_size          , 0x08000000
    GEQU nasys_main_flash_end            , 0x10000000
    GEQU nasys_program_mem              , 0x00004000
    GEQU nasys_program_mem_size          , 0x00000800
    GEQU nasys_program_mem_end          , 0x00004800
    GEQU nasys_data_mem                  , 0x00004000
    GEQU nasys_data_mem_size            , 0x00000800
    GEQU nasys_data_mem_end              , 0x00004800
    GEQU nasys_stack_top                , 0x00004800

Code:

                  HOST_COMM = na_uart
        NASYS_BREAK_ADDRESS = 0x11000020
          NASYS_BREAK_DEVICE = cpu0
          NASYS_DATA_DEVICE = memory_monitor
              NASYS_DATA_MEM = 0x00004000 # 3389014016
          NASYS_DATA_MEM_END = 0x00004800 # 3389016064
        NASYS_DEVICE_FAMILY = "CYCLONEIII"
    NASYS_EXCEPTION_ADDRESS = 0x18000020
      NASYS_EXCEPTION_DEVICE = na_sdram
NASYS_FAST_TLB_MISS_EXC_ADDRESS = 0x00005100
NASYS_FAST_TLB_MISS_EXC_DEVICE = onchip_memory_0
            NASYS_MAIN_FLASH = 0x08000000 # 3489660928
        NASYS_MAIN_FLASH_END = 0x10000000 # 3623878656
              NASYS_OCI_CORE = off
          NASYS_PRINTF_UART = na_uart
  NASYS_PRINTF_UART_ADDRESS = 0x08000060 # 3355443296
        NASYS_PROGRAM_DEVICE = memory_monitor
          NASYS_PROGRAM_MEM = 0x00004000 # 3389014016
      NASYS_PROGRAM_MEM_END = 0x00004800 # 3389016064
        NASYS_RESET_ADDRESS = 0x00004000
          NASYS_RESET_DEVICE = memory_monitor
            NASYS_STACK_TOP = 0x00004800 # 3389016064
          NASYS_VECTOR_TABLE = 0x00004820 # 3395305504
      NASYS_VECTOR_TABLE_END = 0x000048a0 # 3395305632

In Nios II processor reference handbook and http://www.alterawiki.com/wiki/U-Boot_with_MMU ,
Nios run in the supervisor mode after the reset process,so the peripherial(sdram,flash,onchip_memory,uart,timer,j tag_uart)need to be addressed at 0xE0000000?
All the NASYS_* components in excalibur.mk need to be at 0xC0000000,except reset, general
exception, break, and fast TLB miss,vector_table,stack_top must point to low physical memory 0x00000000?
So I modify them as this,am I right?
Code:



    GEQU na_sdram                                    , 0xf8000000 # altera_avalon_new_sdram_controller
    GEQU na_sdram_end                                , 0xfc000000
    GEQU na_sdram_size                                , 0x04000000
    GEQU na_cpu0                                      , 0xf0000000 # altera_nios2
    GEQU na_uart                                      , 0xe8000060 # altera_avalon_uart
    GEQU na_uart_irq                                  , 2
    GEQU na_cpu0_jtag_debug_module                    , 0xf1000000 # altera_nios2
    GEQU na_memory_monitor                            , 0xe0004000 # altera_avalon_onchip_memory
    GEQU na_memory_monitor_end                        , 0xe0004800
    GEQU na_memory_monitor_size                      , 0x00000800
      GEQU na_onchip_memory_0_s1                        , 0xe0005000 # altera_avalon_onchip_memory2
    GEQU na_onchip_memory_0_s1_end                    , 0xe0006000
    GEQU na_onchip_memory_0_s1_size                  , 0x00001000
    GEQU na_sys_clk_timer                            , 0xf0000800 # altera_avalon_timer
    GEQU na_sys_clk_timer_irq                        , 0
    GEQU na_jtag_uart                                , 0xf0000840 # altera_avalon_jtag_uart
    GEQU na_jtag_uart_end                            , 0xf0000848
    GEQU na_jtag_uart_size                            , 0x00000008
    GEQU na_jtag_uart_irq                            , 1
    GEQU na_ext_flash                                , 0xe8000000 # altera_avalon_cfi_flash
    GEQU na_ext_flash_end                            , 0xf0000000
    GEQU na_ext_flash_size                            , 0x08000000
 
    GEQU na_null                        , 0
    GEQU nasys_timer_count              , 1
    GEQU nasys_timer_0                  , na_sys_clk_timer
    GEQU nasys_uart_count                , 1
    GEQU nasys_uart_0                    , na_uart
    GEQU nasys_uart_0_irq                , 2
    GEQU nasys_reset_address            , 0x00004000
    GEQU nasys_exception_address        , 0x18000020
    GEQU nasys_break_address            , 0x11000020
    GEQU nasys_fast_tlb_miss_exc_address , 0x00005100
    GEQU nasys_clock_freq                , 50000000
    GEQU nasys_clock_freq_1000          , 50000
    GEQU nasys_debug_core                , 0
    GEQU nasys_printf_uart              , na_uart
    GEQU nasys_printf_uart_irq          , na_uart_irq
    GEQU nasys_main_flash                , 0xc8000000
    GEQU nasys_main_flash_size          , 0x08000000
    GEQU nasys_main_flash_end            , 0xd0000000
    GEQU nasys_program_mem              , 0xc0004000
    GEQU nasys_program_mem_size          , 0x00000800
    GEQU nasys_program_mem_end          , 0xc0004800
    GEQU nasys_data_mem                  , 0xc0004000
    GEQU nasys_data_mem_size            , 0x00000800
    GEQU nasys_data_mem_end              , 0xc0004800
    GEQU nasys_stack_top                , 0x00004800

Code:

                  HOST_COMM = na_uart
        NASYS_BREAK_ADDRESS = 0x11000020
          NASYS_BREAK_DEVICE = cpu0
          NASYS_DATA_DEVICE = memory_monitor
              NASYS_DATA_MEM = 0xc0004000 # 3389014016
          NASYS_DATA_MEM_END = 0xc0004800 # 3389016064
        NASYS_DEVICE_FAMILY = "CYCLONEIII"
    NASYS_EXCEPTION_ADDRESS = 0x18000020
      NASYS_EXCEPTION_DEVICE = na_sdram
NASYS_FAST_TLB_MISS_EXC_ADDRESS = 0x00005100
NASYS_FAST_TLB_MISS_EXC_DEVICE = onchip_memory_0
            NASYS_MAIN_FLASH = 0xc8000000 # 3489660928
        NASYS_MAIN_FLASH_END = 0xd0000000 # 3623878656
              NASYS_OCI_CORE = off
          NASYS_PRINTF_UART = na_uart
  NASYS_PRINTF_UART_ADDRESS = 0xc8000060 # 3355443296
        NASYS_PROGRAM_DEVICE = memory_monitor
          NASYS_PROGRAM_MEM = 0xc0004000 # 3389014016
      NASYS_PROGRAM_MEM_END = 0xc0004800 # 3389016064
        NASYS_RESET_ADDRESS = 0x00004000
          NASYS_RESET_DEVICE = memory_monitor
            NASYS_STACK_TOP = 0xc0004800 # 3389016064
          NASYS_VECTOR_TABLE = 0xc0004820 # 3395305504
      NASYS_VECTOR_TABLE_END = 0xc00048a0 # 3395305632

Kinder Regards!
Viewing all 19390 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>