October 2009 - U-Boot

[U-Boot] Pull request u-boot-blackfin.git
by Mike Frysinger 15 Oct '09

15 Oct '09

The following changes since commit 14abfe361b3ed23b02f564e2f5d663e158cd5799: Wolfgang Denk (1): Merge branch 'master' of /home/wd/git/u-boot/custodians are available in the git repository at: git://www.denx.de/git/u-boot-blackfin.git master Mike Frysinger (3): Blackfin: Remove relocation fixups Blackfin: reset watchdog in udelay() Blackfin: drop MAC display at boot cpu/blackfin/interrupts.c | 3 +++ include/asm-blackfin/config.h | 3 +++ include/asm-blackfin/global_data.h | 1 - lib_blackfin/board.c | 6 ------ 4 files changed, 6 insertions(+), 7 deletions(-)

2 1

[U-Boot] Board Identification Data
by alan A. A 15 Oct '09

15 Oct '09

Hello, in your Documentation about U-Boot under http://www.denx.de/wiki/view/DULG/UBootInstallBefore , you wrote: >All %BOARDNAME% boards use a serial number for identification >purposes. Also, all boards have at least one ethernet (MAC) address >assigned. You may lose your warranty on the board if this data gets >lost. Before installing U-Boot or otherwise changing the software >configuration of a board (like erasing some flash memory) you should >make sure that you have all necessary information about such data. Can you tell me please, how or where can i find the serial number of the board? I have a PPC_4XX board(i think 405) with IBM STB02500 and U-Boot 1.1.2 already installed on it. Thanks. _________________________________________________________________ http://redirect.gimas.net/?n=M0910xHerbstmode2 So gehst du mir nicht vor die Tür! Herbsttrends entdecken

2 1

[U-Boot] some question about mips/board.c?
by Xiangfu Liu 15 Oct '09

15 Oct '09

Hi why the line 354 not include by ifndef CONFIG_SYS_NO_FLASH. I defined CONFIG_SYS_NO_FLASH in my board head file (qi_lb60.h). this line make compile error. thanks for help. in the lib_mips/board.c -------------- 347 #ifndef CONFIG_SYS_NO_FLASH 348 /* configure available FLASH banks */ 349 size = flash_init(); 350 display_flash_config (size); 351 bd->bi_flashsize = size; 352 #endif 353 354 bd->bi_flashstart = CONFIG_SYS_FLASH_BASE; you can find our source code at http://projects.qi-hardware.com/index.php/p/qi-u-boot/ -- Xiangfu Liu Email: xiangfu at qi-hardware dot com Web: http://www.qi-hardware.com

2 1

[U-Boot] Regarding LM90 support on u-boot
by Thirumalai 15 Oct '09

15 Oct '09

Hi denx, Is there any support for LM90 temperature sensor on u-boot? Any patches Regards, T.

2 1

[U-Boot] TI DA8xx/OMAP-L1x support in U-Boot
by Thompson, Nick (GE EntSol, Intelligent Platforms) 15 Oct '09

15 Oct '09

Hi, First post here, so apologies up front... I was wondering what the status of support for DA8xx in u-boot is. Is anyone working on that? The reason I ask is that I have made an initial port for the TI da830 evm board which seems to be working (serial, ethernet dhcp & tftp and i2c tested) and seems capable of booting Linux at least. It is based on GPL code from several sources, not least of which is from TI's old 1.3.3 version of u-boot, but I have updated it to support CONFIG_NET_MULTI and sorted out the padding changes in the ns16550 driver CONFIGs. It uses already present davinci drivers where possible. I have interest in getting at least USB and NAND support working as well - maybe SPI FLASH too - and will work on that as access to hardware allows. My git tree is up to date, but I'm new to git too, so I have no idea how to dump a patch. Regardless, I wanted to check I'm not treading on anyone's toes first and to gauge interest, especially as TI appear to have done some work on this in the past. Bye, Nick.

3 4

[U-Boot] U-boot doesn't start
by ExpatEgghead 15 Oct '09

15 Oct '09

Hi all; Having installed the ELDK and gitted the latest u-boot I can build it OK. The trouble is after flashing it the ubl will start but not u-boot itself. Reverting to the old u-boot we got from TI on the SDK works just fine but this is 1.2.0 and we wanted the latest version. We are using the DM355 EVM board design with some changes of our own. Does anyone have any pointers as to what I should do next? Regards -- --Adrian Edmonds

