56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

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

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

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

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )