January 2004 - U-Boot

[U-Boot-Users] -- fix the ARM memory layout -- couple errors.
by Woodruff, Richard 09 Feb '04

09 Feb '04

Anders, After tracing though the code I found a couple bugs in the patch. I think I corrected them and included the version of start.S for the ARM925 which I am using. I now get the expected register dump (or alternative function I've defined). -- The 3 reserved words for abort info is carved out at the top of the stack (high addr). The converted macro's treated this info as if it were at the "bottom" of the stack by subtracting off CONFIG_STACKSIZE. This is not correct or consistent with the previous def's which happened just above. The CONFIG_STACKSIZE should not be used at all. It has little meaning at present, perhaps more with irq's are enabled. -- I noticed that get_bad_stack() actually was not correct for SWI's and would crash my board in an unexpected way. The reason is that the SWI enters the system in SVC mode and the get_bad_stack() macro assumes a banked SP (R13)...ie it destroys the SVC mode SP, then switches to SVC mode (its already there) and there it tries to write on the bad stack. I added a new macro to my build which I think fixed the problem (assuming the svc stack is good). -- the introduction of CFG_GBL_DATA_SIZE is sort of a hollow gesture. It is perhaps a good seg way, but at present doesn't do much other than waist some space. Lib_arm/board.c currently sets the global area to a stack allocated object which happens to be on the top of the stack as it's the first definition. Carving out space for it is just fine, however this space never used. ... It might be nice to have a separate section for this object which the loader could initialize at some other spot, say, sram...later perhaps. Other than those few bits everything else seems to be working. Thanks for the effort. Your work is forcing me to switch to the preferred memory setup. Regards/thanks, Richard W. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Woodruff, Richard Sent: Monday, January 19, 2004 12:08 PM To: 'Anders Larsen' Cc: u-boot-users(a)lists.sourceforge.net Subject: RE: [U-Boot-Users] [PATCH] fix the ARM memory layout Anders, I just applied this patch to my ARM board, and it seems to mostly work. Prior to the memory change I would get stack dumps on aborts, since applying the patch I am unable to get on to print. Have you been able to generate one? I hook up the JTAG and do a little tracing... One other comment... I have some test code which does a crc32 over the rom portion of u-boot to help validate the image, this code used armboot_end. In your patch you removed that symbol. Bss_start seems to be an "almost" proper substitution. I say almost as an ALIGN 4 is done before it. If the cmd size ended on a byte or half word boundary this would mess up the crc32 from what I might expect...In practice it might be that GCC generates things such that it pads to this anyway). Adding another symbol is easy, just thought I'd point out that it "might" not be strictly equivalent the way you did it... Regards, Richard W. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Anders Larsen Sent: Friday, January 09, 2004 5:14 AM To: Wolfgang Denk Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] [PATCH] fix the ARM memory layout Wolfgang Denk <wd(a)denx.de> schreibt: >In message <fc.004c4e48001e6497004c4e48001e6497.1e64ae(a)rea.de> you wrote: >> >> here's a fresh version of my rather intrusive patch from the 17.th sept. >> to rearrange the ARM memory layout to bring it in line with the README. > >Sorry, I'm working through my backlog sequentially, and I already >added the other patch. Can you please check your current version >against current top-of-tree in CVS and provide a new diff? Hi Wolfgang, the attached patch (against CVS 2004-01-08) fixes the rest of the ARM stuff I had in the pipe. In particular, the abort-stack is now set up in the correct RAM area (which I had neglected in my previous patches), and the BSS is zeroed out as it should be (which most previous ARM implementations had neglected). Furthermore, the magic variables 'armboot_end' and 'armboot_end_data' of the linker scripts are replaced by '__bss_start' and '_end', resp., which is a further step to eliminate unnecessary differences between the implementation of the CPU architectures. Compilation tested with MAKEALL arm, functionality only tested on my PXA-based board. CHANGELOG: Fix the ARM memory layout. Cheers Anders (Patch gzipped due to size constraints on the list) ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