1 0

[U-Boot] Please pull u-boot-i2c.git next branch
by Heiko Schocher 15 Oct '09

15 Oct '09

The following changes since commit 6b8edfde22acc574b5532e9f086e6a7287a9bc78: Wolfgang Denk (1): Prepare v2009.06-rc1 are available in the git repository at: git://git.denx.de/u-boot-i2c.git next Peter Tyser (12): i2c.h: Provide a default CONFIG_SYS_I2C_SLAVE value cpci750: i2c cleanup Marvell: i2c cleanup mpc7448hpc2: Add CONFIG_SYS_I2C_SPEED define tsi108_i2c: Add i2c_init() stub function cm5200: Make function test command names more unique i2c: Create common default i2c_[set|get]_bus_speed() functions i2c: Remove deprecated individual i2c commands i2c: Update references to individual i2c commands cmd_i2c: Clean up i2c command argument parsing cmd_i2c: Clean up trivial helper functions cmd_i2c: Fix i2c help command output when CONFIG_I2C_MUX README | 20 +---- board/Marvell/common/i2c.c | 19 +++-- board/cm5200/cmd_cm5200.c | 18 ++-- board/esd/cpci750/i2c.c | 16 ++-- board/esd/tasreg/tasreg.c | 4 +- common/cmd_eeprom.c | 4 - common/cmd_i2c.c | 176 +++++++++++++------------------------- cpu/arm920t/at91rm9200/i2c.c | 10 -- cpu/mpc512x/i2c.c | 14 --- cpu/mpc8260/i2c.c | 16 ---- cpu/ppc4xx/40x_spd_sdram.c | 4 - cpu/ppc4xx/44x_spd_ddr.c | 4 - cpu/ppc4xx/i2c.c | 14 --- doc/README.ebony | 20 ++-- doc/README.m52277evb | 8 +-- doc/README.m5373evb | 8 +-- doc/README.m54455evb | 8 +-- doc/README.m5475evb | 8 +-- doc/README.ppc440 | 4 +- doc/README.xpedite1k | 6 +- doc/feature-removal-schedule.txt | 12 --- drivers/i2c/soft_i2c.c | 14 --- drivers/i2c/tsi108_i2c.c | 11 ++- include/configs/DU405.h | 1 - include/configs/DU440.h | 1 - include/configs/MPC8313ERDB.h | 1 - include/configs/MPC8349EMDS.h | 1 - include/configs/MPC8349ITX.h | 1 - include/configs/MPC8360ERDK.h | 1 - include/configs/MPC8536DS.h | 1 - include/configs/MPC8568MDS.h | 1 - include/configs/MPC8569MDS.h | 1 - include/configs/MPC8572DS.h | 1 - include/configs/MVBLM7.h | 1 - include/configs/PMC440.h | 1 - include/configs/SIMPC8313.h | 1 - include/configs/XPEDITE5200.h | 1 - include/configs/XPEDITE5370.h | 1 - include/configs/ads5121.h | 1 - include/configs/at91rm9200ek.h | 1 - include/configs/bubinga.h | 2 +- include/configs/katmai.h | 1 - include/configs/keymile-common.h | 1 - include/configs/kmeter1.h | 1 - include/configs/korat.h | 1 - include/configs/mpc7448hpc2.h | 1 + include/configs/sacsng.h | 6 +- include/configs/sbc8349.h | 1 - include/configs/socrates.h | 1 - include/configs/taihu.h | 2 +- include/i2c.h | 12 ++- 51 files changed, 140 insertions(+), 324 deletions(-) -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

6 5

[U-Boot] NET: SDP3430: trouble with shifting from LAN9C916 to SMC91XX driver
by Nishanth Menon 15 Oct '09

15 Oct '09

