May 2007 - U-Boot

[U-Boot-Users] Changing memory for ixdp
by sapirf fersht 30 May '07

30 May '07

Hello Everyone I need some help regarding changing flash memory on a board that is based on ixdp-425. This is my first time with u-boot and i need to change the memory from 256Mb to 128Mb. How can i do it? Thanks in advance, Sapir

1 0

Re: [U-Boot-Users] OneNAND alternative to X-Load
by Kyungmin Park 30 May '07

30 May '07

Hi Pete Mackay, Before the main story, I explain the history of x-loader. First, it was designed for NAND boot from TI for their platforms. With simple code and similar structure of U-Boot, it's easy to modify for OneNAND. And at that time, we also considered another bootloader, of course, including U-Boot. So we released the X-loader for OneNAND as 1st bootloader. Now you want to add the 1KB bootloader (1st bootloader) for OneNAND at U-Boot. I think there's no problem except the handling of code position at OneNAND. The original handling of xloader is like this 1. The xloader (less than 1KB) loads u-boot image to DRAM using BufferRAM0. 2. Jump to DRAM address 3. run u-boot at DRAM 0x0000 (BootRAM0) __xloader_start --> load u-boot code to BufferRAM0 0x03fff __xloader_end 0x0400 (not valid) 0x0800 (BufferRAM0) used for xloader buffer ram --> u-boot code 0x0bff 0x0c00 (BufferRAM1) not used --> used for u-boot buffer ram 0x0fff But as you mentioned, you can make a u-boot.bin image with linker script handling. Overall structures are similar except that it's built with one time. Also you can find the similar idea at http://linuxdevices.com/articles/AT2779754250.html And please see the below comment. Thank you, Kyungmin Park > > We're developing a PXA-270-based machine that will boot from > OneNAND. I > wanted to share my ideas (and code) with anyone faced with > this challenge, > since this forum (esp. Kyungmin Park - thank you!!) was quite helpful. > I'll start off explaining my u-boot code, then when I get > some time I'll > submit my PXA-270 platform driver as a patch (currently works > on 2.6.18). > > We use a common approach: in lacking JTAG we have chip select > jumpers that > swap CS0/CS1 between NOR and OneNAND. The OneNAND has a > bottom-mapped 2K > boot buffer of which 1K is valid, which is where the level 1 > boot loader > fits. It uses two memory-mapped 'bufferrams' to ping-pong > data out of the > NAND pages, but you want to use BUFFERRAM1 only as writing > BUFFERRAM0 can > corrupt BOOTRAM0 on some revs of the chip. (We're executing out of > BOOTRAM0 so that's bad :). > > There is open-source code called "x-loader" that is a > stripped-down u-boot > for the level 1 boot loader. What I did was integrate the level 1 > function into u-boot itself with a custom configuration and > linker script. > In the top u-boot Makefile I added this: > > myboard_config : unconfig > @./mkconfig $(@:_config=) arm pxa myboard > > myboard_onenand_config : unconfig > @./mkconfig $(@:_config=) arm pxa myboard > @echo "LDSCRIPT := > $(TOPDIR)/board/myboard/u-boot.onenand.lds" >> > include/config.mk > > In include/configs/myboard_onenand.h I simply define > CONFIG_BOOT_ONENAND > and then include myboard.h, with conditional switches inside for base > address, etc (i.e. define CONFIG_IDENT_STRING as " from > OneNAND" or " from > NOR"). > > The linker script replaces cpu/pxa/start.S with oneboot.S and > makes sure > the C code to load the other pages positions there too. Then > it aligns > the rest of u-boot at the 2K boundary (NAND page 1). The > oneboot.S code > melds start.S with lowlevel_init but calls C code to read the > rest of the > block 0 pages into RAM. I later optimized it to replace > start.S entirely > for the NOR version. > > BTW, I lacked originality and stole (liked) the name: oneboot > is not to be > confused with the script that merges x-load and u-boot into one binary > image. > > This is the relevant portion of the u-boot linker script: > > . = 0x00000000; > > . = ALIGN(4); > .text : > { > board/myboard/oneboot.o (.text) > board/myboard/onenand_boot.o (.text) The onenand_boot.c is common code for all platforms. I think it's located in drivers/onenand or onenand_spl as nand_spl in U-Boot. Yes I know the OneNAND patch for U-Boot is not merged yet. In this code, however, there's no problem to boot with OneNAND. > __oneboot_end = .; /* must not exceed 0x400! */ > > . = 0x800; /* reposition to 2K page boundary */ > __page1_start = .; /* OneNAND loading starts here */ > * (.text) > } > > Look at System.map to make sure your level 1 code fits within > 1K. Also in > oneboot.S I commented out labels and used relative branches > to save symbol > space and replaced ldr with mov wherever possible. And with the 270 > optimizations in oneboot.S our system screams! > > The full code is at http://code.architechnical.net/onenand, > including the > 2.6.18 pxa27x OneNAND driver. Please don't laugh at my lame > ancient web > site. > > > > ______________________________________________________ > Linux MTD discussion mailing list > http://lists.infradead.org/mailman/listinfo/linux-mtd/ > >

1 0

[U-Boot-Users] Effect of Large flash memories
by Ulf Samuelsson 30 May '07

30 May '07

I think when we do a new interface we need to look at how we handle situations where the flash is much larger than the SDRAM. It is conceivable that you would want to copy a 300 MB JFFS2 file system from a USB key to internal NAND flash in a system which only has 64-128 MB of SDRAM. An explicit command loop to do this is IMHO too complex and error prone. A command which copies between different storage locations is therefore desirable. (It would need intermediate SDRAM buffers) -- Best Regards, Ulf Samuelsson

1 0

[U-Boot-Users] [PATCH] cosmetic changes to the 5704 driver
by Vadim Bendebury 30 May '07

30 May '07

This is a purely cosmetic change, it does not introduce any generated code changes, done to allow for coding standards compliant driver modifications in the future. The patch is too large, posted right here: http://www.vsbe.com/u-boot/patch.txt -- Vadim Bendebury Platforms SW - (650) 253-7486 - mailto:vbendeb@google.com

2 3

[U-Boot-Users] loads command is not working
by Vaibhav Hiremath 29 May '07

29 May '07

