June 2004 - U-Boot

[U-Boot-Users] u-boot and Linux into an ace file
by Abdelmajid Bouajila 09 Jun '04

09 Jun '04

is it possible to put u-boot with Linux image in an ace file? Hello, I am working on an ML300 board. I build my HW platform and I generate my ace file using the HW and U-boot like this: make an ACE file out of bitstream and U-Boot: $ xmd genace.tcl -jprog -board ml300 -hw \ implementation/download.bit -elf u-boot -ace top.ace is it possible to put u-boot with the Linux in an ace file? Thanks Abdelmajid

2 1

[U-Boot-Users] Patches [Part 2/2] for the MPC8540ADS and MPC8560ADS boards
by Jon Loeliger 09 Jun '04

09 Jun '04

Wolfgang, Here are some patches for the MPC 8540/8560 ADS boards. The patches are in two .tgz files, part 1 and part 2. This is part 2. These patches are derived from the top-of-CVS on 2004-05-10 and have been successfully applied locally to a copy of that tree using a "patch -p1 < MPC85XXADS-20040510-diffs" command. A MAKEALL didn't have any real problems on the first 135 boards. Hey Dan Malek, please let me know if this version of the TSEC driver (merged) does what you expect on the stxgp3 board! Thanks, jdl

2 1

[U-Boot-Users] Patches [Part 1/2] for the MPC8540ADS and MPC8560ADS boards
by Jon Loeliger 09 Jun '04

09 Jun '04

Wolfgang, Here are some patches for the MPC 8540/8560 ADS boards. A CHANGELOG entry follows below, and the patches are in two .tgz files, part 1 and part 2. This is part 1. These patches are derived from the top-of-CVS on 2004-05-10 and have been successfully applied locally to a copy of that tree using a "patch -p1 < MPC85XXADS-20040510-diffs" command. A MAKEALL didn't have any real problems on the first 135 boards. Hey Dan Malek, please let me know if this version of the TSEC driver (merged) does what you expect on the stxgp3 board! Thanks, jdl * Patch by Jon Loeliger, 10-May-2004 Dynamically handle REV1 and REV2 MPC85xx parts. * Patch by Kumar Gala, 10-May-2004 New consistent memory map and Local Access Window across MPC85xx line. New CCSRBAR at 0xE000_0000 now. Add RAPID I/O memory map. New memory map in README.MPC85xxads * Patch by Jon Loeliger, 10-May-2004 Better board and CPU identification on MPC85xx boards at boot. * Patch by Jim Robertson, 10-May-2004 SDRAM clock control fixes on MPC8540ADS & MPC8560 boards. Some configuration options for MPC8540ADS & MPC8560ADS cleaned up. * Patch by Andy Fleming, 10-May-2004 Rewrite of the MPC85xx Three Speed Ethernet Controller (TSEC) driver. Supports multiple PHYs. * Patch by Kumar Gala, 10-May-2004 Some README.MPC85xxads updates. * Patch by Andy Fleming, 10-May-2004 Copyright updates for "Freescale"

2 1

[U-Boot-Users] [patch] Reduce flash handling code for JSE
by Stephen Williams 09 Jun '04

09 Jun '04

The attached patch reduces the JSE flash support to only include what is needed for flashes plausibly with the board. It also adds support for the ST M29W040B flash chip. CHANGELOG: * Patch by Stephen Williams, 11 May 2004 Add flash support for ST M29W040B Reduce JSE specific flash.c to remove dead code. -- Steve Williams "The woods are lovely, dark and deep. steve at XXXXXXXXXX But I have promises to keep, http://www.XXXXXXXXXX and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."

2 1

[U-Boot-Users] BSS initialization wrong on ARM??
by Markus Pietrek 09 Jun '04

09 Jun '04

Hi folks, on the smdk2410 I found out that the BSS segment is initialized at offset 0x4 and not with offset 0x0, leaving the first entry undefined (in my case timer_load_val), at least with gcc-3.3. Cause of pain is arm920t/start.S:clear_bss clear_bss: ldr r0, _bss_start /* find start of bss segment */ add r0, r0, #4 /* start at first byte of bss */ ldr r1, _bss_end /* stop here */ I think the add has to be removed. This also seems to be the case on arm720t and arm926ejs. Bye, -- Markus Pietrek Kueferstrasse 8, D-79206 Breisach, Germany FS Forth-Systeme GmbH Phone: +49 (7667) 908 145, FAX +49 (7667) 908 245

2 1

[U-Boot-Users] help: linux kernel uncompress question
by wyu hotmail 08 Jun '04

08 Jun '04

