Re: Stopped by unknown trap/breakpoint

Ok, I've got most of the problems solved.

The solution to the `sc' instruction was to set in the target (GHS Probe):

target set step trace
target set swbp_type trap

In addition, to get successful stepping over functions and source
lines, the following variables have to be set within the linker file:
 
You will need to use your own labels.

You can also create a wizard project for a ROM target and copy the
linker settings from there.

#############################################################################################################
#   REQUIRED FOR GHS DEBUGGER
#############################################################################################################

// These special symbols mark the bounds of RAM and ROM memory.
// They are used by the MULTI debugger.
//

    __ghs_ramstart  = ADDR(.startofRAM);
    __ghs_ramend    = ADDR(.endofRAM);
    __ghs_romstart  = ADDR(.startofflash);
    __ghs_romend    = ADDR(.endofflash);

 

//
// These special symbols mark the bounds of RAM and ROM images of boot
code.
// They are used by the GHS startup code (_start and __ghs_ind_crt0).
//

    __ghs_rambootcodestart  = 0;
    __ghs_rambootcodeend    = 0;
    __ghs_rombootcodestart  = 0;
    __ghs_rombootcodeend    = MEMENDADDR(FLASH);


John


--- In [email protected], "John Davey" <ewlie@...> wrote:
>
> Hi Folks,
> 
> I'm in the process of getting GreenHills Probe to work with our MPC5xx
> modules, and I'm getting stuck on an 'sc' syscall asm instruction
> within the code.  It reports "Stopped by unknown trap/breakpoint"
> 
> Here are my settings:
> 
> - MPC565 processor on Engine Controller. (Also tried on one of our
> MPC555 Modules)
> 
> - The tick box "Service System Calls" clear in the connection dialog,
> and I've also manually issued the command "target syscalls off"
> 
> - The module and code is good, because without debugger it runs as
> expected.
> 
> - I can debug, step and run using VisionClick with VisionProbe
> debugger.  (My task is to upgrade us to the GHS probe)
> 
> - I use the same initial register setup with GHS as I did for
> VisionClick (setting chip selects, IMMR etc)
> 
> With GHS probe and MULTI, the system will never let me step or run
> past this 'sc' point.
> 
> Has anyone else experienced something similar?
> 
> Is there a solution I can try?
> 
> Thanks
> 
> John Davey
>