Hi All, Can anyone tell me how to test loads command? I have tested loadb and loady command, and they are working fine. While testing loads uboot console only displays message "Ready for loading s-record file" but doing nothing. I think I am testing this command with wrong procedure, I hav used hyperterminal to test loadb and loady commands. So please guide me to test this out. Thanks in advance. Thanks, Vaibhav

6 10

[U-Boot-Users] How to reduce the U-boot image size?
by jack 29 May '07

29 May '07

Hi all: I remove most of commands form u-boot, after I entering bootloader type ?, I can see the command are much less. But why does the size of u-boot.bin still the same, basically it shall be smaller right? I already change the variable "CFG_MONITOR_LEN" and "UBOOT_IMAGE_SIZE" but not working. Can anybody tell me how to make a smaller u-boot image and what variables shall I modify, thanks a lot. jack

1 0

[U-Boot-Users] RAM version of U-Boot
by Midhun Agnihotram 29 May '07

29 May '07

Hi All, I am pretty new to U-boot and the embedded world too. I have a kit with an ARM 926EJ-S based processor and Micromonitor as the boot loader. But we are facing some problems with Micromonitor. So we would like to change it. U-boot seems be a very good option. But I would like to test out my applications on U-boot before I burn it on to the flash. So can U-boot be made as an application ?? So that I can load it into RAM and then run my application without loosing Micromonitor?? Thanks a lot, Midhun Agnihotram.

2 1

[U-Boot-Users] mixup
by maarten 28 May '07

28 May '07

ok my fault, when clicking the downoad I got a .bin, witch I supposed was a binary file of some sort, but after renaming it to .gz and unpacking it, all apears well.

1 0

[U-Boot-Users] [PATCH] LOGO: All logos must be placed into the "logos" directory.
by Rodolfo Giometti 28 May '07

28 May '07

Signed-off-by: Rodolfo Giometti <giometti(a)linux.it> --- tools/Makefile | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/Makefile b/tools/Makefile index 6177f90..14eedf0 100644 --- a/tools/Makefile +++ b/tools/Makefile @@ -40,7 +40,7 @@ endif LOGO_H = $(OBJTREE)/include/bmp_logo.h ifeq ($(LOGO_BMP),) -LOGO_BMP= logos/denx.bmp +LOGO_BMP= denx.bmp endif #------------------------------------------------------------------------- @@ -203,8 +203,8 @@ $(obj)crc32.c: @rm -f $(obj)crc32.c ln -s $(src)../lib_generic/crc32.c $(obj)crc32.c -$(LOGO_H): $(obj)bmp_logo $(LOGO_BMP) - $(obj)./bmp_logo $(LOGO_BMP) >$@ +$(LOGO_H): $(obj)bmp_logo logos/$(LOGO_BMP) + $(obj)./bmp_logo logos/$(LOGO_BMP) >$@ ######################################################################### -- 1.5.1.1

3 7

Re: [U-Boot-Users] U-Boot-Users Digest, Vol 12, Issue 98
by 白栋贤 28 May '07

28 May '07

