Hi all,
>> I have spent quite some time trying to move from U-Boot 1.2 to a newer
>> version.. I am stuck at the initialization of the ram. The ram checksum
>> fails and gives me a "total memory of 0". (the board has 512MB and work
>> when booting uboot 1.2)
>>
>> can anyone pls. point me in the ri
u-boot-1.1.6.
my sdram is 512MB, with CS0_BNDS,DDRLAWAR0,DDRLAWBAR0 modified, 256MB of
512MB sdram can work perfectly.
Then, I defined CONFIG_VERY_BIG_RAM, 512MB can be recognized, but, I can
only read and write 256MB, fault occurred when address move across 256MB.
besides CONFIG_VERY_BIG_RAM,
> u-boot-1.1.6.
Suggest you use the latest u-boot as base, due to the u-boot/kernel
interface has much change since 1.1.6.
> my sdram is 512MB, with CS0_BNDS,DDRLAWAR0,DDRLAWBAR0
> modified, 256MB of
> 512MB sdram can work perfectly.
>
> Then, I defined CONFIG_VERY_BIG_RAM, 512MB can be recogni
Hello,
I have made the following defines in the config header file:
#define CONFIG_CMD_USB
#define CONFIG_USB_OHCI_NEW 1
#define CFG_USB_OHCI_BOARD_INIT 1
#define CFG_USB_OHCI_MAX_ROOT_PORTS 3
#define CFG_USB_OHCI_REGS_BASE0x4C00
#define CFG_USB_OHCI_SLOT_NAME "px
all my other works have been done under this version, so I have no time to
chage .
thanks any way.
Dave Liu-4 wrote:
>
>> u-boot-1.1.6.
>
> Suggest you use the latest u-boot as base, due to the u-boot/kernel
> interface has much change since 1.1.6.
>
>> my sdram is 512MB, with CS0_BNDS,DDRLAW
Hi Pieter,
>I have managed to read the SPD data for the dram. I also confirmed that the
dram control and timing settings correspond to the settings that worked in
the >
>previous uboot.
So it mean that you r using a DIMM, where the configurations are available
on the EEPROM.
Make sure u've decod
On Monday 12 January 2009 01:04:43 Dennis.Yxun wrote:
>I've googled, and some said upstrem was implementing the SD/MMC
> framework.
> So people just have to write SDIO driver.
> Just wondering, is there any experimental code that i can try?
it's in the last release already
-mike
signature.
Dear "A. Geisreiter",
In message <200901120901.n0c91ib21...@sun1.de> you wrote:
>
> How can I use now the usb command? I have a usb stick with a FAT32 file
Try "help usb" ?
> format and an binary file on it. I will download the file to the SDRAM. How
> can I do this?
With the "fatload" comman
Signed-off-by: Wolfgang Denk
---
cpu/mpc86xx/cpu.c |2 +-
cpu/mpc86xx/fdt.c |2 --
2 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/cpu/mpc86xx/cpu.c b/cpu/mpc86xx/cpu.c
index 3568023..dc53bee 100644
--- a/cpu/mpc86xx/cpu.c
+++ b/cpu/mpc86xx/cpu.c
@@ -101,7 +101,7 @@ checkcp
Hi,
I have enabled 'watchdog' in u-boot using flag 'CONFIG_WATCHDOG'.
I wonder how the 'watchdog' gets reset when the cursor is waiting for
user input.
As per my understanding the 'WATCHDOG_RESET()' gets called in
'readline()' prior calling 'getc()'.
In our case, the 'getc()' has been mapped to
I haven't received any communication about this patch in a while.
Is is still being looked at or did it slip through the cracks?
Or did I miss an email?
Let me know.
Ron
--- On Fri, 12/12/08, Ron Madrid wrote:
> From: Ron Madrid
> Subject: [PATCH] mpc83xx: Size optimization of start.S
> To:
Dear Sachin,
In message <73fa539107892c4c8c7a5aca10c161c85be...@mx2.alphioncorp.local> you
wrote:
>
> I have enabled 'watchdog' in u-boot using flag 'CONFIG_WATCHDOG'.
> I wonder how the 'watchdog' gets reset when the cursor is waiting for
> user input.
>
> As per my understanding the 'WATCHDO
When running in PCI agent mode, the PCI_CLK_OUT signals are not used, so do
not enable them. See the MPC8349EA Reference Manual, Section 4.4.2
"Clocking in PCI Agent Mode".
Signed-off-by: Ira W. Snyder
---
board/freescale/mpc8349emds/pci.c |7 ---
1 files changed, 0 insertions(+), 7 dele
When running a system with 2 or more MPC8349EMDS boards in PCI agent mode,
the boards will lock up the PCI bus by scanning against each other.
The boards lock against each other by trying to access the PCI bus before
clearing their configuration lock bit. Both boards end up in a loop,
sending and
> void pci_init_board(void)
> {
> volatile immap_t *immr = (volatile immap_t *)CONFIG_SYS_IMMR;
> - volatile clk83xx_t *clk = (volatile clk83xx_t *)&immr->clk;
> volatile law83xx_t *pci_law = immr->sysconf.pcilaw;
> volatile pcictrl83xx_t *pci_ctrl = &immr->pci_ctrl[0];
>
Stefan et al,
I am trying to troubleshoot a weird PCIe problem on a PPC460GT based
target, and it is getting curiouser and curiouser.
There is a tlb overlap I mentioned in an earlier email; on top of that
there are some things happening in cpu/ppc4xx/4xx_pcie.c which I also
find hard to understan
On Tue, Jan 13, 2009 at 08:09:23AM +0800, Liu Dave wrote:
> > void pci_init_board(void)
> > {
> > volatile immap_t *immr = (volatile immap_t *)CONFIG_SYS_IMMR;
> > - volatile clk83xx_t *clk = (volatile clk83xx_t *)&immr->clk;
> > volatile law83xx_t *pci_law = immr->sysconf.pcilaw;
> >
> Yes, there are two pci_init_board() functions in this file.
> One for PCI
> host mode, and one for PCI agent mode. This version only runs in agent
> mode, it doesn't even get compiled in host mode.
That is fine.
___
U-Boot mailing list
U-Boot@lists.de
Hi,
>> 'cpu/ppc4xx/serial.c'.
>There is no such file in U-Boot.
The version of the u-boot being used is 1.1.4.
The latest version of the u-boot (u-boot-2008.10) has '4xx_uart.c'
instead of 'serial.c'
> Which sort of watchdog device is used on your board?
I am using Software version of Watchdog
19 matches
Mail list logo