Hi Folks, While attempting to address the warning for SDP3430 as pointed out by dirk in [1], I did a patch corresponding to what was done for EVM(353x) as in [2]. unfortunately, this wont work for me, I get: U-Boot 2009.08-00515-gfea6a55-dirty (Oct 12 2009 - 14:03:23) OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz OMAP3 SDP3430 board + LPDDR/NOR I2C: ready DRAM: 128 MB Flash: 128 MB In: serial Out: serial Err: serial smc911x: Invalid chip endian 0xdee0013d Net: No ethernet found. OMAP34XX SDP # and no network, using LEGACY driver seems to be working just great for me. Note: in my patch [2], I did try both CONFIG_SMC911X_32_BIT and CONFIG_SMC911X_16_BIT with no luck either way. I even tried to hack the driver by skipping the supported chip detection code, but the driver still did not work for me. scanning a little more in the git repo, I see all the ancient boards of OMAP family - 5912,2420 etc.. still have LEGACY driver being used.. I am pretty sure I must be missing something here and appreciate any guidance folks can give me on this.. -- Regards, Nishanth Menon Ref: [1] http://www.nabble.com/forum/Permalink.jtp?root=25837696&post=25841367&page=y [2] From fea6a55cb67b3fda1d93da74b2fe68fb25376e7e Mon Sep 17 00:00:00 2001 From: Nishanth Menon <nm(a)ti.com> Date: Mon, 12 Oct 2009 13:54:17 -0500 Subject: [BAD][PATCH] TI OMAP3: SDP3430: dont use legacy ethernet driver Stop using the LEGACY driver and use NET_MULTI this also removes the build warning for SDP3430 --- board/ti/sdp3430/sdp.c | 8 +++++--- include/configs/omap3_sdp3430.h | 7 ++++--- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/board/ti/sdp3430/sdp.c b/board/ti/sdp3430/sdp.c index 40cf26f..85181c8 100644 --- a/board/ti/sdp3430/sdp.c +++ b/board/ti/sdp3430/sdp.c @@ -22,6 +22,7 @@ * MA 02111-1307 USA */ #include <common.h> +#include <netdev.h> #include <twl4030.h> #include <asm/io.h> #include <asm/arch/mux.h> @@ -121,8 +122,8 @@ int board_init(void) return 0; } -#define LAN_RESET_REGISTER (CONFIG_LAN91C96_BASE + 0x01c) -#define ETH_CONTROL_REG (CONFIG_LAN91C96_BASE + 0x30b) +#define LAN_RESET_REGISTER (CONFIG_SMC911X_BASE + 0x01c) +#define ETH_CONTROL_REG (CONFIG_SMC911X_BASE + 0x30b) /** * @brief ether_init Take the Ethernet controller out of reset and wait @@ -130,7 +131,7 @@ int board_init(void) */ static void ether_init(void) { -#ifdef CONFIG_DRIVER_LAN91C96 +#ifdef CONFIG_SMC911X int cnt = 20; writew(0x0, LAN_RESET_REGISTER); @@ -155,6 +156,7 @@ static void ether_init(void) writeb(readb(ETH_CONTROL_REG) & ~0x1, ETH_CONTROL_REG); udelay(1000); + smc911x_initialize(0, CONFIG_SMC911X_BASE); reset_err_out: return; diff --git a/include/configs/omap3_sdp3430.h b/include/configs/omap3_sdp3430.h index 229dc5e..7b0a248 100644 --- a/include/configs/omap3_sdp3430.h +++ b/include/configs/omap3_sdp3430.h @@ -200,9 +200,10 @@ */ #if defined(CONFIG_CMD_NET) -#define CONFIG_DRIVER_LAN91C96 -#define CONFIG_LAN91C96_BASE DEBUG_BASE -#define CONFIG_LAN91C96_EXT_PHY +#define CONFIG_NET_MULTI +#define CONFIG_SMC911X +#define CONFIG_SMC911X_32_BIT +#define CONFIG_SMC911X_BASE DEBUG_BASE #define CONFIG_BOOTP_SEND_HOSTNAME /* -- 1.6.3.3

3 6

[U-Boot] [PATCH v1]ppc/P1_P2_RDB: Data width for eSDHC using I2C device on P1 & P2 RDB Platforms
by Dipen Dudhat 15 Oct '09

15 Oct '09

