ICD BDM, gdb, and error 613 on 68331

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

> 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