January 2006 - U-Boot

[U-Boot-Users] env_size
by J. William Campbell 05 Jan '06

05 Jan '06

Does anybody know what the variable env_size defined in common/environment.c is used for? It is declared extern in envcrc.c but not used otherwise as near as I can determine. It used to be used in envcrc.c, but not after version 1.2. I have done a search of all u-boot files without finding any uses. Should it be removed?? Best Regards, Bill Campbell

1 0

RE: [U-Boot-Users] Suggestion on flash init
by Nuno João (Ext_NBS) 05 Jan '06

05 Jan '06

I am using the CFI driver (as it is in u-boot 1.1.3) with Spansion flash chips (S29GL512N11xxx: 2 x 16 bit chips, 32 bit port). I had no problems; I can do all the usual operations. My config is: #define CFG_FLASH_BASE CFG_FLASH_MEM_BASE #define CFG_MAX_FLASH_BANKS 1 /* number of banks */ #define CFG_MAX_FLASH_SECT 512 /* sectors per device */ #undef CFG_FLASH_CHECKSUM #define CFG_FLASH_ERASE_TOUT 1024000 /* Flash Erase Timeout (ms) */ #define CFG_FLASH_WRITE_TOUT 500 /* Flash Write Timeout (ms) */ #define CFG_FLASH_CFI_DRIVER #define CFG_FLASH_CFI #define CFG_FLASH_EMPTY_INFO Cheers ------------------------------------------------- => flinfo Bank # 1: CFI conformant FLASH (32 x 16) Size: 128 MB in 512 Sectors Erase timeout 16384 ms, write timeout 1 ms, buffer write timeout 4096 ms, buffer size 32 Sector Start Addresses: F8000000 E F8040000 E F8080000 E F80C0000 E F8100000 E F8140000 E F8180000 E F81C0000 E F8200000 E F8240000 E ... -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Tolunay Orkun Sent: quarta-feira, 4 de Janeiro de 2006 22:32 To: Wang Jian Cc: Wolfgang Denk; u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] Suggestion on flash init Wang Jian wrote: >>In message <20051225190658.F3F9.LARK(a)linux.net.cn> you wrote: >> >>>I have tested cfi_flash.c for a while. Unfortuanately, it fails for >>>Spansion S29AL016M. The chip can be recognized, chip information is all >>>correct, but the erase and write routines fail. (...)

1 0

[U-Boot-Users] FEC problem on MPC5200 board (Men PP01)
by Felipe Gil Castiñeira 05 Jan '06

05 Jan '06

