September 2004 - U-Boot

[U-Boot-Users] [PATCH] common framebuffer for PXA and MPC8xx
by himba 10 Oct '04

10 Oct '04

Hi, I reworked my previous proposal for common framebuffer interface on PXA and MPC8xx (other platforms should find it usefull too). There are some differences in contrast to patch I posted on 08.08.2004. They are: o got rid of two extra header files (pxafb.h and mpc823fb.h) introduced earlier o all common stuff is in include/lcd.h and common/lcd.c o CPU dependent stuff remains in cpu/mpc8xx/lcd.c and cpu/pxa/pxafb.c See my previous post for more details. I tested that patch does not break pxa and 8xx boards with ./MAKEALL [pxa|8xx]. CHANGELOG: Patch by Hinko Kocevar, 21 Aug 2004: Group common framebuffer functions in common/lcd.c Group common framebuffer macros and #defines in include/lcd.h Provide calc_fbsize() for video ATAG regards, himba

2 1

[U-Boot-Users] [Patch]A fix in cfi_flash.c
by Sam Song 10 Oct '04

10 Oct '04

Hi, The following patch makes the sector number next to (RO) in order as usual after protect on operation.Really a samll fix... * Patch by Sam Song, 21 August 2004: - Make (RO) next number display in order after protect on Best regards, Sam ==================================================== diff -purN u-boot-2004-08-18-2000-orig/drivers/cfi_flash.c u-boot-2004-08-18-2000/drivers/cfi_flash.c --- u-boot-2004-08-18-2000-orig/drivers/cfi_flash.c Sat Aug 21 17:10:21 2004 +++ u-boot-2004-08-18-2000/drivers/cfi_flash.c Sat Aug 21 17:17:02 2004 @@ -462,7 +462,7 @@ void flash_print_info (flash_info_t * in if ((i % 5) == 0) printf ("\n "); printf (" %08lX%s", - info->start[i], info->protect[i] ? " (RO)" : " "); + info->start[i], info->protect[i] ? " (RO) " : " "); #endif } putc ('\n'); _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有，搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆，雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_…

2 1

[U-Boot-Users] [Patch]A typo in README
by Sam Song 10 Oct '04

10 Oct '04

Hi, I need to send several small patches although there is sth wrong with u-boot CVS server.All against u-boot-2004-08-18-2000. * Patch by Sam Song, 21 August 2004: - Fix a typo in README Best regards, Sam ============================================= diff -purN u-boot-2004-08-18-2000-orig/README u-boot-2004-08-18-2000/README --- u-boot-2004-08-18-2000-orig/README Sat Aug 21 17:10:21 2004 +++ u-boot-2004-08-18-2000/README Sat Aug 21 17:14:59 2004 @@ -784,7 +784,7 @@ The following options need to be configu supported (PIP405, MIP405, MPC5200); define CONFIG_USB_UHCI to enable it. define CONFIG_USB_KEYBOARD to enable the USB Keyboard - end define CONFIG_USB_STORAGE to enable the USB + and define CONFIG_USB_STORAGE to enable the USB storage devices. Note: Supported are USB Keyboards and USB Floppy drives _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有，搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆，雅虎电邮自助扩容！ http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_…

2 1

[U-Boot-Users] [PATCH] lubbock board
by himba 10 Oct '04

10 Oct '04

Hi, Running ./MAKEALL pxa fails with lubbock board because no LCD panel is configured. It is using SHARP LM8V31 according to specs. I'm supplying fix. Maintainer is CC'ed, just in case. CHANGELOG: Patch by Hinko Kocevar, 21 Aug 2004: Define type of LCD panel if CONFIG_LCD is used regards, himba --- u-boot/include/configs/lubbock.h 2004-01-21 00:12:34.000000000 +0100 +++ lcd-u-boot/include/configs/lubbock.h 2004-08-21 11:37:50.000000000 +0200 @@ -43,6 +43,9 @@ #define CONFIG_PXA250 1 /* This is an PXA250 CPU */ #define CONFIG_LUBBOCK 1 /* on an LUBBOCK Board */ #define CONFIG_LCD 1 +#ifdef CONFIG_LCD +#define CONFIG_SHARP_LM8V31 +#endif #define CONFIG_MMC 1 #define BOARD_LATE_INIT 1

2 1

[U-Boot-Users] [PATCH] cradle board
by himba 10 Oct '04

10 Oct '04

