I added the EJTAG stuff, what is does is simply to return to the place where
the EJTAG break point was taken. It doesn't do anything, but simply report
that a EJTAG exception has been taken and then returns.
The EJTAG handler has been added to avoid user application, such as crashme,
will crash the kernel.
I don't think there are anything wrong with the handler, except that you
need the fix that Tommy suggest if you are linking your code to address
0x80000000, which only very few does.
I believe this has been reported before, so I actually thought it was fixed.
"Kevin D. Kissell" wrote:
> I don't know who checked in the EJTAG vector stuff,
> but a few words of explanation and advice are in order.
> MIPS32/MIPS64 CPUs have optional support for
> EJTAG, which introduces a "Debug" mode of
> execution which is similar to, but not identical to,
> Kernel mode. The only way into Debug mode is
> to take a Debug exception - not to be confused with
> a breakpoint or watchpoint exception. These are
> caused either by EJTAG hardware breakpoints
> being hit, or by an external assertion on the EJTAG
> interface. When the CPU enters Debug mode, it
> transfers either to a location in the EJTAG pseudo
> memory (an overlay of high physical memory that
> maps to packet transactions on the JTAG interface)
> or to the boot ROM vector area. They can never
> vector directly to the 0x80000000 page!
> Now, since the hardware breakpoint channels are
> potentially a cool feature to be able to exploit from
> an OS - they allow breakpoints in ROM code, for
> example - I once prototyped and debugged the necessary
> code in OpenBSD to allow the kernel to be invoked
> from a Debug exception, and to allow the kernel to
> "call down" into the Debug mode code to set breakpoints,
> etc.. To do this, one *must* have support in the boot
> ROM of the platform. The boot ROM exception vector
> can take advantage of the EJTAG scratch register to
> save enough context to transfer control, intact, to
> a pseudo-vector in the OS vector page (one of those
> rare occasions where the jump delay slot is a lifesaver).
> The location of that pseudo-vector is purely a software
> convention, and should be chosen to be beyond *any*
> hardware vectors, including those for the MIPS32/64
> and Nevada dedicated hardware interrupt vectors.
> I've been meaning for some time now to re-implement
> the OpenBSD EJTAG hooks in Linux, but have simply
> never had the time. It sounds like someone else has
> started down that path without having looked at all the
> issues. I'll try to dig out my old example ROM vector code
> and post it to the newsgroup (it's only a few lines), along
> with the EJTAG kernel interface code from OpenBSD
> to serve as an example.
> Kevin K.
> ----- Original Message -----
> From: "Tommy S. Christensen" <email@example.com>
> To: <firstname.lastname@example.org>
> Sent: Wednesday, May 16, 2001 12:11 AM
> Subject: Exception handlers get overwritten
> > With LOADADDR set to 0x80000000, except_vec0_r4600 and
> > except_vec0_nevada are overwritten in trap_init() before they
> > get installed at KSEG0.
> > The fix is easy:
> > diff -u -r1.53 traps.c
> > --- arch/mips/kernel/traps.c 2001/04/08 13:24:27 1.53
> > +++ arch/mips/kernel/traps.c 2001/05/15 21:39:56
> > @@ -837,7 +837,9 @@
> > * Copy the EJTAG debug exception vector handler code to it's
> > final
> > * destination.
> > */
> > +#ifdef WHONEEDSTLB
> > memcpy((void *)(KSEG0 + 0x300), &except_vec_ejtag_debug, 0x80);
> > +#endif
> > /*
> > * Only some CPUs have the watch exceptions or a dedicated
> > OK, a kinder fix would be something like:
> > diff -u -r1.25 head.S
> > --- arch/mips/kernel/head.S 2001/05/04 20:43:25 1.25
> > +++ arch/mips/kernel/head.S 2001/05/15 21:39:40
> > @@ -44,7 +44,7 @@
> > * FIXME: Use the initcode feature to get rid of unused handler
> > * variants.
> > */
> > - .fill 0x280
> > + .fill 0x380
> > /*
> > * This is space for the interrupt handlers.
> > * After trap_init() they are located at virtual address KSEG0.
> > I wonder why this never hit anybody else ...
> > Regards,
> > Tommy Christensen
_ _ ____ ___ Carsten Langgaard Mailto:email@example.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556