January 2006 - U-Boot

[U-Boot-Users] network driver link error
by Xuezhang Dong 14 Jan '06

14 Jan '06

I donot have network support in my board, but when I try to remove the network driver support from my config file, I got the link error.(otherwise everything is fine and I can run the u-boot 1.1.4 without any trouble now). So I want to understand that is it the mandatory to have network support? or I can disable the support of network by using some flag? /* * Hardware drivers */ #define CONFIG_DRIVER_LAN91C96 #define CONFIG_LAN91C96_BASE 0x04000300 #define CONFIG_LAN91C96_EXT_PHY Thanks. Xuezhang.

2 1

[U-Boot-Users] CFI flash – Problem with erasing boot block.
by John_s (sent by Nabble.com) 13 Jan '06

13 Jan '06

Hi All, I am developing a CFI based flash driver. I can query the device and get all sector/block information. I am having problems erasing sectors 1, 2, 3 and 4 (bottom 64-KB), please the flash geometry below. The problem is that when I attempt to erase sectors 1, 2, 3, OR 4 I end up erasing sectors 1-4 . Not sure why this is happening. I am able to erase the remaining sectors, sectors 5 through 19 individually without problems. Here is flash’s geometry. I would appreciate your expert opinion as how to avoid this or even as it why it is happening. Thanks in advance. Device: ST’s M29w800DB, Bottom boot block. Sector 1 0x00000 – 0x01fff Sector 2 0x02000 – 0x02fff Sector 3 0x03000 – 0x03fff Sector 4 0x04000 – 0x07fff -> First 64Kb boundary. Sector 5 0x08000 – 0x07fff -> All remaining sectors are 64 -Kb bulk sectors. …………………………………. Sector 19 0x78000 – 0x7ffff - John -- View this message in context: http://www.nabble.com/CFI-flash-Problem-with-erasing-boot-block.-t911704.ht… Sent from the Uboot - Users forum at Nabble.com.

2 1

[U-Boot-Users] MC9328MXL/1 SDRAM initialization
by llandre 13 Jan '06

13 Jan '06

I have a question about how MC9328MXL/1 initializes SDRAM memories. These is the instructions used to set up the Mode Command Register (file board/mx1ads/lowlevel_init.S) for MX1ADS evalutaion board: /* Issue Mode Register Command */ ldr r3, =0x08111800 /* Mode Register Value */ ldr r2, [r3] In my understanding address lines are connected as follows: SDRAM -> MC9328MXL ------------------- A12 -> A13 A11 -> A12 A10 -> MA11 A9 -> MA10 A8 -> A10 A7 -> A9 A6 -> A8 A5 -> A7 A4 -> A6 A2 -> A5 A1 -> A3 A0 -> A2 Thus, when writing to address 0x08111800, microprocessor address lines from A8 to A6 are set to 0. It implies that SDRAM address lines from A6 to A4 are set to 0. These lines are decoded by the SDRAM chips as CAS latency. Allowed values are 010 (CAS latency = 2) and 011 (CAS latency = 3). The value 000 is reserved. So I think I'm misunderstanding how the SDRAM controller works. Anybody can help me? Thanks in advance, llandre DAVE Electronics System House - R&D Department web: http://www.dave-tech.it email: r&d2(a)dave-tech.it

2 2

[U-Boot-Users] how to generate uImage of ramdisk.gz for mips arch?
by zhuzhenhua 13 Jan '06

13 Jan '06

what the -a and -e should be for ramdisk.gz i see in kernel image, the -a means where kernel to load and -e means kernel entry but i am not sure what -a and -e mean for ramdisk.gz, are they always be 0x0? thanks for any hints Best reagards zhuzhenhua

2 1

[U-Boot-Users] board porting question
by Xuezhang Dong 13 Jan '06

13 Jan '06

Hi, all I have a board with arm926 big-endian, serial port, NOR/SRAM. I used omap 1610H2 as my code base since the cpu type is same. Problem is that the printf() function doesnot work, for example: printf("\n%s\n", uboot_version); instead of print the real string, it give me the "%s" as is. So I want to know it is a big-edian problem or ..., any clue will be appreciated. Thanks. Xuezhang.

3 3

[U-Boot-Users] Excluding Env Variable section from the u-boot.bin
by Albert David 13 Jan '06

13 Jan '06

Dears, For my ppc405EP based custom board I would like to make few changes to the u-boot memory map, so that every time I update the u-boot, environment variables in the flash remain untouched. Flash Memory used:S29GL128M(spansion 16MB Flash with 128 uniform sectors of 128KB each) Current mapping U-Boot Start Flash Address 0xFFF60000 - 2 sectors U-Bot Env Variable Start Addr 0xFFFA000 - 1 sector U-Bot Env Variable(Redundant)Start Addr 0xFFFC000 - 1 sector U-Boot End sector - 1 sector Size of the binary output of u-boot(u-boot.bin) after build is 128kb*5sectors=648Kbytes. Current settings in the source tree: U-boot-1.1.4/include/configs/my_board.h #define CFG_FLASH_BASE 0xFFF60000 #define CFG_MONITOR_BASE CFG_FLASH_BASE #define CFG_MONITOR_LEN (640 * 1024) #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_ADDR 0xFFFA0000 #define CFG_ENV_SECT_SIZE 0x20000 #define CFG_ENV_ADDR_REDUND 0xFFFC0000 #define CFG_ENV_SIZE_REDUND 0x20000 U-boot-1.1.4/my_board/config.mk TEXT_BASE = 0xFFF60000 U-boot-1.1.4/my_board/u-boot.lds ppcenv_assert = ASSERT(. < 0xFFFA0000, ".bss section too big, overlaps .ppcenv section. Please update your confguration: CFG_MONITOR_BASE, CFG_MONITOR_LEN and TEXT_BASE may need to be modified."); . = 0xFFFA0000; .ppcenv : { common/environment.o(.ppcenv); } Required mapping: U-Bot Env Variable Start Addr 0xFFF8000 - 1 sector U-Bot Env Variable(Redundant)Start Addr 0xFFFA000 - 1 sector U-Boot Start Flash Address 0xFFFC0000 - 2 sectors Required Size of the binary output of u-boot(u-boot.bin) after build is 128kb*2sectors=256Kbytes. I have already tried to modify the above specified files to: U-boot-1.1.4/include/configs/my_board.h #define CFG_FLASH_BASE 0xFFFC0000 #define CFG_MONITOR_BASE CFG_FLASH_BASE #define CFG_MONITOR_LEN (256 * 1024) #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_ADDR 0xFFF80000 #define CFG_ENV_SECT_SIZE 0x20000 #define CFG_ENV_ADDR_REDUND 0xFFFA0000 #define CFG_ENV_SIZE_REDUND 0x20000 U-boot-1.1.4/my_board/config.mk TEXT_BASE = 0xFFFC0000 U-boot-1.1.4/my_board/u-boot.lds ppcenv_assert = ASSERT(. < 0xFFF80000, ".bss section too big, overlaps .ppcenv section. Please update your confguration: CFG_MONITOR_BASE, CFG_MONITOR_LEN and TEXT_BASE may need to be modified."); . = 0xFFF80000; .ppcenv : { common/environment.o(.ppcenv); } But after doing "make all" I get the message ppc_4xx-ld:.bss section too big, overlaps .ppcenv section. Please update your confguration: CFG_MONITOR_BASE, CFG_MONITOR_LEN and TEXT_BASE may need to be modified. In a simple term, I wanted to build my u-boot by excluding environment variable section of the memory.. Can any one help me? Where am I going wrong?? Is there any other modification needs to be done other than the above specified changes? Thanks in advance for your support, With best regards, Albert.

3 4

RE: [U-Boot-Users] board porting question
by Xuezhang Dong 13 Jan '06

13 Jan '06

I figure out this problem, it is due to the code in start.S set up Align, so the data read from 16-bit-bus throught ldrb will revert in big-endian case, and OMAP is little-endian, so they are OK. cpu_init_crit: /* * flush v4 I/D caches */ mov r0, #0 mcr p15, 0, r0, c7, c7, 0 /* flush v3/v4 cache */ mcr p15, 0, r0, c8, c7, 0 /* flush v4 TLB */ /* * disable MMU stuff and caches */ mrc p15, 0, r0, c1, c0, 0 bic r0, r0, #0x00002300 /* clear bits 13, 9:8 (--V- --RS) */ bic r0, r0, #0x00000087 /* clear bits 7, 2:0 (B--- -CAM) */ orr r0, r0, #0x00000002 /* set bit 2 (A) Align */ orr r0, r0, #0x00001000 /* set bit 12 (I) I-Cache */ mcr p15, 0, r0, c1, c0, 0 /* * Go setup Memory and board specific bits prior to relocation. */ mov ip, lr /* perserve link reg across call */ bl platformsetup /* go setup pll,mux,memory */ mov lr, ip /* restore link */ mov pc, lr /* back to my caller */ I was debugging the ns16550 (serial driver), and find out that my serial port is not logically as same as theirs. I was assume that UART is very standard, is it true? Any suggestion of other serial drive I can try? Regards. Xuezhang. -----Original Message----- From: wd(a)denx.de [mailto:wd@denx.de] Sent: Thursday, January 12, 2006 5:04 PM To: Xuezhang Dong Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] board porting question In message <54AD0F12E08D1541B826BE97C98F99F11C29CE(a)NT-SJCA-0751.brcm.ad.broadcom.co m> you wrote: > Thanks for the reply and my appology for the HTML format, I thought > mail server will convert it. Never mind, it wonot happened again. Thanks. > I was using the latest toolchain from snapgear: > ARM/XSCALE - arm-linux-tools-20051123.tar.gz > > And I supplied the compiler with -mbigarm parameter. > > Any idea how I can verify/debug this problem? Attach your BDI2000 and fire up GDB? 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 Microsoft Multimedia: You have nice graphics, sound and animations when the system crashes.