Hi, Running ./MAKEALL pxa produces this warning with cradle board. warning: deprecated use of label at end of compound statement I'm supplying fix. Maintainer is CC'ed, just in case. CHANGELOG: Patch by Hinko Kocevar, 21 Aug 2004: Fix compiler warning about label usage regards, himba --- u-boot/board/cradle/flash.c 2003-09-18 11:21:33.000000000 +0200 +++ lcd-u-boot/board/cradle/flash.c 2004-08-21 10:26:02.000000000 +0200 @@ -133,7 +133,7 @@ info++; } -Done: +Done:; } /*-----------------------------------------------------------------------

2 1

[U-Boot-Users] Proposed change; What do you think?
by Jon Loeliger 10 Oct '04

10 Oct '04

Guys, I'd like to get your opinion on a proposed change to a few files that handle some aspects of the various enetaddr fields as found in asm-ppc/u-boot.h, common/cmd_bdinfo.c and lib_ppc/board.c. In particular, I'd like to propose a shift from having these fields be present when certain boards are #defined to having these fields be present when CONFIG_ETH1ADDR symbols are defined. So, don't take the following as a literal patch. It is just some cut-n-paste diffs to show what I mean. There are only a few boards for which this might make a difference. I'm the bit swizzler for most of them (MPC85xxXDS), but the others include the PN62, the PPCCHAMEONEVB, the 440GX, the GT_6426x. SXNI855T, SVM_SC8xx and possibly the DB64360, DB64460, CATcenter, and OCOTEA boards. The latter define CONFIG_ETH1ADDR but don't have their cases include in places like the coomon/cmd_bdinfo.c. I think this sorr of change would make the handling of the ETH1ADDR, ETH2ADDR and ETH3ADDR more consistent across any platform that defines these fields. Opinions? If you buy this, I'll submit a proper patch, of course. Thanks, jdl --- include/asm-ppc/u-boot.h 2004/04/13 21:42:46 1.1.1.2.2.1 +++ include/asm-ppc/u-boot.h 2004/08/06 10:51:41 @@ -77,25 +77,15 @@ #if defined(CONFIG_HYMOD) hymod_conf_t bi_hymod_conf; /* hymod configuration information */ #endif -#if defined(CFG_GT_6426x) || \ - defined(CONFIG_PN62) || \ - defined(CONFIG_PPCHAMELEONEVB) || \ - defined(CONFIG_SXNI855T) || \ - defined(CONFIG_SVM_SC8xx) || \ - defined(CONFIG_MPC8540ADS) || \ - defined(CONFIG_MPC8555CDS) || \ - defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_440_GX) +#ifdef CONFIG_ETH1ADDR /* second onboard ethernet port */ unsigned char bi_enet1addr[6]; #endif -#if defined(CFG_GT_6426x) || defined(CONFIG_SVM_SC8xx) || \ - defined(CONFIG_MPC8540ADS) || defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_MPC8555CDS) || defined(CONFIG_440_GX) +#ifdef CONFIG_ETH2ADDR /* third onboard ethernet port */ unsigned char bi_enet2addr[6]; #endif -#if defined(CONFIG_440_GX) +#ifdef CONFIG_ETH3ADDR unsigned char bi_enet3addr[6]; #endif #if defined(CONFIG_405GP) || defined(CONFIG_405EP) || defined (CONFIG_440_GX) and also: diff -u -r1.1.1.2.2.2 cmd_bdinfo.c --- common/cmd_bdinfo.c 2004/06/17 20:37:25 1.1.1.2.2.2 +++ common/cmd_bdinfo.c 2004/08/06 10:51:40 @@ -83,16 +83,13 @@ for (i=0; i<6; ++i) { printf ("%c%02X", i ? ':' : ' ', bd->bi_enetaddr[i]); } -#if (defined CONFIG_PN62) || (defined CONFIG_PPCHAMELEONEVB) \ - || (defined CONFIG_MPC8540ADS) || (defined CONFIG_MPC8560ADS) \ - || (defined CONFIG_MPC8555CDS) +#ifdef CONFIG_ETH1ADDR puts ("\neth1addr ="); for (i=0; i<6; ++i) { printf ("%c%02X", i ? ':' : ' ', bd->bi_enet1addr[i]); } -#endif /* CONFIG_PN62 */ -#if defined(CONFIG_MPC8540ADS) || defined(CONFIG_MPC8560ADS) \ - || defined(CONFIG_MPC8555CDS) +#endif /* CONFIG_ETH1ADDR */ +#ifdef CONFIG_ETH2ADDR puts ("\neth2addr ="); for (i=0; i<6; ++i) { printf ("%c%02X", i ? ':' : ' ', bd->bi_enet2addr[i]) And one other place over in: diff -u -r1.1.1.2.2.4 board.c --- lib_ppc/board.c 2004/06/17 20:37:41 1.1.1.2.2.4 +++ lib_ppc/board.c 2004/08/06 10:51:41 @@ -772,11 +774,7 @@ load_sernum_ethaddr (); #endif -#if defined(CFG_GT_6426x) || defined(CONFIG_PN62) || defined(CONFIG_PPCHAMELEONEVB) || \ - defined(CONFIG_MPC8540ADS) || \ - defined(CONFIG_MPC8555CDS) || \ - defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_440_GX) +#ifdef CONFIG_ETH1ADDR /* handle the 2nd ethernet address */ s = getenv ("eth1addr"); @@ -787,11 +785,7 @@ s = (*e) ? e + 1 : e; } #endif -#if defined(CFG_GT_6426x) || \ - defined(CONFIG_MPC8540ADS) || \ - defined(CONFIG_MPC8555CDS) || \ - defined(CONFIG_MPC8560ADS) || \ - defined(CONFIG_440_GX) +#ifdef CONFIG_ETH2ADDR /* handle the 3rd ethernet address */ s = getenv ("eth2addr"); @@ -807,7 +801,7 @@ } #endif -#if defined(CONFIG_440_GX) +#ifdef CONFIG_ETH3ADDR /* handle 4th ethernet address */ s = getenv("eth3addr"); #if defined(CONFIG_XPEDITE1K)