Hi, I'm porting u-boot on my PPC405EP board. I started from bubinga405ep board, and I have sucessfully loaded a linux kernel and made it run well. Now I try to create another folder for my own board in ../board folder and named it as sgw405ep, I modified makefile and some other places which related to bubinga45ep. The new u-boot can start up and can also download linux kernel (same kernel) via tftp. but when I try to make the kernel run by typing bootm, I get the following message: => bootm ## Booting image at 00400000 ... Image Name: Linux Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 603024 Bytes = 588.9 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x01FAD598 => set upper limit to 0x00800000 ## cmdline at 0x007FFC00 ... 0x007FFC50 bd address = 0x01FADF8C memstart = 0x00000000 memsize = 0x02000000 flashstart = 0x10000000 flashsize = 0x00200000 flashoffset = 0x00000000 sramstart = 0x00000000 sramsize = 0x00000000 bootflags = 0x0000A000 procfreq = 266.666 MHz plb_busfreq = 133.333 MHz pci_busfreq = 33.333 MHz ethaddr = 00:E5:00:08:0F:E5 IP addr = 128.127.18.3 baudrate = 115200 bps No initrd ## Transferring control to Linux (at address 00000000) ... and then, the processor seems halt. I compared the data in sdram from 0x00000000 to 0x00020000 after the kernel was uncompressed into SDRAM for the two u-boot, I found the some data are not same in section 0x00000000 to 0x00002000. Two u-boot all reports that Uncompressing Kernel Image ... OK, but why the data not same? Who can tell me What's possible problems? Thanks very much! yuwp

1 0

RE: [U-Boot-Users] ARM, bootm and bootargs
by Friedrich, Lars 08 Jun '04

08 Jun '04

Curt Brune wrote something slightly offtopic and may the gods forgive me for answering here, but hopefully this answer will prevent further similiar questions: > I'm trying to pass command line arguments from u-boot to the kernel > for an ARM-based board. Following the README I'm setting the > environment variable "bootargs" to the command line I want and booting > with the "bootm" command. > > When the kernel boots it prints it's command line, which is still the > default command line. I was expecting to the see the command line I > stored in the "bootargs" variable. > > I poked around in u-boot/lib_arm/armlinux.c and it looks like I needed > to have CONFIG_CMDLINE_TAG defined in my config, which I did. > > Is there anything else I need to do? Something I'm missing? Assuming you are trying to boot uClinux and the 2.4.x kernel, then you need to modify uClinux-dist/linux-2.4.x/arch/armnommu/kernel/arch.c There you'll find MACHINE_START(NETARM, "NET+ARM). Within the MACHINE_START and MACHINE_END sequence you need to add BOOT_PARAMS(<value>) (no semicolon at the end please). And the value you have to enter is whatever is set in file: u-boot/board/xxxx(modnet50?)/xxxx(modnet50?).c function: int board_init (void) variable: gd->bd->bi_boot_params=<value> If compiled with bdinfo support, you can also type bdinfo at the u-boot command prompt. boot_params is the currently set <value>. The default value for the modnet50 board is f.e. 0x800. You just have to make sure that it is indeed a valid ram address for your custom board (and that of course it doesn't get overwritten when you boot linux). Best regards, Lars Friedrich --

1 0

[U-Boot-Users] Re: Intracom Boards update
by Pantelis Antoniou 08 Jun '04

08 Jun '04

Wolfgang Denk wrote: >Dear Pantelis, > >in message <4098D308.3050404(a)intracom.gr> you wrote: > >>The following patch updates the intracom boards and >>also adds infrastructure for codec post tests. >> >>* Patch by Pantelis Antoniou, 5 May 2004: >>- Intracom board update. >>- Codec POST. >> > >Added. Thanks. > >A few remarks: > >* Please keep the lists of board names (as in MAKEALL) sorted. > OK > >* Please don't mess with the "${CROSS_COMPILE:-ppc_8xx-}size" > definition, especially not without even mentioning it!!! > Sorry, I don't cross compile, and this slipped. > >* How different are the 4 NET* configurations? Do we really have to > build all of them all of the time? > They're different boards. But we can narrow them down to two. > >* Please adhere to the formatting rules! PLEASE DO NOT ADD TRAILING > WHITE SPACE!!! > >* Please make sure not to re-submit modifications you already > submitted (like the status-led extension in > board/netphone/netphone.c, or some changes in > netphone/phone_console.c etc.) > > Will do. Regards Pantelis

1 0

[U-Boot-Users] [PATCH] Support for OMAP5912 OSK platform
by Bhattacharya, Rishi 08 Jun '04

08 Jun '04

Hi Wolfgang, This patch adds support for the TI OMAP5912 OSK platform. Take care, Rishi

2 1

[U-Boot-Users] Re: [Patch]New board support : RPXlite_DW [Last]
by Sam Song 08 Jun '04