1 0

[U-Boot-Users] board porting question
by Xuezhang Dong 13 Jan '06

13 Jan '06

Thanks for the reply and my appology for the HTML format, I thought mail server will convert it. Never mind, it wonot happened again. I was using the latest toolchain from snapgear: ARM/XSCALE - arm-linux-tools-20051123.tar.gz And I supplied the compiler with -mbigarm parameter. Any idea how I can verify/debug this problem? Thanks. Xuezhang. In message <54AD0F12E08D1541B826BE97C98F99F11C29B3(a)NT-SJCA-0751.brcm.ad.broadcom.co m> you wrote: > > I have a board with arm926 big-endian, serial port, NOR/SRAM. I used > omap 1610H2 as my code base since the cpu type is same. Problem is > that the printf() function doesnot work, for example: > printf("\n%s\n", uboot_version); instead of print the real string, it > give me the "%s" as is. > So I want to know it is a big-edian problem or ..., any clue will be > appreciated. I can only speculate here. Eventually this is a toolchain problem (printf() being a variable argument list function and thus sensible against problems with parameter passing). > Content-Type: text/html; > charset=us-ascii > Content-Transfer-Encoding: quoted-printable And will you please stop posting HTML here??? I am *seriously* considering the option to move this list from SF and reject all messages that contain HTML (or even base64) encoded messages!!! Best regards, Wolfgang Denk

2 1

RE: [U-Boot-Users] board porting question
by Xuezhang Dong 12 Jan '06

12 Jan '06

Again this is the screen print out looks like: %s U-Boot code: lFsa:hB%** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn %s sU-Boot code: BlFsa:hB** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn %s sU-Boot code: BlFsa:hB%** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn %s sU-Boot code: BlFsa:hB** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn Regards. Xuezhang. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Xuezhang Dong Sent: Thursday, January 12, 2006 2:31 PM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] board porting question Thanks for the reply and my appology for the HTML format, I thought mail server will convert it. Never mind, it wonot happened again. I was using the latest toolchain from snapgear: ARM/XSCALE - arm-linux-tools-20051123.tar.gz And I supplied the compiler with -mbigarm parameter. Any idea how I can verify/debug this problem? Thanks. Xuezhang. In message <54AD0F12E08D1541B826BE97C98F99F11C29B3(a)NT-SJCA-0751.brcm.ad.broadcom.co m> you wrote: > > I have a board with arm926 big-endian, serial port, NOR/SRAM. I used > omap 1610H2 as my code base since the cpu type is same. Problem is > that the printf() function doesnot work, for example: > printf("\n%s\n", uboot_version); instead of print the real string, it > give me the "%s" as is. > So I want to know it is a big-edian problem or ..., any clue will be > appreciated. I can only speculate here. Eventually this is a toolchain problem (printf() being a variable argument list function and thus sensible against problems with parameter passing). > Content-Type: text/html; > charset=us-ascii > Content-Transfer-Encoding: quoted-printable And will you please stop posting HTML here??? I am *seriously* considering the option to move this list from SF and reject all messages that contain HTML (or even base64) encoded messages!!! Best regards, Wolfgang Denk ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=ick _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

[U-Boot-Users] Re: Problem with the cfi flash driver with a x8/x16 flash configuredin x8 mode.
by Alex BASTOS 12 Jan '06

12 Jan '06

Txema, > Does anybody test the cfi flash driver (cfi_flash.c) with a x8/x16 > flash configured in x8 mode ? I'm trying to port U-Boot for a Lite5200B > with a S29GL128N flash (CFI compliant) using the cfi flash driver. > U-Boot detects the flash correctly but It's unable to erase or write the > flash. In my case the following patch fix the bug but I'm not completly > sure If It's only a bug with my configuration. Any suggestions? Could > anybody test the patch in other architecture? I think your topic is very similar to this recent one: http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/19970 and previous similar patches have been submited and are still pending (but it seems they are coming, read the whole thread) So, yes, til now cfi_flash didn't support x8 mode for AMD chips, but it will. Best regards, Alex BASTOS

1 0

Fwd: Re[2]: [U-Boot-Users] at91rm9200 lowlevel_init.S
by Zhukov 12 Jan '06

12 Jan '06

>> Does anybody know, what can be tuned in "lowlevel_init" procedure in >> lowlevel_init.S module for at91rm9200dk? This init suspends u-boot. I WD> The code is supposed to work fine on the at91rm9200dk board. WD> Are you really using such a board, or is this some custom hardware? Yes, my board is customozed - the hardware engineer edited RomBoot because of some differences in SDRAM system. But... anyway, the lowlevel_init.S seems so strange, that some bug in its code is suspected. Would you explain the meaning of _MTEXT_BASE in fragments like this: ldr r0, =SMRDATA1 ldr r1, _MTEXT_BASE sub r0, r0, r1 add r2, r0, #176 2: /* the address */ ldr r1, [r0], #4 /* the value */ ldr r3, [r0], #4 str r3, [r1] cmp r2, r0 bne 2b I guess _MTEXT_BASE is a start of code, the location just after vectors. But what's the use of it here? Suspecting hardware problem, I skip everything after the first step of the procedure: /* Get the CKGR Base Address */ ldr r1, =AT91C_BASE_CKGR /* Main oscillator Enable register */ #ifdef CFG_USE_MAIN_OSCILLATOR ldr r0, =0x0000FF01 /* Enable main oscillator */ #else ldr r0, =0x0000FF00 /* Disable main oscillator */ #endif str r0, [r1, #CKGR_MOR] ... /* delay */ b exit This cut works fine, u-boot loads. Next, I tried to replace this with the following: ldr r0, =CKGRDATA ldr r1, _MTEXT_BASE sub r0, r0, r1 add r2, r0, #8 /* 8 bytes */ 3: /* the address */ ldr r1, [r0], #4 /* the value */ ldr r3, [r0], #4 str r3, [r1] cmp r2, r0 bne 3b ... /* delay */ ... CKGRDATA: .word AT91C_BASE_CKGR .word 0x0000FF01 /* 8 bytes long */ It FAILS! Obviously, u-boot crashes here. Something wrong in code... Best regards,

2 1

RE: [U-Boot-Users] Excluding Env Variable section from the u-boot.bin
by Nuno João (Ext_NBS) 12 Jan '06

12 Jan '06

As far as I understood / remember, you can have the environment and part of u-boot's code sharing the same sector, which makes it at least more difficult to upgrade the code using a BDI-like tool which usually works on a full-sector basis. -----Original Message----- From: wd(a)denx.de [mailto:wd@denx.de] Sent: quinta-feira, 12 de Janeiro de 2006 14:44 To: Nuno João (Ext_NBS) Cc: u-boot-users(a)lists.sourceforge.net; Albert David Subject: Re: [U-Boot-Users] Excluding Env Variable section from the u-boot.bin (...) It is *always* possible to update the U-Boot image and keep the old environment settings. Typically all you need for embedded environment is a simple "saveenv" command.

2 1

[U-Boot-Users] help reqd for flash
by prabha.j＠tcs.com 12 Jan '06

12 Jan '06

Hi all, I am having some doubts regarding the flashes. I am having two types of flash. One flash is of ST make (M29W040B) having two chips of 512kbit size (total size is 1MB). The total sector in each chip is 8. and another flash used for storing code. This is of AMD make (AM29LV160B).It is also of two chips with 2MBit and total is 4MB size.The total sector is 35. Now my question is how to define these things in myboard.h file. ie #define CFG_MAX_FLASH_BANKS //what values i have to put for these defined variables #define CFG_MAX_FLASH_SECT // what values i have to put for these defined variable #define CFG_FLASH_SIZE //what values i have to put for these defined variable #define CFG_FLASH_ERASE_TOUT 8000 /* Timeout for Flash Erase (in ms) */ #define CFG_FLASH_WRITE_TOUT 5 /* Timeout for Flash Write (in ms) */ #define CFG_FLASH_LOCK_TOUT 5 /* Timeout for Flash Set Lock Bit (in ms) */ #define CFG_FLASH_UNLOCK_TOUT 10000 /* Timeout for Flash Clear Lock Bits (in ms) */ #define CFG_FLASH_PROTECTION 2. I came to know from datasheet of AMD that it is CFI complaint but i did get any info regarding ST make . Can anybody tell is this flash is cfi complaint or not. Please help me in this regard. Thanks in advance. Prabha J. Tata Consultancy Services Limited Mailto: prabha.j(a)tcs.com Website: http://www.tcs.com Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 3

