Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
IP360 and SDS SingleStep
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Markus Krug  
View profile  
 More options Jun 7 1996, 3:00 am
Newsgroups: comp.sys.m68k
From: k...@tunix.vmars.tuwien.ac.at (Markus Krug)
Date: 1996/06/07
Subject: IP360 and SDS SingleStep

Hello,

does anybody use the MicroSys IP360 Board togehter with SDS
SingleStep Debugger ?
What I'm particular interested in is the target initialisation,
because till now I was unable to configure it correctly.
I always get the message 'Unable to initailze stray/reset vector at [address]'
and 'Unable to set breakpoint at [address]'

Could anybody help

Thanks in advance

Markus Krug


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
bsiming  
View profile  
 More options Jun 12 1996, 3:00 am
Newsgroups: comp.sys.m68k
From: bsim...@winternet.com
Date: 1996/06/12
Subject: Re: IP360 and SDS SingleStep

   I believe that the SDS debugger manipulates the contents of the
location pointed at by the VBR for it's breakpoint  control at VBR +
32(??). These are vectors not hard addresses. Also, I believe that the
breakpoint addresses have to be in ram not rom.

So - for the first error message, I believe that you have to do two
things, first include the reserved debug vector in the sstep.ini file, I
believe that it is vector 32. Also, the VBR must be in RAM so the
debugger can modify it.

Second - If the debugger was unable to claim the vector that it needed in
step one, you will not be able to set break points. Also, I believe that
the breakpoints must be for code located in Ram, not rom.

Good luck.

Sorry for being vague, I'm out of the office and I can't check these
things out for accuracy.

bob


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »