Re: [coldfire-gnu-discuss] Using m68k-elf-cfpe-stub with our own board
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldfire-gnu-discuss] Using m68k-elf-cfpe-stub with our own board
- To: David Brown <david@xxxxxxxxxxxxxxx>
- Subject: Re: [coldfire-gnu-discuss] Using m68k-elf-cfpe-stub with our own board
- From: Nathan Sidwell <nathan@xxxxxxxxxxxxxxxx>
- Date: Wed, 15 Nov 2006 13:22:42 +0000
It turns out that you can get the Code Worrier user's guide from without
downloading the whole lot, from:
http://www.freescale.com/files/soft_dev_tools/doc/user_guide/COLDFIREUG.pdf
Glad you found that. We were unable to get permission to distribute those
config files.
Our upcoming update to the tools has implemented a much better xml based
initialization scheme, which we have fully documented. It specifies both board
initialization and board memory maps.
I'd still like to know how to change cpu-space registers from with gdb,
if anyone has any ideas - for some processors, it is important to be
able to do things like turn caching on and off while debugging.
This is not possible with the current gdb -- the bdm.sourceforge.net patches
have not been contributed to FSF gdb. That said, control register access from
gdb is on our todo list, but won't be available in the near term.
In the meantime you could include a function of the form
void set_cache_debug (unsigned v) {
__asm__ __volatile__ ("movec.l %0,%/cacr" :: "r" (v) : "memory");
}
in your application and use it from gdb with
(gdb) call set_cache_debug(0xWHATEVER)
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery
nathan@xxxxxxxxxxxxxxxx :: http://www.planetfall.pwp.blueyonder.co.uk