RE: [U-Boot-Users] Excluding Env Variable section from the u-boot.bin
by Nuno João (Ext_NBS) 12 Jan '06

12 Jan '06

I have a configuration in 2 of "my" boards where the environment variable's area lays in a different sector from u-boot code, also so that it is possible to upgrade u-boot while keeping the environment: In mpc8xx board I have: /* * Environment in flash. It will be on the flash's 3rd 64KB block, fully * using it. U-boot will use the 1st two 64KB blocks, as specified by * CFG_MONITOR_LEN above. */ #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_OFFSET 0x20000 /* Offset of Environment Sector */ #define CFG_ENV_SIZE 0x10000 /* Total Size of Environment Sector */ In a mpc85xx board I have: /* * Environment */ #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_SECT_SIZE 0x40000 /* 256K (one sector) for env */ /* env in its own flash sector, right before u-boot */ #define CFG_ENV_SIZE CFG_ENV_SECT_SIZE #define CFG_ENV_ADDR 0xffe00000 I didn't need to change anything else. There are some preprocessor macros in the environment code that will handle most of the job. Cheers -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Albert David Sent: quinta-feira, 12 de Janeiro de 2006 11:27 To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] Excluding Env Variable section from the u-boot.bin Dears, For my ppc405EP based custom board I would like to make few changes to the u-boot memory map, so that every time I update the u-boot, environment variables in the flash remain untouched. (...)

2 1

[U-Boot-Users] Problem with the cfi flash driver with a x8/x16 flash configuredin x8 mode.
by Txema Lopez 12 Jan '06

12 Jan '06

Hi all, Does anybody test the cfi flash driver (cfi_flash.c) with a x8/x16 flash configured in x8 mode ? I'm trying to port U-Boot for a Lite5200B with a S29GL128N flash (CFI compliant) using the cfi flash driver. U-Boot detects the flash correctly but It's unable to erase or write the flash. In my case the following patch fix the bug but I'm not completly sure If It's only a bug with my configuration. Any suggestions? Could anybody test the patch in other architecture? My configuration for the cfi driver is: #define CFG_MAX_FLASH_BANKS 2 /* max num of memory banks */ #define CFG_MAX_FLASH_SECT 128 /* max num of sects on one chip */ #undef CONFIG_FLASH_16BIT /* Flash is 8-bit */ #define CFG_FLASH_CFI_DRIVER #define CFG_FLASH_CFI #define CFG_FLASH_BANKS_LIST {CFG_CS1_START,CFG_CS0_START} And the patch: --- ../tmp/u-boot/drivers/cfi_flash.c 2006-01-12 12:22:08.000000000 +0100 +++ drivers/cfi_flash.c 2006-01-12 13:35:11.000000000 +0100 @@ -107,9 +107,19 @@ #define AMD_STATUS_TOGGLE 0x40 #define AMD_STATUS_ERROR 0x20 + +#if 0 #define AMD_ADDR_ERASE_START 0x555 #define AMD_ADDR_START 0x555 #define AMD_ADDR_ACK 0x2AA +#else +int amd_addr_erase_start = 0x555; +int amd_addr_start = 0x555; +int amd_addr_ack = 0x2AA; +#define AMD_ADDR_ERASE_START amd_addr_erase_start +#define AMD_ADDR_START amd_addr_start +#define AMD_ADDR_ACK amd_addr_ack +#endif #define FLASH_OFFSET_CFI 0x55 #define FLASH_OFFSET_CFI_RESP 0x10 @@ -1111,6 +1121,9 @@ ulong flash_get_size (ulong base, int ba info->flash_id = FLASH_MAN_CFI; if ((info->interface == FLASH_CFI_X8X16) && (info->chipwidth == FLASH_CFI_BY8)) { info->portwidth >>= 1; /* XXX - Need to test on x8/x16 in parallel. */ + amd_addr_erase_start = 0xAAA; + amd_addr_start = 0xAAA; + amd_addr_ack = 0x555; } } Best regards, Jose Maria Lopez.

1 0

[U-Boot-Users] the custom borad supportting nandflash
by willow (sent by Nabble.com) 12 Jan '06

12 Jan '06

Hi all, Who could tell me any custom board' name which image of the u-boot.bin is saved in the nandflash in a "u-boot-1.1.4.tar.bz2" packet. I am portting the u-boot to a arm926jes cutom borad booting from a nandflash and had successfully boot from a norflash. But what do I need to do for booting from nand? Perhaps I can find some tips from the exist custom boards in the u-boot packet. Please help. Best regards, Willow -- View this message in context: http://www.nabble.com/the-custom-borad-supportting-nandflash-t896328.html#a… Sent from the Uboot - Users forum at Nabble.com.

2 3

[U-Boot-Users] sandpoint8245 Build fails with optimization turned off
by Eric Olsen 12 Jan '06

12 Jan '06