On P1 and P2 RDB Platforms read the I2C EEPROM to get various board switch settings like NOR Flash Bank selection, SD Data width etc. Depending on, switch SW5[6] - select width for eSDHC ON - 4-bit [Enable eSPI] OFF - 8-bit [Disable eSPI] Signed-off-by: Dipen Dudhat <dipen.dudhat(a)freescale.com> --- - applies to http://git.denx.de/u-boot.git board/freescale/p1_p2_rdb/p1_p2_rdb.c | 21 +++++++++++++++++++++ 1 files changed, 21 insertions(+), 0 deletions(-) diff --git a/board/freescale/p1_p2_rdb/p1_p2_rdb.c b/board/freescale/p1_p2_rdb/p1_p2_rdb.c index 4c03468..e3ab73c 100644 --- a/board/freescale/p1_p2_rdb/p1_p2_rdb.c +++ b/board/freescale/p1_p2_rdb/p1_p2_rdb.c @@ -130,9 +130,30 @@ int checkboard (void) int board_early_init_r(void) { + u8 i2c_data; + volatile ccsr_gur_t *gur = (void *)(CONFIG_SYS_MPC85xx_GUTS_ADDR); const unsigned int flashbase = CONFIG_SYS_FLASH_BASE; const u8 flash_esel = 2; + i2c_set_bus_num(1); + if (i2c_read(0x18, 0, 1, &i2c_data, sizeof(i2c_data)) == 0) { + if (i2c_data & 0x2) + printf("NOR Flash Bank : Secondary\n"); + else + printf("NOR Flash Bank : Primary\n"); + + if (i2c_data & 0x1) { + setbits_be32(&gur->pmuxcr,MPC85xx_PMUXCR_SD_DATA); + printf("SD/MMC : 8-bit Mode\n"); + printf("eSPI : Disabled\n"); + } else { + printf("SD/MMC : 4-bit Mode\n"); + printf("eSPI : Enabled\n"); + } + } + else + printf("Failed reading I2C Chip 0x18 on bus 1\n"); + /* * Remap Boot flash region to caching-inhibited * so that flash can be erased properly. -- 1.5.6.3

2 1

[U-Boot] NFS file system mounting problem
by Heyendal, Carl 15 Oct '09

15 Oct '09

Hi, First post, and also a U-Boot newbie. I'm working with a U-Boot configuration that I did not build myself. I'm having trouble getting U-Boot to mount an NFS root file system on my target platform. I have read the U-Boot manual regarding setting up 'bootargs' with all the necessary NFS information, but Linux is ignoring the information and mounting the resident file system that's on my target; which of course I'm trying to bypass. >From printenv: bootargs=console=ttyS0,115200 root=/dev/nfs rw nfsroot=10.10.1.16:/home/heyendal/buildroot/buildroot-2009.08/project_build_arm/ILS_CM/root ip=10.10.1.8:10.10.1.16:10.10.1.1:255.255.252.0:cm_carlh::off Below is the output that I get that clearly shows the correct NFS information is getting passed to Linux, however the subsequent messages after the freeing of memory is from my resident file system: NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. IP-Config: Complete: device=eth0, addr=10.10.1.8, mask=255.255.252.0, gw=10.10.1.1, host=cm_carlh, domain=, nis-domain=(none), bootserver=10.10.1.16, rootserver=10.10.1.16, rootpath= Freeing init memory: 1396K ---------------------- Starting init script ---------------------- ---------------------- Populating /dev ---------------------- ---------------------- Waiting for SD card ---------------------- eth0: link up (10/Half) In the U-Boot Manual section describing how to mount an NFS file system, the example they use shows Linux mounting an NFS root file system, which is more like what I'm expecting. IP-Config: Complete: device=eth0, addr=192.168.100.6, mask=255.255.0.0, gw=255.255.255.255, host=canyonlands, domain=, nis-domain=(none), bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath= Looking up port of RPC 100003/2 on 192.168.1.1 eth0: link is up, 1000 FDX, pause enabled Looking up port of RPC 100005/1 on 192.168.1.1 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 156k init Can someone help with my problem? thanx /carl h. Carl Heyendal Senior Embedded S/W Designer Stanley Healthcare Solutions 309 Legget Drive Ottawa, ON K2K 3A3 Canada Tel: 613-592-6997 ext. 265 Fax: 613 592-4296 cheyendal(a)stanleyworks.com<mailto:cheyendal@stanleyworks.com> www.stanleyhealthcare.com<http://www.stanleyhealthcare.com/> This e-mail, including any attached files, is intended only for the person to whom or the entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

3 4