Re: Help with building gdb with BDM support for the Coldfire
"Mark Giacobbe" <[email protected]> Thu, 15 May 2008 13:02:10 -0400
| Newsgroups | gmane.comp.hardware.motorola.microcontrollers.coldfire |
|---|---|
| Message-ID | <[email protected]> |
Hi Chris - Did you find anything that I missed? And is there a trick to using cvs for sourceforge? I tried several times, and keep getting: [pcmadm@localhost ~]$ cvs -d:pserver:[email protected]:/cvsroot/bdm login Logging in to :pserver:[email protected]:2401/cvsroot/bdm CVS password: cvs [login aborted]: connect to [bdm.cvs.sourceforge.net]:2401 failed: Connection timed out [pcmadm@localhost ~]$ I hit "ENTER" for the password. Thanks Mark On Wed, May 14, 2008 at 7:25 PM, Chris Johns <[email protected]> wrote: > 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: > >> The observations that I see makes sense. Since none of the registers are >> programmed, cs0 will always respond to any memory access, and cs0 is >> programmed by hardware to always to a 32 bit access. >> >> > Makes sense. > > Here is the patch of my changes. Please look it over and I'm sure I >> forgot to change something. >> > > Committed to CVS on Sourceforge. Please checkout CVS and test. The > ChangeLog is: > > 2008-05-15 Mark Giacobbe <[email protected]> > > * gdbserver/m68k-cf5307.xml: New. > > * gdbserver/Makefile.am: Add m68k-cf5307.xml. > > * gdbserver/m68k-bdm-low.c: Add 5307 support. > > 2008-05-15 Chris Johns <[email protected]> > > * README: Fix the TBLCF documentation. > > Thanks for the patch. > > > 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. > >