This leon3 design is tailored to the Altera NiosII Startix2
Development board, with 16-bit DDR SDRAM and 2 Mbyte of SSRAM.
As of this time, the DDR interface only works up to 120 MHz.
At 130, DDR data can be read but not written.
Note: the test bench cannot be simulated with DDR enabled
because the Altera pads do not have the correct delay models.
* How to program the flash prom with a FPGA programming file
1. Create a hex file of the programming file with Quartus.
2. Convert it to srecord and adjust the load address:
objcopy --adjust-vma=0x800000 output_file.hexout -O srec fpga.srec
3. Program the flash memory using grmon:
flash erase 0x800000 0xb00000
flash load fpga.srec
There are many different (and often confusing) terms associated
with clock-based devices. This application Note attempts
to clarify these terms, and hence serves as a comprehensive
reference on clock terminology. This application Note can be
divided into two sections. The first section describes and distinguishes
between various clock sources available today.
The second section defines and distinguishes between various
parameters used to describe clocks. This section also provides methods of measuring some of these parameters.
Jitter is extremely important in systems using PLL-based
clock drivers. The effects of jitter range from not having any
effect on system operation to rendering the system completely
non-functional. This application Note provides the reader
with a clear understanding of jitter in high-speed systems. It
introduces the reader to various kinds of jitter in high-speed
systems, their causes and their effects, and methods of reducing
jitter. This application Note will concentrate on jitter in PLL-based frequency synthesizers.
Each arc of a binary-state network has good/bad states. The system reliability, the probability
that source s communicates with sink t, can be computed in terms of minimal paths (MPs). An
MP is an ordered sequence of arcs from s to t that has no cycle. Note that a minimal path is
different from the so-called minimum path. The latter is a path with minimum cost.
This document contains a general overview in the first few sections as well as a more detailed reference in later sections for SVMpython. If you re already familiar with SVMpython, it s possible to get a pretty good idea of how to use the package merely by browsing through svmstruct.py and multiclass.py. This document provides a more in depth view of how to use the package.
Note that this is not a conversion of SVMstruct to Python. It is merely an embedding of Python in existing C code. All code other than the user implemented API functions is still in C, including optimization.
The Joint Video Team (JVT) of ISO/IEC MPEG and ITU-T VCEG are finalising a new standard for
the coding (compression) of natural video images. The new standard [1] will be known as H.264 and
also MPEG-4 Part 10, “Advanced Video Coding”. This document describes the methods of filtering
reconstructed blocks in an H.264 CODEC. Note that the H.264 draft standard is not yet finalised and
so readers are encouraged to refer to the latest version of the standard.
Samples are organized by chapter, and then by "application" or example name. You should open a project in Visual Studio .NET through the .sln (solution) file.
Note that Visual Studio .NET automatically creates various temporary and debugging files in the obj and bin sub-directory for each project. The actual uncompiled code is only the .vb files that are contained in the root project directory.
This package consists of the executable (UCW), a default script file,
this file, and the library files. It is important that the header files
end up in a include subdirectory of the directory where UCW is found.
If you unzip this file using its path information ( use folder names ) this will
automatically happen. You can optionally specify the UnderC directory
with the environment variable UC_HOME Note that this points to the directory
containing ucw.exe. If you do this, then you can copy the executable anywhere
and it will still be able to find the header files.
Welcome to UnderC version 1.2.9w
This package consists of the executable (UCW), a default script file,
this file, and the library files. It is important that the header files
end up in a include subdirectory of the directory where UCW is found.
If you unzip this file using its path information ( use folder names ) this will
automatically happen. You can optionally specify the UnderC directory
with the environment variable UC_HOME Note that this points to the directory
containing ucw.exe. If you do this, then you can copy the executable anywhere
and it will still be able to find the header files.
