Hello all, I use system with two 21061 processors and the VisualDSP++1.0 tools. I have a problem to reference a variable from DSP1 code if it is declared within the internal memory of DSP2. Generated code looks OK, but it does not work in the debugger nor on my system. Problem is similar with the VIRPT interrupt which is not correct (I guess the write operation is not done at the corect address). Even the example provided by AD "FFTON2PE" seems to suffer from the same problem. Has someone experienced that problem before? FD |
|
21061 MP memory reference
Started by ●February 14, 2001
Reply by ●February 14, 20012001-02-14
Hello, Can VDSP++ generate a build date within the makefile or within some other file? Is there a compiler directive or option for this somewhere? I didn't find anything when I looked through the manuals, but I figured maybe someone had stumbled across this or maybe wrote one and could give me some pointers. Basically I'd like to be able to have a file generate a text file with information in it like current date, most recent compile / build date of program, filename, etc, without having to hard code all that in the first place. thanks again :) Tom Hanley |
|
Reply by ●February 14, 20012001-02-14
On Wed, 14 Feb 2001 10:21:44 -0500 (EST), Tom Hanley wrote: > Can VDSP++ generate a build date within the makefile or within > some other file? Is there a compiler directive or option for this > somewhere? I didn't find anything when I looked through the manuals, but > I figured maybe someone had stumbled across this or maybe wrote one and > could give me some pointers. Basically I'd like to be able to have a file > generate a text file with information in it like current date, most recent > compile / build date of program, filename, etc, without having to hard > code all that in the first place. I haven't done this with VDSP++, but I've done it with other compilers. The idea is to use a small source file that simply has: const char version[] = __DATE__ " " __TIME__; Add the line to compile this just before your link command, so it always gets compiled fresh when you link, something like this: foo.dxe: foo.doj ver.c cc21k -c -21065L ver.c linker foo.doj ver.doj |