* [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board
@ 2004-08-04 0:19 Abhijeet Bisain
2004-08-04 9:37 ` Wolfgang Denk
2004-08-04 16:45 ` Jon Loeliger
0 siblings, 2 replies; 5+ messages in thread
From: Abhijeet Bisain @ 2004-08-04 0:19 UTC (permalink / raw)
To: u-boot
Hi,
I hope this is the right forum to ask this question. I recently received
the rev A board from Motorola with u-boot and Linux on it and everything is
nice. But I need to run Montavista linux on it, so I configure u-boot to
BOOTP and tftp a kernel from them. This works partially fine, I can telnet
into the machine but there is no console on serial. So I was asked to put a
u-boot binary from Montavista onto the board.
I am using BDI2000 to program the flash but am running into difficulty.
The config file I have is from Abatron and I haven't modified any Jumpers
or switches on the board. When I program the flash with u-boot, BDI says it
was successful, but the data read from the flash is incorrect. The data has
the first, third, and the eighth bits of a 32 bit word high all the time.
So a 0x00000000 is seen as 0xa1000000 and a 0x12345678 as 0xb3345678.
I am attaching the BDI config file below. any help on this will be greatly
appreciated.
Thanks,
Abhijeet
;bdiGDB configuration file for MPC8560ADS
;
[INIT]
;
; Move the L2SRAM to the initial MMU page
WM32 0xFF720000 0x68010000 ;L2CTL
WM32 0xFF720100 0xFFFC0000 ;L2SRBAR0
WM32 0xFF720000 0xA8010000 ;L2CTL
;
; load TLB entries, helper code @ 0xfffff000
WM32 0xfffff000 0x7c0007a4 ;tlbwe
WM32 0xfffff004 0x7c0004ac ;msync
WM32 0xfffff008 0x48000000 ;loop
;
; 1MB TLB1 #1 0x40000000 - 0x400fffff
WSPR 624 0x10010000 ;MAS0:
WSPR 625 0x80000500 ;MAS1:
WSPR 626 0x4000000a ;MAS2:
WSPR 627 0x40000015 ;MAS3:
WSPR 628 0x00000000 ;MAS4:
EXEC 0xfffff000
;
; 64 MB TLB1 #2 0xc0000000 - 0xc3ffffff
WSPR 624 0x10020000 ;MAS0:
WSPR 625 0x80000800 ;MAS1:
WSPR 626 0xc0000008 ;MAS2:
WSPR 627 0xc0000015 ;MAS3:
EXEC 0xfffff000
;
; 64 MB TLB1 #3 0x00000000 - 0x03ffffff
WSPR 624 0x10030000 ;MAS0:
WSPR 625 0x80000800 ;MAS1:
WSPR 626 0x00000008 ;MAS2:
WSPR 627 0x00000015 ;MAS3:
EXEC 0xfffff000
;
; 64 MB TLB1 #4 0x04000000 - 0x07ffffff
WSPR 624 0x10040000 ;MAS0:
WSPR 625 0x80000800 ;MAS1:
WSPR 626 0x04000008 ;MAS2:
WSPR 627 0x04000015 ;MAS3:
EXEC 0xfffff000
;
; 16 MB TLB1 #5 0xff000000 - 0xffffffff
WSPR 624 0x10050000 ;MAS0:
WSPR 625 0x80000700 ;MAS1:
WSPR 626 0xff00000a ;MAS2:
WSPR 627 0xff000015 ;MAS3:
EXEC 0xfffff000
;
; 16 MB TLB1 #0 0xf0000000 - 0xf0ffffff
WSPR 624 0x10000000 ;MAS0:
WSPR 625 0x80000700 ;MAS1:
WSPR 626 0xf0000008 ;MAS2:
WSPR 627 0xf0000015 ;MAS3:
EXEC 0xfffff000
;
; Remove the L2SRAM from the initial MMU page
WM32 0xFF720000 0x28010000 ;L2CTL
WM32 0xFF720000 0x28000000 ;L2CTL
;
; Move CCSRBAR to 0x40000000
WM32 0xff700000 0x00040000 ;CCSRBAR to 0x40000000
;
; Initialize LAWBAR's
WM32 0x40000C08 0x00000000 ;LAWBAR0 : @0x00000000
WM32 0x40000C10 0x80f0001b ;LAWAR0 : DDR/SDRAM 256MB
WM32 0x40000C28 0x000c0000 ;LAWBAR1 : @0xc0000000
WM32 0x40000C30 0x8040001d ;LAWAR1 : Local Bus 1GB
;
; Setup DDR (ADS Rev.Pilot , 128MB DDR)
;WM32 0x40002000 0x00000007 ;CS0_BNDS
;WM32 0x40002080 0x80000002 ;CS0_CONFIG
;WM32 0x40002108 0x37544321 ;TIMING_CFG_1
;WM32 0x4000210C 0x00000800 ;TIMING_CFG_2
;WM32 0x40002110 0x02000000 ;DDR_SDRAM_CFG
;WM32 0x40002118 0x00000062 ;DDR_SDRAM_MODE
;WM32 0x40002124 0x03a30000 ;DDR_SDRAM_IVAL
;DELAY 200
;WM32 0x40002110 0xc2000000 ;DDR_SDRAM_CFG
;
; Setup DDR (ADS Rev.A , 256MB DDR)
WM32 0x40002000 0x0000000f ;CS0_BNDS
WM32 0x40002080 0x80000102 ;CS0_CONFIG
WM32 0x40002108 0x36343321 ;TIMING_CFG_1
WM32 0x4000210C 0x00000800 ;TIMING_CFG_2
WM32 0x40002110 0x02008000 ;DDR_SDRAM_CFG
WM32 0x40002118 0x00000062 ;DDR_SDRAM_MODE
WM32 0x40002124 0x045b0100 ;DDR_SDRAM_IVAL
DELAY 200
WM32 0x40002110 0xc2008000 ;DDR_SDRAM_CFG
;
; Setup Flash chip select
WM32 0x40005000 0xff001801 ;BR0
WM32 0x40005004 0xff006ff7 ;OR0
; Setup flash programming workspace in dual port RAM
WSPR 63 0x40080000 ;IVPR to workspace
WSPR 415 0x000007F0 ;IVOR15 : Debug exception
WM32 0x400807F0 0x48000000 ;write valid instruction
;
; Setup for program execution
WM32 0x40020000 0x28010000 ;L2CTL
WM32 0x40020000 0x28000000 ;L2CTL
WSPR 63 0x00000000 ;IVPR to workspace
WSPR 406 0x0000700 ;IVOR6 : Program exception
WSPR 415 0x0001500 ;IVOR15 : Debug exception
WM32 0x00000700 0x48000000 ;write valid instruction
WM32 0x00001500 0x48000000 ;write valid instruction
;
; Clear flash Lock-Bits
WM32 0xFF800000 0x00600060 ;clear Lock-Bits command
WM32 0xFF800000 0x00D000D0
DELAY 1000 ;needs up to 0.7 sec
WM32 0xFF800000 0xFFFFFFFF ;set flash to read mode
;
[TARGET]
CPUTYPE 8560 ;the CPU type
JTAGCLOCK 0 ;use 16 MHz JTAG clock
STARTUP LOOP ;use boot loop in L2SRAM
;STARTUP HALT ;halt core while HRESET is asserted
BREAKMODE SOFT ;SOFT or HARD, HARD uses PPC hardware breakpoint
STEPMODE JTAG ;JTAG or HWBP, HWBP uses a hardware breakpoint
WAKEUP 200 ;give reset time to complete
POWERUP 5000 ;start delay after power-up detected in ms
MEMACCESS SAP ;use SAP or CORE for JTAG memory accesses
;REGLIST E500 ;send registers in E500 sequence to GDB
[HOST]
IP 10.1.0.2
FILE /tftpboot/8560/u-boot.bin.8560ads
FORMAT BIN
LOAD MANUAL ;load code MANUAL or AUTO after reset
DUMP /tftpboot/8560/e500.bin
[FLASH]
CHIPTYPE STRATAX16
CHIPSIZE 0x800000 ;The size of one flash chip in bytes
BUSWIDTH 32 ;The width of the flash memory bus in bits (8 | 16
| 32)
WORKSPACE 0x40080000 ;workspace in dual port RAM
;WORKSPACE 0xf0000000 ;workspace in L2SRAM
FILE /tftpboot/8560/u-boot.bin.8560ads
FORMAT BIN 0xFFF80000
ERASE 0xFFF80000
ERASE 0xFFFC0000
[REGS]
FILE /tftpboot/8560/reg8560.def
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board
2004-08-04 0:19 [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board Abhijeet Bisain
@ 2004-08-04 9:37 ` Wolfgang Denk
2004-08-04 16:45 ` Jon Loeliger
1 sibling, 0 replies; 5+ messages in thread
From: Wolfgang Denk @ 2004-08-04 9:37 UTC (permalink / raw)
To: u-boot
In message <6.0.0.22.2.20040803170059.035df108@qcmail1.qualcomm.com> you wrote:
>
> I hope this is the right forum to ask this question. I recently received
> the rev A board from Motorola with u-boot and Linux on it and everything is
> nice. But I need to run Montavista linux on it, so I configure u-boot to
> BOOTP and tftp a kernel from them. This works partially fine, I can telnet
> into the machine but there is no console on serial. So I was asked to put a
Maybe your kernel is misconfigured? Did you try passing something
like "console=ttyS0,$(baudrate)" on the command line?
> u-boot binary from Montavista onto the board.
If everything else is working this seems a bogus advice to me.
> I am using BDI2000 to program the flash but am running into difficulty.
> The config file I have is from Abatron and I haven't modified any Jumpers
> or switches on the board. When I program the flash with u-boot, BDI says it
> was successful, but the data read from the flash is incorrect. The data has
> the first, third, and the eighth bits of a 32 bit word high all the time.
> So a 0x00000000 is seen as 0xa1000000 and a 0x12345678 as 0xb3345678.
Now this looks like a hardware problem to me.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
My challenge to the goto-less programmer is to recode tcp_input()
without any gotos ... without any loss of efficiency (there has to be
a catch). - W. R. Stevens
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board
2004-08-04 0:19 [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board Abhijeet Bisain
2004-08-04 9:37 ` Wolfgang Denk
@ 2004-08-04 16:45 ` Jon Loeliger
2004-08-04 17:22 ` Abhijeet Bisain
1 sibling, 1 reply; 5+ messages in thread
From: Jon Loeliger @ 2004-08-04 16:45 UTC (permalink / raw)
To: u-boot
On Tue, 2004-08-03 at 19:19, Abhijeet Bisain wrote:
> Hi,
>
> I hope this is the right forum to ask this question. I recently received
> the rev A board from Motorola with u-boot and Linux on it
Can you tell us what versions of U-Boot and Linux?
> and everything is
> nice. But I need to run Montavista linux on it,
Was the Linux on it MontaVista already?
> so I configure u-boot to
> BOOTP and tftp a kernel from them.
What version was this image?
> This works partially fine, I can telnet
> into the machine but there is no console on serial.
No Linux console? Did you pass in a console= command line option?
> So I was asked to put a
> u-boot binary from Montavista onto the board.
Again, which version?
> I am using BDI2000 to program the flash but am running into difficulty.
> The config file I have is from Abatron and I haven't modified any Jumpers
> or switches on the board. When I program the flash with u-boot, BDI says it
> was successful, but the data read from the flash is incorrect. The data has
> the first, third, and the eighth bits of a 32 bit word high all the time.
> So a 0x00000000 is seen as 0xa1000000 and a 0x12345678 as 0xb3345678.
Ewww. This sounds like broken hardware to me.
> I am attaching the BDI config file below. any help on this will be greatly
> appreciated.
That all looks fine to me. Minor differences compared to the (older)
version I am using. For example, I use L2SRAM rather than dual port RAM
for the flash programming set up. Both should work, though.
;
; Setup flash programming workspace in L2SRAM
WM32 0x40020000 0x68010000 ;L2CTL
WM32 0x40020100 0xf0000000 ;L2SRBAR0
WM32 0x40020000 0xA8010000 ;L2CTL
WSPR 63 0xf0000000 ;IVPR to workspace
WSPR 415 0x0001500 ;IVOR15 : Debug exception
WM32 0xf0001500 0x48000000 ;write valid instruction
> Thanks,
> Abhijeet
>
I'm voting for a hardware problem to be fixed first, though. :-)
jdl
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board
2004-08-04 16:45 ` Jon Loeliger
@ 2004-08-04 17:22 ` Abhijeet Bisain
2004-08-04 18:33 ` Jon Loeliger
0 siblings, 1 reply; 5+ messages in thread
From: Abhijeet Bisain @ 2004-08-04 17:22 UTC (permalink / raw)
To: u-boot
At 09:45 AM 8/4/2004, Jon Loeliger wrote:
>On Tue, 2004-08-03 at 19:19, Abhijeet Bisain wrote:
> > Hi,
> >
> > I hope this is the right forum to ask this question. I recently
> received
> > the rev A board from Motorola with u-boot and Linux on it
>
>Can you tell us what versions of U-Boot and Linux?
U-boot 1.0.1 and Linux 2.4.25
> > and everything is
> > nice. But I need to run Montavista linux on it,
>
>Was the Linux on it MontaVista already?
No, it was from Metrowerks and was burnt onto the flash. U-boot was
programmed to load it from flash and was passing the console=ttyS0,115200
to the kernel
> > so I configure u-boot to
> > BOOTP and tftp a kernel from them.
>
>What version was this image?
This is Linux kernel 2.4.20
> > This works partially fine, I can telnet
> > into the machine but there is no console on serial.
>
>No Linux console? Did you pass in a console= command line option?
yes, a dmesg on Linux confirms this option too.
> > So I was asked to put a
> > u-boot binary from Montavista onto the board.
>
>Again, which version?
This is 1.1.0 as i see from hexedit.
> > I am using BDI2000 to program the flash but am running into
> difficulty.
> > The config file I have is from Abatron and I haven't modified any Jumpers
> > or switches on the board. When I program the flash with u-boot, BDI
> says it
> > was successful, but the data read from the flash is incorrect. The data
> has
> > the first, third, and the eighth bits of a 32 bit word high all the time.
> > So a 0x00000000 is seen as 0xa1000000 and a 0x12345678 as 0xb3345678.
>
>Ewww. This sounds like broken hardware to me.
That's what I was afraid of :).
Thanks,
Abhijeet
> > I am attaching the BDI config file below. any help on this will
> be greatly
> > appreciated.
>
>That all looks fine to me. Minor differences compared to the (older)
>version I am using. For example, I use L2SRAM rather than dual port RAM
>for the flash programming set up. Both should work, though.
>
>;
>; Setup flash programming workspace in L2SRAM
>WM32 0x40020000 0x68010000 ;L2CTL
>WM32 0x40020100 0xf0000000 ;L2SRBAR0
>WM32 0x40020000 0xA8010000 ;L2CTL
>WSPR 63 0xf0000000 ;IVPR to workspace
>WSPR 415 0x0001500 ;IVOR15 : Debug exception
>WM32 0xf0001500 0x48000000 ;write valid instruction
>
> > Thanks,
> > Abhijeet
> >
>
>I'm voting for a hardware problem to be fixed first, though. :-)
>
>jdl
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board
2004-08-04 17:22 ` Abhijeet Bisain
@ 2004-08-04 18:33 ` Jon Loeliger
0 siblings, 0 replies; 5+ messages in thread
From: Jon Loeliger @ 2004-08-04 18:33 UTC (permalink / raw)
To: u-boot
On Wed, 2004-08-04 at 12:22, Abhijeet Bisain wrote:
> U-boot 1.0.1 and Linux 2.4.25
These will be using the so-called "Old Memory Map" on
the 85xx boards.
> >Was the Linux on it MontaVista already?
>
> No, it was from Metrowerks and was burnt onto the flash. U-boot was
> programmed to load it from flash and was passing the console=ttyS0,115200
> to the kernel
So, that should work just fine.
> >What version was this image?
>
> This is Linux kernel 2.4.20
Interesting. It would have to be patched a lot, though. OK.
> > > u-boot binary from Montavista onto the board.
> >
> >Again, which version?
>
> This is 1.1.0 as i see from hexedit.
This probably has a so-called "New Memory Map" on
it for the 85xx boards. Note that the U-Boot and
the Linux must agree on which memory map to use.
> >
> >Ewww. This sounds like broken hardware to me.
>
> That's what I was afraid of :).
So with U-Boot, can you verify memory at all?
> Thanks,
> Abhijeet
jdl
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-08-04 18:33 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-04 0:19 [U-Boot-Users] Having trouble programming u-boot to MPC8560ADS board Abhijeet Bisain
2004-08-04 9:37 ` Wolfgang Denk
2004-08-04 16:45 ` Jon Loeliger
2004-08-04 17:22 ` Abhijeet Bisain
2004-08-04 18:33 ` Jon Loeliger
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.