March 2006 - U-Boot

[U-Boot-Users] [PATCH] CFI: fix timeout calculations
by Anders Larsen 30 Mar '06

30 Mar '06

This patch fixes two problems with the cfi_flash timeout handling: 1) Correctly handle the cases where CFG_HZ != 1000 (several XScale-based boards) 2) Fix the timeout calculation of buffered writes (off by a factor of 1000) Additionally, the patch trivially removes a redundant call of getenv() Signed-off-by: Anders Larsen <al(a)alarsen.net> --- drivers/cfi_flash.c | 11 ++++++++--- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/drivers/cfi_flash.c b/drivers/cfi_flash.c index a989d34..c7c9983 100644 --- a/drivers/cfi_flash.c +++ b/drivers/cfi_flash.c @@ -360,7 +360,7 @@ #ifdef CFG_FLASH_PROTECTION else { char *s = getenv("unlock"); - if (((s = getenv("unlock")) != NULL) && (strcmp(s, "yes") == 0)) { + if ((s != NULL) && (strcmp(s, "yes") == 0)) { /* * Only the U-Boot image and it's environment is protected, * all other sectors are unprotected (unlocked) if flash @@ -746,6 +746,10 @@ static int flash_status_check (flash_inf { ulong start; +#if CFG_HZ != 1000 + tout *= CFG_HZ/1000; +#endif + /* Wait for command completion */ start = get_timer (0); while (flash_is_busy (info, sector)) { @@ -1160,8 +1164,9 @@ #endif info->buffer_size = (1 << flash_read_ushort (info, 0, FLASH_OFFSET_BUFFER_SIZE)); tmp = 1 << flash_read_uchar (info, FLASH_OFFSET_ETOUT); info->erase_blk_tout = (tmp * (1 << flash_read_uchar (info, FLASH_OFFSET_EMAX_TOUT))); - tmp = 1 << flash_read_uchar (info, FLASH_OFFSET_WBTOUT); - info->buffer_write_tout = (tmp * (1 << flash_read_uchar (info, FLASH_OFFSET_WBMAX_TOUT))); + tmp = (1 << flash_read_uchar (info, FLASH_OFFSET_WBTOUT)) * + (1 << flash_read_uchar (info, FLASH_OFFSET_WBMAX_TOUT)); + info->buffer_write_tout = tmp / 1000 + (tmp % 1000 ? 1 : 0); /* round up when converting to ms */ tmp = (1 << flash_read_uchar (info, FLASH_OFFSET_WTOUT)) * (1 << flash_read_uchar (info, FLASH_OFFSET_WMAX_TOUT)); info->write_tout = tmp / 1000 + (tmp % 1000 ? 1 : 0); /* round up when converting to ms */

1 0