I was attempting to debug an issue so I wanted to turn off the optimization (change from -Os to -O0 in config.mk) so I can more easily step thru code in gdb. When I do this for the sandpoint8245 target I get the following error. I am using u-boot 1.1.4 pulled down yesterday and gcc 4.0.1 toolchain built by crosstool. a - virtex2.o a - xilinx.o gmake[1]: Leaving directory `/home/eolsen/tree/u-boot-1.1.4/u-boot-1.1.4/common' UNDEF_SYM=`powerpc-603e-linux-gnu-objdump -x lib_generic/libgeneric.a board/sandpoint/libsandpoint.a cpu/mpc824x/libmpc824x.a lib_ppc/libppc.a fs/cramfs/libcramfs.a fs/fat/libfat.a fs/fdos/libfdos.a fs/jffs2/libjffs2.a fs/reiserfs/libreiserfs.a fs/ext2/libext2fs.a net/libnet.a disk/libdisk.a rtc/librtc.a dtt/libdtt.a drivers/libdrivers.a drivers/sk98lin/libsk98lin.a post/libpost.a post/cpu/libcpu.a common/libcommon.a |sed -n -e 's/.*$__u_boot_cmd_.*$/-u\1/p'|sort|uniq`;\ powerpc-603e-linux-gnu-ld -Bstatic -T /home/eolsen/tree/u-boot-1.1.4/u-boot-1.1.4/board/sandpoint/u-boot.lds -Ttext 0xFFF00000 -n $UNDEF_SYM cpu/mpc824x/start.o \ --start-group lib_generic/libgeneric.a board/sandpoint/libsandpoint.a cpu/mpc824x/libmpc824x.a lib_ppc/libppc.a fs/cramfs/libcramfs.a fs/fat/libfat.a fs/fdos/libfdos.a fs/jffs2/libjffs2.a fs/reiserfs/libreiserfs.a fs/ext2/libext2fs.a net/libnet.a disk/libdisk.a rtc/librtc.a dtt/libdtt.a drivers/libdrivers.a drivers/sk98lin/libsk98lin.a post/libpost.a post/cpu/libcpu.a common/libcommon.a --end-group -L /usr/local/opt/crosstool/gcc-4.0.1-glibc-2.3.5/powerpc-603e-linux-gnu/bin/../lib/gcc/powerpc-603e-linux-gnu/4.0.1/nof -lgcc \ -Map u-boot.map -o u-boot /home/eolsen/tree/u-boot-1.1.4/u-boot-1.1.4/board/sandpoint/u-boot.lds:134 cannot move location counter backwards (from fff04288 to fff04000) gmake: *** [u-boot] Error 1 Has anyone else managed to fix this? Thanks Eric

2 1

[U-Boot-Users] ssi.h missing for sc520_spunk
by sunjo (sent by Nabble.com) 11 Jan '06

11 Jan '06

I am using the AMD Elan SC520 microcontroller. Trying to create a bootloader using u-boot. However i although i am able to configure the file using make sc520_spunk_config I am not fully able to make all and i always get the error # make distclean ......... # make sc520_spunk_config ......... #make all ......... error msg: ------------- a - vsprintf.o a - zlib.o make[1]: Leaving directory `/home/karthik/i386-uboot/src/u-boot-1.1.2/lib_generic' make -C `dirname board/sc520_spunk/libsc520_spunk.a` make[1]: Entering directory `/home/karthik/i386-uboot/src/u-boot-1.1.2/board/sc520_spunk' gcc -M -g -Os -D__KERNEL__ -DTEXT_BASE=0x387c0000 -I/home/karthik/i386-uboot/src/u-boot-1.1.2/include -fno-builtin -ffreestanding -nostdinc -isystem /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/include -pipe -DCONFIG_I386 -D__I386__ -march=i386 -Werror sc520_spunk_asm.S sc520_spunk_asm16.S sc520_spunk.c flash.c > .depend sc520_spunk.c:27:17: ssi.h: No such file or directory make[1]: *** [.depend] Error 1 make[1]: Leaving directory `/home/karthik/i386-uboot/src/u-boot-1.1.2/board/sc520_spunk' make: *** [board/sc520_spunk/libsc520_spunk.a] Error 2 I have tried to apply the patch that u have already provided in this forum, but that still does not solve the problem. Has there been any fix available for this yet. I presume it is a problem that all AMD users have when using U-boot. Hope to hear a reply soon. Thank you Sunjo -- View this message in context: http://www.nabble.com/ssi.h-missing-for-sc520_spunk-t897496.html#a2326260 Sent from the Uboot - Users forum at Nabble.com.

1 0

[U-Boot-Users] the custom borad supportting nandflash
by willow (sent by Nabble.com) 11 Jan '06

11 Jan '06

Hi all, Who could tell me any custom board' name which image of the u-boot.bin is saved in the nandflash in a "u-boot-1.1.4.tar.bz2" packet. I am portting the u-boot to a arm926jes cutom borad booting from a nandflash and had successfully boot from a norflash. But what do I need to do for booting from nand? Perhaps I can find some tips from the exist custom boards in the u-boot packet. Please help. Best regards, Willow -- View this message in context: http://www.nabble.com/the-custom-borad-supportting-nandflash-t896330.html#a… Sent from the Uboot - Users forum at Nabble.com.

1 0

[U-Boot-Users] at91rm9200 lowlevel_init.S
by Zhukov 11 Jan '06

11 Jan '06

Hello, everybody. Does anybody know, what can be tuned in "lowlevel_init" procedure in lowlevel_init.S module for at91rm9200dk? This init suspends u-boot. I tried to play with delays (loops), but it won't work anyway. Regards Andrew Zhukov

2 1

[U-Boot-Users] help for porting u-boot.bin into flash of ibm440ep board
by satish kumar 11 Jan '06

11 Jan '06

Hi i am trying to load the u-boot.bin file which i generated by using u-boot -1.1.3 code for powerpc IBM440ep board(ciss). after loading to the board,command prompt is not coming........... if any one knows pease tell me how to load the u-boot .bin into the flash of the particular architecture. Thanks& Regards Satish Send instant messages to your online friends http://in.messenger.yahoo.com

2 1

[U-Boot-Users] Help: Am29LV160B flash driver
by s.maiti＠tcs.com 11 Jan '06

11 Jan '06

I am using the /board/tqm5200/flash.c as the flash driver for our flash, since it has the support for Am29LV160B. But it's unable to identify the manufacture id and device id. Because of this the code is failing. Any help in this regard will be highly appreciated. Thanks and Regards, Souvik Maiti Tata Consultancy Services Limited Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

3 2

[U-Boot-Users] u-boot locking ?
by alfred hitch 11 Jan '06

11 Jan '06

Hi, I have some (basic) question .. 1) Does u-boot lock the block on which it resides by default ? I mean the sector /erase block on which u-boot is there, it will be locked using the block lock bit by default ? Plafform in question being IXDP 425 with Intel J3 NOR Flash. 2) The flash content changing has to work in block sizes erase - modify - write cyecles only ?? Reason for all this is that we have few boards on which u-boot is getting corrupted (on flash image corruption itself). And so am wondering even if its a noise issue, how can it first cause an unlock of sector before write. Any help in understanding of above issues will be really appreciated, Regards, Alfred

3 6

[U-Boot-Users] LED-D2,D3 on LN2410SBC
by Shakthi Kannan 10 Jan '06

10 Jan '06

Greetings! I am trying to get the leds, D2 and D3 to glow on the LN2410SBC board from littlechips.com. I am using u-boot-1.1.1 My code: /* * led.c */ #include <common.h> #include <exports.h> int main (int argc, char *argv[]) { int *r_gpbcon = 0x56000010; int *r_gpbdat = 0x56000014; app_startup(argv); printf ("r_gpbcon = %x\n", *(r_gpbcon)); *(r_gpbcon) = ((*(r_gpbcon))&~(0xf<<10))|(0x5<<10); printf ("r_gpbcon = %x\n", *(r_gpbcon)); printf ("r_gpbdat = %x\n", *(r_gpbdat)); *(r_gpbdat) |= (3<<5); printf ("r_gpbdat = %x\n", *(r_gpbdat)); return 0; } The Makefile I use to build it: # Makefile # Tools CROSS = /usr/local/arm/2.95.3/bin/arm-linux- CC = $(CROSS)gcc AS = $(CROSS)as LD = $(CROSS)ld OBJCOPY = $(CROSS)objcopy TARGET = led BASE = 0x30100000 CFLAGS = -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -fno-builtin -ffreestanding -nostdinc -isystem /usr/local/arm/2.95.3/bin/../lib/gcc-lib/arm-linux/2.95.3/include -pipe -DCONFIG_ARM -D__ARM__ -march=armv4 -Wall -Wstrict-prototypes INCLUDE = -I/home/shaks/code/ln2410sbc/uboot-1.1.1/include -I/usr/local/arm/2.95.3/lib/gcc-lib/arm-linux/2.95.3/include LIBSTUBS = /home/shaks/code/ln2410sbc/uboot-1.1.1/examples/libstubs.a LGCC = -L/usr/local/arm/2.95.3/bin/../lib/gcc-lib/arm-linux/2.95.3 -lgcc -L/home/shaks/code/ln2410sbc/uboot-1.1.1/examples -lstubs LIBSTUB_INCLUDE = /usr/local/arm/2.95.3/bin/../lib/gcc-lib/arm-linux/2.95.3/include LDFLAGS = -g -Ttext $(BASE) -e main all: $(CC) $(CFLAGS) $(INCLUDE) -c $(TARGET).c -o $(TARGET).o $(LD) $(LDFLAGS) $(TARGET).o -o $(TARGET) $(LIBSTUBS) $(LGCC) $(OBJCOPY) -O binary $(TARGET) $(TARGET).bin 2>/dev/null clean: rm -f *~ *.o *.bin $(TARGET) semantic.cache* I copy the led.bin file to /tftpboot in my host system, and I copy it to the board using "tftp 0x30100000 led.bin". It runs, but, leds d2 and d3 won't glow. Can anyone tell me what I am doing wrong and how I can get this up and running? Thanking you, SK -- Shakthi Kannan, MS Software Engineer, Hexaware Technologies [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

2 1

[U-Boot-Users] qemu + uboot
by Xavier Grave 10 Jan '06

10 Jan '06

Hi, Does somebody already try to boot some uboot executable from qemu-system-ppc ? I would like to have a starting point to port my small tiny OS written in Ada from x86 arch to ppc. Thanks in advance, xavier

1 0

[U-Boot-Users] [PATCH] Rename remaining CONFIG_INIT_CRITICAL to CONFIG_SKIP_LOWLEVEL_INIT for ARM targets
by Jean-Paul Saman 10 Jan '06

10 Jan '06

Patch by Jean-Paul Saman, 10 Jan 2006. CHANGELOG: * Rename remaining CONFIG_INIT_CRITICAL to CONFIG_SKIP_LOWLEVEL_INIT for ARM targets Kind greetings, Jean-Paul Saman Philips Semiconductors CTO/RTG Philips HighTech Campus, building WDA 3.29 Professor van den Holstlaan 4 5655 AA Eindhoven tel: +31 (0)40 27 45131

1 0

[U-Boot-Users] Help needed: Am29LV160B flash driver in mpc8260 based board
by s.maiti＠tcs.com 10 Jan '06

10 Jan '06

Hi all, Can any one help me regarding the flash driver (Am29LV160B) for our board? Which flash driver should I consider as reference code? Any help will be highly appreciated. Thanks and regards, Souvik Maiti Tata Consultancy Services Limited Mailto: s.maiti(a)tcs.com Website: http://www.tcs.com Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

[U-Boot-Users] RE: U-Boot-Users digest, Vol 1 #1658 - 10 msgs
by Akshay Kumar Behera 10 Jan '06

10 Jan '06

Hi , I am akshay Here. I want to make U-Boot for arm7tdmi architecture. The main aim my Boot Loader should acccept the image, which made in uclinux os for arm7tdmi processor. I have downloaded u-boot-1.1.4. Now i am using linux-9.0 version. Can you suggest me, how i will compile the same source code. Atfirst I am building thr Buildroot for arm architecture. I have downloaded Buildroot anapshot. Then I made menuconfig in Build root. After that, I went for make command for building the buildroot. At the last step, I am getting Following errors, [root@localhost staging_dir]# cd /buildroot [root@localhost buildroot]# make make -C /buildroot/toolchain_build_arm/uClibc \ PREFIX= \ DEVEL_PREFIX=/buildroot/build_arm/staging_dir/ \ RUNTIME_PREFIX=/buildroot/build_arm/staging_dir/ \ install_runtime install_dev make[1]: Entering directory `/buildroot/toolchain_build_arm/uClibc' install -d /buildroot/build_arm/staging_dir/lib install -m 644 lib/lib*-0.9.28.so \ /buildroot/build_arm/staging_dir/lib install: cannot stat `lib/lib*-0.9.28.so': No such file or directory make[1]: *** [install_runtime] Error 1 make[1]: Leaving directory `/buildroot/toolchain_build_arm/uClibc' make: *** [/buildroot/build_arm/staging_dir/lib/libc.a] Error 2 [root@localhost buildroot]# Will anybody please tell me what's the problem and how to solve it? Thanking you, Regards, Akshay -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of u-boot-users-request(a)lists.sourceforge.net Sent: Tuesday, January 10, 2006 1:40 AM To: u-boot-users(a)lists.sourceforge.net Subject: U-Boot-Users digest, Vol 1 #1658 - 10 msgs Send U-Boot-Users mailing list submissions to u-boot-users(a)lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/u-boot-users or, via email, send a message with subject or body 'help' to u-boot-users-request(a)lists.sourceforge.net You can reach the person managing the list at u-boot-users-admin(a)lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of U-Boot-Users digest..." Today's Topics: 1. Linux stops at turn_on_mmu when jumping to start_here (=?iso-8859-1?Q?Jose_Fran=E7a_=28Ext=5FGTBC=29?=) 2. About the u-boot (in ELF binary format) (=?GB2312?B?zNq3ycH6?=) 3. Re: u-boot locking ? (alfred hitch) 4. Re: u-boot locking ? (Wolfgang Denk) 5. Re: About the u-boot (in ELF binary format) (Wolfgang Denk) 6. Re: Linux stops at turn_on_mmu when jumping to start_here (Jerry Van Baren) 7. How do the arm926ejs boot from nand in Uboot? (willow (sent by Nabble.com)) 8. Re: Toolchain select (Khem Raj) 9. [PATCH] Allow top-level distclean target to descend to board Makefiles. (Jon Loeliger) --__--__-- Message: 1 Date: Mon, 9 Jan 2006 10:19:22 -0000 From: =?iso-8859-1?Q?Jose_Fran=E7a_=28Ext=5FGTBC=29?= <Jose.Franca.Ext(a)siemens.com> To: <u-boot-users(a)lists.sourceforge.net> Subject: [U-Boot-Users] Linux stops at turn_on_mmu when jumping to start_here Hello! I hope this subject isn't too much off-topic, but i'm stucked... I read = the FAQ's and searched in the mailing-list history for an answer, but = still i can't make it work and so i'm asking for your help. The situation is this... I am develloping the bootloader and kernel for = a board based on mpc8247: - u-boot is almost fully configured and running well - bd_t on u-boot and on linux have the same definitions - the platform header file that i created is based on rpx8260.h and = i'm using m8260_setup to fill ppc_md - CPM_MAP_ADDR and CFG_IMMR have the same value =09 I don't have yet a debugger at hand, but from what i've discovered it = stops in rfi instruction, when turning on MMU. Any suggestions would be = most welcomed... Many thanks for reading and many more if you respond :)! Filipe. --__--__-- Message: 2 Date: Mon, 9 Jan 2006 18:35:47 +0800 From: =?GB2312?B?zNq3ycH6?= <jinlongwei(a)gmail.com> To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] About the u-boot (in ELF binary format) Hi, I have successfully compiled u-boot and ,as you know, there are several object files produced after"make all", one of which is u-boot(in ELF binary format) . Now, i run the u-boot(in ELF binary format) in target board (Embedded Planet EP405)with Linux kernel and NFS file system. # ./u-boot then appears the error echo: Segmentation fault will you please tell me what's the problem and how to solve it? Thank you and best wishes!! --__--__-- Message: 3 Date: Mon, 9 Jan 2006 05:44:08 -0500 From: alfred hitch <alfred.hitch(a)gmail.com> To: Wolfgang Denk <wd(a)denx.de> Subject: Re: [U-Boot-Users] u-boot locking ? Cc: u-boot-users(a)lists.sourceforge.net Hi, just to add to my last post, the u-boot seems to be hanging in the function= : flash_get_size ???? Code comments in header for function says: * * The following code cannot be run from FLASH! * */ Any option I am missing which could be causing it to screw up ? My compilation is simple: make clean; make ixdp425_config; make (Before doing this, u-boot was working just fine for us ) Anyone has already tried marking blocks as locked on J3 Flash ? and can hel= p ? Regards, Alfred On 1/9/06, alfred hitch <alfred.hitch(a)gmail.com> wrote: > Hi Wolfgang, > > Thanks for your mails, u-boot in mycase also I observed wasnt being > called with hardware protection on. > > I will appreciate if someone can help me with following questions: > 1) I enabled these 3 defines in the include/configs/ixdp425.h #define > CFG_FLASH_PROTECTION #define CFG_FLASH_CFI_DRIVER #define > CFG_FLASH_CFI > > From what appeared logical (and compilation needs) to me. > But, when I am booting the system now, its hanging after displaying > the RAM configuration. > > I have just begun to trace down on what could be wrong,but it looks > from initial traces to be in flash_init. > > Anything I am missing / doing wrong ?? > > 2) Read somewhere on net, that by deault all sectors are locked after > reboo t ? true ? does J3 Intel strata flash does it also automatically > ? > > 3) Remember to do so after relocation to RAM. :: Can you please help > me to correct place, code path / function to do so ? I am very new to > u-boot. > > Regards, > Alfred > > > On 1/8/06, Wolfgang Denk <wd(a)denx.de> wrote: > > In message > > <29f916510601080721vd20b512u819ee9bce7ad1408(a)mail.gmail.com>= you wrote: > > > > > > 1) Does u-boot lock the block on which it resides by default ? > > > > Not by default, but you can inplement in your flah driver > > whichever features you like. > > > > > I mean the sector /erase block on which u-boot is there, it will > > > be locked using the block lock bit by default ? > > > > Remember that only few flash chips provide such hardware locking, > > and that some boards implement even other ways of write > > protection of parts of or of the whole flash device. > > > > > 2) The flash content changing has to work in block sizes erase - > > > modify - write cyecles only ?? > > > > No. You can write single bytes (as long as you are only changing '1' > > bits to '0'). > > > > > Reason for all this is that we have few boards on which u-boot is > > > getting corrupted (on flash image corruption itself). > > > And so am wondering even if its a noise issue, how can it first > > > cause an unlock of sector before write. > > > > Normally the flash is not hardare write protected, and if > > your hardware designer used flash chips which can be corrupted for > > example by just writing arbitrary data to a sequential address > > range you may easily see such corruption. There is a very good > > reason why AMD flash chips require a specific programming sequence > > which must be written in a certain sequence to certain non-consequitive addresses. > > > > 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 PoB =3D "Prisoner of Bill" -- those held captive, > > unwillingly or other- wise, by the contemptible Microsoft monopoly. > > -- Tom Christiansen in > > <6abo45$3lc$2(a)csnews.cs.colorado.edu> > > > --__--__-- Message: 4 To: alfred hitch <alfred.hitch(a)gmail.com> cc: u-boot-users(a)lists.sourceforge.net From: Wolfgang Denk <wd(a)denx.de> Subject: Re: [U-Boot-Users] u-boot locking ? Date: Mon, 09 Jan 2006 12:52:42 +0100 In message <29f916510601090155q21ac4a8dy8ad8a9012b3b3603(a)mail.gmail.com> = you wrote: >=20 > Thanks for your mails, u-boot in mycase also I observed wasnt being >called with hardware protection on. >=20 > I will appreciate if someone can help me with following questions: ... You may want to search the archive and read the previous postings to this topic first. There has been a long discussion about locking and what could or should be done about it. Best regards, Wolfgang Denk --=20 Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de "I've finally learned what `upward compatible' means. It means we get to keep all our old mistakes." - Dennie van Tassel --__--__-- Message: 5 To: =?GB2312?B?zNq3ycH6?= <jinlongwei(a)gmail.com> cc: u-boot-users(a)lists.sourceforge.net From: Wolfgang Denk <wd(a)denx.de> Subject: Re: [U-Boot-Users] About the u-boot (in ELF binary format) Date: Mon, 09 Jan 2006 12:53:56 +0100 In message <c002eb610601090235h7b139895p(a)mail.gmail.com> you wrote: > > I have successfully compiled u-boot and ,as you know, there are > several object files produced after"make all", one of which is > u-boot(in ELF binary format) . Now, i run the u-boot(in ELF binary > format) in target board (Embedded Planet EP405)with Linux kernel and > NFS file system. > # ./u-boot > then appears the error echo: > Segmentation fault > will you please tell me what's the problem and how to solve it? U-Boot is a boot loader and not an application programm which can be run under Linux. Best regards, Wolfgang Denk --=20 Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de Every little picofarad has a nanohenry all its own. - Don Vonada --__--__-- Message: 6 Date: Mon, 09 Jan 2006 09:23:09 -0500 From: Jerry Van Baren <gerald.vanbaren(a)smiths-aerospace.com> To: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] Linux stops at turn_on_mmu when jumping to start_here Jose França (Ext_GTBC) wrote: > Hello! > > I hope this subject isn't too much off-topic, but i'm stucked... I read the FAQ's and searched in the mailing-list history for an answer, but still i can't make it work and so i'm asking for your help. > The situation is this... I am develloping the bootloader and kernel for a board based on mpc8247: > > - u-boot is almost fully configured and running well > - bd_t on u-boot and on linux have the same definitions > - the platform header file that i created is based on rpx8260.h and i'm using m8260_setup to fill ppc_md > - CPM_MAP_ADDR and CFG_IMMR have the same value > > I don't have yet a debugger at hand, but from what i've discovered it stops in rfi instruction, when turning on MMU. Any suggestions would be most welcomed... > > Many thanks for reading and many more if you respond :)! > Filipe. That is where the MMU gets turned on and is a very delicate place. If there is anything wrong with your memory map/MMU configuration, life stops here with pretty much no indication of what is wrong (a hardware debugger can be used to get some clues, but even that is difficult). Since you are working without a hardware debugger, I would note that one common trap is to try to blink LEDs/toggle ports/transmit serial messages just after the IRET to get a progress report. Unfortunately, it generally causes a _lack_ of progress because the LED/port/serial is not part of the initial memory map and thus causes an address error, which _causes_ the total lock up. If you are trying to get progress indications, make sure the resources (port) is accessable in your memory map _before_ you try to use the port. This means either delaying your progress indicator till after the MMU is initialized or using a BAT to map it (making sure nobody else uses that BAT or re-initializes that BAT). Many of the BATs are dedicated to the start up of the MMU so you have to be careful of what one you use for mapping your progress port. gvb --__--__-- Message: 7 Date: Mon, 9 Jan 2006 07:55:22 -0800 (PST) From: "willow (sent by Nabble.com)" <lists(a)nabble.com> Reply-To: willow <liugeng-ws(a)163.com> To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] How do the arm926ejs boot from nand in Uboot? ------=_Part_938_11713481.1136822122949 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, My linux kernel has successfully run by U-booting from a norflash. 1)can the kernel based on arm 926ejs boot from nandflash? 2)which files I must modifiy in the U-boot packet if the kernel can boot from nandflash and where can I find more imforation about this. will you please tell me what's the problem and how to solve it? Thanks. Yours, Wilow -- View this message in context: http://www.nabble.com/How-do-the-arm926ejs-boot-from-nand-in-Uboot--t880880. html#a2282897 Sent from the Uboot - Users forum at Nabble.com. ------=_Part_938_11713481.1136822122949 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, My linux kernel has successfully run by U-booting from a norflash. 1)can the kernel based on arm 926ejs boot from nandflash? 2)which files I must modifiy in the U-boot packet if the kernel can boot from nandflash and where can I find more imforation about this. will you please tell me what's the problem and how to solve it? Thanks. Yours, Wilow <br><hr align="left" width="300"> View this message in context: <a href="http://www.nabble.com/How-do-the-arm926ejs-boot-from-nand-in-Uboot--t8 80880.html#a2282897">How do the arm926ejs boot from nand in Uboot?</a><br> Sent from the <a href="http://www.nabble.com/Uboot---Users-f553.html">Uboot - Users</a> forum at Nabble.com. ------=_Part_938_11713481.1136822122949-- --__--__-- Message: 8 Date: Mon, 09 Jan 2006 10:32:27 -0800 From: Khem Raj <khem(a)mvista.com> Organization: MontaVista Software To: Li Weichen <iaadoa(a)gmail.com> Cc: u-boot-users(a)lists.sourceforge.net, linux-arm-toolchain(a)lists.arm.linux.org.uk, linux-arm(a)lists.arm.linux.org.uk, linux-omap-open-source(a)linux.omap.com Subject: [U-Boot-Users] Re: Toolchain select Li Weichen said the following on 01/05/2006 05:38 AM: >Hi all, > >I encountered several toolchain problems while cross-compiling such as >u-boot, kernel. I find it mostly problem about the version. I don't >know which one is proper and stable for embedded system developing. > You may look at http://www.kegel.com/crosstool/crosstool-0.38/buildlogs/ which is a matrix of possible working tool combo's > > -- Khem Raj <khem(a)mvista.com> MontaVista Software, Inc. www.mvista.com --__--__-- Message: 9 From: Jon Loeliger <jdl(a)freescale.com> To: u-boot-users <u-boot-users(a)lists.sourceforge.net> Date: Mon, 09 Jan 2006 14:09:44 -0600 Subject: [U-Boot-Users] [PATCH] Allow top-level distclean target to descend to board Makefiles. Only applies to boards where it has been explicitly enabled. So far, that is 83xx and 85xx boards. Signed-off-by: Jon Loeliger <jdl(a)freescale.com> --- Soon, 85xx and 83xx boards will have generated files in their board directories that will need to be cleaned out. This patch provides the infrastructure to do so in one generic patch. Makefile | 20 +++++++++++++++++++- board/cds/mpc8541cds/Makefile | 3 +++ board/cds/mpc8548cds/Makefile | 3 +++ board/cds/mpc8555cds/Makefile | 3 +++ board/mpc8349ads/Makefile | 3 +++ board/mpc8540ads/Makefile | 4 +++- board/mpc8540eval/Makefile | 3 +++ board/mpc8560ads/Makefile | 4 +++- board/pm854/Makefile | 3 +++ board/pm856/Makefile | 3 +++ board/sbc8560/Makefile | 3 +++ board/stxgp3/Makefile | 3 +++ board/tqm834x/Makefile | 3 +++ board/tqm85xx/Makefile | 3 +++ 14 files changed, 58 insertions(+), 3 deletions(-) 996e2c2225222c1a016d14faf13b8bf2e325bae6 diff --git a/Makefile b/Makefile index 9305cab..e73d618 100644 --- a/Makefile +++ b/Makefile @@ -135,6 +135,14 @@ SUBDIRS = tools \ post/cpu .PHONY : $(SUBDIRS) +# Subdirectories that will be "clean" and "distclean". +# Not all board Makefiles have "clean" and "distclean" yet, +# so only add those that support it to this list. +ifneq ($(filter $(CPU),mpc85xx mpc83xx),) +CLEANDIRS = board/$(BOARDDIR) +endif + + ######################################################################### ######################################################################### @@ -1846,7 +1854,17 @@ clobber: clean rm -f include/asm/proc include/asm/arch include/asm mrproper \ -distclean: clobber unconfig +distclean: cleansubdirs clobber unconfig + + +.PHONY: cleansubdirs +cleansubdirs: +ifneq ($(strip $(CLEANDIRS)),) + @for dir in $(CLEANDIRS) ; do \ + $(MAKE) -C $$dir distclean; \ + done +endif + backup: F=`basename $(TOPDIR)` ; cd .. ; \ diff --git a/board/cds/mpc8541cds/Makefile b/board/cds/mpc8541cds/Makefile index 0d4abbd..1161532 100644 --- a/board/cds/mpc8541cds/Makefile +++ b/board/cds/mpc8541cds/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/cds/mpc8548cds/Makefile b/board/cds/mpc8548cds/Makefile index 0d4abbd..1161532 100644 --- a/board/cds/mpc8548cds/Makefile +++ b/board/cds/mpc8548cds/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/cds/mpc8555cds/Makefile b/board/cds/mpc8555cds/Makefile index 0d4abbd..1161532 100644 --- a/board/cds/mpc8555cds/Makefile +++ b/board/cds/mpc8555cds/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8349ads/Makefile b/board/mpc8349ads/Makefile index 4327b0d..4e89e21 100644 --- a/board/mpc8349ads/Makefile +++ b/board/mpc8349ads/Makefile @@ -32,6 +32,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(SOBJS) $(OBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -40,6 +41,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8540ads/Makefile b/board/mpc8540ads/Makefile index 5d8ea34..af4c293 100644 --- a/board/mpc8540ads/Makefile +++ b/board/mpc8540ads/Makefile @@ -27,7 +27,6 @@ LIB = lib$(BOARD).a OBJS := $(BOARD).o SOBJS := init.o -#SOBJS := $(LIB): $(OBJS) $(SOBJS) $(AR) crv $@ $(OBJS) @@ -35,6 +34,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +43,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8540eval/Makefile b/board/mpc8540eval/Makefile index 6f1995e..bb37c73 100644 --- a/board/mpc8540eval/Makefile +++ b/board/mpc8540eval/Makefile @@ -36,6 +36,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -44,6 +45,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8560ads/Makefile b/board/mpc8560ads/Makefile index 5d8ea34..eb45dcd 100644 --- a/board/mpc8560ads/Makefile +++ b/board/mpc8560ads/Makefile @@ -27,7 +27,6 @@ LIB = lib$(BOARD).a OBJS := $(BOARD).o SOBJS := init.o -#SOBJS := $(LIB): $(OBJS) $(SOBJS) $(AR) crv $@ $(OBJS) @@ -35,6 +34,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +43,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/pm854/Makefile b/board/pm854/Makefile index 7828166..43022ff 100644 --- a/board/pm854/Makefile +++ b/board/pm854/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/pm856/Makefile b/board/pm856/Makefile index 5d8ea34..3cccb58 100644 --- a/board/pm856/Makefile +++ b/board/pm856/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/sbc8560/Makefile b/board/sbc8560/Makefile index da295fb..20c4439 100644 --- a/board/sbc8560/Makefile +++ b/board/sbc8560/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/stxgp3/Makefile b/board/stxgp3/Makefile index d150df8..b7b562e 100644 --- a/board/stxgp3/Makefile +++ b/board/stxgp3/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/tqm834x/Makefile b/board/tqm834x/Makefile index 3ecc7d0..6b5b0c5 100644 --- a/board/tqm834x/Makefile +++ b/board/tqm834x/Makefile @@ -32,6 +32,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(SOBJS) $(OBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -40,6 +41,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/tqm85xx/Makefile b/board/tqm85xx/Makefile index 3933d46..446b102 100644 --- a/board/tqm85xx/Makefile +++ b/board/tqm85xx/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### -- 0.99.9n --__--__-- _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users End of U-Boot-Users Digest

