Hi all, I&#39;m trying to allocate a buffer in SDRAM using the declaration: volatile int buff1_app[1280] __attribute__((section(".SDRAM"))); in SOPC i&#39;ve defined a SDRAM controller named "sdram". I&#39;ve set the reset address of my system in flash, exception address,program and data memory resides in SDRAM. When i compile i receive the error message: *** [ext_flash.flash] Error 5 H320_prove Error 5-mag-2005 12.29.36 - * *** [ext_flash.flash] Error 5 Boot copier overlaps data in flash H320_prove line 0 Error 5-mag-2005 12.29.36 - * Boot copier overlaps data in flash Error generating Flash file, exiting H320_prove line 0 if i define the buffer: volatile int buff1_app[1280] ; everything works fine. Any suggestion?

I&#39;d expect to see this error if you had (for example) left your .rodata in flash while your .text sections was in sdram. Check your system library properties are really set correctly. Also, the tools are case sensitive, so if you have named your memory sdram then you should assign your data to ".sdram" not ".SDRAM".

Hi monkeyboy, if I use lowcase: volatile int buff1_app[1280] __attribute__((section(".sdram"))); I have no compilation error. I download my code in flash, power on the board, the program boots but, after some printf, it stops its execution. If i declare my buffer: volatile int buff1_app[1280]; everything works. What&#39;s the difference between the two declarations? In my system library properties i have program data,read only data, read\write data in sdram. thanks

Soin, Are your SDRAM signals shared on avalon tri-state bus? I also had a problem with hanging CPU ... see topic: cpu hangs after sdram-refresh (http://www.niosforum.com/forum/index.php?act=st&f=2&t=1038&hl=) This behaviour should be resolved with Quartus/NIOSII 5.0. Your section name depends on what you&#39;ve entered in SOPC builder as device name. Mike

Hi MIR, I&#39;ve read your old topic but I&#39;m not sure it&#39;s my case. My SDRAM signals are not shared on avalon tri-state bus, with other peripheral: I have the SDRAM controller component, whose signals are connected only with my SDRAM. In particular my design has two CPUs, and each one can access SDRAM. Any ideas?

Probably a stupid question, on my part, but do you have a Mutex to avoid SDRAM access collisions? - slacker

"__attribute__((section(".SDRAM")))" problem

14 Replies

Altera_Forum
Honored Contributor
20 years ago
I've verified a strange behaviour: if i download my code (with "attribute") in SDRAM, it works;instead if i download my code in flash and than boot, it doesn't work.
Altera_Forum
Honored Contributor
20 years ago
One possible explanation is that in your application code you are over running the end of buff1_app, or have some other kind of memory over write. If this was the case then the changes in memory organisation could cause the otherwise apparently harmless over write to cause a problem.

However that doesn't tie with it working on JTAG download, but not when booting from flash. If it only fails on boot from flash, then that would suggest the problem is related to how the bootloader loads the code.

Could this be a cache coherency problem? Do you have any cache in your system? If so, try disabling the caches and see if that changes the behaviour.
Altera_Forum
Honored Contributor
20 years ago
I usually get a similar error when I try to use the attribute compiler flag, putting in a section name that does not exist.

for example, writing

<div class='quotetop'>QUOTE </div>
--- Quote Start ---
volatile int my_shared_data __attribute__ ((section (".fake")));;[/b]
--- Quote End ---

gives me the following error:

<div class='quotetop'>QUOTE </div>
--- Quote Start ---
16-mag-2005 12.26.47 - (GRAVE) elf2flash: Boot copier overlaps data in flash
16-mag-2005 12.26.48 - (GRAVE) elf2flash: Error generating Flash file, exiting[/b]
--- Quote End ---
Altera_Forum
Honored Contributor
20 years ago
yes..u r right: infact i used ".SDRAM" instead of ".sdram"...

Forum Discussion

"attribute((section(".SDRAM")))" problem

14 Replies

Recent Discussions

JTAG_UART stuck in printf

NIOS SDK SBOM/FOSS info

NiosV µC/OS-II

Recommended Quartus Prime Standard Edition for Nios V Development on MAX 10 FPGA (10M25DAF4817G)

AshlingRISCFree IDE Build system: 'source directory does not appear to contain CMakeLists.txt"