[U-Boot-Users] Re: [DNX#2006033042000045] Test
by U-Boot patch tracking system 30 Mar '06

30 Mar '06

Dear Mr. U. Boot, thank you for your contribution to the U-Boot project. Your e-mail was registered at our system under the ticket number [DNX#2006033042000045]. Your U-Boot support team Powered by OTRS (http://otrs.org/)

2 1

[U-Boot-Users] u-boot and at91rm9200 (on skyeye)
by Rohit 30 Mar '06

30 Mar '06

Hi Guys, I am trying to run u-boot on skyeye emulator. When i load the u-boot.bin via skyeye. I can see the following output but then u-boot hangs at the prompt. The same doesn't appear when i use the ep7321 binary image. Also irrespective what i do i always get the mesage Flash: 0 kB or ATMEL Flash : 0Kb This is my first time with both skyeye and u-boot. Any pointers are most appreciated. Best Regards, rohit Please let me know if you need any more info. [root@localhost at91rm]# skyeye SKYEYE: If you have ELF kernel file, please use -e option to indicate your ELF format kernel filename SKYEYE: If you only have kernel binary image, you should put the filename of kernel binary image in skyeye.conf file arch: arm cpu info: armv4, arm920t, 41009200, ff00fff0, 2 mach info: name at91rm92, mach_init addr 0x8069ca0 uart info: input device is /dev/stdin, fd is 4. uart info: output device is /dev/stdout, fd is 5. SKYEYE: use arm920t mmu ops Loaded RAM ./u-boot.bin U-Boot 1.1.4 (Mar 29 2006 - 14:29:46) U-Boot code: 21F00000 -> 21F16470 BSS: -> 21F32E04 RAM Configuration: Bank #0: 20000000 32 MB Flash: 0 kB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial U-Boot>

2 2

[U-Boot-Users] about some variables in Makefile
by lucasjin 30 Mar '06

30 Mar '06

Hi guys: I am a beginner of U-Boot, and now I am trying to understand the Makefiles. There are some variables in the Makefile under the top directory, which are used without being defined and initiated. For example: PLATFORM_LIBS: "PLATFORM_LIBS += --no-warn-mismatch -L $(shell dirname `$(CC) $(CFLAGS) -print-libgcc-file-name`) -lgcc", and OBJCFLAGS: "$(OBJCOPY) ${OBJCFLAGS} -O srec $< $@". I've checked all the *.mk which are included directly or indirectly by this Makefile and have not find any defination or initiation. I also have made sure that they are not environment variables of LINUX. I'm so wondering. If anyone could give me an explaination, I will appreciate it so much! Best Wishes Lucas Jin lucasjin(a)126.com 2006-03-29

1 0

RE: [U-Boot-Users] Detailed documents......
by Truong, Loc 30 Mar '06

30 Mar '06

Hi Mehul, The u-boot for DaVinci EVM has not been uploaded to open source yet. Please contact Jignesh Shah for the app note and necessary files on how to do this. Regards, Loc ________________________________ From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Mehul Gohel Sent: Friday, March 17, 2006 5:57 AM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] Detailed documents...... Hi All, I am fresh engineer in this field working with DM6446 EVM DAVINCI board which contains DSP as well ARMEJ9. I need to bring that board up. I don't have any experience of how to load the boot loader, how the things goes after boot loader get loaded, so and so. I am working by reading all the document in u-boot source tree and going through the code of u-boot-1.1.3. So can anybody help me to provide document kind of material that gives step wise DETAIL of all the steps starting from boot loader installation to running kernel. such that it helps me to make my task ease. I am going to download the boot loader file through UART to internal RAM of ARM. Because I am confused that how to write the image in NAND FLASH, thats why I am using the other option and that is to download the boot image from UART where one host utility will be runing on the host PC that does few handshaking with board's primary boot loader and than downloads secondry boot loader from the host PC. Thanks, Mehul Gohel

2 1

[U-Boot-Users] [PATCH] Pass NULL for cmd_start/end when bootcmd not present
by Martin Hicks 29 Mar '06

29 Mar '06

Update the way cmd_start and cmd_end are passed to the kernel when there is no provided 'bootcmd' environment variable. In this case r6 and r7, which are optional arguments, should be passed as NULL. This lets the kernel fall back on its default command line arguments as defined in the kernel .config as CONFIG_CMDLINE Signed-off-by: Martin Hicks <mort(a)bork.org> --- common/cmd_bootm.c | 17 +++++++++++------ 1 files changed, 11 insertions(+), 6 deletions(-) 7bd5192777d195833d18fe4a224ca71bfb55117c diff --git a/common/cmd_bootm.c b/common/cmd_bootm.c index 8599a49..c628946 100644 --- a/common/cmd_bootm.c +++ b/common/cmd_bootm.c @@ -567,18 +567,23 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int fl cmdline = (char *)((sp - CFG_BARGSIZE) & ~0xF); kbd = (bd_t *)(((ulong)cmdline - sizeof(bd_t)) & ~0xF); - if ((s = getenv("bootargs")) == NULL) + if ((s = getenv("bootargs")) == NULL) { + cmd_start = cmd_end = 0; s = ""; + } else { + strcpy (cmdline, s); - strcpy (cmdline, s); - - cmd_start = (ulong)&cmdline[0]; - cmd_end = cmd_start + strlen(cmdline); + cmd_start = (ulong)&cmdline[0]; + cmd_end = cmd_start + strlen(cmdline); + } *kbd = *(gd->bd); #ifdef DEBUG - printf ("## cmdline at 0x%08lX ... 0x%08lX\n", cmd_start, cmd_end); + if (cmd_start) + printf ("## cmdline at 0x%08lX ... 0x%08lX\n", cmd_start, cmd_end); + else + printf ("## cmdline len is 0. Not passing a cmdline\n"); do_bdinfo (NULL, 0, 0, NULL); #endif -- 1.2.4

1 0

[U-Boot-Users] RE: LCD on OMAP2430
by Goswami Jigisha-ejg014 29 Mar '06

29 Mar '06

I realized about the Bad CRC warning afterwards. Anyway, the U-Boot hangs after that message and I do not see stdout, stdin and stderr that should come up on the console. How can I change that to my target LCD? I know that stdin cannot be LCD, it has to be UART, But how can I change stdout to LCD? Can any one help? Thanks, Jigisha -----Original Message----- From: Woodruff, Richard [mailto:r-woodruff2@ti.com] Sent: Wednesday, March 29, 2006 11:13 AM To: Goswami Jigisha-ejg014; u-boot-users(a)lists.sourceforge.net Subject: RE: [U-Boot-Users] LCD on OMAP2430 Hello, > *** Warning - bad CRC, using default environment > > This message is coming from common/env_common.c file. Can anyone help me > identify the mistake? This warning is nothing to worry about; it just means you have not saved a copy of your environment into flash. The built in defaults will be used then. If you do a 'saveenv' then reboot the message will go away. It's a little more work in a production sense to program up a proper per-device value but its doable, though a little harder for things like NAND. > Is that all I have to do to enable my target LCD within U-Boot? My goal > is to be able to write images on the LCD verify if it is OK. In the past I have added such support into u-boot for an OMAP device. That code likely would be a good starting point and probably would work with a few tweaks. Regards, Richard W.

2 1

[U-Boot-Users] LCD on OMAP2430 target
by Goswami Jigisha-ejg014 29 Mar '06

29 Mar '06

Hello, I am working on getting my target LCD up with U-Boot. My board is OMAP2430 and the display controller is that of OMAP2430. The LCD is an 18 bit QVGA TFT. Here is what is changed in U-Boot: 1) I added a new file called omap2430fb.c, which is my Display Driver, and put with my board specific files. I took pxafb.c as reference. 2) I declared my panel structure in lcd.h file 2) I defined CONFIG_LCD in my board config file. 3) I wanted to use the cmd_bmp command so I added CFG_CMD_BMP to my board config file as well. After I built my changes with U-Boot and flashed the image, I turn on the board and get the following message: U-Boot 1.1.3 (Mar 28 2006 - 17:48:08) U-Boot code: 80E80000 -> 80EA1450 BSS: -> 80ECC518 OMAP2430C-GP revision 0, PRCM #5A TI 2430SDP Base Board + 0.1 Version + mDDR RAM Configuration: Bank #0: 80000000 128 MB Bank #1: 88000000 0 kB Flash: 64 MB NAND:64 MB *** Warning - bad CRC, using default environment This message is coming from common/env_common.c file. Can anyone help me identify the mistake? Is that all I have to do to enable my target LCD within U-Boot? My goal is to be able to write images on the LCD verify if it is OK. Thanks, Jigisha

