Re: Help with building gdb with BDM support for the Coldfire

X-SpamDetect-Info: ------------- Start ASpam results ---------------
X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information 
X-SpamDetect: *****: 5.400000 From3consonants=0.3, DodgySource=2.0, SPF Default Fail=2.5, X-Verify-SMTP present=0.6
X-SpamDetect-Info: ------------- End ASpam results -----------------

Mark Giacobbe wrote:
> Using the attached script, although I am still testing, it seems that my 
> debugging system is working.  My memory issues are gone, and I can 
> access the correct memory locations, with the correct access sizes.
> 
> I had to add the
>     monitor bdm-ctl-set
> command for the mbar and rambar addresses.  The old way of "set $mbar" 
> did not work with the new gdbserver.
> 
> Later this week, or beginning of next week, I will download CoLiLo to my 
> target and see if it works.  I will then test the breakpoints, watches, etc.
> 

I have fixed the register cache so this problem should not exist any more. The 
monitor register control commands and GDB should be in sync. The changes are 
in CVS and I have made a snapshot which you can find here:

   http://www.rtems.org/ftp/pub/rtems/people/chrisj/bdm/

Please download, test and let me know how it goes.

I have also added support for the 52223 (52235) processor. Thanks to Matthew 
Riek for some help and testing of this code.

The snapshot also includes a reworked hardware break and watch point support. 
The 52223 is a debug version B+ and has 4 hardware break points and an address 
breakpoint. I have added a -B option to the GDB server which should help debug 
code in flash automatically.

Regards
Chris

---
[email protected]              Send a post to the list.
[email protected]        Join the list.
[email protected]    Join the list in digest mode.
[email protected]     Leave the list.