3 5

[U-Boot-Users] [patch] trivial parameter type fix for NetSetTimeout
by Andreas Engel 09 Oct '04

09 Oct '04

Attached is a trivial patch not worth mentioning in the ChangeLog. As NetSetTimeout just stores the timeout value in an ulong variable, the value itself should be ulong too. Regards, Andreas

2 1

[U-Boot-Users] [PATCH] - fixed missing System ACE CF device
by Sean Chang 01 Oct '04

01 Oct '04

Hi, If there are any problems please let me know and I'll be more than happy to fix it. This patch is applied against the u-boot 1.1.1 release. The CHANGELOG is below. Regards, Sean ======================================================================= CHANGELOG (ace_fat.patch): Patch by Sean Chang, 9 Aug 2004: Fixed missing System ACE CF device during get FAT partition info in fat_register_device function. =======================================================================

3 8

RE: [U-Boot-Users] PCI cards known to work on the LITE5200
by Jonas Mark-r50740 01 Oct '04

01 Oct '04

Hello, > I am currently using a LITE5200. There is a known (annoying) > PCI issue with the MPC5200, and therdfore most of the PCI > cards I have tried on the LITE5200 were not recognized. For > several of them, u-boot even crashed (bus error). I was > wondering if somedy has tried with success common PCI > graphics cards and gigabit ethernet cards... Please note that this problem needs two partners to be seen. On the one hand, MPC5200 violates Tvalmin by having this about 1ns instead of at least 2 ns according to spec. On the other hand, a PCI card needs to be able to handle a Tvalmin of down to 0 ns when somebody reads from it. So if both sides behave badly the card is not recognized during Type-0 configuration. > I have tried a suggested workaround, using an ICS574 to > adjust the MPC5200 PCI clock signal from the PCI bus, but > still no luck with the PCI cards I have tried (although it > should work with the PCI SM712 eval board). How did you adjust the clock using the clock buffer mentioned above? Overdoing it will also cause harm especially during writes. My suggestion is to measure the real Tvalmin and then adjust it that it just reaches 2 ns. Regards Mark Jonas

2 1

[U-Boot-Users] Support for ZBT SRAM in MPC8560ADS?
by Fillod Stephane 01 Oct '04

01 Oct '04

Hi, Is there any plan for support of the ZBT SRAM found in MPC8560ADS ? Does someone at Freescale can share the CS and clock setup? TIA -- Stephane

2 1

[U-Boot-Users] when load another u-boot.bin, failed cp.b from memory to flash
by Tyler Jia 01 Oct '04

01 Oct '04

