Hi Navin,
What is the value you have given to TEXT_BASE in
board/pxa255_idp/config.mk
Regards
Amit
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Monday, June 16, 2008 4:23 PM
To: u-boot-users@lists.sourceforge.net
Subject: U-Boot-Users Digest, Vol 25, Issue 133
Send U-Boot-Users mailing list submissions to
u-boot-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/u-boot-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of U-Boot-Users digest..."
Today's Topics:
1. Re: Value of CFG_PCI_MEMBASE (Stefan Roese)
2. Stops booting after RAM info (navin karnam)
3. [PATCH] cfi-flash: Fix problem in flash_toggle(), busy was
not detected reliably (Stefan Roese)
4. Re: [PATCH 1/1] FAT Bare Partition Support (Michal Simek)
5. Re: U-Boot booting from NAND (Kenneth Johansson)
6. Re: Hi All (Nobuhiro Iwamatsu)
7. How do work qemu_mips image? (Nobuhiro Iwamatsu)
8. Re: Hi All (harshadnimje)
----------------------------------------------------------------------
Message: 1
Date: Mon, 16 Jun 2008 09:43:07 +0200
From: Stefan Roese <[EMAIL PROTECTED]>
Subject: Re: [U-Boot-Users] Value of CFG_PCI_MEMBASE
To: "Sachin Rane" <[EMAIL PROTECTED]>
Cc: u-boot-users@lists.sourceforge.net
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-15"
On Monday 16 June 2008, Sachin Rane wrote:
> Infact I was looking for the info to create a proper 'tlbentry' in 'init.S'
> As per my understanding the 'tlbentry' is to map 32-bit address to 36-bit
> address.
>
> The 'tlbenry' for the PCI Memory in 'init.S' is :
> tlbentry( CFG_PCI_MEMBASE, SZ_256M, 0x00000000, 3, AC_R|AC_W|SA_G|SA_I )
>
> The 'CFG_PCI_MEMBASE' is set to 0x80000000 in 'ocotea.h'.
>
> My question is how to select the value for 'CFG_PCI_MEMBASE'.
> Can I use any value (say 0x50000000 ) provided it is not overlapping with
> other devices?
Yes. I suggest to start with 0x80000000 since this leaves the first 2 GB for
SDRAM.
> If we are using Board Memory Map as a reference then the 32-bit address
> 'CFG_PCI_MEMBASE' used in 'telbentry' should have set to: 0x90000000
Why is this? Which "Board Memory Map" are you referring to?
> I am trying to find out the logic behind the selection of value for the
> variabale 'CFG_PCI_MEMBASE' in: tlbentry( CFG_PCI_MEMBASE, SZ_256M,
> 0x00000000, 3, AC_R|AC_W|SA_G|SA_I )
Whats the problems with using 0x80000000 here?
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: [EMAIL PROTECTED]
=====================================================================
------------------------------
Message: 2
Date: Mon, 16 Jun 2008 13:35:55 +0530
From: "navin karnam" <[EMAIL PROTECTED]>
Subject: [U-Boot-Users] Stops booting after RAM info
To: u-boot-users@lists.sourceforge.net
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
-- Hi all,
I am new to this list, I planned port u-boot on my board(pxa255),
followed the procedure in README and i am able to compile the uboot.
I loaded the image on board. The messages i got when i boot the board
are
-------------------------------------------------------------
U-Boot 0.4.5 (Jun 16 2008 - 12:24:00)
U-Boot code: A3000000 -> A301BD30 BSS: -> A301FE98
DRAM Configuration:
Bank #0: a0000000 64 MB
Bank #1: a4000000 0 kB
Bank #2: a8000000 0 kB
Bank #3: ac000000 0 kB
-------------------------------------------------------------
and it stops at that point. Please give me an hint where i am making the
mistake.
Regards,
Naveen
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Mon, 16 Jun 2008 10:43:41 +0200
From: Stefan Roese <[EMAIL PROTECTED]>
Subject: [U-Boot-Users] [PATCH] cfi-flash: Fix problem in
flash_toggle(), busy was not detected reliably
To: u-boot-users@lists.sourceforge.net
Message-ID: <[EMAIL PROTECTED]>
This patch simplifies flash_toggle() (AMD commandset), which is used to
detect if a FLASH device is still busy with erase/program operations. On
800MHz Canyonlands/Glacier boards (460EX/GT) the current implementation
did not detect the busy state reliably, resulting in non erased sectors
etc. This patch now simplifies this function by "just" comparing the
complete data-word instead of ANDing it with the command-word (0x40)
before the compatison. It is done the same way in the Linux implementation
chip_ready() in cfi_cmdset_0002.c.
Signed-off-by: Stefan Roese <[EMAIL PROTECTED]>
---
I have to admit that I don't really understand *why* this simplified version
fixes this problem. Does anybody else have some ideas on this?
BTW: I'll leave for a short trip in a few hours. So please don't expect any
further mails from me till Thursday this week.
Thanks,
Stefan
drivers/mtd/cfi_flash.c | 12 ++++--------
1 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
index d505bc8..c0ea97b 100644
--- a/drivers/mtd/cfi_flash.c
+++ b/drivers/mtd/cfi_flash.c
@@ -581,20 +581,16 @@ static int flash_toggle (flash_info_t * info,
flash_sect_t sect,
flash_make_cmd (info, cmd, &cword);
switch (info->portwidth) {
case FLASH_CFI_8BIT:
- retval = ((flash_read8(addr) & cword.c) !=
- (flash_read8(addr) & cword.c));
+ retval = flash_read8(addr) != flash_read8(addr);
break;
case FLASH_CFI_16BIT:
- retval = ((flash_read16(addr) & cword.w) !=
- (flash_read16(addr) & cword.w));
+ retval = flash_read16(addr) != flash_read16(addr);
break;
case FLASH_CFI_32BIT:
- retval = ((flash_read32(addr) & cword.l) !=
- (flash_read32(addr) & cword.l));
+ retval = flash_read32(addr) != flash_read32(addr);
break;
case FLASH_CFI_64BIT:
- retval = ((flash_read64(addr) & cword.ll) !=
- (flash_read64(addr) & cword.ll));
+ retval = flash_read64(addr) != flash_read64(addr);
break;
default:
retval = 0;
--
1.5.5.3
------------------------------
Message: 4
Date: Mon, 16 Jun 2008 10:58:54 +0200
From: Michal Simek <[EMAIL PROTECTED]>
Subject: Re: [U-Boot-Users] [PATCH 1/1] FAT Bare Partition Support
To: "Antonio R. Costa" <[EMAIL PROTECTED]>
Cc: u-boot-users@lists.sourceforge.net, "Antonio R. Costa"
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
Hi Antonio
I am not responsible for this part of U-BOOT but your patch contain coding style
violation.
Regards,
Michal Simek
> Logic unit:
> Purpose: Add support for bare partitions (no partition table)
> Author: Antnoio R. Costa <antonio.costa <at> atmel.com>
> Date : 11 Jun 2008
>
> Status:
> ~~~~~~
> Some SD cards are not formatted with a partition table but with
> just a bare partition at the beginnig of the memory.
>
> I modified get_partition_info_extended to call test_block_type
> as done by print_partition_extended. In this way bare FAT partitions
> are recognised. Now we need a test for Ext2.
>
> Signed-off-by: Antonio R. Costa <[EMAIL PROTECTED]>
>
> diff --git a/disk/part_dos.c b/disk/part_dos.c
> index 4d778ec..e5cc8aa 100644
> --- a/disk/part_dos.c
> +++ b/disk/part_dos.c
> @@ -1,4 +1,7 @@
> /*
> + * (C) Copyright 2008 Atmel Corp.
> + * Antonio R. Costa <antonio.costa <at> atmel.com>
> + * <costa.antonior <at> gmail.com>
choose only one email
> * (C) Copyright 2001
> * Raymond Lo, [EMAIL PROTECTED]
> * Wolfgang Denk, DENX Software Engineering, [EMAIL PROTECTED]
> @@ -53,6 +56,11 @@ static inline int le32_to_int(unsigned char *le32)
> );
> }
>
> +static inline int le16_to_int(unsigned char *le16)
> +{
> + return ((le16[1] << 8) + le16[0]);
> +}
> +
this should be in header file
> static inline int is_extended(int part_type)
> {
> return (part_type == 0x5 ||
> @@ -166,12 +174,20 @@ static int get_partition_info_extended
> (block_dev_desc_t *dev_desc, int ext_part
> unsigned char buffer[DEFAULT_SECTOR_SIZE];
> dos_partition_t *pt;
> int i;
> -
> +
Coding style issue.
> if (dev_desc->block_read (dev_desc->dev, ext_part_sector, 1, (ulong *)
> buffer) != 1) {
> printf ("** Can't read partition table on %d:%d **\n",
> dev_desc->dev, ext_part_sector);
> return -1;
> }
> +
> +/*
> + * ARC: This check is bad:
> + * unfortunately both MBR and FAT bootsector
> + * have a sign 0x55aa @ 0x1FF
> + * I replaced it by test_block_type as in
> + * print_partition_extended
> +
> if (buffer[DOS_PART_MAGIC_OFFSET] != 0x55 ||
> buffer[DOS_PART_MAGIC_OFFSET + 1] != 0xaa) {
> printf ("bad MBR sector signature 0x%02x%02x\n",
> @@ -179,7 +195,19 @@ static int get_partition_info_extended (block_dev_desc_t
> *dev_desc, int ext_part
> buffer[DOS_PART_MAGIC_OFFSET + 1]);
> return -1;
> }
> -
> +*/
> + i=test_block_type(buffer);
> +
> + if(i==-1) {
> + printf ("bad MBR sector signature 0x%02x%02x\n",
> + buffer[DOS_PART_MAGIC_OFFSET],
> + buffer[DOS_PART_MAGIC_OFFSET + 1]);
> + return -1;
> + }
> +
> + if(i==DOS_PBR)
> + return -1;
> +
> /* Print all primary/logical partitions */
> pt = (dos_partition_t *) (buffer + DOS_PART_TBL_OFFSET);
> for (i = 0; i < 4; i++, pt++) {
> @@ -193,6 +221,7 @@ static int get_partition_info_extended (block_dev_desc_t
> *dev_desc, int ext_part
> info->blksz = 512;
> info->start = ext_part_sector + le32_to_int
> (pt->start4);
> info->size = le32_to_int (pt->size4);
> +
> switch(dev_desc->if_type) {
> case IF_TYPE_IDE:
> case IF_TYPE_SATA:
> @@ -208,6 +237,13 @@ static int get_partition_info_extended (block_dev_desc_t
> *dev_desc, int ext_part
> case IF_TYPE_DOC:
> sprintf ((char *)info->name,
> "docd%c%d\n", 'a' + dev_desc->dev, part_num);
> break;
> + case IF_TYPE_MMC:
> + sprintf ((char *)info->name,
> "mmc%c%d\n", 'a' + dev_desc->dev, part_num);
> + break;
> + case IF_TYPE_SD:
> + case IF_TYPE_SDHC:
> + sprintf ((char *)info->name,
> "sd%c%d\n", 'a' + dev_desc->dev, part_num);
> + break;
> default:
> sprintf ((char *)info->name,
> "xx%c%d\n", 'a' + dev_desc->dev, part_num);
> break;
>
>
Regards,
Michal Simek
------------------------------
Message: 5
Date: Mon, 16 Jun 2008 12:22:04 +0200
From: Kenneth Johansson <[EMAIL PROTECTED]>
Subject: Re: [U-Boot-Users] U-Boot booting from NAND
To: Wolfgang Denk <[EMAIL PROTECTED]>
Cc: u-boot-users@lists.sourceforge.net
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
On Sat, 2008-06-14 at 23:50 +0200, Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]> you wrote:
> >
> > I ditched the entire reuse thing when I implemented nand boot for a
> > 5121e platform. 2k was to little space to try to force in the generic
> > files. just make a new start.S that do only the things it needs to.
>
> I seriously hope you based your code on the nand_spl/ frame work, so
> it has a chance to get merged into mainline, and I also hope you will
> post patches soon?
>
> Viele Gr??e,
>
> Wolfgang Denk
>
It is based on the nand boot support that existed for some 4xx boards.
The code is going to be made available in someway sometime but I do not
think that anyone will ever try to merge it into the mainline.
Maybe I will have some time between project to port the stuff over to
the ads5121 board but it's not going to be in near time.
------------------------------
Message: 6
Date: Mon, 16 Jun 2008 19:30:29 +0900
From: "Nobuhiro Iwamatsu" <[EMAIL PROTECTED]>
Subject: Re: [U-Boot-Users] Hi All
To: [EMAIL PROTECTED]
Cc: u-boot-users@lists.sourceforge.net
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
2008/6/16 harshadnimje <[EMAIL PROTECTED]>:
>
> For which peripherals I need to write the driver as far as U-boot is
> concerned?
1.Real time clock
Not Supported
2.Timer Unit
Supported
3.Bus state controller
Supported
4.DMA cotroller
Not Supported
5.Serial communication interface
Not Suported
6.I/O Ports
Supported
7.Interrupt controller
Not Supported
8.PCI conroller.
Supported. But check on SH7751R only.
> In generic U-Boot1.3.2 directory structure where do I need to make the
> change?
> At what places the config files and make files will have undergo
> changes?
>
You need create your board configration file and Bus state controller
initialization file(lowleve_init.S).
You can take a source code of r2d board into account.
This board has SH7751R cpu too.
board/r2dplus/*
Best reagards,
Nobuhiro
------------------------------
Message: 7
Date: Mon, 16 Jun 2008 19:51:29 +0900
From: "Nobuhiro Iwamatsu" <[EMAIL PROTECTED]>
Subject: [U-Boot-Users] How do work qemu_mips image?
To: u-boot-users@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
Hi, all.
I want to use MIPS archtechtute on Qemu.
I compiled qemu_mips and read doc/README.qemu_mips and was going
to work it, but U-boot boot stopped.
Is this right behavior?
Please give me advice to work a qemu_mips image on Qemu.
-------
U-boot version:
Get from Git tree ( hash:a94f22f08f280905926219e568568964cb9eeb9d)
use cross compiller:
$ mips-linux-gnu-gcc -v
Using built-in specs.
Target: mips-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,obj-c++ --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/mips-linux-gnu/include/c++/4.2.4
--program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug
--disable-libssp --enable-checking=release
--program-prefix=mips-linux-gnu-
--includedir=/usr/mips-linux-gnu/include --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=mips-linux-gnu
Thread model: posix
gcc version 4.2.4 (Debian 4.2.4-2)
use Qemu version:
0.9.1
U-boot log:
$ ln -s u-boot.bin mips_bios.bin
$ xps-iwamatsu(iwamatsu:)$ qemu-system-mips -L . /dev/null -nographic
U-Boot 1.3.3-00235-ga94f22f-dirty (Jun 16 2008 - 19:18:35)
Board: Qemu -M mips CPU: 24Kf proc_id=0x19300
DRAM: 128 MB
(stopped)
Best regards,
Nobuhiro
------------------------------
Message: 8
Date: Mon, 16 Jun 2008 16:25:09 +0530
From: "harshadnimje" <[EMAIL PROTECTED]>
Subject: Re: [U-Boot-Users] Hi All
To: "'Nobuhiro Iwamatsu'" <[EMAIL PROTECTED]>
Cc: u-boot-users@lists.sourceforge.net
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hi Nobuhiro;
Thanks for your support.
I am not able to see the /board/r2dplus/* in uboot directory stucture.
Can you please send me the link for this board specific source code.
Thanks in Advance
Regards;
Harshad
-----Original Message-----
From: Nobuhiro Iwamatsu [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2008 4:00 PM
To: [EMAIL PROTECTED]
Cc: u-boot-users@lists.sourceforge.net
Subject: Re: [U-Boot-Users] Hi All
Hi,
2008/6/16 harshadnimje <[EMAIL PROTECTED]>:
>
> For which peripherals I need to write the driver as far as U-boot is
> concerned?
1.Real time clock
Not Supported
2.Timer Unit
Supported
3.Bus state controller
Supported
4.DMA cotroller
Not Supported
5.Serial communication interface
Not Suported
6.I/O Ports
Supported
7.Interrupt controller
Not Supported
8.PCI conroller.
Supported. But check on SH7751R only.
> In generic U-Boot1.3.2 directory structure where do I need to make the
> change?
> At what places the config files and make files will have undergo
> changes?
>
You need create your board configration file and Bus state controller
initialization file(lowleve_init.S).
You can take a source code of r2d board into account.
This board has SH7751R cpu too.
board/r2dplus/*
Best reagards,
Nobuhiro
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments contained in it.
Contact your Administrator for further information.
------------------------------
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
------------------------------
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
End of U-Boot-Users Digest, Vol 25, Issue 133
*********************************************
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not
to copy, disclose, or distribute this e-mail or its contents to any other
person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has
taken
every reasonable precaution to minimize this risk, but is not liable for any
damage
you may sustain as a result of any virus in this e-mail. You should carry out
your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this
e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