3 4

[U-Boot-Users] Patch for NAND Booting on SMDK2410
by Markus Pietrek 08 Feb '04

08 Feb '04

Hi folks, here is a patch to enable U-Boot 1.0 to boot from NAND/SmartMedia cards. smdk2410.h must include the line '#define CONFIG_BOOT_NAND 1" and the resulting u-boot.bin must be copied to the first SmartMedia sectors (with a JTAG tool for example). The first sector of the SmartMedia card should also be marked as "Defect". With J33 and J34 closed the board should then boot from SmartMedia. This first version is very simple as U-Boot is linear on the SmartMedia and don't allows a filesystem. Later version may include placing U-Boot on a filesystem. This patch also includes code for clearing the BSS segment. This is not the same code Larsen submitted this morning :-( Bye, -- Markus Pietrek FS Forth-Systeme GmbH Phone: +49 (7667) 908 145, FAX +49 (7667) 908 221

4 5

[U-Boot-Users] Intel LXT971A PHY support
by Tolunay Orkun 08 Feb '04

08 Feb '04

Hi, I am in the process of creating a U-Boot port for Cogent CSB272 board (PPC405) Working from U-Boot 1.0.0 tarball sources, I got CSB272 running. I still have some work done for it so I am not submitting CSB272 board support yet. Maybe next week or so after I complete work on it and make sure Linux boots OK. Anyway, CSB272 board has Intel LXT971A PHY. I could not get this PHY working initially. After investigation I have found: 1) LXT971A requires some recovery time (~300usec) before any register access after reset. This is documented in the datasheet on page 70, table 40. 2) LXT971A requires some time after command is issued before polling EMAC_STACR_OC is valid. I am not sure why this is needed but it is needed for this particular PHY or otherwise it does not work. I have found this to be minimum 32usec. I used 40usec for some safety margin. Thus, to get it working I had to patch two shared files: cpu/ppc4xx/miiphy.c common/miiphyutil.c The code added are conditional for each change and without those macro definitions it compiles exactly as it is right now. The macros are as follows (from my include/configs/csb272.h): #define CONFIG_PHY_CMD_DELAY 40 /* PHY COMMAND delay */ /* 32usec min. for LXT971A */ #define CONFIG_PHY_RESET_DELAY 300 /* PHY RESET recovery delay */ Here is the patch (I can resend it as an attachment if format is broken) --- u-boot-1.0.0/cpu/ppc4xx/miiphy.c 2003-09-02 18:08:13.000000000 -0500 +++ u-boot/cpu/ppc4xx/miiphy.c 2004-01-11 02:56:16.000000000 -0600 @@ -110,7 +110,9 @@ int miiphy_read (unsigned char addr, uns #if 0 /* test-only */ printf ("a2: write: EMAC_STACR=0x%0x\n", sta_reg); /* test-only */ #endif - +#if defined(CONFIG_PHY_CMD_DELAY) + udelay(CONFIG_PHY_CMD_DELAY); /* Intel LXT971A needs this */ +#endif sta_reg = in32 (EMAC_STACR); i = 0; while ((sta_reg & EMAC_STACR_OC) == 0) { @@ -166,6 +168,9 @@ int miiphy_write (unsigned char addr, un memcpy (&sta_reg, &value, 2); /* put in data */ out32 (EMAC_STACR, sta_reg); +#if defined(CONFIG_PHY_CMD_DELAY) + udelay(CONFIG_PHY_CMD_DELAY); /* Intel LXT971A needs this */ +#endif /* wait for completion */ i = 0; --- u-boot-1.0.0/common/miiphyutil.c 2003-10-08 17:33:00.000000000 -0500 +++ u-boot/common/miiphyutil.c 2004-01-11 22:42:42.249886108 -0600 @@ -103,6 +103,9 @@ int miiphy_reset (unsigned char addr) return (-1); } +#if defined(CONFIG_PHY_RESET_DELAY) + udelay(CONFIG_PHY_RESET_DELAY); /* Intel LXT971A needs this */ +#endif /* * Poll the control register for the reset bit to go to 0 (it is * auto-clearing). This should happen within 0.5 seconds per the

