June 2011 - U-Boot

[U-Boot] Congrtulations !!!!
by Mrs. Anita R�diger 13 Jun '11

13 Jun '11

Microsoft Corporation Sweepstakes Promotion, Customer Service. Your Winning Batch No: POK/LTY/2901 Your Winning Reference No: GFMS/600/3011 OFFICIAL WINNING NOTIFICATION. We are pleased to inform you of the release of the long awaited results of Sweepstakes promotion organized by Microsoft Corporations, in conjunction with the FOUNDATION FOR THE PROMOTION OF SOFTWARE products, (F.P.S.) held this June 2011, in Madrid Spain. Where in your email address emerged as one of the online Winning emails in the 2nd category and therefore attracted a cash award of 350,000.00 euro (Three Hundred and Fifty Thousand Euros Only) and a Toshiba laptop. To begin your claim, do file for the release of your winning by contacting our Foreign Transfer Manager: Mr. Steven Magua Tel:0034-634- 020-681 Fax:0034-911-881-484 Email:info_claims@micsp-online.com The Microsoft Internet E-mail lottery Awards is sponsored by former CEO/Chairman, Bill Gates and a consortium of software promotion companies. The Intel Group, Toshiba, Dell Computers and other International Companies. The Microsoft internet E-mail draw is held periodically and is organized to encourage the use of the Internet and promote computer literacy worldwide. Congratulations!! Sincerely, Mrs. Anita Rьdiger , Promotions Manager. (Group Co-ordinator)

1 0

[U-Boot] convention for SPI dummy data?
by wolfgang＠leila.ping.de 13 Jun '11

13 Jun '11

Hi, I have finally got MMC/SD working on my coldfire board and would like to send some patches. However, one of the things I had to change was the dummy data sent out by SPI for read-only transactions. The original driver had all zeros, for SD/MMC all ones (0xFF) is needed. Is such a change acceptable, or is there any configuration option/flag I could use? Regards, Wolfgang

4 7

[U-Boot] [STATUS] Release delayed by two weeks
by Wolfgang Denk 13 Jun '11

13 Jun '11

Hello all, I decided to delay the release by two weeks. The new scheduled release date is June 27. The reason for the shift is that we still have heavy cleanup activity going on in the ARM area, especially there is a number of patyches pending for At91 based boards. I would like to get these into the upcoming release, to have a clear position for the planned Big Board Cleanup (= removal) after the release. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de "'Tis true, 'tis pity, and pity 'tis 'tis true." - Poloniouius, in Willie the Shake's _Hamlet, Prince of Darkness_

1 0

[U-Boot] Helpdesk Technical Issue!!
by Rebecca Cousin 13 Jun '11

13 Jun '11

Your mailbox has exceeded one or more size limits set by your administrator. Your mailbox size is 47796 KB.This is a notification warning message that your mailbox reaches 47500 KB.You may not be able to send or receive new mail until you Increase and Re-actviate and update your mailbox size. Click to Validate and update Your Mailbox and make more space available. Click Here:<https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEVfRmR4dnNjZz…> Failure To Validate and update Your Mailbox To make more space available; May Result In Loss Of Important Information In Your Mailbox/Or Cause Limited Access To It. Thanks for the Inconveniences. Administration Help desk.

1 0

[U-Boot] [PATCH 0/6] OMAP: fix build breaks on OMAP boards
by Aneesh V 13 Jun '11

13 Jun '11

Fix build breaks for OMAP boards. All the build breaks were due to couple of missing defines in the config file, namely: CONFIG_SYS_SDRAM_BASE and CONFIG_SYS_INIT_SP_ADDR They have been fixed by providing the right SDRAM base address and by using SRAM base as the initial stack address. None of these have been tested as I do not have any of these boards. Aneesh V (6): omap1610h2: fix build breaks omap5912osk: fix build breaks omap1510inn: fix build breaks omap1610inn: fix build breaks omap2420h4: fix build breaks omap730p2: fix build breaks include/configs/omap1510inn.h | 3 +++ include/configs/omap1610h2.h | 3 +++ include/configs/omap1610inn.h | 3 +++ include/configs/omap2420h4.h | 3 +++ include/configs/omap5912osk.h | 3 +++ include/configs/omap730p2.h | 3 +++ 6 files changed, 18 insertions(+), 0 deletions(-)

2 26

[U-Boot] Please pull u-boot-ti/master
by s-paulraj＠ti.com 13 Jun '11

13 Jun '11