Hello, I try to update the new u-boot.bin (128k) with an u-boot already run in a ppc405ep board (8mb flash, 32mb ram), using serial port, Using original u-boot to install another u-boot.bin, for example: flash memory from ff800000 to ffffffff, u-boot.bin in fffe0000 to ffffffff, . loadb 0x1000000 . kermit send u-boot.bin Then we can see u-boot.bin (128k) shows in 0x1000000 - 0x1020000, if copy from memory to flash, After protect off 0xfffe0000 sector And erase 0xfffe0000 sector Cp.b 0x1000000 0xfffe0000 0x20000 but no u-boot.bin shows in 0xfffe0000 - 0xfffffff, all byts from fff80000 to ffffffff become 008000880 . if copy from memory to memory cp.b 0x1000000 0x1050000 0x20000 In 0x1050000 - 0x106ffff u-boot.bin shows right. So cp.b copy from memory to memory workes , but cp.b copy from memory to flash does not work! the cp.b seems just could copy memory to memory, but how to enable it copy from memory to flash? Thanks a lot! Best regards Tyler _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com

2 1

RE: [U-Boot-Users] SDRAM Access Question
by VanBaren, Gerald (AGRE) 30 Sep '04

30 Sep '04

> -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of Jihua > Cheng > Sent: Thursday, September 30, 2004 11:24 AM > To: u-boot-users(a)lists.sourceforge.net > Subject: [U-Boot-Users] SDRAM Access Question > > > Hi, > > My question about SDRAM may be out of track, forgive me. > > I am working on the bring-up of a customer board based on > PQ2FADS. I use BDI2000. When I use "mm addr value count" cmd > to write any data( such as, 0x12345678) to any address > between address 0x0 to 0x7fc, then I use "md" cmd to show the > contents of address 0x0 to 0x7fc, I found all the contents > between 0x0 and 0x7fc (2KB range)are the same value ( > 0x12345678), the contents above address 0x800 are not > changed. If I write a data to any address between address > 0x800 to 0xc00, the whole block from 0x800 to 0xffc (2KB > range)are changed, and address 0x0 to address 0x7fc. The My > BDI2000 configuration file works fine to my PQ2FADS > evaluation board, and the SDRAM component and design of my > customer board are copied from PQ2FADS. > > I am atruggling for the problem for a quite while. I do not > know what can cause the 2K range problem? Any point or clue > are appreciated. > > Thanks! > > Jihua Wolfgang Knows. Then to add to his response... SDRAM has multiplexed address lines with half of the address lines being presented as a "row" and then the other half as a "column". SDRAM configuration requires you to configure the SDRAM machine where the row ends and column starts. If you are wrong, the addressing gets all balled up and you are likely writing and reading into/from an unintended address. That would be the good news. The bad news is that, if it isn't a software configuration problem, it is a hardware problem and that would be really bad news indeed (can you spell board spin $$$). My bet is the SDRAMs you use are different from the SDRAMs used on the PQ2FADS and you didn't reconfigure your SDRAM initialization. Time to read the SDRAM and 82xx manuals. You have my sympathy, it takes some time and serious concentration to figure out SDRAM configuration :-/. gvb ****************************************** The following messages are brought to you by the Lawyers' League of IdioSpeak: ****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************

1 0

RE: [U-Boot-Users] RE: help: images in example directory are inva lid
by Scott McNutt 30 Sep '04

30 Sep '04

> => loads > ....fine I load the hello_world.srec Good. > go 40004 blah blah blah > ## Starting application at 0x00040004 Good. > HANG Bad. You should see something like (PQ2FADS board): ==> loads ## Ready for S-Record download ... ## First Load Addr = 0x00040000 ## Last Load Addr = 0x00050323 ## Total Size = 0x00010324 = 66340 Bytes ## Start Addr = 0x00040004 => go 40004 this is a test ## Starting application at 0x00040004 ... Example expects ABI version 2 Actual U-Boot ABI version 2 Hello World argc = 5 argv[0] = "40004" argv[1] = "this" argv[2] = "is" argv[3] = "a" argv[4] = "test" argv[5] = "<NULL>" Hit any key to exit ... ## Application terminated, rc = 0x0 => > hmm....The hang very much bugs me, and I have no > idea why it happens Set a breakpoint and debug. This should not happen. Check your addresses -- make sure they're valid. I'm assuming you have RAM at 40000, and u-boot is running high enough above it (i.e. your stack stack, heap, etc, are not being corrupted). > and lo and behold: > > => imi 0x00040004 > Bad Magic Number imi is for u-boot image files (see mkimage). > What have I read incorrectly, please? >From 'loads' to 'go' you are executing the correct commands. Check your addresses with objdump. --Scott

