This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Support for PPC405 / PPC440 registers


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I recently tried to debug an embedded IBM PowerPC 405 and 440 over JTAG.
The necessary GDB stub was written by myself (unfortunately using
confidential information, so I won't be able to publish it).

When trying to display the contents of the processor's registers I
noticed only the PPC403 register layout was included in the standard GDB
distribution. As the registers of the different processors in the
4xx-series differ, I tried to modify GDB and BFD to handle the registers
of the additional processors. The following files were changed:

- - bfd/cpu-powerpc: Added definitions for the additional processors in
the struct 'bfd_powerpc_archs'
- - bfd/archures.c: Added processors in 'bfd_architecture'
- - gdb/ppc-tdep.h: Added SPR numbers for new registers
- - gdb/rs6000-tdep.c: Added processors to the struct 'variants' and
created appropriate 'static const struct reg registers_...' entries with
the available registers

After that the registers showed up and could be used after setting the
new processors with "set architecture".

Question 1: What did I destroy by doing this?
Question 2: Would a patch to add support for these processors be useful?
What else should be done before even thinking about doing so?

Thanks,
- --
Ignaz Forster <ignaz.forster@gmx.de>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFGCCzZ/2+SjQTlQJkRArxWAJ4qrRKwQkaD/0qIuPMaYrAT4TxjSwCgkt7i
W99pT7iGjJ49m3BUO76LeRk=
=xvW9
-----END PGP SIGNATURE-----


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