|
|
This file errata.txt lists known issues with the Nios II
processor version 1.0 and the Nios II IDE.
For the most up to date information please go to
https://mysupport.altera.com
This errata file may have been updated following release.
If that is the case, an errata.txt file will be located at
top level of the CD.
If there is a number associated with the text, that number
is the Software problem Report (SPR) number. Please use this
number if you are communicating with an Altera representative
regarding an issue listed here.
=====================================================================
Known problems/limitations in Nios II Hardware Development Tools/Flow
Download Cables:
You must use a supported download cable when downloading,
debugging, or communicating with Nios II systems over JTAG.
Using the USB Blaster Rev A, ByteBlaster, ByteBlaster MV,
ByteBlaster II, and MasterBlaster cables may cause intermittent
JTAG communication failures.
The modes of failure are:
* Debugging Failure with the Nios II IDE - Debug session
terminates with JTAG I/O error
* Nios II JTAG UART Failure - Invalid characters transmitted
and received via Nios II Terminal
* Device Configuration Failure - Device configuration fails
with an error message from the Quartus II Programmer
* SignalTap Failure - SignalTap session terminates with JTAG
communication error
If you receive the following message while using the Nios II Terminal,
the tools could not verify whether you are using a supported cable.
nios2-terminal: Warning: Unable to verify whether your download cable is supported for Nios II systems.
nios2-terminal: If you use an unsupported cable, you may experience intermittent JTAG communication failures.
nios2-terminal: Please refer to the file errata.txt included in the Nios II development kit documents directory for
nios2-terminal: information on how to update your system.
In general, the above message will only occur if you have
re-installed Quartus II 4.0 SP1 after you installed Nios II
version 1.0. Re-installing Nios II will allow your system to
detect if your cable is supported. The warning message will
occur each time Nios II Terminal is started until you re-install
Nios II.
If you receive the following message from Nios II Terminal, you
are not using a supported download cable. The warning message will
occur each time Nios II Terminal is started and an unsupported cable
is detected.
nios2-terminal: Warning: The JTAG cable you are using is not supported for Nios II systems.
nios2-terminal: You may experience intermittent JTAG communication failures with this cable.
nios2-terminal: Please use a USB Blaster revision B cable or another supported cable.
nios2-terminal: Please refer to the file errata.txt included in the Nios II development kit documents directory for more information.
The supported cables for downloading, debugging, or communicating
with Nios II systems are:
* USB Blaster Revision B or later
Revision B cables are clearly labeled as Revision B.
(Revision A cables have no revision label.)
* Please contact Altera for additional information
about supported cables.
The input PIOs in the example hardware designs 151570 - The external trace feature of Nios II JTAG debugging 128922 - Interface to user logic can't read files that 145658 - When the DEV_CLRn input (in Quartus II) is used to 143402 - Problem: If there is a Compact Flash card inserted on the 151666 - If your program reads the value of an uninitialized BSS ============================================================ 151802 - If you have two USB-Blasters attached to your machine 151950 - If the C/C++ Search fails, try the File Search facility. 151193 - Problem: "Flash programming within Nios II IDE terminates Solution: The Flash Programmer tool allows you 151262 - The flash programmer tool will automatically download 151588 - Changing active build configuration for a Nios II 150078 - If launching a debug session fails after a long "Launch Failed. Failed launching debugger" increase the debugger timeouts in the IDE and 151453 - Problem: Modal dialog gets hidden so Nios II IDE appears 151394 - Problem: You get an error message 146874 - Outline View only opens files in the current project. 148840 - Creating an app & lib in a non-default location 148723 - If you have renamed your cpu in SOPC Builder you must 150983 - If you want to use the flash programmer GUI with an 151055 - When you first create a components inc directory, 151095 - When using the Flash Programmer tool for advanced 151029 - Read-only zip file systems are automatically programmed ============================================================ 152783 - If you are using the rand() or srand() function with 151770 - Problem: nios2-terminal exits with the error Problem: nios2-terminal does not display uart Solution: make sure code is legal C (ANSI). 143099 - Problem: The SOPC Builder and Nios II SDK 145610 - JTAG UARTs 151073 - ISA-NIOS "BlackBox" users: OR If you can do without APU programmer support on your computer and cd 149046 - When assembling large functions you may receive an error 148220 - The following error in nios2-elf-gcc (the compiler) 147524 - In the ISS, you may only use one printing-device at a time. For v1.0, the ISS technically only supports systems with one 151759 - The ISS only provides full support for output from character 151948 - ELF files larger that 30 Megabytes in size can cause ============================================================ 151846 - There is a known limitation in Quartus II v4.0 SP1 This problem will be fixed in Quartus II v4.1.
E-mail:
Modelsim simulation:
If you attempted to use ModelSim Altera version 5.7e without
installing the Quartus II 4.0 SP1 precompiled libraries
available at
https://www.altera.com/support/software/download/eda_software/modelsim/dnl-msim-57e.jsp,
you must delete your
Quartus II project directory and regenerate your SOPC Builder
system. This is to ensure that the appropriate ModelSim
ini file is created for the simulation.
contains simulation settings to drive the inputs
to 0xFF during simulation. You can change this
setting in the Simulation tab in the PIO wizard
in SOPC Builder to match your desired simulation
criteria.
involves the hidden instantiation of a PLL. This
may become an issue if the customer is using a device
with limited PLL resources (like Cyclone) or creating
a design that utilizes all available PLL resources.
Possible workarounds include:
- choosing a debug option without external trace,
- deleting or combining PLLs to reduce design resources,
- feeding the SOPC Builder clock directly from an
external pin instead of from an internal PLL,
- using the "full_featured" example design as a platform
for system development, which has special allowances
to use 1 PLL for both system clock and external trace
clock.
use ' defines.
generate a device wide reset then if the fpga is
reset while the JTAG UART is active, the UART may
become unstable. Solution is to turn off the
"Enable device wide reset (DEV_CLRn)" setting
in the Quartus II software.
development board, the LCD (or indeed many things
connected to proto header 1) won't work.
Solution: Remove the Compact Flash card.
variable during HDL simulation when the HAL system library
has been compiled with the 'Modelsim only, no hardware support'
property enabled in Nios II IDE, a warning will be produced
about unfiltered data being ‘x’. This occurs because when
this property is enabled, the code that clears the BSS memory
region is omitted to speed up HDL simulation so this
memory region is uninitialized. The BSS region contains
global and static local variables that are not initialized
by the application so they default to a value of zero.
When the Nios II CPU reads uninitialized variables, it
displays a warning and converts any of the bits of the
uninitialized data to zero which correctly mimics the
effect of the missing BSS clearing code. The HAL code that
executes before and after main() may use BSS variables
so these warnings may be generated even if your application
doesn’t use the BSS.
Known Problems/Limitations with the Nios II IDE
and are using Quartus II 4.0 SP1 then you will not be
able to select which USB-Blaster to use. The workaround
is to unplug the USB cable from the USB-Blaster which
you are not using.
with error:
"make: *** No rule to make target 'epcs/user/factory'. Stop.
to program FPGA configuration (sof) files to any of
the CONFIGURATION locations specified for a target
board in SOPC Builder. However, if the SOPC Builder system
does not actually include a flash device corresponding to
a CONFIGURATION, the above error will occur.
the contents of a read-only zip file system for
"managed" applications. File system flash programming
does not occur for Advanced C/C++ applications. To
program a read-only flash file system for an advanced
application, first create a managed application which
uses the same system library as the advanced application.
Program the flash for the managed application, then
program it again for the advanced application. The
file system programmed in flash by the managed
application will then be available to the advanced
application.
project - On the C/C++ build property page, the
configuration dropdown box can be used to select
the active configuration (e.g. Release or Debug).
When the active configuration is changed, this
does not automatically update the rest of the
window containing the settings such as Compiler
flags, optimization level, etc. The user must
deselect then reselect a category (e.g. click on
PreProcessor then General) to see the settings
for that configuration.
time (20 secs), with the following error message:
try again. In the Nios II IDE, set Windows
menu -> Preferences -> C/C++ -> Debug ->
GDB MI -> Debugger Timeout to 0x100000.
and
Windows menu -> Preferences -> C/C++ ->
Debug -> GDB MI -> Launch Timeout to 0x100000.
151583 - The recommended ways to terminate a run session are:
1. Select the Nios II Terminal process in the debug
view and click the terminate icon (the red square).
or 2. Select the top line of the launch configuration
(typically named
configuration [Nios II Hardware}) and select the
terminate icon.
or 3. If you want to re-download and re-launch your run,
simply click the running man icon. This will
terminate the previous run session for you.
unusable.
Solution: Use Alt-Tab to bring the modal dialog to
the front.
saying that a resource or resources are
out of sync with the file system.
Solution: Select the out of sync resource (e.g. project)
and select Refresh from the File menu.
147571: Using a "Dazzle" USB media reader on your computer
may result in this error while browsing for a file
or folder in the Nios II IDE:
javaw.exe - No Disk
The error results from "Browsing for a folder" from
the Nios II IDE.
Solution: Shut off the media reader. Turn it back on
after you are finished with the Nios II IDE.
You must specifically set the location for the app
AND the lib separately if you want them to be
located in the same non-default location.
If they are in the default location, no action is
required.
recreate a system library targeted to the system with
the new cpu.
Alternatively you can delete the system library project
(without deleting the contents) and re-import it
selecting the new cpu.
advanced C/C++ Project, the makefiles and ELF files
need to be in a subdirectory of the application
project, for example Debug/adv.elf.
or HAL component header file, you may need to perform
a clean build, i.e. rebuild, of existing system
library projects for the new files to be detected.
C/C++ projects, you may see a spurious error message:
"You must select a target board for this system in SOPC
Builder before programming flash." This message will
appear even if the associated hardware project did select
a target board. To clear the error condition, specify
a cable in the "Target Connection" tab, then return
to the Main tab.
into flash when an application associated with the system
library containing the file system is programmed into flash.
Advanced C/C++ applications associated with such system
libraries, however, will not have their file system
programmed into flash. To accomplish file system flash
programming for advanced C/C++ applications, first create a
managed application which is associated with the system
library containing the file system, and program it into flash.
Then, program the advanced C/C++ application into flash.
Known problems with the Nios II Compiler Tool Chain & Utilities
the small C library, a manual initialization of the
random number generator is needed. Add:
rand(); srand(1);
before the first occurance of these functions.
"can't get uart attributes" when using a standard
UART
Solution: Initialize the port by running (and then quitting)
`nios2-run -t` from a command-line first.
(COM port) output
Solution: Run `nios2-run -t` from a command-line
(before running or debugging in Nios II IDE)
to see output from a UART.
140968 - The first-generation Nios processor incorrectly
overlooked non-standard ANSI C coding.
The Nios II processor enforces ANSI C standards.
Shell may "hang" and become unresponsive
when run while the Frisk antivirus software
is running.
Solution: Turn off the Dynamic Virus Checking feature
of the Frisk software before running SOPC
Builder or the Nios SDK.
The Legacy SDK flow does not support JTAG UARTs.
150485 - The HAL DMA driver has no support for double word
and quad word transfers.
FS2 ISA-NIOS customers will have to obtain the newest install
from FS2 in order to use ISA-Nios or ISA-Nios/T devices.
The required LPT port "parport2k" driver is not installed
by the Nios II installer. Install the JTAGServer driver
using the FS2 ISA-NIOS installer on all PCs on which you
wish to use the ISA-NIOS; this will also install the
required "parport2k" driver.
151036 - If the jtagserver.exe process on your machine is using
151035 large amounts of memory when not in use then it can be
restarted by issuing the following commands from the
command line:
jtagserver --stop
jtagserver --start
would like to get rid of the memory leak then please
try the following:
./jtagserver --stop
rename pgm_pgmdrv_apu_usb.dll pgm_pgmdrv_apu_usb.leak.dll
./jtagserver --start
such as: Error: branch offset 33008 out of range -32768 to 32764.
If this happens, tell the assembler to "relax branches" by
adding -relax-section to the assembler. If this occurs
while compiling a C/C++ program, add -Wa,-relax-sections to the
compile command line directly, by modifying the CFLAGS
makefile variable, or changing the C/C++ Build Setting
in the Nios II Integrated Development Environment.
is caused by having a large stack frame (> 32K) combined
with debugging information and high optimization levels.
Either reduce the number of local variables in the named function,
remove the debugging information or reduce the optimization level.
Or do not use -03 and -g together in nios2-elf-gcc compilations.
For example, you cannot have STDERR go to one UART (or JTAG UART)
and STDOUT go to another.
printing device. It does work for systems with multiple
comms devices, and it even lets you pick which ONE you
want to use. It just doesn't let you pick two.
stream devices (UART, JTAG UART).
build errors. The Elf2flash utility may fail with a
"java.lang.OutOfMemoryError". To work around this
problem you can either lower the number of symbols
in your ELF file (by turning off debug symbols), or
specify less initialized data in the application.
Known problems with Quartus II 4.0 sp1
which sometimes prevents registered output signals
from being allocated to I/O cells. This may result
in intermittent failure to access off-chip peripherals
such as flash memory and SRAM.
If your design relies on I/O registers being placed
in I/O cells, refer to the Quartus II Compilation Report.
See the Fitter > Resource Section > Output Pins section,
and look at the 'Output Register' column to find out
whether registered output signals were placed into I/O cells.
(SPR 148659 is the Quartus II SPR for tracking purposes.)
Ответы
info@telesys.ru