1 0

[U-Boot-Users] SDRAM Access Question
by Jihua Cheng 30 Sep '04

30 Sep '04

Hi, My question about SDRAM may be out of track, forgive me. I am working on the bring-up of a customer board based on PQ2FADS. I use BDI2000. When I use "mm addr value count" cmd to write any data( such as, 0x12345678) to any address between address 0x0 to 0x7fc, then I use "md" cmd to show the contents of address 0x0 to 0x7fc, I found all the contents between 0x0 and 0x7fc (2KB range)are the same value ( 0x12345678), the contents above address 0x800 are not changed. If I write a data to any address between address 0x800 to 0xc00, the whole block from 0x800 to 0xffc (2KB range)are changed, and address 0x0 to address 0x7fc. The My BDI2000 configuration file works fine to my PQ2FADS evaluation board, and the SDRAM component and design of my customer board are copied from PQ2FADS. I am atruggling for the problem for a quite while. I do not know what can cause the 2K range problem? Any point or clue are appreciated. Thanks! Jihua

2 1

[U-Boot-Users] RE: help: images in example directory are invalid
by Scott McNutt 30 Sep '04

30 Sep '04

> Using powerpc-linux-objdump -fs hello_world.srec, I see: > > hello_world.srec: file format srec > architecture: UNKNOWN!, flags 0x00000000: > > start address 0x00040004 You're getting warmer ... try README. It's all there. The images are valid. --Scott

3 2

[U-Boot-Users] help: images in example directory are invalid
by Benjamin Collar 30 Sep '04

30 Sep '04

Hi Nicholas, I've written to the u-boot this about this question, but thought I would write to you as well. u-boot is supposed to build valid stand-alone applications, and I do indeed get .srec stuff in the examples directory. (We did get past the loads problem, btw). However, these srecs are not valid images. (We also confirmed that what we're writing into ram and flash are actually being written -- the data dump shows the same data as we see with objdump). After I loads the hello_world app, I check it with iminfo and get: "bad magic number". Using mkimage -l hello_world.srec, I get 'Bad Magic Number: "hello_world.srec" is no valid image' I get the same result for hello_world (the elf format). Using powerpc-linux-objdump -fs hello_world.srec, I see: hello_world.srec: file format srec architecture: UNKNOWN!, flags 0x00000000: start address 0x00040004 Contents of section .sec1: 40000 000182b0 9421ffd8 7c0802a6 429f0005 .....!..|...B... 40010 bf610014 7fc802a6 9001002c 801efff0 .a.........,.... 40020 7c7c1b78 7fc0f214 7c832378 7c9b2378 ||.x....|.#x|.#x Indeed, the first numbers there are not the magic number from image.h: 0x27051956. We tried to load a kernel, just for kicks (just because we're hopeful folk), but of course got the same result. Do you have any idea how I'm doing this wrong? Why is u-boot creating invalid stand-alone images? Thanks Ben -- Benjamin Collar Siemens AG CT SE 2 Embedded Linux 089-636-53711

2 1

[U-Boot-Users] help: images in example directory are invalid
by Benjamin Collar 30 Sep '04

30 Sep '04

Greetings folks As I've mentioned, u-boot is running on the board now. However, I've so far failed to get a stand-alone application to run. For instance, when I load hello_world.srec, then check it with iminfo, I get "bad magic number". Using mkimage -l hello_world.srec, I get 'Bad Magic Number: "hello_world.srec" is no valid image' I get the same result for hello_world (the elf format). Using powerpc-linux-objdump -fs hello_world.srec, I see: hello_world.srec: file format srec architecture: UNKNOWN!, flags 0x00000000: start address 0x00040004 Contents of section .sec1: 40000 000182b0 9421ffd8 7c0802a6 429f0005 .....!..|...B... 40010 bf610014 7fc802a6 9001002c 801efff0 .a.........,.... 40020 7c7c1b78 7fc0f214 7c832378 7c9b2378 ||.x....|.#x|.#x Can anyone explain why u-boot is building invalid images? Thanks Ben -- Benjamin Collar Siemens AG CT SE 2 Embedded Linux 089-636-53711

2 1

[U-Boot-Users] Mips board support...
by Arun SR 30 Sep '04

30 Sep '04