Sorry, I forgeted to check its formatting before sending last mail. My board's info as following: 1 CPU: PXA270 2 SDRAM :0xA0000000 - 0xA4000000 64M 3 BOOT: nCS<0> CODE: 0x00000000 4 FFUART GPIO34 FFRXD GPIO35 FFCTS GPIO36 FFDCD GPIO37 FFDSR GPIO38 FFRI GPIO39 FFTXD GPIO40 FFDTR GPIO41 FFRTS As I'm a newer to uboot and PXA270, so in my opine, after patched the uboot114 directory, I just need to modify the mainstone.h to fit my board. But I failed. Then after compared with start.S for other cpus such as ixp, I found that the reset code are very similar to each other. At first I doubted about the reset code, so I modified start.S and lowlevel_Init.S with the start code of blob. But I failed yet. Could you possible give me some suggestion? Thank you very much. Best regards John> From: u-boot-users-request(a)lists.sourceforge.net> Subject: U-Boot-Users Digest, Vol 12, Issue 98> To: u-boot-users(a)lists.sourceforge.net> Date: Fri, 25 May 2007 07:29:03 -0700> > Send U-Boot-Users mailing list submissions to> u-boot-users(a)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> u-boot-users-request(a)lists.sourceforge.net> > You can reach the person managing the list at> u-boot-users-owner(a)lists.sourceforge.net> > 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: Imminent u-boot-fdt pull request (Jerry Van Baren)> 2. Abour JFFS2 commands (Vaibhav Hiremath)> 3. Re: Abour JFFS2 commands (Ladislav Michl)> 4. [PATCH] Fix ppc4xx bootstrap letter displayed on startup> (Benoit Monin)> 5. Re: [RFC] logos directory & default logo (Rodolfo Giometti)> 6. [PATCH] LOGO: All logos must be placed into the "logos"> directory. (Rodolfo Giometti)> 7. [PATCH] LOGO: Allow define "LOGO_BMP" to be globally defined.> (Rodolfo Giometti)> 8. Re: [PATCH] LOGO: All logos must be placed into the "logos"> directory. (Wolfgang Denk)> 9. Re: [PATCH] LOGO: Allow define "LOGO_BMP" to be globally> defined. (Wolfgang Denk)> > > ----------------------------------------------------------------------> > Message: 1> Date: Fri, 25 May 2007 07:54:47 -0400> From: Jerry Van Baren <gerald.vanbaren(a)smiths-aerospace.com>> Subject: Re: [U-Boot-Users] Imminent u-boot-fdt pull request> To: Kim Phillips <kim.phillips(a)freescale.com>> Cc: u-boot-users(a)lists.sourceforge.net> Message-ID: <4656CE87.8080200(a)smiths-aerospace.com>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed> > Kim Phillips wrote:> > On Tue, 22 May 2007 00:06:06 -0400> > Jerry Van Baren <gvb.uboot(a)gmail.com> wrote:> > > >> Dear all,> >>> >> Please review the u-boot-fdt changes. I intend to request Wolfgang pull > >> the pending changes soon. All of the changes (except the last trivial > > > > I have properties being placed at the wrong level, timebase- and> > bus-frequencies not being updated, there are multiple copies of the> > code, and, it is hard to read - I saw a line length of 139!> > > > Please work on your CodingStyle. I haven't finished debugging here.> > > > Kim> > Hi Kim,> > Thanks for the feedback, I'll check things. Pointers to files (and > lines) would be helpful. :-/> > WRT line lengths, Wolfgang dinged me on them so I created a cleanup > patch. As a result, one patch has line length violations and a later > patch fixes them. This may be related to your line length and multiple > copy comment.> > Thanks,> gvb> > > > ------------------------------> > Message: 2> Date: Fri, 25 May 2007 17:41:01 +0530> From: "Vaibhav Hiremath" <hvaibhav(a)gmail.com>> Subject: [U-Boot-Users] Abour JFFS2 commands> To: u-boot-users(a)lists.sourceforge.net> Message-ID:> <fde666620705250511l1c5002fcy5a312f19f4423552(a)mail.gmail.com>> Content-Type: text/plain; charset="iso-8859-1"> > Hi All,> > How many JFFS commands uboot supports?> > Actually,> I have ported UBoot for ARM1176 CPU, and I am using Intel NOR Flash.> After mounting JFFS2 on to Flash memory I am able to see only "fsinfo" and> "ls" command only.> > There should be rm, cd, etc.. commands. Is I am missing something?> > Thanks in advance.> > Thanks,> Vaibhav> -------------- next part --------------> An HTML attachment was scrubbed...> > ------------------------------> > Message: 3> Date: Fri, 25 May 2007 14:22:56 +0200> From: Ladislav Michl <ladis(a)linux-mips.org>> Subject: Re: [U-Boot-Users] Abour JFFS2 commands> To: Vaibhav Hiremath <hvaibhav(a)gmail.com>> Cc: u-boot-users(a)lists.sourceforge.net> Message-ID: <20070525122256.GA10916(a)michl.2n.cz>> Content-Type: text/plain; charset="us-ascii"> > On Fri, May 25, 2007 at 05:41:01PM +0530, Vaibhav Hiremath wrote:> > Hi All,> > > > How many JFFS commands uboot supports?> > > > Actually,> > I have ported UBoot for ARM1176 CPU, and I am using Intel NOR Flash.> > After mounting JFFS2 on to Flash memory I am able to see only "fsinfo" and> > "ls" command only.> > > > There should be rm, cd, etc.. commands. Is I am missing something?> > jffs2 is read-only in u-boot, there fore there is no 'rm' command.> Change directory is not implemented. The only command are:> fsinfo, fsload and ls (it takes agrument: directory to list files in)> > Best regards,> ladis> > > > > ------------------------------> > Message: 4> Date: Fri, 25 May 2007 14:56:05 +0200> From: "Benoit Monin" <benoit.monin(a)laposte.net>> Subject: [U-Boot-Users] [PATCH] Fix ppc4xx bootstrap letter displayed> on startup> To: "wd" <wd(a)denx.de>> Cc: u-boot-users <u-boot-users(a)lists.sourceforge.net>> Message-ID: <JILL9H$2EBD6CBE5F7929B929E9F4475080EFCD(a)laposte.net>> Content-Type: text/plain; charset="iso-8859-1"> > The attached patch is mainly cosmetic, allowing u-boot to> display the correct bootstrap option letter according to the> datasheets.> > Signed-off-by: Beno?t Monin <bmonin <at> adeneo.eu>> ---> The patch is against U-Boot 1.2.0.> > --> > > Cr?ez votre adresse ?lectronique prenom.nom(a)laposte.net > 1 Go d'espace de stockage, anti-spam et anti-virus int?gr?s.> -------------- next part --------------> A non-text attachment was scrubbed...> Name: fix_ppc4xx_bootstrap_letter.patch> Type: text/x-patch> Size: 1511 bytes> Desc: not available> > ------------------------------> > Message: 5> Date: Fri, 25 May 2007 15:26:13 +0200> From: Rodolfo Giometti <giometti(a)enneenne.com>> Subject: Re: [U-Boot-Users] [RFC] logos directory & default logo> To: u-boot-users(a)lists.sourceforge.net> Message-ID: <20070525132610.GC4199(a)enneenne.com>> Content-Type: text/plain; charset=us-ascii> > On Thu, May 24, 2007 at 04:34:57PM +0200, Rodolfo Giometti wrote:> > > > I'd like to modify the logo support. Currently I notice that there are> > only one logo file into "u-boot/tools/logos", however I think is> > About this topic I suppose is better define a "default" logo. My idea> is to leave to the developer the ability to specify its preferre logo> as follow:> > wwpc1100_config : unconfig> @$(MKCONFIG) $(@:_config=) arm pxa wwpc1100> @echo "LOGO_BMP = wwpc1100.bmp" >> include/config.mk> > if no LOGO_BMP is specified then the system uses a "default" logo> which can still be the "denx.bmp".> > Comments?> > Rodolfo> > -- > > GNU/Linux Solutions e-mail: giometti(a)enneenne.com> Linux Device Driver giometti(a)gnudd.com> Embedded Systems giometti(a)linux.it> UNIX programming phone: +39 349 2432127> > > > ------------------------------> > Message: 6> Date: Fri, 25 May 2007 16:20:01 +0200> From: Rodolfo Giometti <giometti(a)linux.it>> Subject: [U-Boot-Users] [PATCH] LOGO: All logos must be placed into> the "logos" directory.> To: u-boot-users(a)lists.sourceforge.net> Message-ID: <20070525142001.GD4199(a)enneenne.com>> Content-Type: text/plain; charset=us-ascii> > Signed-off-by: Rodolfo Giometti <giometti(a)linux.it>> ---> tools/Makefile | 6 +++---> 1 files changed, 3 insertions(+), 3 deletions(-)> > diff --git a/tools/Makefile b/tools/Makefile> index 6177f90..14eedf0 100644> --- a/tools/Makefile> +++ b/tools/Makefile> @@ -40,7 +40,7 @@ endif> LOGO_H = $(OBJTREE)/include/bmp_logo.h> > ifeq ($(LOGO_BMP),)> -LOGO_BMP= logos/denx.bmp> +LOGO_BMP= denx.bmp> endif> > #-------------------------------------------------------------------------> @@ -203,8 +203,8 @@ $(obj)crc32.c:> @rm -f $(obj)crc32.c> ln -s $(src)../lib_generic/crc32.c $(obj)crc32.c> > -$(LOGO_H): $(obj)bmp_logo $(LOGO_BMP)> - $(obj)./bmp_logo $(LOGO_BMP) >$@> +$(LOGO_H): $(obj)bmp_logo logos/$(LOGO_BMP)> + $(obj)./bmp_logo logos/$(LOGO_BMP) >$@> > #########################################################################> > -- > 1.5.1.1> > > > > ------------------------------> > Message: 7> Date: Fri, 25 May 2007 16:20:55 +0200> From: Rodolfo Giometti <giometti(a)linux.it>> Subject: [U-Boot-Users] [PATCH] LOGO: Allow define "LOGO_BMP" to be> globally defined.> To: u-boot-users(a)lists.sourceforge.net> Message-ID: <20070525142054.GE4199(a)enneenne.com>> Content-Type: text/plain; charset=us-ascii> > This allow developers to define per board logo file into main configuration> file as follow:> > wwpc1100_config : unconfig> @$(MKCONFIG) $(@:_config=) arm pxa wwpc1100> @echo "LOGO_BMP = wwpc1100.bmp" >> include/config.mk> > Signed-off-by: Rodolfo Giometti <giometti(a)linux.it>> ---> Makefile | 4 ++--> 1 files changed, 2 insertions(+), 2 deletions(-)> > diff --git a/Makefile b/Makefile> index 093df4e..c819afb 100644> --- a/Makefile> +++ b/Makefile> @@ -115,7 +115,7 @@ ifeq ($(OBJTREE)/include/config.mk,$(wildcard $(OBJTREE)/include/config.mk))> > # load ARCH, BOARD, and CPU configuration> include $(OBJTREE)/include/config.mk> -export ARCH CPU BOARD VENDOR SOC> +export ARCH CPU BOARD VENDOR SOC LOGO_BMP> > ifndef CROSS_COMPILE> ifeq ($(HOSTARCH),ppc)> @@ -125,7 +125,7 @@ ifeq ($(ARCH),ppc)> CROSS_COMPILE = powerpc-linux-> endif> ifeq ($(ARCH),arm)> -CROSS_COMPILE = arm-eurotech-linux-> +CROSS_COMPILE = arm-linux-> endif> ifeq ($(ARCH),i386)> ifeq ($(HOSTARCH),i386)> -- > 1.5.1.1> > > > > ------------------------------> > Message: 8> Date: Fri, 25 May 2007 16:26:04 +0200> From: Wolfgang Denk <wd(a)denx.de>> Subject: Re: [U-Boot-Users] [PATCH] LOGO: All logos must be placed> into the "logos" directory.> To: Rodolfo Giometti <giometti(a)linux.it>> Cc: u-boot-users(a)lists.sourceforge.net> Message-ID: <20070525142604.C486C352B1F(a)atlas.denx.de>> Content-Type: text/plain; charset=ISO-8859-1> > In message <20070525142001.GD4199(a)enneenne.com> you wrote:> >> > Subject: ... All logos must be placed into the "logos" directory.> > Why?> > > ifeq ($(LOGO_BMP),)> > -LOGO_BMP= logos/denx.bmp> > +LOGO_BMP= denx.bmp> > Which problem is this supposed to fix? I don't see any advantage, but> I see the disadvantage that with your patch you cannot chose to place> your logo - say - in board/.../ any more.> > Best regards,> > Wolfgang Denk> > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de> Landing: a controlled mid-air collision with a planet.> > > > ------------------------------> > Message: 9> Date: Fri, 25 May 2007 16:29:13 +0200> From: Wolfgang Denk <wd(a)denx.de>> Subject: Re: [U-Boot-Users] [PATCH] LOGO: Allow define "LOGO_BMP" to> be globally defined.> To: Rodolfo Giometti <giometti(a)linux.it>> Cc: u-boot-users(a)lists.sourceforge.net> Message-ID: <20070525142913.0675C352B1F(a)atlas.denx.de>> Content-Type: text/plain; charset=ISO-8859-1> > In message <20070525142054.GE4199(a)enneenne.com> you wrote:> > This allow developers to define per board logo file into main configuration> > file as follow:> > > > wwpc1100_config : unconfig> > @$(MKCONFIG) $(@:_config=) arm pxa wwpc1100> > @echo "LOGO_BMP = wwpc1100.bmp" >> include/config.mk> > I don't like this. This adds configuration information into Makefile,> where it does not belong.> > Please don't do this.> > > > --- a/Makefile> > +++ b/Makefile> > @@ -115,7 +115,7 @@ ifeq ($(OBJTREE)/include/config.mk,$(wildcard $(OBJTREE)/include/config.mk))> ...> > @@ -125,7 +125,7 @@ ifeq ($(ARCH),ppc)> > CROSS_COMPILE = powerpc-linux-> > endif> > ifeq ($(ARCH),arm)> > -CROSS_COMPILE = arm-eurotech-linux-> ^^^^^^^^^^^^^^^^^^^ What's that?> > +CROSS_COMPILE = arm-linux-> > Also, this patch does not apply.> > Best regards,> > Wolfgang Denk> > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de> "Just think of a computer as hardware you can program."> - Nigel de la Tierre> > > > ------------------------------> > -------------------------------------------------------------------------> This SF.net email is sponsored by DB2 Express> Download DB2 Express C - the FREE version of DB2 express and take> control of your XML. No limits. Just data. Click to get it now.> http://sourceforge.net/powerbar/db2/> > ------------------------------> > _______________________________________________> U-Boot-Users mailing list> U-Boot-Users(a)lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/u-boot-users> > > End of U-Boot-Users Digest, Vol 12, Issue 98> ******************************************** _________________________________________________________________ 探索 Windows Vista 的世界 http://search.live.com/results.aspx?q=windows+vista&mkt=zh-cn&FORM=LIVSOP

1 0

[U-Boot-Users] FW: RE: about the softgun
by MPE Visitor MPEV4 27 May '07

27 May '07

Hi everyone, I set the bootargs root=/dev/mtdblock/2 rw mem=64M But when boot the kernel, it seems not working that show NULL As below Any one can help me? Joe Uncompressing Linux................................................................ done, booting the kernel. Starting kernel............. Linux version 2.4.20-mx2bsp, BSP version mx21_to3_rel_3.2 - (root@joenote) (gcc version 3.2.3) #164 Sun May 27 22:12:33 CST 2007 Processor: ARM ARM926EJ-Ssid(wb) revision 4 Architecture: Freescale MX2ADS Command line is :<NULL> On node 0 totalpages: 12288 zone(0): 12288 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line:

2 1

[U-Boot-Users] How I can write testing for the SDRAM in PPC in UBOOT source
by hamid khateb 27 May '07

27 May '07

Hi How I can write testing for the SDRAM in PPC in UBOOT source best regards hamid _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 1

[U-Boot-Users] what's the problem?
by MPE Visitor MPEV4 27 May '07

27 May '07

Hi everyone, I'm working on a mx21ads like board and have ported u-boot-1.1.4 to it. When I boot my linux 2.4.20 on it, it seems not working so better. The messages are as below 1. Firstly, I think my initialize is not complete, but the older bootloader run in my u-boot Without initialize (I recommend all code, just remain the boot kernel code) can boot the Same linux kernel yet! The messages are as below 2. So, what's the problem? Thanks Joe 1. <Information from my termitate> Filename 'image.bootm'. Load address: 0xc3000000 Loading: ################################################################# ################################################################# ########################################################### done Bytes transferred = 966136 (ebdf8 hex) # bootm c3000000 ## Booting image at c3000000 ... Image Name: image Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 966072 Bytes = 943.4 kB Load Address: c0008000 Entry Point: c0008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux............................................................. .... done, booting the kernel. 2. # tftp c3000000 bootloader.bin TFTP from server 172.20.40.68; our IP address is 172.20.40.69 Filename 'bootloader.bin'. Load address: 0xc3000000 Loading: ########## done Bytes transferred = 46656 (b640 hex) # go c3000400 DBMX21 Linux Bootloader ver mx21_to2_rel_beta_1.0 Copyright (C) 2003 Freescale Semiconductors Suzhou Ltd. root=/dev/mtdblock/2 rw mem=64M MPLL = 266, FCLK = 266, BCLK = 133 Press any key for alternate boot-up options ... 07 Copying kernel from Flash to RAM ... Booting kernel ... Uncompressing Linux............................................................. .... done, booting the kernel. Starting kernel............. Linux version 2.4.20-mx2bsp, BSP version mx21_to3_rel_3.2 - (root(a)localhost.loca ldomain) (gcc version 3.2.3) #122 Fri Mar 24 01:58:09 ACT 2006 Processor: ARM ARM926EJ-Ssid(wb) revision 4 Architecture: Freescale MX2ADS root=/dev/mtdblock/2 rw mem=64M MPLL = 266, FCLK = 266, BCLK = 133 Press any key for alternate boot-up options ... 00 Copying kernel from Flash to RAM ... Booting kernel ... Uncompressing Linux............................................................. .... done, booting the kernel. Starting kernel............. Linux version 2.4.20-mx2bsp, BSP version mx21_to3_rel_3.2 - (root(a)localhost.loca ldomain) (gcc version 3.2.3) #122 Fri Mar 24 01:58:09 ACT 2006 Processor: ARM ARM926EJ-Ssid(wb) revision 4 Architecture: Freescale MX2ADS Command line is :root=/dev/mtdblock/2 rw mem=64M On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/mtdblock/2 rw mem=64M Console: colour dummy device 80x30 Calibrating delay loop...

2 1

[U-Boot-Users] How I can write testing for the SDRAM in PPC in UBOOT source
by hamid khateb 27 May '07

27 May '07

Hi How I can write testing for the SDRAM in PPC in UBOOT source best regards hamid _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

1 0

[U-Boot-Users] [PATCH] LOGO: Allow define "LOGO_BMP" to be globally defined.
by Rodolfo Giometti 26 May '07

26 May '07

This allow developers to define per board logo file into main configuration file as follow: wwpc1100_config : unconfig @$(MKCONFIG) $(@:_config=) arm pxa wwpc1100 @echo "LOGO_BMP = wwpc1100.bmp" >> include/config.mk Signed-off-by: Rodolfo Giometti <giometti(a)linux.it> --- Makefile | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 093df4e..c819afb 100644 --- a/Makefile +++ b/Makefile @@ -115,7 +115,7 @@ ifeq ($(OBJTREE)/include/config.mk,$(wildcard $(OBJTREE)/include/config.mk)) # load ARCH, BOARD, and CPU configuration include $(OBJTREE)/include/config.mk -export ARCH CPU BOARD VENDOR SOC +export ARCH CPU BOARD VENDOR SOC LOGO_BMP ifndef CROSS_COMPILE ifeq ($(HOSTARCH),ppc) @@ -125,7 +125,7 @@ ifeq ($(ARCH),ppc) CROSS_COMPILE = powerpc-linux- endif ifeq ($(ARCH),arm) -CROSS_COMPILE = arm-eurotech-linux- +CROSS_COMPILE = arm-linux- endif ifeq ($(ARCH),i386) ifeq ($(HOSTARCH),i386) -- 1.5.1.1

3 6

[U-Boot-Users] [PATCH libfdt 0/3] Fix CONFIG_OF_LIBFDT problems discussed yesterday
by Jerry Van Baren 26 May '07

26 May '07

Hi Kim et al. I dug into the CONFIG_OF_LIBFDT issue discussed 2007-05-25 and it turns out that my guess that OF_CPU was undefined was wrong. The problem was actually errors in my adapting of the original code to LIBFDT. This is a 3x patch set, the first two patches fix the problems that Kim noted and the third is a related clean up of cmd_bootm.c An explanation of what when wrong, starting with some historical background: the original CONFIG_OF_FLAT_TREE has a utility routine ft_setup() which it calls just before booting the linux kernel. This routine does some significant modifications to the fdt blob and then starts the kernel. The only way to see what it did to the fdt was to uncomment a fdt printout call which dumped the blob out the console and then started the kernel. NOT friendly. With the libfdt utilities and the "fdt" command, I modified this rather nasty behavior to give the user the ability to do the modifications of the fdt blob at the command line, observe what was done, hand edit it, and _then_ boot linux. Much friendlier. In order to do this, I had to break up what ft_setup() was doing in one unobservable step into three functions, fdt_chosen(), fdt_env(), and fdt_bd_t() which I then was able to invoke for the "fdt chosen", "fdt env", and "fdt bd_t" commands. There also is a ft_board() utility (which potentially calls ft_cpu_setup() and ft_pci_setup() functions) that does (board, CPU, PCI)-specific fdt fixups. I adapted the versions used by the MPC8360EMDS (the board I have) to use libfdt. So far, so good. The problem was that, in my adaption (breaking up) of ft_setup(), I missed the call to ft_board() and thus the (board, CPU, PCI)-specific fdt modifications were not done. IIRC, factoring into this omision was the fact that ft_setup() does /some/ of the CPU-specific modifications itself (improperly IMHO). This confused me and I made two errors: 1) I didn't call ft_board() to properly do the (board, CPU, PCI)-specific modifications and, worse, 2) I adapted the (misplaced IMHO) duplicated fdt modifications INCORRECTLY. This is why/where "clock-frequency" was incorrectly set as "/cpu/clock-frequency" instead of "/cpu/PowerPC,8360@0/clock-frequency" (I lost the OF_CPU part of the node path when I did the adaption). Once I figured out my errors (above), I changed fdt_chosen() to remove the erroneous sets and, instead, call ft_board() to properly set the (board, CPU, PCI)-specific fdt values. This turned up some errors in the table fixup_props[] property strings: I had some trailing "/"s on node paths and some node paths still had the property name appended. Sloppy coding that makes me ashamed to have my --signed-off-by on. :-( Because of my other errors (previous paragraph), these functions were never called and thus I did not detect the errors in my testing. :-( Anyway, this above novelette could have been more concisely written "I'm sorry and ashamed, please accept the following patches as an indication of my resolve to be more thorough in the future." Best regards, gvb