2 1

[U-Boot-Users] About the u-boot (in ELF binary format)
by 腾飞龙 10 Jan '06

10 Jan '06

Hi, I have successfully compiled u-boot and ,as you know, there are several object files produced after"make all", one of which is u-boot(in ELF binary format) . Now, i run the u-boot(in ELF binary format) in target board (Embedded Planet EP405)with Linux kernel and NFS file system. # ./u-boot then appears the error echo: Segmentation fault will you please tell me what's the problem and how to solve it? Thank you and best wishes!!

3 4

[U-Boot-Users] [PATCH] Allow top-level distclean target to descend to board Makefiles.
by Jon Loeliger 09 Jan '06

09 Jan '06

Only applies to boards where it has been explicitly enabled. So far, that is 83xx and 85xx boards. Signed-off-by: Jon Loeliger <jdl(a)freescale.com> --- Soon, 85xx and 83xx boards will have generated files in their board directories that will need to be cleaned out. This patch provides the infrastructure to do so in one generic patch. Makefile | 20 +++++++++++++++++++- board/cds/mpc8541cds/Makefile | 3 +++ board/cds/mpc8548cds/Makefile | 3 +++ board/cds/mpc8555cds/Makefile | 3 +++ board/mpc8349ads/Makefile | 3 +++ board/mpc8540ads/Makefile | 4 +++- board/mpc8540eval/Makefile | 3 +++ board/mpc8560ads/Makefile | 4 +++- board/pm854/Makefile | 3 +++ board/pm856/Makefile | 3 +++ board/sbc8560/Makefile | 3 +++ board/stxgp3/Makefile | 3 +++ board/tqm834x/Makefile | 3 +++ board/tqm85xx/Makefile | 3 +++ 14 files changed, 58 insertions(+), 3 deletions(-) 996e2c2225222c1a016d14faf13b8bf2e325bae6 diff --git a/Makefile b/Makefile index 9305cab..e73d618 100644 --- a/Makefile +++ b/Makefile @@ -135,6 +135,14 @@ SUBDIRS = tools \ post/cpu .PHONY : $(SUBDIRS) +# Subdirectories that will be "clean" and "distclean". +# Not all board Makefiles have "clean" and "distclean" yet, +# so only add those that support it to this list. +ifneq ($(filter $(CPU),mpc85xx mpc83xx),) +CLEANDIRS = board/$(BOARDDIR) +endif + + ######################################################################### ######################################################################### @@ -1846,7 +1854,17 @@ clobber: clean rm -f include/asm/proc include/asm/arch include/asm mrproper \ -distclean: clobber unconfig +distclean: cleansubdirs clobber unconfig + + +.PHONY: cleansubdirs +cleansubdirs: +ifneq ($(strip $(CLEANDIRS)),) + @for dir in $(CLEANDIRS) ; do \ + $(MAKE) -C $$dir distclean; \ + done +endif + backup: F=`basename $(TOPDIR)` ; cd .. ; \ diff --git a/board/cds/mpc8541cds/Makefile b/board/cds/mpc8541cds/Makefile index 0d4abbd..1161532 100644 --- a/board/cds/mpc8541cds/Makefile +++ b/board/cds/mpc8541cds/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/cds/mpc8548cds/Makefile b/board/cds/mpc8548cds/Makefile index 0d4abbd..1161532 100644 --- a/board/cds/mpc8548cds/Makefile +++ b/board/cds/mpc8548cds/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/cds/mpc8555cds/Makefile b/board/cds/mpc8555cds/Makefile index 0d4abbd..1161532 100644 --- a/board/cds/mpc8555cds/Makefile +++ b/board/cds/mpc8555cds/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8349ads/Makefile b/board/mpc8349ads/Makefile index 4327b0d..4e89e21 100644 --- a/board/mpc8349ads/Makefile +++ b/board/mpc8349ads/Makefile @@ -32,6 +32,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(SOBJS) $(OBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -40,6 +41,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8540ads/Makefile b/board/mpc8540ads/Makefile index 5d8ea34..af4c293 100644 --- a/board/mpc8540ads/Makefile +++ b/board/mpc8540ads/Makefile @@ -27,7 +27,6 @@ LIB = lib$(BOARD).a OBJS := $(BOARD).o SOBJS := init.o -#SOBJS := $(LIB): $(OBJS) $(SOBJS) $(AR) crv $@ $(OBJS) @@ -35,6 +34,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +43,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8540eval/Makefile b/board/mpc8540eval/Makefile index 6f1995e..bb37c73 100644 --- a/board/mpc8540eval/Makefile +++ b/board/mpc8540eval/Makefile @@ -36,6 +36,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -44,6 +45,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/mpc8560ads/Makefile b/board/mpc8560ads/Makefile index 5d8ea34..eb45dcd 100644 --- a/board/mpc8560ads/Makefile +++ b/board/mpc8560ads/Makefile @@ -27,7 +27,6 @@ LIB = lib$(BOARD).a OBJS := $(BOARD).o SOBJS := init.o -#SOBJS := $(LIB): $(OBJS) $(SOBJS) $(AR) crv $@ $(OBJS) @@ -35,6 +34,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +43,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/pm854/Makefile b/board/pm854/Makefile index 7828166..43022ff 100644 --- a/board/pm854/Makefile +++ b/board/pm854/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/pm856/Makefile b/board/pm856/Makefile index 5d8ea34..3cccb58 100644 --- a/board/pm856/Makefile +++ b/board/pm856/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/sbc8560/Makefile b/board/sbc8560/Makefile index da295fb..20c4439 100644 --- a/board/sbc8560/Makefile +++ b/board/sbc8560/Makefile @@ -38,6 +38,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -46,6 +47,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/stxgp3/Makefile b/board/stxgp3/Makefile index d150df8..b7b562e 100644 --- a/board/stxgp3/Makefile +++ b/board/stxgp3/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/tqm834x/Makefile b/board/tqm834x/Makefile index 3ecc7d0..6b5b0c5 100644 --- a/board/tqm834x/Makefile +++ b/board/tqm834x/Makefile @@ -32,6 +32,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(SOBJS) $(OBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -40,6 +41,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### diff --git a/board/tqm85xx/Makefile b/board/tqm85xx/Makefile index 3933d46..446b102 100644 --- a/board/tqm85xx/Makefile +++ b/board/tqm85xx/Makefile @@ -35,6 +35,7 @@ $(LIB): $(OBJS) $(SOBJS) clean: rm -f $(OBJS) $(SOBJS) +.PHONY: distclean distclean: clean rm -f $(LIB) core *.bak .depend @@ -43,6 +44,8 @@ distclean: clean .depend: Makefile $(SOBJS:.o=.S) $(OBJS:.o=.c) $(CC) -M $(CPPFLAGS) $(SOBJS:.o=.S) $(OBJS:.o=.c) > $@ +ifeq ($(filter distclean,$(MAKECMDGOALS)),) -include .depend +endif ######################################################################### -- 0.99.9n

