This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: ICD BDM, gdb, and error 613 on 68331

To: wzielins at kki dot net dot pl (Wojtek Zielinski)
Subject: Re: ICD BDM, gdb, and error 613 on 68331
From: Josef Wolf <jw at raven dot inka dot de>
Date: Sun, 14 Nov 1999 11:47:44 +0100 (MET)
Cc: qqi at world dot std dot com, aaron at frye dot com, crossgcc at sourceware dot cygnus dot com


> I have just read your mail. I'm working now on setting up the environment
> for developing 68332 system and I have the same problems. I'm struggling
> with that for about month. The only difference is that I use PD cable. Under
> DOS everything works fine, also bdmv ported to Linux works great.
> But my bdm.o module with gdb works erroneous in the same manner you
> described. Even the address is the same (0xfffa00). I tried to initialize
> it through file cpu32init. I analyzed logs of gdb (gdb-bdm.log) and
> bdm.o module and the problem is in verifying read operation after
> write operation (see bdmlib.c file in gdb bdm patch).

The interface from the kernel to device drivers has changed several
times. Just take a look at k_compat.h in the bdm-sources. The problem
is that k_compat.h is not very accurate :-(


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

References:
- Re: ICD BDM, gdb, and error 613 on 68331
  - From: Wojtek Zielinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]