1 0

[U-Boot-Users] Imminent u-boot-fdt pull request
by Jerry Van Baren 25 May '07

25 May '07

Dear all, Please review the u-boot-fdt changes. I intend to request Wolfgang pull the pending changes soon. All of the changes (except the last trivial patch "For fdt_find_node_by_path(), handle the root path properly.") have been previously published to the list. The following changes are pending: libfdt: Conditionally compile based on CONFIG_OF_LIBFDT <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=6b…> Improve error messages, more informative. <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=5a…> Minor code clean up. <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=19…> Improve fdt move length handling. <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=4b…> Fix bugs in the CONFIG_OF_LIBFDT <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=3c…> Reorganize and fix problems (returns) in the bootm command. <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=74…> FDT command improvements. <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=f2…> Fix cmd_fdt line lengths, refactor code. <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=79…> Replace fdt_node_offset() with fdt_find_node_by_path(). <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=5e…> Add fdt_find_node_by_type() and fdt_find_compatible_node() to LIBFDT <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=ef…> For fdt_find_node_by_path(), handle the root path properly. <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=cd…> Best regards, gvb

7 18

[U-Boot-Users] dataflash broken on at91sam9260ek
by Jonathan Kotta 25 May '07

25 May '07

Hello, I have a at91sam9260ek with a DataFlash on CS1. It seems like U-boot is detecting the flash, but it is not working properly. I uncommented the printf()s in drivers/dataflash.c, and I think it has something to do with how it's configuring the partitions. The "found * dataflash" lines are printf()s I put in the first switch statement of AT91F_DataflashInit(). I am using U-Boot 1.2.0 within Ulf's buildroot. found no dataflash found AT45DB642 dataflash Start=C0000000, End (computed)=C0000000, To: , From: Data To: Data, From: Data Start=BFFFFFFF, End=C0000000, Invalid To: , From: <Invalid> To: <Invalid>, From: <Invalid> Start=BFFFFFFF, End=C0000000, Invalid To: , From: <Invalid> To: <Invalid>, From: <Invalid> Start=BFFFFFFF, End=C0000000, Invalid To: , From: <Invalid> To: <Invalid>, From: <Invalid> Start=BFFFFFFF, End=C0000000, Invalid To: , From: <Invalid> To: <Invalid>, From: <Invalid> Start=BFFFFFFF, End=C0000000, Invalid To: , From: <Invalid> To: <Invalid>, From: <Invalid> -- Thanks, Jonathan Kotta Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law.

