verify error

[Altera_Forum]

when I build the kernel,I press "run",the error appears. 

the error is: Using cable "USB-Blaster [USB-0]", device 1, instance 0x00 Processor is already paused  Downloading 01000000 ( 0%) Downloading 01010000 ( 4%) Downloading 01020000 ( 8%) Downloading 01030000 (12%) Downloading 01040000 (16%) Downloading 01050000 (20%) Downloading 01060000 (24%) Downloading 01070000 (29%) Downloading 01080000 (33%) Downloading 01090000 (37%) Downloading 010A0000 (41%) Downloading 010B0000 (45%) Downloading 010C0000 (49%) Downloading 010D0000 (53%) Downloading 010E0000 (58%) Downloading 010F0000 (62%) Downloading 01100000 (66%) Downloading 01110000 (70%) Downloading 01120000 (74%) Downloading 01130000 (78%) Downloading 01140000 (82%) Downloading 01150000 (87%) Downloading 01160000 (91%) Downloading 01170000 (95%) Downloading 01180000 (99%) Downloaded 1543KB in 19.2s (80.3KB/s)  Verifying 01000000 ( 0%) Verify failed between address 0x1000000 and 0x100FFFF Leaving target processor paused    what is the case?how to solve it?

[Altera_Forum]

Hello! 

 Did you also try to upload the kernel with the Flash Programmer? You find this tool in the Nios IDE in menu Tools.   Bye, Lothar.

[Altera_Forum]

Please read again the instructions. You cannot upload it by " run". 

In your NIOS IDE:  look in your kernel build project for vmlinux.bin. Highlight this file and press right mouse button. A menu pops up. From this menu choose >Upload<

[Altera_Forum]

I choose "upload" before.but failed. 

it appears such information:  ------------------------------------------------ Microtronix Linux Extensions Version 1.4, Built June 20, 2005 ------------------------------------------------ (note: only Altera-provided flash components will work, since install.ptf was not found. This will probably be fine for you.) The flash programmer has been updated. Please see the documentation for instructions on how to update your command line.  The flash programmer has been updated. Please see the documentation for instructions on how to update your command line.  usage: nios2-flash-programmer [-h/--help] [-c/--cable <cable name>]  [-d/--device <device index>] [-i/--instance <instance>]  [-s/--sidp <address>] [-I/--id <id>] [-t/--timestamp <timestamp>]  -b/--base <address> [-e/--epcs]  <action> [-g/--go]  actions can be either:   [--erase-all | --erase <bytes>] [--no-keep-nearby] [--verify] <file>*  --read <filename> [--read-bytes <start>+<size>]   -h/--help Print this message  -Q/--quiet Don&#39;t print anything if everything works  --debug Print debug information   -c/--cable <cable name> Specifies which JTAG cable to use (not needed if  you only have one cable)  -d/--device <device index> Specifies in which device you want to look for the  Nios II debug core (1 = device nearest TDI etc.)  -i/--instance <instance> Specifies the INSTANCE value of the debug core  (not needed if there is exactly one on the chain)   -s/--sidp <address> Base-address of System ID peripheral on target  -I/--id <system-id-value> Unique ID code for target system  -t/--timestamp <time-stamp> Timestamp for target-system (when last generated)  --accept-bad-sysid Continue even if the system ID comparison fails   -b/--base <address> Base address of FLASH/EPCS to operate on  -e/--epcs This operation is on an EPCS flash  -E/--erase <start>+<size> Erase a range of bytes in the flash, or the entire  --erase-all flash before/instead of programming it.  -P/--program Program flash from the input files (the default)  --no-keep-nearby Don&#39;t preserve bytes which need to be erased but  which aren&#39;t specified in the input file  -Y/--verify Verify that contents of flash match input files  <filename>* The names of the file(s) to program or verify   -R/--read <file> Read flash contents into file  -B/--read-bytes <start>+<size> Specify which bytes to read   -g/--go Run processor from reset vector after program.  Input files should be in Motorola S-Record format. Addresses within the files are interpreted as offsets from the base address of the flash. Output files written by the tool are in the same format.  The flash programmer supports all CFI flashes which use the AMD programming algorithm (CFI algorithm 2) or the Intel algorithm (1 or 3).      what&#39;s the problem?who can tell me? thanks.