linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Yosemite board ala, PPC405EP
@ 2006-03-08 19:45 Jeff.Fellin
  2006-03-08 20:21 ` Eugene Surovegin
  2006-03-08 20:27 ` David Hawkins
  0 siblings, 2 replies; 6+ messages in thread
From: Jeff.Fellin @ 2006-03-08 19:45 UTC (permalink / raw)
  To: linuxppc-embedded


I have been using an Albatron BDI for a PPC405GP board in a project.
According to the documentation I've read the Yosemite board is identical
register wise to the 405GP, except for two sets of EMAC registers.

My problem is when I use the Albatron BDI using the register definitions
for the 405GP, the BDI cannot communicate with the 405EP.

Anyone have experience with usingg the BDI for the PPC 405EP?

Thank you in advance for you help.
Jeff Fellin
RFL Electronics
Jeff.Fellin@rflelect.com
973 334-3100, x 327

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Yosemite board ala, PPC405EP
  2006-03-08 19:45 Jeff.Fellin
@ 2006-03-08 20:21 ` Eugene Surovegin
  2006-03-08 20:27 ` David Hawkins
  1 sibling, 0 replies; 6+ messages in thread
From: Eugene Surovegin @ 2006-03-08 20:21 UTC (permalink / raw)
  To: Jeff.Fellin; +Cc: linuxppc-embedded

On Wed, Mar 08, 2006 at 02:45:54PM -0500, Jeff.Fellin@rflelect.com wrote:
> 
> I have been using an Albatron BDI for a PPC405GP board in a project.
> According to the documentation I've read the Yosemite board is identical
> register wise to the 405GP, except for two sets of EMAC registers.
> 
> My problem is when I use the Albatron BDI using the register definitions
> for the 405GP, the BDI cannot communicate with the 405EP.
> 
> Anyone have experience with usingg the BDI for the PPC 405EP?

AFAIK, Yosemite is 440EP, not 405EP. And 440EP is quite different from 
405GP.

-- 
Eugene

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Yosemite board ala, PPC405EP
  2006-03-08 19:45 Jeff.Fellin
  2006-03-08 20:21 ` Eugene Surovegin
@ 2006-03-08 20:27 ` David Hawkins
  1 sibling, 0 replies; 6+ messages in thread
From: David Hawkins @ 2006-03-08 20:27 UTC (permalink / raw)
  To: Jeff.Fellin; +Cc: linuxppc-embedded

Jeff.Fellin@rflelect.com wrote:
> I have been using an Albatron BDI for a PPC405GP board in a project.
> According to the documentation I've read the Yosemite board is identical
> register wise to the 405GP, except for two sets of EMAC registers.
> 
> My problem is when I use the Albatron BDI using the register definitions
> for the 405GP, the BDI cannot communicate with the 405EP.
> 
> Anyone have experience with usingg the BDI for the PPC 405EP?

Hey Jeff,

Can you please clarify;

Are you using a Yosemite board (440EP) or are you using a 405EP board
(which is *not* the Yosemite board)?

If you are using the Yosemite board, then I have one here,
and my BDI2000 just arrived. I haven't had a chance to test
the BDI2000, but I can let you know the results when I do.

Dave

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Yosemite board ala, PPC405EP
@ 2006-03-08 21:18 Jeff.Fellin
  2006-03-08 21:33 ` David Hawkins
  0 siblings, 1 reply; 6+ messages in thread
From: Jeff.Fellin @ 2006-03-08 21:18 UTC (permalink / raw)
  To: dwh; +Cc: linuxppc-embedded


Sorry, I was confused. I have a PPC405EP. not a Yosemite board.

Jeff Fellin
RFL Electronics
Jeff.Fellin@rflelect.com
973 334-3100, x 327


                                                                                                               
                      David Hawkins                                                                            
                      <dwh@ovro.caltech        To:       Jeff.Fellin@rflelect.com                              
                      .edu>                    cc:       linuxppc-embedded@ozlabs.org                          
                                               Subject:  Re: Yosemite board ala, PPC405EP                      
                      03/08/2006 15:27                                                                         
                                                                                                               
                                                                                                               




Jeff.Fellin@rflelect.com wrote:
> I have been using an Albatron BDI for a PPC405GP board in a project.
> According to the documentation I've read the Yosemite board is identical
> register wise to the 405GP, except for two sets of EMAC registers.
>
> My problem is when I use the Albatron BDI using the register definitions
> for the 405GP, the BDI cannot communicate with the 405EP.
>
> Anyone have experience with usingg the BDI for the PPC 405EP?

Hey Jeff,

Can you please clarify;

Are you using a Yosemite board (440EP) or are you using a 405EP board
(which is *not* the Yosemite board)?

If you are using the Yosemite board, then I have one here,
and my BDI2000 just arrived. I haven't had a chance to test
the BDI2000, but I can let you know the results when I do.

Dave

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Yosemite board ala, PPC405EP
  2006-03-08 21:18 Yosemite board ala, PPC405EP Jeff.Fellin
@ 2006-03-08 21:33 ` David Hawkins
  2006-03-09 13:18   ` Stefan Roese
  0 siblings, 1 reply; 6+ messages in thread
From: David Hawkins @ 2006-03-08 21:33 UTC (permalink / raw)
  To: Jeff.Fellin; +Cc: linuxppc-embedded



> Sorry, I was confused. I have a PPC405EP. not a Yosemite board.

Ok, sorry then, I can't help.

Take a look at the Denx web site, they have a bunch of
BDI2000 configuration files, I'm not sure whether they
have a 405EP, but take a look.

Dave

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Yosemite board ala, PPC405EP
  2006-03-08 21:33 ` David Hawkins
