Disclaimer: I'm not running ppc these days
However, having no NOR flash means:
- NAND should be programmable via JTAG (BDI3000 doesn't support
this, Lauterbach/trace32 does)
My personal preference for bringing up a new board is placing u-boot
in RAM using the available information to
On 15:02 Tue 02 Dec , arun c wrote:
Hi all,
Does u-boot support loading custom binary executables?
I know u-boot supports standalone applications and operating systems.
The scenario is like this.
1) u-boot completes the hardware booting.
2) It loads the custom binary image(elf
Dear Tomy,
In message [EMAIL PROTECTED] you wrote:
I am currently working on AT91SAM9260 based board. In this board we
are using LXT971A as PHY. We are using u-boot version 1.1.5. We have
connected one Ethernet cross-over cable between the board and my PC. After
rebooting we are
Hi all,
Does u-boot support loading custom binary executables?
I know u-boot supports standalone applications and operating systems.
The scenario is like this.
1) u-boot completes the hardware booting.
2) It loads the custom binary image(elf file) from flash to SDRAM and pass
over the
Signed-off-by: Stefan Roese [EMAIL PROTECTED]
---
common/cmd_ubi.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/common/cmd_ubi.c b/common/cmd_ubi.c
index 495d71e..fd33a67 100644
--- a/common/cmd_ubi.c
+++ b/common/cmd_ubi.c
@@ -546,7 +546,7 @@ static int
Hi ... I would like to compile uboot for x86 and run it on qemu (so i
can take a look see at what uboot is all about).
Could someone please recommend which make _config i should use?
Jim
___
U-Boot mailing list
U-Boot@lists.denx.de
- Add subpage write support
- Add onenand_oob_64/32 ecclayout
This has been missing and without it UBI has some incompatibilies issues
with the current (= 2.6.27) Linux kernel version. vid_hdr_offset is
placed differently (2048 instead of 512) without this fix.
Signed-off-by: Stefan Roese [EMAIL
On Thursday 27 November 2008 13:36, Dirk Eibach wrote:
Signed-off-by: Dirk Eibach [EMAIL PROTECTED]
+int board_early_init_f(void)
+{
+ register uint reg;
+
+ /*
+ * Setup the external bus controller/chip
This patch fix the problem that only the [NB_DATAFLASH_AREA - 1] dataflash
partition can be defined to use the area to the end of dataflash size.
Now it is possible to have only one dataflash partition from 0 to the end
of of dataflash size.
Signed-off-by: Ilko Iliev [EMAIL PROTECTED]
---
When CONFIG_SYS_HUSH_PARSER is defined network download
commands with 1 argument in the format 'tftp /path/file'
do not work as expected. The hush command parser strips
the quotes from /path/file which causes the network
commands to interpret /path/file as an address
instead of the intended
Carlos kescuin wrote:
Hi, everyone:
I'm working with u-boot 2008 version for a freescale M5329EVB.
Which version? There were multiple releases in 2008.
nand.c: In function 'nand_hwcontrol':
nand.c:50: error: 'NAND_CTL_SETNCE' undeclared (first use in this function)
nand.c:50: error:
Thomas == Thomas De Schampheleire [EMAIL PROTECTED] writes:
Thomas I'd change the error message as well, to be independent of the tool
Thomas used to get the file size. For example:
Thomas fprintf (stderr, %s: Can't get size of %s: %s\n,
Ahh yes, good idea.
From
Added a CONFIG_SYS_FLASH_BASE_PHYS for use as the physical address and
maintain CONFIG_SYS_FLASH_BASE as the virtual address of the flash.
This allows us to deal with 36-bit phys on these boards in the future.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
These require the 'FSL: Moved
Added a PIXIS_BASE_PHYS for use as the physical address and maintain
PIXIS_BASE as the virtual address of the PIXIS fpga registers.
This allows us to deal with 36-bit phys on these boards in the future.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
These require the 'FSL: Moved BR_PHYS_ADDR
On Tue, 2008-12-02 at 14:19 -0600, Kumar Gala wrote:
Added a PIXIS_BASE_PHYS for use as the physical address and maintain
PIXIS_BASE as the virtual address of the PIXIS fpga registers.
This allows us to deal with 36-bit phys on these boards in the future.
Signed-off-by: Kumar Gala [EMAIL
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD [EMAIL PROTECTED]
---
cpu/arm920t/start.S |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/cpu/arm920t/start.S b/cpu/arm920t/start.S
index 5143cfc..fbcfe6d 100644
--- a/cpu/arm920t/start.S
+++ b/cpu/arm920t/start.S
@@
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD [EMAIL PROTECTED]
---
common/usb_kbd.c |4
include/devices.h |2 ++
2 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/common/usb_kbd.c b/common/usb_kbd.c
index cf14560..89e6ee7 100644
--- a/common/usb_kbd.c
+++
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD [EMAIL PROTECTED]
---
include/configs/at91rm9200dk.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/configs/at91rm9200dk.h b/include/configs/at91rm9200dk.h
index 5c239d7..746f0ef 100644
---
On 17:27 Tue 02 Dec , Ilko Iliev wrote:
This patch fix the problem that only the [NB_DATAFLASH_AREA - 1] dataflash
partition can be defined to use the area to the end of dataflash size.
Now it is possible to have only one dataflash partition from 0 to the end
of of dataflash size.
On Tue, Nov 25, 2008 at 12:31 PM, Ben Warren [EMAIL PROTECTED] wrote:
Hi Michal,
Michal Simek wrote:
Hi Ben,
how does look like your propose work about PHY lib?
Thanks,
Michal
I'd like to have the PHY library included in the 02.2009 release. One
of the things I'm struggling with is
On Tue, Dec 2, 2008 at 3:31 AM, Anatolij Gustschin [EMAIL PROTECTED] wrote:
This patch tries to ensure that phy interrupt pin
won't be asserted after booting. We experienced
following issues with current 88E1121R phy init:
Marvell 88E1121R phy can be hardware-configured
to share MDC/MDIO and
Use CONFIG_SYS_{PCI,RIO}_MEM_BUS for the bus relative address instead
of _MEM_BASE so we are more explicit.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8536ds/mpc8536ds.c | 20 ++--
board/freescale/mpc8540ads/law.c|2 +-
Introduce a new define to seperate out the virtual address that PCI
IO space is at from the physical address. In most situations these are
mapped 1:1. However any code accessing the bus should use VIRT.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8536ds/tlb.c |2 +-
Introduce a new define to seperate out the virtual address that PCI
memory is at from the physical address. In most situations these are
mapped 1:1. However any code accessing the bus should use VIRT.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8536ds/tlb.c |2
Use CONFIG_SYS_PCI*_IO_BUS for the bus relative address instead
of _IO_BASE so we are more explicit.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8536ds/mpc8536ds.c |8
board/freescale/mpc8544ds/mpc8544ds.c |8
Martijn,
On Fri, Sep 12, 2008 at 8:18 PM, Martijn de Gouw
[EMAIL PROTECTED] wrote:
We have u-boot running on a ixp425 board (pdnb3), without the intel
stuff.
The npe binaries are stored seperated in flash, and loaded by u-boot.
All the code is now gplv2.
We tried to get these patches in
On 23:28 Tue 02 Dec , Leon Woestenberg wrote:
Martijn,
On Fri, Sep 12, 2008 at 8:18 PM, Martijn de Gouw
[EMAIL PROTECTED] wrote:
We have u-boot running on a ixp425 board (pdnb3), without the intel
stuff.
The npe binaries are stored seperated in flash, and loaded by u-boot.
All the
On Dec 2, 2008, at 2:29 PM, Jon Loeliger wrote:
On Tue, 2008-12-02 at 14:19 -0600, Kumar Gala wrote:
Added a PIXIS_BASE_PHYS for use as the physical address and maintain
PIXIS_BASE as the virtual address of the PIXIS fpga registers.
This allows us to deal with 36-bit phys on these boards in
On Dec 2, 2008, at 4:36 PM, Kumar Gala wrote:
On Dec 2, 2008, at 2:29 PM, Jon Loeliger wrote:
On Tue, 2008-12-02 at 14:19 -0600, Kumar Gala wrote:
Added a PIXIS_BASE_PHYS for use as the physical address and maintain
PIXIS_BASE as the virtual address of the PIXIS fpga registers.
This
Dear Peter Korsgaard,
In message [EMAIL PROTECTED] you wrote:
Thomas == Thomas De Schampheleire [EMAIL PROTECTED] writes:
Thomas I'd change the error message as well, to be independent of the tool
Thomas used to get the file size. For example:
Thomas fprintf (stderr, %s: Can't get size
On Fri, Nov 28, 2008 at 05:25:29PM +0100, Daniel Mack wrote:
the net/net.c implemenation of timeouts assumes that get_timer() returns
values in milliseconds. As this is true for most platforms, it does not
apply to PXA3x where the OSCR register increments with more than 3MHz.
The following
Hi Daniel,
Daniel Mack wrote:
On Fri, Nov 28, 2008 at 05:25:29PM +0100, Daniel Mack wrote:
the net/net.c implemenation of timeouts assumes that get_timer() returns
values in milliseconds. As this is true for most platforms, it does not
apply to PXA3x where the OSCR register increments
This adds CONFIG_NE2000_NOPROM. If set, the ethernet MAC address is taken
from the environment variable 'ethaddr' and the NIC is configured
accordingly. Needed for boards that don't have an EEPROM to store this
setting permanently.
Signed-off-by: Daniel Mack [EMAIL PROTECTED]
---
ne2000_base.c
Signed-off-by: Maxim Artamonov scn1874 at yandex.ru
---
Simple bugfix.
include/asm-arm/arch-mx31/mx31-regs.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/asm-arm/arch-mx31/mx31-regs.h
b/include/asm-arm/arch-mx31/mx31-regs.h
index 78825f5..7d6bd45 100644
---
On Tue, 02 Dec 2008 09:55:24 +0100
Norbert van Bolhuis [EMAIL PROTECTED] wrote:
Nowadays, do many (PowerPC) embedded devices already risk omitting
NOR flash and use a NAND device solely for booting and storing
images ?
I'm talking about systems with 10 years life-cycle (so no
MP3-players
Hi ,
As suggested I migrated to Fedora 9 . However in the site all examples are
with power PC as reference . I am downloading the arm iso image
arm-2008-11-24.iso and intend to use it to compile U boot . There is no
definition for Cross compile variable for ARM , it talks mostly about Power
PC
On Wednesday 03 December 2008, Sean MacLennan wrote:
We use a 256M NAND on the PIKA Warp appliance and where unable to boot
u-boot from the NAND. It worked on a smaller 64M NAND.
Currently you need to define the page-size of the NAND used for booting (512
bytes vs. 2k). The 2k 4xx NAND booting
Hi, everybody:
I am new to uboot and reading source code, I have a question: how does
compilor know where .text section starts from?
For example, I am using MPC8548CDS, document says .text section begins
from 0xfff8000, but I haven't find this value in u-boot.lds?
So it must be specified in some
On Wed, 3 Dec 2008 06:48:57 +0100
Stefan Roese [EMAIL PROTECTED] wrote:
Currently you need to define the page-size of the NAND used for
booting (512 bytes vs. 2k). The 2k 4xx NAND booting support is was
done about 1/2 a year ago. So perhaps you tested this when this 2k
support was not
On Wed, 3 Dec 2008, Sean MacLennan wrote:
Yes, I would recommend to do it this way if possible. A small NOR for
U-Boot and environment and everything else in NAND. This makes things
much easier. But I understand that this is sometimes a problem with
space (2 FLASH chips) and costs.
Mainly
Wolfgang == Wolfgang Denk [EMAIL PROTECTED] writes:
Hi,
Wolfgang Hm... but lseek() on /dev/mtdblockN will return the size of
Wolfgang the MTD device, not of the image that may be stored in it,
Wolfgang right?
Yes.
Wolfgang Later, you should get data checksum errors because of the
41 matches
Mail list logo