1 1

[U-Boot-Users] [PATCH] remove #ifdef maze from stand alone program support
by Jeffrey Mann 25 May '07

25 May '07

[PATCH] update stand alone program support to remove #ifdef maze Based upon an idea by Håvard Skinnemoen <hskinnemoen(a)gmail.com>, the #if-def maze in the initialization of the jumptable for stand alone programs has been removed. Signed-off-by: Jeffrey Mann <mannj(a)embeddedplanet.com> ------ Could someone else please check this patch and ack it? Documentation updates will follow.

1 0

[U-Boot-Users] [PATCH] PXAFB: Adds 16bits color depth support.
by Rodolfo Giometti 25 May '07

25 May '07

Signed-off-by: Rodolfo Giometti <giometti(a)linux.it> --- cpu/pxa/pxafb.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/cpu/pxa/pxafb.c b/cpu/pxa/pxafb.c index b2caa73..cd529e3 100644 --- a/cpu/pxa/pxafb.c +++ b/cpu/pxa/pxafb.c @@ -148,7 +148,7 @@ vidinfo_t panel_info = { /*----------------------------------------------------------------------*/ -#if LCD_BPP == LCD_COLOR8 +#if LCD_BPP == LCD_COLOR8 || LCD_BPP == LCD_COLOR16 void lcd_setcolreg (ushort regno, ushort red, ushort green, ushort blue); #endif #if LCD_BPP == LCD_MONOCHROME @@ -200,7 +200,7 @@ lcd_getcolreg (ushort regno, ushort *red, ushort *green, ushort *blue) #endif /* NOT_USED_SO_FAR */ /*----------------------------------------------------------------------*/ -#if LCD_BPP == LCD_COLOR8 +#if LCD_BPP == LCD_COLOR8 || LCD_BPP == LCD_COLOR16 void lcd_setcolreg (ushort regno, ushort red, ushort green, ushort blue) { @@ -225,7 +225,7 @@ lcd_setcolreg (ushort regno, ushort red, ushort green, ushort blue) red, green, blue, palette[regno]); } -#endif /* LCD_COLOR8 */ +#endif /* LCD_COLOR8 || LCD_BPP == LCD_COLOR16 */ /*----------------------------------------------------------------------*/ #if LCD_BPP == LCD_MONOCHROME -- 1.5.1.1

1 0

[U-Boot-Users] [RFC] logos directory
by Rodolfo Giometti 25 May '07

25 May '07

Hello, I'd like to modify the logo support. Currently I notice that there are only one logo file into "u-boot/tools/logos", however I think is better move each board's logo into itsown directories. So, for example, if "foo" board wants to use the "foo.bmp" logo it should add this file into "u-boot/board/foo" directory. Comments? :) Rodolfo -- GNU/Linux Solutions e-mail: giometti(a)enneenne.com Linux Device Driver giometti(a)gnudd.com Embedded Systems giometti(a)linux.it UNIX programming phone: +39 349 2432127