2 4

[U-Boot-Users] How do the arm926ejs boot from nand in Uboot?
by willow (sent by Nabble.com) 09 Jan '06

09 Jan '06

Hi, My linux kernel has successfully run by U-booting from a norflash. 1)can the kernel based on arm 926ejs boot from nandflash? 2)which files I must modifiy in the U-boot packet if the kernel can boot from nandflash and where can I find more imforation about this. will you please tell me what's the problem and how to solve it? Thanks. Yours, Wilow -- View this message in context: http://www.nabble.com/How-do-the-arm926ejs-boot-from-nand-in-Uboot--t880880… Sent from the Uboot - Users forum at Nabble.com.

2 1

[U-Boot-Users] Toolchain select
by Li Weichen 09 Jan '06

09 Jan '06

Hi all, I encountered several toolchain problems while cross-compiling such as u-boot, kernel. I find it mostly problem about the version. I don't know which one is proper and stable for embedded system developing. Could you please help me? I have already used the crosstool to make my own toolchain, and chose the gcc-4.0.1, binutils-2.16.1, glibc-2.3.5. But it seems that it has some problem. When I build u-boot it shows that the examples cannot be compiled. Regards, Li Weichen 2006-1-5

4 4

[U-Boot-Users] Linux stops at turn_on_mmu when jumping to start_here
by Jose França (Ext_GTBC) 09 Jan '06