Hi everyone! I am porting U-Boot to "Men mikro elektronik" PP01 module (MPC5200). The FEC is integrated on the MPC5200 and the PHY is a LXT971ALE transceiver. U-Boot boots and recognizes the Ethernet device (I can read the PHY transceiver registers, change the LED status, etc.), but when I try to ping a target the system freezes (and the Watchdog resets the board). The behavior is just the same with tftp or bootp. I am sure it is not a hardware problem, as I can transfer files (for example u-boot.bin) from a computer to the same module using the original monitor (MENMON). >From the debugging information *it seems the code fails in the function "mpc5xxx_fec_recv"*. Furthermore, analyzing the network with Ethereal I can observe an ARP request generated by the PING and the corresponding answer (at this moment the watchdog resets the board). If I ping a non existent address the timer expires and I receive a "ping failed; host 192.168.1.25 is not alive" (Ethereal detects the ARP request, but of course, there is not an ARP answer). Any idea? Thanks in advance. Best regards, Felipe. P.S.: I paste below the debugging info *======================================================* *Ping to a non existent address (No answer)* *======================================================* => ping 192.168.1.22 Mii reg 0: 0x0000 Mii reg 1: 0x0000 Mii reg 2: 0x0000 Mii reg 3: 0x0000 Mii reg 4: 0x0000 Mii reg 5: 0x0000 Mii reg 6: 0x0000 Mii reg 7: 0x0000 Mii reg 8: 0x0000 Mii reg 16: 0x0000 Mii reg 17: 0x0000 Mii reg 18: 0x0000 Mii reg 19: 0x0000 Mii reg 20: 0x0000 Ethernet task stopped mpc5xxx_fec_init... Begin tfifo_status: 0x00010000 tfifo_alarm: 0x00000080 Mii reg 0: 0x1000 Mii reg 1: 0x782d Mii reg 2: 0x0013 Mii reg 3: 0x78e2 Mii reg 4: 0x01e1 Mii reg 5: 0x41e1 Mii reg 6: 0x0007 Mii reg 7: 0x2001 Mii reg 8: 0x0000 Mii reg 16: 0x0084 Mii reg 17: 0x4780 Mii reg 18: 0x0000 Mii reg 19: 0x0000 Mii reg 20: 0x0422 mpc5xxx_fec_init... Done Using FEC ETHERNET device sending ARP for c0a80116 ARP broadcast 1 tbd status: 0x0000 tbd_scrub: fec->cleanTbdNum = 48, fec->usedTbdIndex = 0 Tx Buffer Descriptor ring (tbd) limpo SDMA_TASK_ENABLE, fec->tbdIndex = 1 + ------------------------------------------------------------------------------------------------------------------------------------------2 tbd status: 0x0c00 tbd_scrub: fec->cleanTbdNum = 47, fec->usedTbdIndex = 0 SDMA_TASK_ENABLE, fec->tbdIndex = 2 + ------------------------------------------------------------------------------------------------------------------------------------------0 Mii reg 1: 0x782d Mii reg 2: 0x0013 Mii reg 3: 0x78e2 Mii reg 4: 0x01e1 Mii reg 5: 0x41e1 Mii reg 6: 0x0007 Mii reg 7: 0x2001 Mii reg 8: 0x0000 Mii reg 16: 0x0084 Mii reg 17: 0x4780 Mii reg 18: 0x0000 Mii reg 19: 0x0000 Mii reg 20: 0x0422 Ethernet task stopped ping failed; host 192.168.1.22 is not alive => *======================================================* *Ping to a existent address * *======================================================* => ping 192.168.1.1 Mii reg 0: 0x1000 Mii reg 1: 0x782d Mii reg 2: 0x0013 Mii reg 3: 0x78e2 Mii reg 4: 0x01e1 Mii reg 5: 0x41e1 Mii reg 6: 0x0007 Mii reg 7: 0x2001 Mii reg 8: 0x0000 Mii reg 16: 0x0084 Mii reg 17: 0x4780 Mii reg 18: 0x0000 Mii reg 19: 0x0000 Mii reg 20: 0x0422 Ethernet task stopped mpc5xxx_fec_init... Begin tfifo_status: 0x00010000 tfifo_alarm: 0x00000080 Mii reg 0: 0x1000 Mii reg 1: 0x782d Mii reg 2: 0x0013 Mii reg 3: 0x78e2 Mii reg 4: 0x01e1 Mii reg 5: 0x41e1 Mii reg 6: 0x0007 Mii reg 7: 0x2001 Mii reg 8: 0x0000 Mii reg 16: 0x0084 Mii reg 17: 0x4780 Mii reg 18: 0x0000 Mii reg 19: 0x0000 Mii reg 20: 0x0422 mpc5xxx_fec_init... Done Using FEC ETHERNET device sending ARP for c0a80101 ARP broadcast 1 tbd status: 0x0000 tbd_scrub: fec->cleanTbdNum = 48, fec->usedTbdIndex = 0 Tx Buffer Descriptor ring (tbd) limpo SDMA_TASK_ENABLE, fec->tbdIndex = 1 + <<<----After the "+" the system hangs.

3 3

[U-Boot-Users] Please add my id in mailing list
by Akshay Kumar Behera 05 Jan '06

05 Jan '06

hi.. Send instant messages to your online friends http://in.messenger.yahoo.com

1 0

[U-Boot-Users] Suggestion on flash init
by Wang Jian 05 Jan '06