2 3

[U-Boot-Users] Abour JFFS2 commands
by Vaibhav Hiremath 25 May '07

25 May '07

Hi All, How many JFFS commands uboot supports? Actually, I have ported UBoot for ARM1176 CPU, and I am using Intel NOR Flash. After mounting JFFS2 on to Flash memory I am able to see only "fsinfo" and "ls" command only. There should be rm, cd, etc.. commands. Is I am missing something? Thanks in advance. Thanks, Vaibhav

2 1

[U-Boot-Users] [PATCH] ARM Versatile PB926EJ-S, Rev.D: Added support for flash 28F256L30B, Resend
by Josef Meser 25 May '07

25 May '07

Current u-boot works with ARM Versatile PB926EJ-S, HW- Rev.C (NOR flash 28F256K3). This patch adds support for 28F256L30B (asymmetrical sectors: 4 small sectors at bottom) used on HW-Rev.D. Resend: patch was line wrapped. This patch might be obsolete because of CFI flash driver: http://sourceforge.net/mailarchive/forum.php?thread_name=000201c79ea4%24be3… Signed-off-by: Josef Meser <josef.meser(a)odm.at> --- board/versatile/flash.c | 84 +++++++++++++++++++++++++++++++++++-------- include/configs/versatile.h | 2 +- include/flash.h | 10 ++++-- 3 files changed, 77 insertions(+), 19 deletions(-) diff --git a/board/versatile/flash.c b/board/versatile/flash.c index 7153371..b79761f 100644 --- a/board/versatile/flash.c +++ b/board/versatile/flash.c @@ -31,7 +31,9 @@ #include <common.h> #include <linux/byteorder/swab.h> -#define PHYS_FLASH_SECT_SIZE 0x00020000 /* 256 KB sectors (x2) */ +#define PHYS_FLASH_SECT_SIZE 0x00020000 /* *2 = 256 KB sectors */ +#define PHYS_FLASH_MAIN_SECT_SIZE 0x00020000 /* *2 = 256 KB sectors */ +#define PHYS_FLASH_PARAM_SECT_SIZE 0x00008000 /* *2 = 64 KB sectors */ flash_info_t flash_info[CFG_MAX_FLASH_BANKS]; /* info for FLASH chips */ /* Board support for 1 or 2 flash devices */ @@ -62,10 +64,19 @@ typedef struct OrgDef { /* Flash Organizations */ -OrgDef OrgIntel_28F256K3[] = { +OrgDef OrgIntel_28F256K3[] = { /* for Hw-Rev. C */ {256, 128 * 1024}, /* 256 * 128kBytes sectors */ }; +OrgDef OrgIntel_28F256L18T[] = { + {255, 128 * 1024}, /* 255 * 128kBytes sectors */ + { 4, 32 * 1024}, /* 4 * 32kBytes sectors */ +}; + +OrgDef OrgIntel_28F256L30B[] = { /* for Hw-Rev. D */ + { 4, 32 * 1024}, /* 4 * 32kBytes sectors */ + {255, 128 * 1024}, /* 255 * 128kBytes sectors */ +}; /*----------------------------------------------------------------------- * Functions @@ -132,23 +143,55 @@ static void flash_get_offsets (ulong base, flash_info_t * info) int i; OrgDef *pOrgDef; - pOrgDef = OrgIntel_28F256K3; - if (info->flash_id == FLASH_UNKNOWN) { + switch (info->flash_id & FLASH_VENDMASK) { + case FLASH_MAN_INTEL: + break; + default: return; } - if ((info->flash_id & FLASH_VENDMASK) == FLASH_MAN_INTEL) { + switch (info->flash_id & FLASH_TYPEMASK) { + case FLASH_28F256K3: + pOrgDef = OrgIntel_28F256K3; for (i = 0; i < info->sector_count; i++) { + info->start[i] = base + (i * PHYS_FLASH_SECT_SIZE); + info->protect[i] = 0; + } + break; + case FLASH_28F256L18T: + pOrgDef = OrgIntel_28F256L18T; + for (i = 0; i < info->sector_count; i++) { + /* top param block type */ if (i > 255) { - info->start[i] = base + (i * 0x8000); - info->protect[i] = 0; + info->start[i] = base + + (255 * PHYS_FLASH_MAIN_SECT_SIZE) + + ((i -255)* PHYS_FLASH_PARAM_SECT_SIZE); + } else { + info->start[i] = base + + (i * PHYS_FLASH_MAIN_SECT_SIZE); + } + info->protect[i] = 0; + } + break; + case FLASH_28F256L30B: + pOrgDef = OrgIntel_28F256L30B; + for (i = 0; i < info->sector_count; i++) { + /* bottom param block type */ + if (i < 4) { + info->start[i] = base + + (i * PHYS_FLASH_PARAM_SECT_SIZE); } else { info->start[i] = base + - (i * PHYS_FLASH_SECT_SIZE); - info->protect[i] = 0; + ((i - 3) * PHYS_FLASH_MAIN_SECT_SIZE); } + info->protect[i] = 0; } + break; + default: + return; } + + return; } /*----------------------------------------------------------------------- @@ -172,11 +215,14 @@ void flash_print_info (flash_info_t * info) } switch (info->flash_id & FLASH_TYPEMASK) { + case FLASH_28F256K3: + printf ("FLASH 28F256K3\n"); + break; case FLASH_28F256L18T: printf ("FLASH 28F256L18T\n"); break; - case FLASH_28F256K3: - printf ("FLASH 28F256K3\n"); + case FLASH_28F256L30B: + printf ("FLASH 28F256L30B\n"); break; default: printf ("Unknown Chip Type\n"); @@ -221,6 +267,7 @@ static ulong flash_get_size (FPW * addr, flash_info_t * info) info->flash_id = FLASH_UNKNOWN; info->sector_count = 0; info->size = 0; + printf ("Unknown flash vendor %0x\n", value); addr[0] = (FPW) 0x00FF00FF; /* restore read mode */ return (0); /* no or unknown flash */ } @@ -229,20 +276,27 @@ static ulong flash_get_size (FPW * addr, flash_info_t * info) value = addr[1]; /* device ID */ switch (value) { + case (FPW)(INTEL_ID_28F256K3): + info->flash_id += FLASH_28F256K3; + info->sector_count = 256; + info->size = 0x02000000; + break; + case (FPW) (INTEL_ID_28F256L18T): info->flash_id += FLASH_28F256L18T; info->sector_count = 259; info->size = 0x02000000; break; /* => 32 MB */ - case (FPW)(INTEL_ID_28F256K3): - info->flash_id += FLASH_28F256K3; - info->sector_count = 256; - info->size = 0x02000000; + case (FPW)(INTEL_ID_28F256L30B): + info->flash_id += FLASH_28F256L30B; + info->sector_count = 259; + info->size = 0x02000000; /* 32 MB */ break; default: info->flash_id = FLASH_UNKNOWN; + printf ("Unknown chip type %0x\n", value); break; } diff --git a/include/configs/versatile.h b/include/configs/versatile.h index 16db43b..fe26c42 100644 --- a/include/configs/versatile.h +++ b/include/configs/versatile.h @@ -166,7 +166,7 @@ /* timeout values are in ticks */ #define CFG_FLASH_ERASE_TOUT (20*CFG_HZ) /* Timeout for Flash Erase */ #define CFG_FLASH_WRITE_TOUT (20*CFG_HZ) /* Timeout for Flash Write */ -#define CFG_MAX_FLASH_SECT (256) +#define CFG_MAX_FLASH_SECT (259) #define PHYS_FLASH_1 (CFG_FLASH_BASE) diff --git a/include/flash.h b/include/flash.h index 43b9c6b..c1e327f 100644 --- a/include/flash.h +++ b/include/flash.h @@ -284,10 +284,12 @@ extern void flash_read_factory_serial(flash_info_t * info, void * buffer, int of #define INTEL_ID_28F640J3A 0x00170017 /* 64M = 128K x 64 */ #define INTEL_ID_28F128J3A 0x00180018 /* 128M = 128K x 128 */ #define INTEL_ID_28F256J3A 0x001D001D /* 256M = 128K x 256 */ +#define INTEL_ID_28F64K3 0x88018801 /* 64M = 32K x 256 */ +#define INTEL_ID_28F128K3 0x88028802 /* 128M = 64K x 256 */ +#define INTEL_ID_28F256K3 0x88038803 /* 256M = 128K x 256 */ #define INTEL_ID_28F256L18T 0x880D880D /* 256M = 128K x 255 + 32k x 4 */ -#define INTEL_ID_28F64K3 0x88018801 /* 64M = 32K x 255 + 32k x 4 */ -#define INTEL_ID_28F128K3 0x88028802 /* 128M = 64K x 255 + 32k x 4 */ -#define INTEL_ID_28F256K3 0x88038803 /* 256M = 128K x 255 + 32k x 4 */ +#define INTEL_ID_28F256L30T 0x88138813 /* 256M = 128K x 255 + 32k x 4 */ +#define INTEL_ID_28F256L30B 0x88168816 /* 256M = 128K x 255 + 32k x 4 */ #define INTEL_ID_28F64P30T 0x88178817 /* 64M = 32K x 255 + 32k x 4 */ #define INTEL_ID_28F64P30B 0x881A881A /* 64M = 32K x 255 + 32k x 4 */ #define INTEL_ID_28F128P30T 0x88188818 /* 128M = 64K x 255 + 32k x 4 */ @@ -420,6 +422,8 @@ extern void flash_read_factory_serial(flash_info_t * info, void * buffer, int of #define FLASH_28F64K3 0x00B4 /* Intel 28F64K3 ( 64M) */ #define FLASH_28F128K3 0x00B6 /* Intel 28F128K3 ( 128M = 8M x 16 ) */ #define FLASH_28F256K3 0x00B8 /* Intel 28F256K3 ( 256M = 16M x 16 ) */ +#define FLASH_28F256L30T 0x00B9 /* Intel 28F256L30T ( 256M = 16M x 16 ) */ +#define FLASH_28F256L30B 0x00BA /* Intel 28F256L30B ( 256M = 16M x 16 ) */ #define FLASH_28F320J3A 0x00C0 /* INTEL 28F320J3A ( 32M = 128K x 32) */ #define FLASH_28F640J3A 0x00C2 /* INTEL 28F640J3A ( 64M = 128K x 64) */ -- 1.5.0.2

