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 am trying to run Mode 0B on a DSP56F807 and not having much luck.  Has anyone else tried
that?

I am using CW 5.1 and SDK.  My program runs just fine in Mode 0A but freaks out (basically does
not boot properly) in Mode 0B.  So you wonder why I want to run Mode 0B then?  It's a long
story.

My program fits in the lower 32k of pFLASH (0x0004 to 0x6FF) and I think I have changed the
linker.cmd properly but am not sure.  The problem I see is, how does the program know that the
pRAM has been remapped to the lower 32k of memory when switching to Mode 0B.  The only thing I
see that goes into pRAM is the data from paramdata.c which looks like stuff the Interrupt
Dispatcher uses.  I use both Normal and SuperFast interrupts.

Any thoughts?

Thanks,
Pete
	

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