05 Jan '06

Hi, After reading many board/*/flash.c and writing customer board driver for one of my customer, I think the current flash interface can be improved. I suggest adding a subdir $(TOPDIR)/include/flash/ and putting flash chip information here. When you use some kinds of flash chips, just include relevant header files. If we go further, many information in $(TOPDIR)/include/flash.h can be put into these header files. And, even flash operation (non-CFI) sample code can be put into $(TOPDIR)/contrib/flash/. The following is an example of AMD Spansion S29AL016M chip. --snip-- #ifndef _FLASH_S29AL016M_H_ #define _FLASH_S29AL016M_H_ #define FLASH_S29AL016M_T_SECTORS 35 #define FLASH_S29AL016M_B_SECTORS 35 #define FLASH_S29AL016M_T_SIZE 0x00200000 #define FLASH_S29AL016M_B_SIZE 0x00200000 int FLASH_S29AL016M_T_BYTE_SA[] = { 0x000000, 0x010000, 0x020000, 0x030000, 0x040000, 0x050000, 0x060000, 0x070000, 0x080000, 0x090000, 0x0A0000, 0x0B0000, 0x0C0000, 0x0D0000, 0x0E0000, 0x0F0000, 0x100000, 0x110000, 0x120000, 0x130000, 0x140000, 0x150000, 0x160000, 0x170000, 0x180000, 0x190000, 0x1A0000, 0x1B0000, 0x1C0000, 0x1D0000, 0x1E0000, 0x1F0000, 0x1F8000, 0x1FA000, 0x1C0000 }; int FLASH_S29AL016M_T_WORD_SA[] = { 0x000000, 0x008000, 0x010000, 0x018000, 0x020000, 0x028000, 0x030000, 0x038000, 0x040000, 0x048000, 0x050000, 0x058000, 0x060000, 0x068000, 0x070000, 0x078000, 0x080000, 0x088000, 0x090000, 0x098000, 0x0A0000, 0x0A8000, 0x0B0000, 0x0B8000, 0x0C0000, 0x0C8000, 0x0D0000, 0x0D8000, 0x0E0000, 0x0E8000, 0x0F0000, 0x0F8000, 0x0FC000, 0x0FD000, 0x0FE000 }; int FLASH_S29AL016M_B_BYTE_SA[] = { 0x000000, 0x004000, 0x006000, 0x008000, 0x010000, 0x020000, 0x030000, 0x040000, 0x050000, 0x060000, 0x070000, 0x080000, 0x090000, 0x0A0000, 0x0B0000, 0x0C0000, 0x0D0000, 0x0E0000, 0x0F0000, 0x100000, 0x110000, 0x120000, 0x130000, 0x140000, 0x150000, 0x160000, 0x170000, 0x180000, 0x190000, 0x1A0000, 0x1B0000, 0x1C0000, 0x1D0000, 0x1E0000, 0x1F0000 }; int FLASH_S29AL016M_B_WORD_SA[] = { 0x000000, 0x002000, 0x003000, 0x004000, 0x008000, 0x010000, 0x018000, 0x020000, 0x028000, 0x030000, 0x038000, 0x040000, 0x048000, 0x050000, 0x058000, 0x060000, 0x068000, 0x070000, 0x078000, 0x080000, 0x088000, 0x090000, 0x098000, 0x0A0000, 0x0A8000, 0x0B0000, 0x0B8000, 0x0C0000, 0x0C8000, 0x0D0000, 0x0D8000, 0x0E0000, 0x0E8000, 0x0F0000, 0x0F8000 }; #endif --snip-- In flash_get_size() --snip-- switch (device) { case BYTEME(AMD_ID_S29AL016M_T): info->flash_id += FLASH_S29AL016M_T; info->sector_count = FLASH_S29AL016M_T_SECTORS; info->size = FLASH_S29AL016M_T_SIZE; break; case BYTEME(AMD_ID_S29AL016M_B): info->flash_id += FLASH_S29AL016M_B; info->sector_count = FLASH_S29AL016M_B_SECTORS; info->size = FLASH_S29AL016M_B_SIZE; break; --snip-- In flash_get_offset() --snip-- switch (info->flash_id & FLASH_TYPEMASK) { case FLASH_S29AL016M_T: for (i = 0; i < info->sector_count; i++) { info->start[i] = base + FLASH_S29AL016M_T_BYTE_SA[i]; } break; case FLASH_S29AL016M_B: for (i = 0; i < info->sector_count; i++) { info->start[i] = base + FLASH_S29AL016M_B_BYTE_SA[i]; } break; --snip-- -- lark

3 10

[U-Boot-Users] Jump vector table after relocation
by Umar Qureshey 05 Jan '06

05 Jan '06

Hi, I am studying the startup code in cpu/arm926ejs/start.S. I have a question regarding relocation. I understand how and under what conditions the code is relocating. But it seems to me that during relocation, u-boot copies verything including the jump vector table to the RAM. However, the CPU is only aware of a fixed address for the vector jump table i.e. 0x00000000. So my question is, is this copying redundant? Or does the CPU somehow use the newly copied table residing in RAM, rather than the original flash one? On the ARM Integrator/CP board I am using, external switches do allow RAM to be located at 0x00000000 instead of flash but I don't think this switch can be done at run time. Regards, Umar

1 0

[U-Boot-Users] OS dependencies on the bootloader
by Andrew Wozniak 04 Jan '06

04 Jan '06

Hello everyone, A general bootloader question: How much hardware initialization should a bootloader perform for the target OS? I see a minimal memory controller setup to allow subsequent loading of an OS image. ECC might also be setup but all remaining resources would typically be setup by the OS. Although I haven't tried booting Linux (we boot the vxworks bootrom), does an embedded Linux make any assumptions about what the bootloader initializes? Thank you and best regards, Andy

2 1

Re: [U-Boot-Users] Re: Git clone problems?
by Wolfgang Denk 04 Jan '06

04 Jan '06

In message <1136376985.43bbbc99a5ae2@webmail.televes.com:443> you wrote: > > > Try again, please. I think I cleaned up a few problems yesterday. > > Yeah, I finally got it (but it lasted almost one hour to clone). The whole repository is *big* (350+ MB), and HTTP is not exactly an efficient access method. I always use rsync for the initial clone, and then change it (in ".git/branches/origin") to http for updates. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de The goal of science is to build better mousetraps. The goal of nature is to build better mice.

2 1

[U-Boot-Users] bl cpu_init_f jumps to an wrong point.
by Nekto Peresmeshnik 04 Jan '06

04 Jan '06

Hello community, I've problem with jump to cpu_init_f. I trace the begin of u-boot execution, i.e. assembler code. It is okay, until it achieves the jump to cpu_init_f. Then it jumps to a random point. "Random" means that it is same point for every compilation. After next compilation this point changes randomly. The picture is next: in debugger I see that cpu_init_f placed on the address 0xfff06924. I see same when I do disassemble the u-boot image. Please hint where may I be mistaken? The board: custom 8247A based, 2 M. flash. Compilation: configured and compiled for 8260. Neither error nor warnings during compilation. Toolchain: ELDK version 3.1.1 Build 2005-06-07 Linux: SuSE 9.3 kernel 2.6.11.4-21.9-default

2 1

Re: [U-Boot-Users] Re: Git clone problems?
by Wolfgang Denk 04 Jan '06

04 Jan '06

In message <1136384022.43bbd816d8f32@webmail.televes.com:443> you wrote: > > Yes, I usually do like you. But this time it seems rsync has similar problem. > > $> time cg-clone rsync://source.denx.net/git/linux-2.6-denx.git "source.denx.net" is bandwith-throttled at 30 kB/s ;-) I recommend to use our official public server instead, i. e. http://www.denx.de/git/<project_name> Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de It is common sense to take a method and try it. If it fails, admit it frankly and try another. But above all, try something. - Franklin D. Roosevelt

1 0