1 0

[U-Boot-Users] Question about CFG_ENV_ADDR during RAMBOOT
by Timur Tabi 25 May '07

25 May '07

On a lot of boards, if CFG_RAMBOOT is defined, the following code is compiled: #define CFG_ENV_ADDR (CFG_MONITOR_BASE - 0x1000) #define CFG_ENV_SIZE 0x2000 This means that the environment is stored 0x1000 bytes before the start of u-boot.bin. Doesn't that mean that if the environment is larger than 0x1000 bytes, that it will overwrite the beginning of u-boot.bin whenever someone does a saveenv? -- Timur Tabi Linux Kernel Developer @ Freescale

7 39

Re: [U-Boot-Users] [PATCH] ARM Versatile PB926EJ-S, Rev.D: Added support for flash 28F256L30B
by Josef Meser 25 May '07

25 May '07

> From: Stefan Roese [mailto:sr@denx.de] > Sent: Friday, May 25, 2007 8:03 AM > To: u-boot-users(a)lists.sourceforge.net > Cc: Josef Meser; Peter Pearse > Subject: Re: [U-Boot-Users] [PATCH] ARM Versatile PB926EJ-S, > Rev.D: Added support for flash 28F256L30B > > Hi Josef, > > On Friday 25 May 2007, Josef Meser wrote: > > Current u-boot works with ARM Versatile PB926EJ-S, HW- Rev.C > > (NOR flash 28F256K3). > > This patch adds support for 28F256L30B (asymmetrical sectors: > > 4 small sectors at bottom) used on HW-Rev.D. > > Your patch is line wrapped. Please fix and resend. Hi Stefan, sorry about that. Yesterday I sent the patch to myself and it was not line wrapped. Now I learned that this is a feature of our famous M$-MUA, which does line wraps in plain text messages, when sending to "Internet addresses". I will fix this by using a real MUA. > One question: Why can't you use the common CFI driver on this board? I have to admit that I am not familiar with the CFI driver. I made the patch for u-boot-1.1.5 which we used up to now. There it makes a []> make versatile_config []> make all work on the new HW. Rev.D. As i did not find the new type of flash in the current source tree, I submitted my changes. This changes are minimal (in terms of size and function) for me, which does not mean that they are optimal for someone who is more into u-boot. Regards, Josef

3 2