.rwdata

You should be able to use a custom linker script to do what you like, with the current rev. of tools that you have. However, I would advocate upgrading to Quartus II 4.2 and Nios II 1.1.....if still possible!

The default linker script is "generated.x", located in the System Library project....post build. Just copy this into the _top_ level of your syslib project, change it's name, and edit where you'd like your code to reside. Then, disable the "use auto-generated linker script" on the syslib properties page and point it at your script, instead.

Note that, for the tools you&#39;re using, stack and heap will always follow .rwdata. There is already a .exceptions section in the linker script. ... All you&#39;d have to do is change it&#39;s > <memory> target. You could also define your own sections and locate them in a memory of your choice... Take a look at

http://www.altera.com/literature/hb/nios2/...n2sw_nii5v2.pdf (http://www.altera.com/literature/hb/nios2/n2sw_nii5v2.pdf)

on page 4-32. That&#39;s only if you&#39;re getting extremely anal about where your code resides, though! :-)

Hope you find this helpful, regardless of which path you decide to take.

Cheers,

- slacker

P.S.: I think support is generally tied to dollars, right? I&#39;ve been on both sides of the vendor/client relationship at startup shops and large companies. All I can say, is that if you&#39;re a small/startup shop, you shouldn&#39;t expect premium support... That being said, this forum should provide most of the info. you need... If you are with a large company with large dollars, I&#39;d expect that you&#39;d be beating Altera&#39;s door down by now :-)