Re: PB555 and Codewarrior

No doubt you still have references somewhere to non-existent (i.e. 
external) memory areas from the CME-555 example.
Go through the linker file again, and understand the memory-map of a 
single-chip MPC555. Everything HAS to be in the memory range 0x3F9800 
to 0x38FFFF or it won't work. Then, check the CW target settings for 
your project and make sure again that the stack, heap etc. are in the 
valid memory range.
Just to let you know that it's possible I routinely build PB-0555 
projects that operate entirely out of the internal SRAM, including 
the area 0x3f9800 -> 0x3fa000, even though the Axiom documentation 
claims that area for their monitor.
Ian


--- In [email protected], "coles555" <coles555@y...> wrote:
> Hi Ian,
> Thanks so much for your help, I got the FPU Buffer to be in the 
right 
> place. However, I still get another error "Program Exception" on 
this 
> line of code:
>  
> /*	PowerPC EABI init registers (stack, small data areas)
> */
> 	bl		__init_registers
> 
> I am guessing this line of code initializes the registers/stacks. 
Do 
> you know how I can fix this?
> 
> Please advise!
> Lei
> 
> 
> --- In [email protected], "murphynetuk" <murphynetuk@y...> 
wrote:
> > 0x003fff00 works for this location with the PB555.
> > To alter it, for P&E debugger, (also MSI Wiggler I think)
> > 
> > 1. Launch CodeWarrior IDE 
> >    from the Start->Programs->Metrowerks CodeWarrior menu
> > 2. Open IDE Preferences dialog window using Edit->Preferences...
> > 3. Choose Remote Connections under IDE Preference Panel->Debugger
> > 4. Select Debugger "P&E BDM" and click 'Change...'
> > 6. Choose Connection Type as Parallel
> > 7. Choose Parallel Port, e.g. LPT1
> > 8. Set IO Delay Count to 0
> > 9. Set FPU Buffer Address to 0x003fff00
> > 10. Click OK to finish
> > 
> > Ian
> > 
> > --- In [email protected], "coles555" <coles555@y...> wrote:
> > > Hi Randy,
> > > If I understand you correctly, the warning I am receiving is 
due 
> to 
> > > the scratchpad area that is needed by the debugger and the 
> default 
> > > scratchpad area starts in 0x00C00000, which, according to the 
CME 
> > > manual, is the External Flash Memory for the CME board. Does 
this 
> > > mean I need to modify the linker code so that the scratchpad 
area 
> > can 
> > > be moved to on-chip internal SRAM? Is this the only 
modification 
> I 
> > > need to make in Codewarrior for the PB to work?
> > > 
> > > Please advise and thank you for responding to my question!
> > > Lei
> > > 
> > > --- In [email protected], Dees Randy-rsaf30 
> <randy.dees@f...> 
> > > wrote:
> > > > linker files usually must be modified for any board specific 
> > > details such as areas of memory that are ROM (or Flash) and 
SRAM.
> > > >  
> > > > the PB board does not have any external memory. the linker 
file 
> > > usually must be modified for this.
> > > >  
> > > > The Floating Point Unit (FPU) registers can only be moved 
from 
> > the 
> > > floating point register directly to memory. in order for the 
> > debugger 
> > > to read a floating point register is to transfer it to memory 
and 
> > > then read it from memory into a general purpose register, it 
can 
> > then 
> > > display the 64-bit value by reading the 32-bit registers. the 
> > > CodeWarrior debugger requires a scratch pad area in RAM to be 
> able 
> > to 
> > > read the Floating Point registers. They save the current values 
> of 
> > > the SRAM, read the FPU registers, and then put the original 
> > contents 
> > > back into the SRAM. Therefore, you must define in the debugger 
an 
> > > area of SRAM in the target system that the debugger can use.  
> > > >  
> > > > One minor issue is that CodeWarrior always assumes that you 
> have 
> > > external SRAM at location 0x00C0_0000 that it can use for this 
> > > scratchpad area.
> > > >  
> > > > randy 
> > > > 
> > > > -----Original Message-----
> > > > From: [email protected] [mailto:[email protected]] 
On 
> > > Behalf Of coles555
> > > > 
> > > > 
> > > > Thank you so much for the help Ian. I was wondering if you 
> could 
> > be 
> > > > more specific about the linker file, is that the 
> > 5xx_Axiom_ROM.lcf 
> > > > file? There are some address declarations within that file. 
Do 
> > you 
> > > know 
> > > > of any other parameters I need to change for Codewarrior to 
> work 
> > > with 
> > > > the PB board? If you are not sure or can't be more specific, 
> can 
> > > you 
> > > > direct me to another source for this kind of information? Do 
> you 
> > > think 
> > > > emailing Metrowerks or Axiom would help?
> > > > 
> > > > I'm not sure if this is something important but I do get a 
> > warning 
> > > in 
> > > > Codewarrior saying that "0x00c00000 is invalid for FPU buffer"
> > > > 
> > > > 
> > > > 
> > > > [Non-text portions of this message have been removed]




------------------------ Yahoo! Groups Sponsor --------------------~--> 
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/dN_tlB/TM
--------------------------------------------------------------------~-> 

-----------------------------------------------------------
To learn more about Freescale Microcontrollers, please visit
http://www.freescale.com/mcu


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/MPC500/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/