May 2004 - U-Boot

[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] [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

[U-Boot-Users] [PATCH] OMAP730 Perseus2 support
by Dave Peverley 07 Jun '04

07 Jun '04

Hi all, I'm pleased to submit back to the list this patch for the OMAP730 Perseus2 board. The patch adds support for the OMAP730 Perseus2 board. For detailed information, see the doc/README.omap730p2 text file contained in the patch. The patch itself was created against the CVS repository tag "U-Boot-1_1_0" using the command : diff -purN u-boot u-boot-omap730p2 > u-boot-1.1.0-omap730p2.patch Changelog Entry : * Patch by Dave Peverley, 29th Apr 2004: Added support for OMAP730 Perseus2 Development board CREDITS Entry : N: Dave Peverley E: dpeverley(a)mpc-data.co.uk W: http://www.mpc-data.co.uk D: OMAP730 P2 board support All comments and feedback welcome. Best Wishes, Dave Peverley --------------------------------------------------------------------------- Dave Peverley, Software Engineer, MPC Data Limited. Phone : [+44] (0) 1225 868 228 Web : http://www.mpc-data.co.uk

2 2

[U-Boot-Users] [RFC] NAND Flash
by Pantelis Antoniou 07 Jun '04

07 Jun '04

Hello there. As you remember earlier I have sent a small patch for the NAND portion of u-boot. This forced me to really take a hard look at the code and really evaluate it. The big problem with the code as it is its its tendancy not to account properly for errors which are not only probable but certain during the life of the device. For example the current code cannot boot reliably from NAND and the read and write routines are also unreliable. It's basic assumption made that you can read/write from the NAND at any position is false. This is impossible because of the bad blocks that may force you to skip a bad sector. I'm currently in the process of rewritting to actually make it work reliably. I can keep backwards compatibility with the old code but you can only use it at your own risk. I'm asking for any people currently working with NAND to comment on the following points: 1. Do you read and write the NAND at arbitrary offsets? That means not in page boundaries. 2. Do you use the NAND boot command? It can be replaced by a copy and bootm sequence. 3. Do you use it as a raw device without employing ECC? Do you understand the implications? 4. What kind of filesystem do you use? JFFS2 & YAFS have different OOB placement of ECC and status bits? 5. What kind of bad block management options would you like? I'm thinking of implementing a bad block detection mechanism which would erase and test the whole chip for any bad blocks. Another command could also utilise ECC to detect borderline working pages and relocate them to avoid a permanent failure. Awaiting your input... Regards Pantelis

2 2

[U-Boot-Users] [Patch]New board support : lite_dw
by Sam Song 07 Jun '04

07 Jun '04

Dear Mr. Wolfgang, Before sending the patch,I need to consult with you a couple of points.First is the new board name.I prefer to give a new name,lite_dw.Actually,it is DW version of RPXlite board but have three differences with CW version,which was ported by Yoo. Jonghoon. Board CPU SDRAM FLASH CW[u-boot] MPC850 16MB 4MB DW[On my hand] MPC823e 64MB 16MB So the possible name could be RPXlite_DW or lite_dw.In Linux kernel tree,it can be found as RPXlite_DW.But I add some new features for this board,a software development platform of EmbeddedPlanet Co. Secondly,I'd like to support the following features on this board for the moment. 1. LCD panel support; 2. 64MHz/48MHz system clock options; 3. ENV_IS_IN_FLASH/ENV_IS_IN_NVRAM; Any suggestion? Best regards, Sam _________________________________________________________ Do You Yahoo!? 惠普TT游戏剧，玩游戏，中大奖！ http://cn.rd.yahoo.com/mail_cn/tag/SIG=1402c0to2/**http%3A%2F%2Fhp.allyes.c…

2 5

[U-Boot-Users] New NAND code draft
by Pantelis Antoniou 07 Jun '04

07 Jun '04

Hi there In the attached patch you can see the progress of my work in the NAND rewrite. This is not suitable for inclusion yet. Things that work now: 1. Correct handling of bad blocks. 2. NAND boot works 3. Updated to latest MTD snapshot. 4. Direct to NAND tftp/nfs support. Things that are probably borked: 1. Multiple chip support (I don't have such hardware available and the previous code was kinda of unclear. 2. Since there is DOC support in u-boot that utilizes the old code and definitions I left the linux/mtd/nand.h header in place, and created a new mtd_nand.h header for the new stuff. 3. JFFS2 support although there is probably b0rken. 4. The read.xxx/write.xxx support is just not there yet. I would appreciate it if you could take a look and report back to me. Regards Pantelis

2 1

[U-Boot-Users] MPC8xx FADS Board Flash Chip Select
by Alan J. Luse 07 Jun '04

07 Jun '04

The setting of the Flash chip select extent on MPC8xx FADS boards (board/fads/flash.c) is too big by a factor of 2. A board with 2 Mbytes will have its chip select set to allocate a region of 4 Mbytes. * Patch by Alan J. Luse, 29 Apr 2004: Flash chip-select (OR0) option register was being set incorrectly to twice the available Flash for FADS boards. Alan J. Luse Embedded Systems Engineer Time America, Inc. 51 West Third Street, Suite 310 Tempe, AZ 85281 Voice: (480) 296-0408 Fax: (480) 296-0444

2 1

[U-Boot-Users] MII Speed & Duplex Readback
by Alan J. Luse 07 Jun '04

07 Jun '04

The MII PHY utility (common/miiphyutil.c) does not report network speed and duplex mode properly if auto-negotiate is not enabled. The attached patch checks if auto-negotiate is enabled and looks in the proper registers based on that bit to return speed and duplex values. * Patch by Alan J. Luse, 29 Apr 2004: Report MII network speed and duplex setting properly when auto-negotiate is not enabled. Alan J. Luse Embedded Systems Engineer Time America, Inc. 51 West Third Street, Suite 310 Tempe, AZ 85281 Voice: (480) 296-0408 Fax: (480) 296-0444

2 1