Hi, I am trying to understand the mips support code in the uboot source code. In the cpu/mips directory, there are references to incaip in the file name as well as source. Isn't cpu directory supposed to be independent of the board? If I wanted to add support to a new mips board how should I modify the cpu/mips directory? Regards, Arun.

2 1

[U-Boot-Users] crap!
by Benjamin Collar 30 Sep '04

30 Sep '04

sorry folks, I sent that message to the wrong target. Ben -- Benjamin Collar Siemens AG CT SE 2 Embedded Linux 089-636-53711

1 0

[U-Boot-Users] (no subject)
by Richard Dong 30 Sep '04

30 Sep '04

u-boot-users(a)lists.sourceforge.net

1 0

[U-Boot-Users] porting ht1070 board help
by Charles Agaton 30 Sep '04

30 Sep '04

i got this error: -------- make[1]: Entering directory `/home/charles/hermit/u-boot-1.1.1/common' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/charles/hermit/u-boot-1.1.1/common' UNDEF_SYM=`arm-linux-objdump -x lib_generic/libgeneric.a board/ht1070/libht1070.a cpu/arm720t/libarm720t.a lib_arm/libarm.a fs/cramfs/libcramfs.a fs/fat/libfat.a fs/fdos/libfdos.a fs/jffs2/libjffs2.a fs/reiserfs/libreiserfs.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_.*$/ 1/p'|sort|uniq`;\ arm-linux-ld -Bstatic -T /home/charles/hermit/u-boot-1.1.1/board/ht1070/u-boot.lds -Ttext $UNDEF_SYM cpu/arm720t/start.o \ --start-group lib_generic/libgeneric.a board/ht1070/libht1070.a cpu/arm720t/libarm720t.a lib_arm/libarm.a fs/cramfs/libcramfs.a fs/fat/libfat.a fs/fdos/libfdos.a fs/jffs2/libjffs2.a fs/reiserfs/libreiserfs.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 --no-warn-mismatch -L /home/charles/test/buildroot/build_arm/staging_dir/lib/gcc-lib/arm-linux-uclibc/2.95.4 -lgcc --end-group \ -Map u-boot.map -o u-boot arm-linux-ld: cannot find entry.o make: *** [u-boot] Error 1 ------ i have no idea why this happened. can anyone help? __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail

1 0

[U-Boot-Users] [PATCH] - enabled System ACE CF support on ML300
by Sean Chang 30 Sep '04

30 Sep '04

Hi, If there are any problems please let me know and I'll be more than happy to fix it. This patch is applied after the previous eeprom.patch. Regards, Sean ======================================================================= CHANGELOG (ace_ml300.patch): Patch by Sean Chang, 9 Aug 2004: Enabled System ACE CF support on ML300. =======================================================================

2 1

[U-Boot-Users] [PATCH] - Added 8 and 16 bit mode access for System ACE CF
by Sean Chang 30 Sep '04

30 Sep '04

Hi, If there is any problems please let me know and I'll be more than happy to fix it. This patch is applied against the u-boot 1.1.1 release. The CHANGELOG is below. Regards, Sean ======================================================================= CHANGELOG (ace_cmd.patch): Patch by Sean Chang, 9 Aug 2004: Added support for both 8 and 16 bit mode access to System ACE CF through MPU. =======================================================================

3 2

[U-Boot-Users] [PATCH] - "saveenv" and "do_saveenv" compile synch
by Sean Chang 30 Sep '04

30 Sep '04

Hi, If there is any problems please let me know and I'll be more than happy to fix it. This patch is applied against the u-boot 1.1.1 release. The CHANGELOG is below. Regards, Sean ======================================================================= CHANGELOG (nvedit.patch): Patch by Sean Chang, 9 Aug 2004: Synch defines for saveenv and do_saveenv functions so they get compiled under the same statement. =======================================================================

2 1

[U-Boot-Users] [PATCH] - I2C and EEPROM support for ML300
by Sean Chang 30 Sep '04

30 Sep '04

Hi, If there are any problems please let me know and I'll be more than happy to fix it. This patch is applied against the u-boot 1.1.1 release. The CHANGELOG is below: Regards, Sean ======================================================================= CHANGELOG (eeprom.patch): Patch by Sean Chang, 9 Aug 2004: Added I2C support for ML300. Added support for ML300 to read out its environment information stored on the EEPROM. Added support to use board specific parameters as part of U-Boot's environment information. Updated MLD files to support configuration for new features above. =======================================================================

2 2