09 Jan '06

Hello! I hope this subject isn't too much off-topic, but i'm stucked... I read the FAQ's and searched in the mailing-list history for an answer, but still i can't make it work and so i'm asking for your help. The situation is this... I am develloping the bootloader and kernel for a board based on mpc8247: - u-boot is almost fully configured and running well - bd_t on u-boot and on linux have the same definitions - the platform header file that i created is based on rpx8260.h and i'm using m8260_setup to fill ppc_md - CPM_MAP_ADDR and CFG_IMMR have the same value I don't have yet a debugger at hand, but from what i've discovered it stops in rfi instruction, when turning on MMU. Any suggestions would be most welcomed... Many thanks for reading and many more if you respond :)! Filipe.

2 1

[U-Boot-Users] Make for AmigaOneG3SE fails
by Felipe Gil Castiñeira 08 Jan '06

08 Jan '06

Hi, I am studying the feasibility of using the "x86 BIOS emulator" (in /board/MAI/bios_emulator) to initialize an ATI graphics card. As a first step, I am trying to compile U-Boot for AmigaOneG3SE (which uses the bios_emulator), but there are lots of warnings and errors. I am correcting the code, but the errors are endless. At least some of them seem related to the toolchain or to changes in the U-Boot includes. For example (an error compiling unmodified code): In file included from ../bios_emulator/scitech/include/x86emu.h:50, from ../bios_emulator/x86interface.c:1: ../bios_emulator/scitech/include/x86emu/types.h:42:23: sys/types.h: No such file or directory Has anyone here compiled U-Boot for AmigaOne? If the answer is affirmative, which toolchain (and version) did you use for the cross-compile? Thanks in advance. Best regards, Felipe. P.S.: I use the ELDK compiler configured for ppc_74xx- under linux x86.