08 Jun '04

The following patch are against CVS. Sam ==================================================== --- Makefile Tue May 4 14:34:57 2004 +++ Makefile_new Tue May 4 22:51:15 2004 @@ -457,6 +457,30 @@ RPXClassic_config: unconfig RPXlite_config: unconfig @./mkconfig $(@:_config=) ppc mpc8xx RPXlite +RPXlite_DW_64_config \ +RPXlite_DW_LCD_config \ +RPXlite_DW_64_LCD_config \ +RPXlite_DW_FLASH_config \ +RPXlite_DW_FLASH_64_config \ +RPXlite_DW_FLASH_LCD_config \ +RPXlite_DW_FLASH_64_LCD_config \ +RPXlite_DW_config: unconfig + @ >include/config.h + @[ -z "$(findstring _64,$@)" ] || \ + { echo "#define RPXlite_64MHz" >>include/config.h ; \ + echo "... with 64MHz system clock ..."; \ + } + @[ -z "$(findstring _LCD,$@)" ] || \ + { echo "#define CONFIG_LCD" >>include/config.h ; \ + echo "#define CONFIG_NEC_NL6448BC20" >>include/config.h ; \ + echo "... with LCD display ..."; \ + } + @[ -z "$(findstring _FLASH,$@)" ] || \ + { echo "#define CFG_ENV_IS_IN_FLASH" >>include/config.h ; \ + echo "... with ENV in FLASH ..."; \ + } + @./mkconfig -a RPXlite_DW ppc mpc8xx RPXlite_dw + rmu_config: unconfig @./mkconfig $(@:_config=) ppc mpc8xx rmu --- README Tue May 4 14:32:37 2004 +++ README_new Tue May 4 14:48:21 2004 @@ -278,14 +278,15 @@ The following options need to be configu CONFIG_pcu_e, CONFIG_PIP405, CONFIG_PM826, CONFIG_ppmc8260, CONFIG_QS823, CONFIG_QS850, CONFIG_QS860T, CONFIG_RBC823, CONFIG_RPXClassic, - CONFIG_RPXlite, CONFIG_RPXsuper, CONFIG_rsdproto, - CONFIG_sacsng, CONFIG_Sandpoint8240, CONFIG_Sandpoint8245, - CONFIG_sbc8260, CONFIG_SM850, CONFIG_SPD823TS, - CONFIG_STXGP3, CONFIG_SXNI855T, CONFIG_TQM823L, - CONFIG_TQM8260, CONFIG_TQM850L, CONFIG_TQM855L, - CONFIG_TQM860L, CONFIG_TTTech, CONFIG_UTX8245, - CONFIG_V37, CONFIG_W7OLMC, CONFIG_W7OLMG, - CONFIG_WALNUT405, CONFIG_ZPC1900, CONFIG_ZUMA, + CONFIG_RPXlite, CONFIG_RPXlite_DW CONFIG_RPXsuper, + CONFIG_rsdproto, CONFIG_sacsng, CONFIG_Sandpoint8240, + CONFIG_Sandpoint8245, CONFIG_sbc8260, CONFIG_SM850, + CONFIG_SPD823TS, CONFIG_STXGP3, CONFIG_SXNI855T, + CONFIG_TQM823L, CONFIG_TQM8260, CONFIG_TQM850L, + CONFIG_TQM855L, CONFIG_TQM860L, CONFIG_TTTech, + CONFIG_UTX8245, CONFIG_V37, CONFIG_W7OLMC, + CONFIG_W7OLMG, CONFIG_WALNUT405, CONFIG_ZPC1900, + CONFIG_ZUMA, ARM based boards: ----------------- @@ -2036,11 +2037,11 @@ configurations; the following names are omap1510inn_config omap1610h2_config omap1610inn_config pcu_e_config PIP405_config QS823_config QS850_config QS860T_config RPXlite_config - RPXsuper_config rsdproto_config Sandpoint8240_config - sbc8260_config SM850_config SPD823TS_config - stxgp3_config SXNI855T_config TQM823L_config - TQM850L_config TQM855L_config TQM860L_config - WALNUT405_config ZPC1900_config + RPXlite_DW_config RPXsuper_config rsdproto_config + Sandpoint8240_config sbc8260_config SM850_config + SPD823TS_config stxgp3_config SXNI855T_config + TQM823L_config TQM850L_config TQM855L_config + TQM860L_config WALNUT405_config ZPC1900_config Note: for some board special configuration names may exist; check if additional information is available from the board vendor; for _________________________________________________________ Do You Yahoo!? 嫌邮箱太小？雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/10m/*http://cn.mail.yahoo.com/event/10m.…

2 11