Re: PB555 and Codewarrior

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 --------------------~--> 
Most low income households are not online. Help bridge the digital divide today!
http://us.click.yahoo.com/cd_AJB/QnQLAA/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/