2 2

[U-Boot-Users] Flash erasing problem
by Takács Áron 07 Jan '06

07 Jan '06

Hi, first of all I wish you all a happy new year! I am using a PXA270 based board with u-boot 1.1.2. I'm trying to write an ext2 filesystem image to flash (I want to mount it read only). First I erase the sectors, and I get no error messages. But when I try to copy the image into the flash, I get the error message: Copy to Flash... not erased at 00480000 (ffff0000). Could anyone please help me in solving this problem? Thanky you very much! Áron Takács I have the following outputs of u-boot: U-Boot 1.1.2 (Jun 7 2005 - 08:34:02) U-Boot code: A3F80000 -> A3F98C1C BSS: -> A3F9D354 RAM Configuration: Bank #0: a0000000 0 kB Bank #1: 00000000 0 kB Bank #2: 00000000 0 kB Bank #3: 00000000 0 kB Flash: 32 MB In: serial Out: serial Err: serial CPU speed: 520000kHz Hit any key to stop autoboot: 0 >flinfo: Bank # 1: INTEL 28F128J3A Size: 32 MB in 128 Sectors Sector Start Addresses: 00000000 (RO) 00040000 (RO) 00080000 000C0000 00100000 00140000 00180000 001C0000 00200000 00240000 00280000 002C0000 00300000 00340000 00380000 003C0000 00400000 00440000 00480000 004C0000 00500000 00540000 00580000 005C0000 00600000 00640000 00680000 006C0000 00700000 00740000 00780000 007C0000 00800000 00840000 00880000 008C0000 00900000 00940000 00980000 009C0000 00A00000 00A40000 00A80000 00AC0000 00B00000 00B40000 00B80000 00BC0000 00C00000 00C40000 00C80000 00CC0000 00D00000 00D40000 00D80000 00DC0000 00E00000 00E40000 00E80000 00EC0000 00F00000 00F40000 00F80000 00FC0000 01000000 01040000 01080000 010C0000 01100000 01140000 01180000 011C0000 01200000 01240000 01280000 012C0000 01300000 01340000 01380000 013C0000 01400000 01440000 01480000 014C0000 01500000 01540000 01580000 015C0000 01600000 01640000 01680000 016C0000 01700000 01740000 01780000 017C0000 01800000 01840000 01880000 018C0000 01900000 01940000 01980000 019C0000 01A00000 01A40000 01A80000 01AC0000 01B00000 01B40000 01B80000 01BC0000 01C00000 01C40000 01C80000 01CC0000 01D00000 01D40000 01D80000 01DC0000 01E00000 01E40000 01E80000 01EC0000 01F00000 01F40000 01F80000 01FC0000 >erase 00480000 01fbffff Erasing sector 18 ... done Erasing sector 19 ... done Erasing sector 20 ... done ... Erasing sector 125 ... done Erasing sector 126 ... done Erased 109 sectors >tftp a0000000 uImage24 dm9000 i/o: 0x08000000, id: 0x90000a46 MAC: 00:04:ff:ff:01:aa operating at 100M full duplex mode TFTP from server 192.168.1.11; our IP address is 192.168.1.20 Filename 'uImage24'. Load address: 0xa0000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ########################## done Bytes transferred = 2128628 (207af4 hex) >cp a0000000 00480000 207af4 Copy to Flash... not erased at 00480000 (ffff0000) Flash not Erased

4 10

[U-Boot-Users] need PPC asm. help. for 83xx watchdog
by David Updegraff 07 Jan '06

07 Jan '06

Hi. Attempting to enable&use watchdog in 8343; but run into Assembler (v.2.15) problem in cpu/mpc83xx/start.S:424 .... /* and reset it */ li r4, 0x556C sth r4, SWSRR@l(r3) li r4, 0xAA39 <-------- gas barks here, 0xAA39 > 0x8000 sth r4, SWSRR@l(r3) which I do not understand, since I thought 'li' was an UNsigned 16bit load. I can work around it in a kludgey way with. lis r4, 0 ori r4, r4, 0xAA39 sth r4, SWSRR@l(r3) but wonder if one you PowerPC assembler gurus could offer better suggestion. Thanx. -dbu.

3 2

[U-Boot-Users] subscribe
by Jeff Collins 06 Jan '06

06 Jan '06

jcollins(a)innovative-ss.com

1 0

[U-Boot-Users] U-boot reset problem
by batsayan.das＠tcs.com 06 Jan '06

06 Jan '06

Hello, We are able to build ROM u-boot for MPC8260 based customs board. We have observed a strange behavior of the board. When we power it up at the beginning of the day; it resets and resets. After a couple of power on/off we get the boot prompt. I am giving the log what we get after we power it up for the first time. Any help will be appreciated. *****LOG******************** U-Boot 1.1.2 (Jan 5 2006 - 15:01:10) MPC8260 Reset Status: External Soft, External Hard MPC8260 Clock Configuration - Bus-to-Core Mult 3x, VCO Div 2, 60x Bus Freq 33-100, Core Freq 100-300 - dfbrg 1, corecnf 0x08, busdf 3, cpmdf 1, plldf 0, pllmf 1 - vco_out 248000000, scc_clk 62000000, brg_clk 15500000 - cpu_clk 186000000, cpm_clk 124000000, bus_clk 62000000 CPU: MPC8260 (HiP4 Rev 14, Mask B.1 4K25A) at 186 MHz Board: Motorola MPC8260ADS DRAM: 256 MB Top of RAM usable for U-Boot at: 10000000 Reserving 221k for U-Boot at: 0ffc8000 Reserving 4352k for malloc() at: 0fb88000 Reserving 76 Bytes for Board Info at: 0fb87fb4 Reserving 72 Bytes for Global Data at: 0fb87f6c Stack Pointer at: 0fb87f48 New Stack Pointer is: 0fb87f48 Now running in RAM - U-Boot at: 0ffc8000 FLASH: Address at 0th 8 and 1st 8 b4 Address at 0th 8 and 1st 8 a4 Address at 0th 8 and 1st 8 a4 vals ### Unknown flash ID 00000008 00000008 at address FE000000 ### 0 th flash size = 524288 bytes1 th flash size = 524288 bytesflash_protect ON: from 0xFE000000 to 0xFE031FFF flash_protect ON: from 0xFE040000 to 0xFE07FFFF 1 MBTesting Flash Size Flash Start fe000000 Flash Size 100000 Flash Offset 2 32000 CPU INIT U-Boot 1.1.2 (Jan 5 2006 - 15:01:10) **************LOG********************* Thanks, Batsayan Das Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 1

[U-Boot-Users] Info required for Am29LV160B flash driver
by s.maiti＠tcs.com 06 Jan '06

06 Jan '06

Hi All, Any one of you have any experience in using CFI flash driver for Am29LV160B? I have the following questions: 1) What all informations have to be included in the header file for the mpc8260ads board, other than the following: #define CFG_MAX_FLASH_BANKS 1 /* number of banks */ #define CFG_MAX_FLASH_SECT 35 /* sectors per device */ #undef CFG_FLASH_CHECKSUM #define CFG_FLASH_ERASE_TOUT 1750000 /* Flash Erase Timeout (ms) */ #define CFG_FLASH_WRITE_TOUT 0 /* Flash Write Timeout (ms) */ #define CFG_FLASH_CFI_DRIVER #define CFG_FLASH_CFI #define CFG_FLASH_EMPTY_INFO 2) Are the informations i am providing are correct? Thanks in advance, Regards, Souvik Maiti Tata Consultancy Services Limited M2 & N2, Sector V, Block GP, Salt Lake Electronics Complex Kolkata - 700091,West Bengal India Cell:- 9831185648 Mailto: s.maiti(a)tcs.com Website: http://www.tcs.com Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

[U-Boot-Users] still error: Not enough room for program headers
by 腾飞龙 06 Jan '06

06 Jan '06

I'm porting u-boot to EP405 as i said in last letter, and i have made some changes in ../include/configs/ep405.h(changed from cpci4052.h ) mainly on Flash and also on other files to make them suitful(i think) with my board . Then follows compile,but atfter "make all" ,there is still an error as follow: ppc_4xx-ld: u-boot: Not enough room for program headers (allocated 2, need 3) ppc_4xx-ld: final link failed: Bad value Would you please tell me what's the problem on earth and how to solve it? Thank you in advace !

1 0

[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