@ 2006-03-09 13:18   ` Stefan Roese
  0 siblings, 0 replies; 6+ messages in thread
From: Stefan Roese @ 2006-03-09 13:18 UTC (permalink / raw)
  To: linuxppc-embedded; +Cc: Jeff.Fellin

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On Wednesday, 8. March 2006 22:33, David Hawkins wrote:
> > Sorry, I was confused. I have a PPC405EP. not a Yosemite board.
>
> Ok, sorry then, I can't help.
>
> Take a look at the Denx web site, they have a bunch of
> BDI2000 configuration files, I'm not sure whether they
> have a 405EP, but take a look.

Yes, we have. Take a look at the attached bubinga config file (AMCC 405EP 
evaluation board).

The 405EP is quite different from the 405GP(r) regarding it initialization. 
The PLL is setup normally not via strapping pins as on the 405GP(r) but by 
reading values from a EEPROM. This can behavior can be configured by one 
strapping pin (don't know which one right now). Please take a look at the PLL 
setup in the BDI config file.

Best regards,
Stefan

[-- Attachment #2: bubinga.cfg --]
[-- Type: text/plain, Size: 4625 bytes --]

;bdiGDB configuration file for PPChameleonEVB for U-Boot
; ------------------------------------------------------
;
[INIT]
; init core register
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	0xFFF80000	;EVPR: Exception Vector Table @0x00000000

;
WDCR    0x0F9   0x08000000

; Setup PLL
; CPU=133MHz
; PLB=133MHz
; OPB=66MHz
; EBC=33MHz
WDCR    0x0F0    0x00001203
WDCR    0x0F4    0x8042223E


; Setup Peripheral Bus

; CS0 (default mode)
WDCR	18	0x00000010	;Select PB0AP
WDCR	19	0x92015480	;PB0AP: NOR Flash/SRAM
WDCR	18	0x00000000	;Select PB0CR
;WDCR	19	0xFFC5A000	;PB0CR: BAS=0xFFC,BS=4MB,BU=R/W,BW=16bit
WDCR	19	0xFFC58000	;PB0CR: BAS=0xFFC,BS=4MB,BU=R/W,BW=8bit
WDCR	18	0x00000011	;Select PB1AP
WDCR	19	0x92015480	;PB1AP: SRAM/NOR Flash
WDCR	18	0x00000001	;Select PB1CR
WDCR	19	0xFF85A000	;PB1CR: BAS=0xFF8,BS=4MB,BU=R/W,BW=16bit




;WDCR	18	0x00000011	;Select PB1AP
;WDCR	19	0x02815480	;PB1AP: NVRAM and RTC
;WDCR	18	0x00000001	;Select PB1CR
;WDCR	19	0xF0018000	;PB1CR: 1MB at 0xF0000000, r/w, 8bit
;WDCR	18	0x00000012	;Select PB2AP
;WDCR	19	0x04815A80	;PB2AP: Keyboard and Mouse
;WDCR	18	0x00000002	;Select PB2CR
;WDCR	19	0xF0118000	;PB2CR: 1MB at 0xF0100000, r/w, 8bit
;WDCR	18	0x00000013	;Select PB3AP
;WDCR	19	0x01815280	;PB3AP: IRDA
;WDCR	18	0x00000003	;Select PB3CR
;WDCR	19	0xF0218000	;PB3CR: 1MB at 0xF0200000, r/w, 8bit
;WDCR	18	0x00000017	;Select PB7AP
;WDCR	19	0x01815280	;PB7AP: FPGA
;WDCR	18	0x00000007	;Select PB7CR
;WDCR	19	0xF0318000	;PB7CR: 1MB at 0xF0300000, r/w, 8bit



; Setup SDRAM Controller
WDCR	16	0x00000080	;Select SDTR1
WDCR	17	0x01074015	;SDTR1: SDRAM Timing Register
WDCR	16	0x00000040	;Select MB0CF
WDCR	17	0x00084001	;MB0CF: 16MB @ 0x00000000
WDCR	16	0x00000030	;Select RTR
WDCR	17	0x07f00000	;RTR: Refresh Timing Register
WDCR	16	0x00000020	;Select MCOPT1
WDCR	17	0x80800000	;MCOPT1: Enable SDRAM Controller


; Setup MMU info - these lines must be uncommented to debug Linux kernel
;WM32    0x000000f4  0x00000000  ;invalidate kernel  page table base
;WM32    0x000000f8  0x00000000  ;invalidate process page table base
;WM32    0x000000f0  0xc00000f4  ;invalidate page table base

; Setup OCM
WDCR    0x01A   0xEC000000
WDCR    0x01B   0xC0000000

[TARGET]
JTAGCLOCK   0                   ;use 16 MHz JTAG clock
CPUTYPE     405 		;the used target CPU type
BDIMODE     AGENT   	        ;the BDI working mode (LOADONLY | AGENT)
WAKEUP      2000                ;wakeup time after reset
BREAKMODE   HARD      	        ;SOFT or HARD, HARD uses PPC hardware breakpoint
STEPMODE    HWBP                ;JTAG or HWBP, HWPB uses one or two hardware breakpoints
;VECTOR      CATCH               ;catch unhandled exceptions
;MMU         XLAT 0xC0000000     ;enable virtual address mode
;PTBASE      0x000000f0          ;address where kernel/user stores pointer to page table
;SIO         7 9600              ;TCP port for serial IO

;REGLIST     SPR                 ;select register to transfer to GDB
REGLIST      ALL                 ;select register to transfer to GDB
;SCANPRED    2 2                 ;JTAG devices connected before PPC400
;SCANSUCC    3 3                 ;JTAG devices connected after PPC400

[HOST]
IP           192.168.1.1
FORMAT       BIN
FILE         /tftpboot/bubinga/u-boot.bin
LOAD        MANUAL 	       ;load code MANUAL or AUTO after reset
DEBUGPORT   2001
PROMPT      PPC405EP>

[FLASH]
; ###FIXME### - workspace does not work with onchip memory
WORKSPACE   0x100000  ;workspace in on-chip SRAM for fast programming algorithm
; WORKSPACE   0  ;workspace in on-chip SRAM for fast programming algorithm
;CHIPTYPE    AM29BX16       ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16)
;CHIPSIZE    0x400000    ;The size of one flash chip in bytes (e.g. AM29F040 = 0x80000)
;BUSWIDTH    16           ;The width of the flash memory bus in bits (8 | 16 | 32)
CHIPTYPE    AM29F       ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16)
CHIPSIZE    0x80000    ;The size of one flash chip in bytes (e.g. AM29F040 = 0x80000)
BUSWIDTH    8           ;The width of the flash memory bus in bits (8 | 16 | 32)
FILE        /tftpboot/bubinga/u-boot.bin
FORMAT      BIN   0xFFFC0000

; erase whole Flash
;ERASE       0xFFC00000 CHIP
; Erase just the last seven blocks for U-Boot
ERASE       0xFFFC0000
ERASE       0xFFFD0000
ERASE       0xFFFE0000
ERASE       0xFFFF0000

[REGS]
IDCR1	0x010	0x011	;MEMCFGADR and MEMCFGDATA
IDCR2	0x012	0x013	;EBCCFGADR and EBCCFGDATA
;IDCR3	0x014	0x015	;KIAR and KIDR
FILE    /tftpboot/BDI2000/reg405ep.def

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-03-09 13:19 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-08 21:18 Yosemite board ala, PPC405EP Jeff.Fellin
2006-03-08 21:33 ` David Hawkins
2006-03-09 13:18   ` Stefan Roese
  -- strict thread matches above, loose matches on Subject: below --
2006-03-08 19:45 Jeff.Fellin
2006-03-08 20:21 ` Eugene Surovegin
2006-03-08 20:27 ` David Hawkins

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).