Hi,

I am having a problem running a program from flash memory on the=20=20
DSK5510 and I was hoping someone could give me a pointer (no pun=20=20
intended - really) as to what I might be doing wrong. I am using the=20=20
eDSP DSKAudio4 4-channel audio daughterboard for audio I/O and Code=20=20
Composer 3.2 with DSP/BIOS.

My problem is that the exact same compilation of my software works=20=20
fine when run in Code Composer with the built-in USB emulator, but=20=20
does not work when run from the DSK's flash memory. Flashburn runs and=20=20
verifies. The DSK boots from flash, but freezes when accessing arrays=20=20
in the SDRAM.

My program works perfectly fine when loaded and run through Code=20=20
Composer and the built-in USB emulator, but freezes whenever it=20=20
accesses the DSK's onboard SDRAM when running booted from the flash.=20=20
Oddly, the same program also runs perfectly from the flash when the=20=20
built-in USB emulator is connected to Code Composer and the 'run'=20=20
button is pressed WITHOUT loading a program through the emulator (code=20=20
composer even warns me about this) - it is as if connecting the=20=20
emulator does/sets/resets something that does not get set/reset when=20=20
the DSK boots from the flash. But I can't figure out what it could be!

If I remove all references of the arrays that live in the SDRAM from=20=20
the program, recompile and re-flashburn, it boots and runs correctly=20=20
from flash without a connection to the computer.

Sometimes, when I have had the DSK powered off for a long time, the=20=20
program will initialize the arrays I am placing in the SDRAM correctly=20=20
at first, and will freeze later - when manipulating them. If I press=20=20
RESET or power cycle the DSK quickly, it tends to crash during the=20=20
initialization of the arrays in the SDRAM - which suggests something=20=20
is persisting through resets - but I don't know what.

I can get other software (Compiled in Code Composer 2.2) that accesses=20=20
the SDRAM (though less of it) to run off the flash memory in the DSK=20=20
fine, just not my software (made in CCS 3.2). I have tried modifying=20=20
my software to use the same amount or less of the SDRAM that the other=20=20
software uses, but it did not work.

I am using flashburn DSK 3.11 from
http://www.softwaredesignsolutions.com/flashburn.aspx

I have experimented with many of the hex utility's options,  such as -=20
boot, .SECTIONS, the type of hex file it generates, using image mode,=20=20
and adding boot delays. But nothing worked. I was thinking maybe my=20=20
hex file is too big? It verifies though when I flashburn it.

I thought adding this

EMIF_RSET(EMIRST,0xFFFFu);

might help, but i did not. I also tried putting a loop at the=20=20
beginning of my main() so that the DSP would wait for a while before=20=20
doing anything. That did not help either.
Thanks!
Arvid

=96=96=96
Arvid Tomayko-Peters

WEB: http://arvidtp.net
BAND: http://metropoliscares.com
PHONE: (401) 490-1320
AIM: arvthecarve


______________________________
New Year Gift for Members of DSPRelated.com.  Details here.