|
I think rather this is a problem in the linker.cmd file you have. For me
it indicates the memory overrun, but I have defined an own region in the linker command file and it works this way. (But with dynamic assignment this feautre doesn't work.) Georg Bende Softwareentwickler Abteilung Elektronik Dr. Fritz Faulhaber GmbH & Co KG Daimlerstr. 23 71101 Schaich Tel: +49 7031 638294 > -----Ursprgliche Nachricht----- > Von: Pete Becher [mailto:] > Gesendet: Mittwoch, 4. Februar 2004 15:43 > An: > Betreff: [motoroladsp] Re: DSP56F827: Flash to RAM copy - > Compiler Overflow w/o Error? > Hi Boaz, > > Yes this is a problem in CodeWarrior. It does not flag any memory > overruns. The problem is still in version 5.1 and I have not seen > any indication that it has been fixed in version 6.0. I had > contacted tech support about this problem a while back. Maybe > someone from Metrowerks can confirm whether or not this is fixed or > will be fixed. > > Pete > --- In , "bmbmz123" <boaz_b@m...> wrote: > > Hi all, > > I've come across a problem. > > > > The sw has some constant data, which is copied after reset from > > pflash to RAM, as one big block - the data is mirrored to RAM. > > > > It seems that the this constant data block is placed after the sw > in > > pflash. > > > > Now, that the sw is large, and there are many constants, it looks > > that the constant data block has overflowed the pflash boundry! > > > > I came across this when some constant data was bad. > > As I check with the debugger, I saw that some data was ok, up to a > > point, and from that address on, there was bad constant data. > > > > I looked at the MAP file, and measured that constant data block > after > > the last sw routine address, and it is overflowed!! > > > > Why didn't the compiler shout an error? > > Has anyone seen this before? > > > > As the '827 has another pflash2 memory, will the compiler know to > > place an even larger sw in the two pflas sections? > > > > I'm using CW ver 4.1 (a bit old, I know!) > > > > boaz > _____________________________________ > Note: If you do a simple "reply" with your email client, only > the author of this message will receive your answer. You > need to do a "reply all" if you want your answer to be > distributed to the entire group. > > _____________________________________ > About this discussion group: > > To Join: > > To Post: > > To Leave: > > Archives: http://www.yahoogroups.com/group/motoroladsp > > More Groups: http://www.dsprelated.com/groups.php3 > |
|
|
AW: Re: DSP56F827: Flash to RAM copy - Compiler Overflow w/o Error?
Started by ●February 4, 2004
Reply by ●February 4, 20042004-02-04
|
Hi Georg, How does the part you defined work? I do not have any dynamic assignments. I pretty much use the default linker.cmd file. All the IDE linkers I have used in the past automatically check for and flag memory overruns. Pete At 04:04 PM 2/4/2004 +0100, Bende Georg wrote: >I think rather this is a problem in the linker.cmd file you have. For me it indicates the memory overrun, but I have defined an own region in the linker command file and it works this way. (But with dynamic assignment this feautre doesn't work.) > >Georg Bende >Softwareentwickler >Abteilung Elektronik >Dr. Fritz Faulhaber GmbH & Co KG >Daimlerstr. 23 >71101 Schaich >Tel: +49 7031 638294 >> -----Ursprgliche Nachricht----- >> Von: Pete Becher [mailto:] >> Gesendet: Mittwoch, 4. Februar 2004 15:43 >> An: >> Betreff: [motoroladsp] Re: DSP56F827: Flash to RAM copy - >> Compiler Overflow w/o Error? >> >> >> Hi Boaz, >> >> Yes this is a problem in CodeWarrior. It does not flag any memory >> overruns. The problem is still in version 5.1 and I have not seen >> any indication that it has been fixed in version 6.0. I had >> contacted tech support about this problem a while back. Maybe >> someone from Metrowerks can confirm whether or not this is fixed or >> will be fixed. >> >> Pete >> >> >> --- In , "bmbmz123" <boaz_b@m...> wrote: >> > Hi all, >> > I've come across a problem. >> > >> > The sw has some constant data, which is copied after reset from >> > pflash to RAM, as one big block - the data is mirrored to RAM. >> > >> > It seems that the this constant data block is placed after the sw >> in >> > pflash. >> > >> > Now, that the sw is large, and there are many constants, it looks >> > that the constant data block has overflowed the pflash boundry! >> > >> > I came across this when some constant data was bad. >> > As I check with the debugger, I saw that some data was ok, up to a >> > point, and from that address on, there was bad constant data. >> > >> > I looked at the MAP file, and measured that constant data block >> after >> > the last sw routine address, and it is overflowed!! >> > >> > Why didn't the compiler shout an error? >> > Has anyone seen this before? >> > >> > As the '827 has another pflash2 memory, will the compiler know to >> > place an even larger sw in the two pflas sections? >> > >> > I'm using CW ver 4.1 (a bit old, I know!) >> > >> > boaz >> >> >> _____________________________________ >> Note: If you do a simple "reply" with your email client, only >> the author of this message will receive your answer. You >> need to do a "reply all" if you want your answer to be >> distributed to the entire group. >> >> _____________________________________ >> About this discussion group: >> >> To Join: >> >> To Post: >> >> To Leave: >> >> Archives: http://www.yahoogroups.com/group/motoroladsp >> >> More Groups: http://www.dsprelated.com/groups.php3 >> >> >> >> >> >> > |