The following changes since commit 9571865e0d32b1bcf8a6625497d1cd5d4bbad354: Wolfgang Denk (1): Merge branch 'master' of git://git.denx.de/u-boot-arm are available in the git repository at: git://git.denx.de/u-boot-ti.git master Aneesh V (6): omap1610h2: fix build breaks omap5912osk: fix build breaks omap1510inn: fix build breaks omap1610inn: fix build breaks omap2420h4: fix build breaks omap730p2: fix build breaks include/configs/omap1510inn.h | 5 +++++ include/configs/omap1610h2.h | 5 +++++ include/configs/omap1610inn.h | 5 +++++ include/configs/omap2420h4.h | 4 ++++ include/configs/omap5912osk.h | 5 +++++ include/configs/omap730p2.h | 5 +++++ 6 files changed, 29 insertions(+), 0 deletions(-)

2 1

[U-Boot] Fw:Re: encounter 'bad length' problem in u-boot
by jxnuxdy 13 Jun '11

13 Jun '11

Wolfgang,The version is 2010.03-rc1 (Netlogic ported it), I heard there is also some change on mainline uboot, but I am not sure the exactly version, however I only want to know how this issue happens? and what's the solution then?Thanks again.Dennis-------- Forwarding messages -------- From: "Wolfgang Denk" <wd(a)denx.de> Date: 2011-06-10 14:20:51 To: jxnuxdy <jxnuxdy(a)163.com> Cc: u-boot(a)lists.denx.de Subject: Re: encounter 'bad length' problem in u-boot Dear jxnuxdy, In message <71744a2e.17da7.130777b8fa1.Coremail.jxnuxdy(a)163.com> you wrote: > > I enconter the problem 'bad length' during the ping, can anybody > give a point as how this issue happen, how to kill it even this maybe > not an critical issue ... Which board is this, and which exact version of U-Boot? > u-boot $ ping 10.4.58.48> > Using nae-6 device This does not look like any code supported in mainline U-Boot? Best regards,Wolfgang Denk-- DENX Software Engineering GmbH, MD: Wo lfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de On a clear disk you can seek forever.

1 0

Re: [U-Boot] [PATCH v3] mx31ads: Use the new relocation scheme
by Felix Radensky 13 Jun '11

13 Jun '11

Hi Fabio, On 01/-10/-28163 09:59 PM, wrote: > Signed-off-by: Fabio Estevam fabio.estevam(a)freescale.com > --- > Changes since v2: > - Use PHYS_SDRAM_1 in get_ram_size > - Remove local config.mk > > Changes since v1: > > - Fixed lines over 80 characters. > > Build tested only. > > Do not have the hardware handy to test. > I've tested your patch on mx31ads. Unfortunately it bricks the board. There are no messages on console. The latest u-boot version that works on this board is 2010.09. I've compiled u-boot using ELDK-4.2. If you have any ideas, I'm ready to test your patches. Felix.

2 6

[U-Boot] why I can't run the u-boot from flash?
by Jason.Sun 12 Jun '11

12 Jun '11

