RE: debugging IBM405GP with abatron bdi 2000

[Steven Blakeslee <BlakesleeS@embeddedplanet.com>]

I found a work around that would suggest the opposite.  If I do the
following I can get Linux to boot with an Abatron connected.
1.  Connect the board to the abatron and power up.
2.  Wait for the configuration to complete.
3.  Give the go command, the bootloader now runs.
4.  Give the reset command in the bootloader, this causes a checkstop reset.
A checkstop reset sets most registers to their default values.
5.  The bootloader loads a second time.
6.  Download Linux and boot from bootloader.

This tells me that the abatron is doing some type of initialization other
than the config file.  Whatever it is doing behind the scenes is causing a
problem after the rfi instruction.

-----Original Message-----
From: Chris Hallinan [mailto:clh@net1plus.com]
Sent: Tuesday, August 05, 2003 1:40 PM
To: Steven Blakeslee
Subject: RE: debugging IBM405GP with abatron bdi 2000


It is likely that your kernel is mucking with the debug registers in
the processor core.  This is typically what happens if that is the
case...  Just a thought...

> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On
> Behalf Of Steven
> Blakeslee
> Sent: Tuesday, August 05, 2003 11:53 AM
> To: 'linuxppc-embedded@lists.linuxppc.org'
> Subject: debugging IBM405GP with abatron bdi 2000
>
>
>
> Has anyone used an Abatron BDI 2000 to debug Linux on an IBM 405GP
> processor?  I am using an Embedded Planet ep405 with the latest
> linuxppc_2_4_devel tree.  Linux boots fine on the board
> until I connect the
> Abatron.  When the Abatron is connected I can step
> through the code until
> the rfi command in head_4xx.S then I get the following.
>
> - TARGET: target has entered debug mode
>     Target state      : debug mode
>     Debug entry cause : JTAG stop request
>     Current PC        : 0x00000700
>     Current CR        : 0x28004088
>     Current MSR       : 0x00000000
>     Current LR        : 0x000007a8
> # Step timeout detected
>
>
> Below is the config file I am using.  I would appreciate
> any adive anyone
> can offer.
>
>
> [INIT]
> ;
> WSPR	954	0x00000000	;DCWR: Disable data cache write-thru
> WSPR	1018	0x00000000	;DCCR: Disable data cache
> WSPR	1019	0x00000000	;ICCR: Disable instruction cache
> WSPR	982	0x00000000	;EVPR: Exception Vector
> Table @0x00000000
> ;
> ; Setup TCR (Timer Control Register)
> WSPR	986	0x00400000
> ; Setup MMU info
> WM32    0x000000f0  0x00000000  ;invalidate page table base
> ;
> ;
> [TARGET]
> JTAGCLOCK   0			;use 16 MHz JTAG clock
> CPUTYPE	405			;the used target CPU type
> BDIMODE	AGENT			;the BDI working
> mode (LOADONLY | AGENT)
> BREAKMODE   SOFT			;SOFT or HARD, HARD uses PPC
> hardware breakpoint
> STEPMODE    JTAG			;JTAG or HWBP, HWPB
> uses one or two
> hardware breakpoints
> MMU	    XLAT 0xC0000000	;enable virtual address mode
> PTBASE      0x000000f0  	;here is the pointer to the
> page table
> pointers
> ;
> [HOST]
> IP          10.0.0.198     ;Windows host
> FILE        rImage.srec
> FORMAT      SREC
> LOAD        MANUAL              ;load code MANUAL or AUTO
> after reset
> ;
> ;
> [REGS]
> IDCR1	0x010	0x011	;MEMCFGADR and MEMCFGDATA
> IDCR2	0x012	0x013	;EBCCFGADR and EBCCFGDATA
> IDCR3	0x014	0x015	;KIAR and KIDR
> FILE    defs/reg405gp.def
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/