Verify failed between address 0x80000 and 0x8FFFF

[harishac]

Hello,

I've been attempting to basically run through the mem_test template an
tutorial,on CycloneÂŽ III EP3C120 chip board.

I am able to compile the custom SOPC design, the encompassing Quartus file
download the SRAM Object File .sof to the board correctly, create th
Application from BSP and Template, and even build the file in NIOS II wit
no errors. The problem comes about when I attempt to run the system; th
.elf downloads in its entirety , but then fails during verification.


Verifying 08000000 ( 0%)
Verify failed between address 0x80000 and 0x08FFFF
Leaving target processor paused.




---------------------------------------
Posted through http://www.FPGARelated.com

 

[Górski Adam]

Hello,

Do you have system ID included in your SOPC design ?

Adam

Hello,

I've been attempting to basically run through the mem_test template and
tutorial,on CycloneÂŽ III EP3C120 chip board.

I am able to compile the custom SOPC design, the encompassing Quartus file,
download the SRAM Object File .sof to the board correctly, create the
Application from BSP and Template, and even build the file in NIOS II with
no errors. The problem comes about when I attempt to run the system; the
elf downloads in its entirety , but then fails during verification.


Verifying 08000000 ( 0%)
Verify failed between address 0x80000 and 0x08FFFF
Leaving target processor paused.




---------------------------------------
Posted through http://www.FPGARelated.com

 

[carlob]

Hi,
No idea about sysid...but you can investigate it...anyway there is a men
in EDS to say that is not needed to check it ...to avoid any problem wit
sysid...

In my experience, if I remember well, I've seen this happening only whe
ram is not working properly...let me suppose...0x80000 is a ram addres
where your application is linked to???

Usually you link an application to start from base address of a "ram
inside your system...but before starting the processor the tools check wha
you have downloaded....
Is the link address correct?? Is the ram working??? If you have, actually
any problem with ram...insert an onchip ram in your design...build th
memtest small template that comes with eds and check external ram for rea
problems...

Carlo

Hello,

I've been attempting to basically run through the mem_test template and
tutorial,on CycloneÂŽ III EP3C120 chip board.

I am able to compile the custom SOPC design, the encompassing Quartu
file,
download the SRAM Object File .sof to the board correctly, create the
Application from BSP and Template, and even build the file in NIOS I
with
no errors. The problem comes about when I attempt to run the system; the
.elf downloads in its entirety , but then fails during verification.


Verifying 08000000 ( 0%)
Verify failed between address 0x80000 and 0x08FFFF
Leaving target processor paused.




---------------------------------------
Posted through http://www.FPGARelated.com

---------------------------------------
Posted through http://www.FPGARelated.com

 

[Simon]

On May 24, 2:19 pm, "carlob"
<carlo.beccia@n_o_s_p_a_m.n_o_s_p_a_m.libero.it> wrote:

Hi,
No idea about sysid...but you can investigate it...anyway there is a menu
in EDS to say that is not needed to check it ...to avoid any problem with
sysid...

In my experience, if I remember well, I've seen this happening only when
ram is not working properly...let me suppose...0x80000 is a ram address
where your application is linked to???

Usually you link an application to start from base address of a "ram"
inside your system...but before starting the processor the tools check what
you have downloaded....
Is the link address correct?? Is the ram working??? If you have, actually,
any problem with ram...insert an onchip ram in your design...build the
memtest small template that comes with eds and check external ram for real
problems...

Carlo

Not sure about the board you're using, but on my DE0 board, the code
defaults to going into the largest RAM section (which of course is the
SDRAM). So, if you're testing from 0x800000, you'll be overwriting the
code itself. The memtest.c that comes with Quartus 10.1 allows you to
specify a start and end address to test, so I was using 0x820000 to
0xf00000. Note that the top-end of ram is used for the stack, so you
need to not overwrite part of that too.

If you need to test all your ram, you'll need to set up an 8k+ on-chip
RAM, and edit your BSP's linker-script to place the code in the
smaller on-chip RAM. Then you'll have all the SDRAM to play with.

Simon

 

[Górski Adam]

Hi,
No idea about sysid...but you can investigate it...anyway there is a menu
in EDS to say that is not needed to check it ...to avoid any problem with
sysid...

In my experience, if I remember well, I've seen this happening only when
ram is not working properly...let me suppose...0x80000 is a ram address
where your application is linked to???

Usually you link an application to start from base address of a "ram"
inside your system...but before starting the processor the tools check what
you have downloaded....
Is the link address correct?? Is the ram working??? If you have, actually,
any problem with ram...insert an onchip ram in your design...build the
memtest small template that comes with eds and check external ram for real
problems...

Carlo

Hello,

I've been attempting to basically run through the mem_test template and
tutorial,on CycloneÂŽ III EP3C120 chip board.

I am able to compile the custom SOPC design, the encompassing Quartus
file,
download the SRAM Object File .sof to the board correctly, create the
Application from BSP and Template, and even build the file in NIOS II
with
no errors. The problem comes about when I attempt to run the system; the
.elf downloads in its entirety , but then fails during verification.


Verifying 08000000 ( 0%)
Verify failed between address 0x80000 and 0x08FFFF
Leaving target processor paused.

I had similar problem once. Even with "don't check sysid" feature
marked, I couldn't download app.
As I remember with Q10.0 or similar.
What is located in this area from hardware side ? Program ram, flash , IO ?

Adam

 

[carlob]

I had similar problem once. Even with "don't check sysid" feature
marked, I couldn't download app.

Uhmmm..strange...10.0 bug???

As I remember with Q10.0 or similar.
What is located in this area from hardware side ? Program ram, flash , I
?

Adam

This is the best question...what is starting from 0x80000 and where do yo
link your sw...said in other way...which address your software start
from??
As somebody suggested...you cannot test a piece of ram where you ar
running your test code...pay attention....

Anyway in my opinion this is not the case....eds is not able to downloa
correctly the code...if this is not related to sysid (I never experimente
that problem so I cannot say) it should be related to memory problems o
link address problems...check it..

If you are using a demo board with a standard project..I tend to exclud
ram problems...the board and the netlist have been already checked befor
selling ...if you are using custom hw...ram could not be working...if yo
are using custom project..check againg your .sopc and, eventually, timin
constraints for the ram...that can be the problem...

Carlo

---------------------------------------
Posted through http://www.FPGARelated.com

 

[Simon]

On May 25, 2:10 pm, "carlob"
<carlo.beccia@n_o_s_p_a_m.n_o_s_p_a_m.libero.it> wrote:

I had similar problem once. Even with "don't check sysid" feature
marked, I couldn't download app.

Uhmmm..strange...10.0 bug???

I ran into this myself earlier today while I was trying to debug DMA.
The problem (in my case) was that I'd forgotten to include the PLL
that offsets the SDRAM (off-chip) clock from the cpu (on-chip) clock.
The SDRAM would work intermittently, sometimes the download would
succeed, sometimes it would fail.

Adding the PLL solved this for me, although it didn't help me get DMA
working I had to jump to Quartus2 v11 to get the DMA to
successfully transfer data - what appeared to be the same design in
10.1 didn't work for me.

Simon