I am porting a boot from sequoia. I have use the BDI3000 to load the u-boot.bin and flash to norflash. I can trace the codes by BDI3000 and receive the u-boot info from uart as following. but when I try to power on and run the codes itself but not use BDI3000 to send "go". there are not any characters from the uart port. I have no idea to find the bug. have any one can give some advice? Jason U-Boot 1.3 CPU: AMCC PowerPC 440EPx Rev. A at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz) Security/Kasumi support Bootstrap Option A - Boot ROM Location EBC (8 bits) Internal PCI arbiter enabled, PCI async ext clock used 32 kB I-Cache 32 kB D-Cache Board: Sequoia - AMCC PPC440EPx Evaluation Board, Rev. 0, PCI=33 MHz I2C: ready DTT: 1 FAILED INIT DRAM: 256 MB FLASH: 64 MB NAND: 512 MiB PCI: Bus Dev VenId DevId Class Int 00 04 7080 0001 7b20 43 USB: Host(int phy) Device(ext phy) Net: ppc_4xx_eth0, ppc_4xx_eth1 Type run flash_nfs to mount root filesystem over NFS Hit any key to stop autoboot: 0 => => => printe bootcmd=run flash_self bootdelay=5 baudrate=115200 loads_echo= preboot=echo;echo Type "run flash_nfs" to mount root filesystem over NFS;echo hostname=sequoia netdev=eth0 nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ramargs=setenv bootargs root=/dev/ram rw addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off panic=1 addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate} addmisc=setenv bootargs ${bootargs} initrd_high=30000000 kernel_addr_r=400000 fdt_addr_r=800000 hostname=sequoia bootfile=sequoia/uImage rootpath=/opt/eldk/ppc_4xxFP flash_self=run ramargs addip addtty addmisc;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} flash_nfs=run nfsargs addip addtty addmisc;bootm ${kernel_addr} - ${fdt_addr} net_nfs=tftp ${kernel_addr_r} ${bootfile}; tftp ${fdt_addr_r} ${fdt_file}; run nfsargs addip addtty addmisc;bootm ${kernel_addr_r} - ${fdt_addr_r} fdt_file=sequoia/sequoia.dtb flash_self_old=run ramargs addip addtty addmisc;bootm ${kernel_addr} ${ramdisk_addr} flash_nfs_old=run nfsargs addip addtty addmisc;bootm ${kernel_addr} net_nfs_old=tftp ${kernel_addr_r} ${bootfile};run nfsargs addip addtty addmisc;bootm ${kernel_addr_r} load=tftp 200000 sequoia/u-boot.bin update=protect off 0xFFFA0000 FFFFFFFF;era 0xFFFA0000 FFFFFFFF;cp.b ${fileaddr} 0xFFFA0000 ${filesize};setenv filesize;saveenv upd=run load update nload=tftp 200000 sequoia/u-boot-nand.bin nupdate=nand erase 0 100000;nand write 200000 0 100000;setenv filesize;saveenv nupd=run nload nupdate kernel_addr=FC000000 ramdisk_addr=FC180000 ethaddr=00:10:EC:00:1D:95 eth1addr=00:10:EC:80:1D:95 ethact=ppc_4xx_eth0 bootargs=root=/dev/ram rw ip=::::sequoia:eth0:off panic=1 console=ttyS0,115200 ipaddr=172.17.25.69 mem=262120k ver=U-Boot 1.3 Environment size: 1799/8187 bytes =>

1 0

[U-Boot] [PATCH] at91_emac: fix compile warning
by Andreas Bießmann 12 Jun '11

12 Jun '11

This patch removes the warning ---8<--- at91_emac.c: In function 'at91emac_write_hwaddr': at91_emac.c:487:2: warning: dereferencing type-punned pointer will break strict-aliasing rules --->8--- Signed-off-by: Andreas Bießmann <andreas.devel(a)gmail.com> --- BEWARE! This patch is only compile tested! It is possible, that there is an endianess problem. It would be great, if one could test it on real hardware! Reinhard, you could adopt the macb driver also to get the warning there fixed. If it works on at91sam this way it would also work on at91rm9200 cause they have the same endianess. drivers/net/at91_emac.c | 12 +++++++----- 1 files changed, 7 insertions(+), 5 deletions(-) diff --git a/drivers/net/at91_emac.c b/drivers/net/at91_emac.c index b09ff8c..97d2739 100644 --- a/drivers/net/at91_emac.c +++ b/drivers/net/at91_emac.c @@ -481,11 +481,13 @@ static int at91emac_write_hwaddr(struct eth_device *netdev) dev = (emac_device *) netdev->priv; writel(1 << ATMEL_ID_EMAC, &pmc->pcer); - DEBUG_AT91EMAC("init MAC-ADDR %x%x \n", - cpu_to_le16(*((u16 *)(netdev->enetaddr + 4))), - cpu_to_le32(*((u32 *)netdev->enetaddr))); - writel(cpu_to_le32(*((u32 *)netdev->enetaddr)), &emac->sa2l); - writel(cpu_to_le16(*((u16 *)(netdev->enetaddr + 4))), &emac->sa2h); + DEBUG_AT91EMAC("init MAC-ADDR %02x:%02x:%02x:%02x:%02x:%02x\n", + netdev->enetaddr[5], netdev->enetaddr[4], netdev->enetaddr[3], + netdev->enetaddr[2], netdev->enetaddr[1], netdev->enetaddr[0]); + writel( (netdev->enetaddr[0] | netdev->enetaddr[1] << 8 | + netdev->enetaddr[2] << 16 | netdev->enetaddr[3] << 24), + &emac->sa2l); + writel((netdev->enetaddr[4] | netdev->enetaddr[5] << 8), &emac->sa2h); DEBUG_AT91EMAC("init MAC-ADDR %x%x \n", readl(&emac->sa2h), readl(&emac->sa2l)); return 0; -- 1.7.2.5

2 5