2 1

[U-Boot-Users] about some variables in Makefile
by Lucas Jin 29 Mar '06

29 Mar '06

Hi guys: I am a beginner of U-Boot, and now I am trying to understand the Makefiles. There are some variables in the Makefile under the top directory, which are used without being defined and initiated. For example: PLATFORM_LIBS: "PLATFORM_LIBS += --no-warn-mismatch -L $(shell dirname `$(CC) $(CFLAGS) -print-libgcc-file-name`) -lgcc", and OBJCFLAGS: "$(OBJCOPY) ${OBJCFLAGS} -O srec $< $@". I've checked all the *.mk which are included directly or indirectly by this Makefile and have not find any defination or initiation. I also have made sure that they are not environment variables of LINUX. I'm so wondering. If anyone could give me an explaination, I will appreciate it so much! Best Wishes 　　　　　　　　Lucas Jin 　　　　　　　　lucasjin(a)126.com 　　　　　　　　　　2006-03-29

2 1

RE: [U-Boot-Users] LCD on OMAP2430
by Woodruff, Richard 29 Mar '06

29 Mar '06

Hello, > *** Warning - bad CRC, using default environment > > This message is coming from common/env_common.c file. Can anyone help me > identify the mistake? This warning is nothing to worry about; it just means you have not saved a copy of your environment into flash. The built in defaults will be used then. If you do a 'saveenv' then reboot the message will go away. It's a little more work in a production sense to program up a proper per-device value but its doable, though a little harder for things like NAND. > Is that all I have to do to enable my target LCD within U-Boot? My goal > is to be able to write images on the LCD verify if it is OK. In the past I have added such support into u-boot for an OMAP device. That code likely would be a good starting point and probably would work with a few tweaks. Regards, Richard W.

1 0