2 1

[U-Boot-Users] [PATCH] small correction (again)
by Stephan Linz 08 Feb '04

08 Feb '04

Hi all, - makes the DK1C20 board configuration related to ASMI more conform to documentation Best Regards, Stephan Linz

2 1

[U-Boot-Users] [PATCH] small correction
by Stephan Linz 08 Feb '04

08 Feb '04

Hi all, - avoid harmless warning: unused variable `piop' in board/altera/common/sevenseg.c Best Regards, Stephan Linz

2 1

[U-Boot-Users] [PATCH] fix the ARM memory layout
by Anders Larsen 08 Feb '04

08 Feb '04

Hi, here's a fresh version of my rather intrusive patch from the 17.th sept. to rearrange the ARM memory layout to bring it in line with the README. This has the positive side-effect of actually allow U-Boot to run on PXA- and IXP-based targets; the current implementation sets up the heap using bogus addresses causing u-boot to crash (this even applies to the recently added board "ixdp425"). This patch doesn't go all the way, though, since doing away with the board-specific setting of TEXT_BASE would require the code to be position-independent, which at least the cpu initialization code in cpu/*/start.S is _not_. CHANGELOG: Bring the ARM memory layout in line with the documentation. Cheers Anders

5 11

[U-Boot-Users] cpu/mpc8xx/cpu.c version 1.7 breaks get_tbclk for mpc850
by Ruhland, Paul 07 Feb '04

07 Feb '04

In 'cpu/mpc8xx/cpu.c' the 'get_tbclk()' function was modified to check the immr PARTNUM and MASKNUM fields in an attempt to identify newer parts. As it is now, if the PARTNUM field is >= 0x08 the osclk divisor is calculated for newer parts. However, an 850s PARTNUM field is 0x20. This causes the divisor to be calculated incorrectly using the 'new' method. I don't know all the PARTNUM fields so I can't really fix this. I'm just commenting it out for now. -- Paul Ruhland Microwave Data Systems, Inc. 175 Science Parkway Rochester, NY 14620 pruhland(a)microwavedata.com

2 1

[U-Boot-Users] PATCH: include/linux/byteorder/swab.h
by Leon Kukovec 07 Feb '04

07 Feb '04

Fixes: o the optimization can now be disabled (config.mk: OPTFLAGS = -O0) (makes debugging easier) Change: o changed extern __inline__ into static __inline__ in include/linux/byteorder/swab.h COMPILER: ELDK x86 2.1.0 (RedHat 9.0) BUILD FOR: ppc mips arm BUILD STATUS: ERIC FAILED ixdp425 FAILED lubbock FAILED MPC8540ADS FAILED MPC8560ADS FAILED NOTE: the same builds fail for U-Boot HEAD branch. -- Best Regards, Leon.

2 3

[U-Boot-Users] PATCH: itest - an integer compare function
by Robin Gilks 07 Feb '04

07 Feb '04

Changelog: Introduce a new command to be used in conditional expressions (such as hush 'if') to test the value of a memory location. Supports -eq, -ne, -gt, -lt, -ge, -le Allows scalars or memory contents (value prefixed by '*') Makes use of command data width expression of .l, .wm .b for 4, 2 or 1 byte wide comparisons e.g. if itest.l *40000 -eq 12345678; then bootm 41000; else bootm 80000; fi Patch is against u-boot-1.0.0 Note: I'm still concerned that the CONFIG_COMMANDS mask has run out of bits - maybe time for a different mechanism as I'm sure the bit I've used has gone by now!! -- Robin Gilks Senior Design Engineer Phone: (+64)(3) 357 1569 Tait Electronics Fax : (+64)(3) 359 4632 PO Box 1645 Christchurch Email : robin.gilks(a)tait.co.nz New Zealand

2 1

[U-Boot-Users] [patch] CONFIG_SILENT_CONSOLE
by Wolter Kamphuis 06 Feb '04

06 Feb '04

Hi all, I've changed the implementation of the CONFIG_SILENT_CONSOLE flag a bit. Instead of checking for the CONFIG_SILENT_CONSOLE flag in lib_*/board.c I've moved the code to common/console.c. Now all (and future) architectures and boards can use the CONFIG_SILENT_CONSOLE flag. The patch is against the current CVS. Wolter Kamphuis MuLogic B.V. diff -purN u-boot/common/console.c u-boot.silent/common/console.c --- u-boot/common/console.c 2003-10-16 01:53:50.000000000 +0200 +++ u-boot.silent/common/console.c 2003-12-15 10:37:49.000000000 +0100 @@ -191,6 +191,11 @@ void putc (const char c) { DECLARE_GLOBAL_DATA_PTR; +#ifdef CONFIG_SILENT_CONSOLE + if (gd->flags & GD_FLG_SILENT) + return(0); +#endif + if (gd->flags & GD_FLG_DEVINIT) { /* Send to the standard output */ fputc (stdout, c); @@ -204,6 +209,11 @@ void puts (const char *s) { DECLARE_GLOBAL_DATA_PTR; +#ifdef CONFIG_SILENT_CONSOLE + if (gd->flags & GD_FLG_SILENT) + return; +#endif + if (gd->flags & GD_FLG_DEVINIT) { /* Send to the standard output */ fputs (stdout, s); diff -purN u-boot/doc/README.silent u-boot.silent/doc/README.silent --- u-boot/doc/README.silent 2003-10-10 12:05:42.000000000 +0200 +++ u-boot.silent/doc/README.silent 2003-12-15 10:54:52.000000000 +0100 @@ -9,8 +9,6 @@ The following actions are taken if "sile - Until the console devices have been initialized, output has to be suppressed by testing for the flag "GD_FLG_SILENT" in "gd->flags". - Currently only the messages for the TRAB board are handled in this - way. - When the console devices have been initialized, "stdout" and "stderr" are set to "nulldev", so subsequent messages are diff -purN u-boot/lib_arm/board.c u-boot.silent/lib_arm/board.c --- u-boot/lib_arm/board.c 2003-12-07 01:46:27.000000000 +0100 +++ u-boot.silent/lib_arm/board.c 2003-12-15 10:39:02.000000000 +0100 @@ -115,13 +115,6 @@ static int init_baudrate (void) static int display_banner (void) { -#ifdef CONFIG_SILENT_CONSOLE - DECLARE_GLOBAL_DATA_PTR; - - if (gd->flags & GD_FLG_SILENT) - return (0); -#endif - printf ("\n\n%s\n\n", version_string); printf ("U-Boot code: %08lX -> %08lX BSS: -> %08lX\n", _armboot_start, _armboot_end_data, _armboot_end); @@ -148,11 +141,6 @@ static int display_dram_config (void) DECLARE_GLOBAL_DATA_PTR; int i; -#ifdef CONFIG_SILENT_CONSOLE - if (gd->flags & GD_FLG_SILENT) - return (0); -#endif - puts ("RAM Configuration:\n"); for(i=0; i<CONFIG_NR_DRAM_BANKS; i++) { @@ -165,12 +153,6 @@ static int display_dram_config (void) static void display_flash_config (ulong size) { -#ifdef CONFIG_SILENT_CONSOLE - DECLARE_GLOBAL_DATA_PTR; - - if (gd->flags & GD_FLG_SILENT) - return; -#endif puts ("Flash: "); print_size (size, "\n"); }

2 1