July 2005 - U-Boot

[U-Boot-Users] David Ho is out of the office.
by David Ho 25 Jul '05

25 Jul '05

I will be out of the office starting 07/20/2005 and will not return until 07/25/2005. Please direct your questions to Hoang for Satcom project management, or the appropriate expert for Taurus.

2 1

RE: [U-Boot-Users] Silicon Image 0680A and CF-ATA drive
by Rune Torgersen 25 Jul '05

25 Jul '05

Didn't implement anything at all. I just used the generic IDE driver already present in U-Boot. All I had to change were those four #defines. > -----Original Message----- > From: Sam Pham [mailto:anhmn@yahoo.com] > Sent: Monday, July 25, 2005 12:47 > To: Rune Torgersen; u-boot-users(a)lists.sourceforge.net > Subject: RE: [U-Boot-Users] Silicon Image 0680A and CF-ATA drive > > > > --- Rune Torgersen <runet(a)innovsys.com> wrote: > > > I use a 0680A under u-boot, using the standard IDE > > driver. Works > > perfect. Only had to give the IDE driver the address > > of the register > > base. > > #define CFG_ATA_BASE_ADDR 0xa0000000 // > > BaseAddress 5 > > #define CFG_ATA_REG_OFFSET 0x80 > > #define CFG_ATA_DATA_OFFSET 0x80 > > #define CFG_ATA_ALT_OFFSET 0x80 > > > > It's good to know that somebody had implemented uboot > for the Sil 0680A controller. Do you have a patch for > this driver? I'd like compare it with my > implementation to see if I'm missing anything because > I can't test my implementation until the eval board > arrives. Also, did you implement POST for this > controller? I plan to do this as well. > > Thanks. > > Sam > > > > > -----Original Message----- > > > From: u-boot-users-admin(a)lists.sourceforge.net > > > [mailto:u-boot-users-admin@lists.sourceforge.net] > > On Behalf > > > Of Sam Pham > > > Sent: Tuesday, July 05, 2005 12:12 > > > To: u-boot-users(a)lists.sourceforge.net > > > Subject: Re: [U-Boot-Users] Silicon Image 0680A > > and CF-ATA drive > > > > > > > > > > > > --- Wolfgang Denk <wd(a)denx.de> wrote: > > > > > > > In message > > > > > > <20050705161452.30133.qmail(a)web54108.mail.yahoo.com> > > > > you wrote: > > > > > > > > > > My custom board has the PCI to ATA chip > > Silicon > > > > Image > > > > > 0680A, which connects to the CompactFlash > > Storage > > > > Card > > > > > that acts as a standard IDE disk if configured > > > > right. > > > > > Anyone knows if U-boot already had the > > > > implementation > > > > > for the Silicon Image 0680A and CF-ATA drive? > > I > > > > > > > > No. > > > > > > > > > looked through the source code but didn't find > > > > > anything. If not, any recommendations of how > > to > > > > > implement them? > > > > > > > > Find the Linux driver for this controller, > > analyze > > > > it, and port the > > > > unavoidable parts of it to U-Boot. > > > > > > Thanks. This would help for starting. > > > > > > Sam > > > > > > > > > > > > > > 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 > > > > To know how another being, another creature > > feels - > > > > that is impos- > > > > sible. - Terry Pratchett, _The > > Dark > > > > Side of the Sun_ > > > > > > > > > > > > > > > > > > > > > ____________________________________________________ > > > > > Yahoo! Sports > > > Rekindle the Rivalries. Sign up for Fantasy > > Football > > > http://football.fantasysports.yahoo.com > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net email is sponsored by: Discover Easy Linux > > Migration Strategies > > > from IBM. Find simple to follow Roadmaps, > > straightforward articles, > > > informative Webcasts and more! Get everything you > > need to get up to > > > speed, fast. > > > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > > _______________________________________________ > > > U-Boot-Users mailing list > > > U-Boot-Users(a)lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/u-boot-users > > > > > > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux > > Migration Strategies > > from IBM. Find simple to follow Roadmaps, > > straightforward articles, > > informative Webcasts and more! Get everything you > > need to get up to > > speed, fast. > > http://ads.osdn.com/?ad_idt77&alloc_id492&op=click > > _______________________________________________ > > U-Boot-Users mailing list > > U-Boot-Users(a)lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/u-boot-users > > > > > > > ____________________________________________________ > Start your day with Yahoo! - make it your home page > http://www.yahoo.com/r/hs > > >

2 1

RE: [U-Boot-Users] Silicon Image 0680A and CF-ATA drive
by Rune Torgersen 25 Jul '05

25 Jul '05

I use a 0680A under u-boot, using the standard IDE driver. Works perfect. Only had to give the IDE driver the address of the register base. #define CFG_ATA_BASE_ADDR 0xa0000000 // BaseAddress 5 #define CFG_ATA_REG_OFFSET 0x80 #define CFG_ATA_DATA_OFFSET 0x80 #define CFG_ATA_ALT_OFFSET 0x80 > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf > Of Sam Pham > Sent: Tuesday, July 05, 2005 12:12 > To: u-boot-users(a)lists.sourceforge.net > Subject: Re: [U-Boot-Users] Silicon Image 0680A and CF-ATA drive > > > > --- Wolfgang Denk <wd(a)denx.de> wrote: > > > In message > > <20050705161452.30133.qmail(a)web54108.mail.yahoo.com> > > you wrote: > > > > > > My custom board has the PCI to ATA chip Silicon > > Image > > > 0680A, which connects to the CompactFlash Storage > > Card > > > that acts as a standard IDE disk if configured > > right. > > > Anyone knows if U-boot already had the > > implementation > > > for the Silicon Image 0680A and CF-ATA drive? I > > > > No. > > > > > looked through the source code but didn't find > > > anything. If not, any recommendations of how to > > > implement them? > > > > Find the Linux driver for this controller, analyze > > it, and port the > > unavoidable parts of it to U-Boot. > > Thanks. This would help for starting. > > Sam > > > > > > 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 > > To know how another being, another creature feels - > > that is impos- > > sible. - Terry Pratchett, _The Dark > > Side of the Sun_ > > > > > > > ____________________________________________________ > Yahoo! Sports > Rekindle the Rivalries. Sign up for Fantasy Football > http://football.fantasysports.yahoo.com > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users > >

2 1

[U-Boot-Users] Problem with bootm command
by Mirco Fuchs 25 Jul '05

25 Jul '05

I have a problem getting started a 2.6.12 kernel with initrd on my csb637 board using u-boot 1.1.3 as bootloader. I allready searched the mailing list archive but i did not find a solution for this problem. I placed an initrd- u-boot image to 0x10160000 and an u-boot kernel image to 0x10040000. My kernel parameters are as follows: mem=64M console=ttyS0,115200 initrd=0x21200000,0x001b06b6 root=/dev/ram rw The kernel is compiled with initrd support. When using the u-boot 'bootm 0x10040000 0x10160000' command, the kernel is decompressed and starts but is not able to mount the initrd as it's root file system. If I change the kernel command line to mem=64M console=ttyS0,115200 initrd=0x21200040,0x001b06b6 root=/dev/ram rw, the kernel boots correctly with initrd as it's root fs. The images were created with the mkimage tool delivered with u-boot. For creating the initrd image i used the following command: mkimage -n 'rootfs' -A arm -O linux -T ramdisk -C gzip -a 0x21200000 -e 0x21200000 initrd.bin initrd.img I think the problem occures because of the added file-header to the initrd binary file. I compared the original binary file with the u-boot initrd image and found out, that a header with the size of 0x40 bytes is appended at the beginning of the original binary file. Maybe i only have to change the Entry Point to 0x21200040, but normally i do not know the size of the appended header information. I thought that when using the bootm command u-boot copies the initrd image to it's designated sdram location without the header information (-- but obviously it does not), am i wrong? Maybe there's another mistake. Best Regards Mirco _________________________________________________________________________ Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179

2 1

[U-Boot-Users] configuring initrd problem.
by Yoon Kah Leow 25 Jul '05

25 Jul '05

Hi, I have been trying to configure my eval board to boot up using the ramdisk through an initrd. I have included the initrd and ramdisk support in the kernel configuration. Under-attached is my .config file for your reference. . . . . # # RAM/ROM/Flash chip drivers # CONFIG_MTD_CFI=y # CONFIG_MTD_JEDECPROBE is not set CONFIG_MTD_GEN_PROBE=y # CONFIG_MTD_CFI_ADV_OPTIONS is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_CFI_I4 is not set # CONFIG_MTD_CFI_I8 is not set # CONFIG_MTD_CFI_INTELEXT is not set CONFIG_MTD_CFI_AMDSTD=y CONFIG_MTD_CFI_AMDSTD_RETRY=0 # CONFIG_MTD_CFI_STAA is not set CONFIG_MTD_CFI_UTIL=y # CONFIG_MTD_RAM is not set # CONFIG_MTD_ROM is not set # CONFIG_MTD_ABSENT is not set . . . # # NAND Flash Device Drivers # # CONFIG_MTD_NAND is not set # # Plug and Play support # # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set CONFIG_BLK_DEV_NBD=y # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_CDROM_PKTCDVD is not set . . . . . . # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT3_FS is not set # CONFIG_JBD is not set # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # # XFS support # # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set CONFIG_ROMFS_FS=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y # # CD-ROM/DVD Filesystems # # CONFIG_ISO9660_FS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y # CONFIG_MSDOS_FS is not set CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y # CONFIG_DEVFS_MOUNT is not set # CONFIG_DEVFS_DEBUG is not set # CONFIG_DEVPTS_FS_XATTR is not set # CONFIG_TMPFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_JFFS_FS is not set CONFIG_JFFS2_FS=y CONFIG_JFFS2_FS_DEBUG=0 # CONFIG_JFFS2_FS_NAND is not set # CONFIG_JFFS2_FS_NOR_ECC is not set # CONFIG_JFFS2_COMPRESSION_OPTIONS is not set CONFIG_JFFS2_ZLIB=y CONFIG_JFFS2_RTIME=y # CONFIG_JFFS2_RUBIN is not set CONFIG_CRAMFS=y # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V4 is not set # CONFIG_NFS_DIRECTIO is not set # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_SUNRPC=y # CONFIG_RPCSEC_GSS_KRB5 is not set # CONFIG_RPCSEC_GSS_SPKM3 is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set . . . . . . However, during bootup it seems that the kernel is unable to locate the correct magic number for the ext2fs format initrd and refuses to bootup. The printk statements which I included shows that the kernel seems to extract the magic number from the wrong location in the function, identify_ramdisk_image of do_mounts_rd.c which is suppose to be 'ef53' for the case of an ext2fs image. The bootargs which i used are : bootargs=console=ttyS1 root=/dev/ram0 The under-attached are the messages from the console upon bootup. U-Boot# bootm 10000 300000 ## Booting image at 00010000 ... Image Name: Linux-2.6.11-Cooper Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1189964 Bytes = 1.1 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK ## Loading Ramdisk Image at 00300000 ... Image Name: Ext2fs Ramdisk Image Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 415164 Bytes = 405.4 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Transferring control to Linux (at address 00008000) ... Starting kernel ... Uncompressing Linux.............................................................................. done, bootin g the kernel. Linux version 2.6.11-Cooper (root@debianworld) (gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)) #8 Mon Jul 25 15:31:15 SGT 2005 CPU: ARM926EJ-Sid(wb) [41069264] revision 4 (ARMv5TEJ) CPU0: D VIVT write-back cache CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets CPU0: D cache: 4096 bytes, associativity 4, 32 byte lines, 32 sets Machine: NS9360 Memory policy: ECC disabled, Data cache writeback NS9360 Rev. 0, running at 176 MHz Built 1 zonelists Kernel command line: console=ttyS1 root=/dev/ram0 PID hash table entries: 128 (order: 7, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 16MB = 16MB total Memory: 13240KB available (2001K code, 415K data, 100K init) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Freeing initrd memory: 405K NET: Registered protocol family 16 SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub i2c_ns: I2C ns9750 driver $Revision: 1.1 $ initializing NetWinder Floating Point Emulator V0.97 (double precision) devfs: 2004-01-31 Richard Gooch (rgooch(a)atnf.csiro.au) devfs: boot_options: 0x0 JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc. ns9360fb: Using LCD display STN LCD Console: switching to colour frame buffer device 40x30 fb0: ns9360fb frame buffer device NS9750 Watchdog initialized Serial: NS9750 driver $Revision: 1.2 $ ttyS1 at MMIO 0xf9200040 (irq = 36) is a NS9750 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) nbd: registered device at major 43 Setting GPIOs for NS9360 ethernet Ethernet: NS9750 driver $Revision: 1.1 $ ns9360_map Using NOR Flash device: 4096 kB @ 0x50000000 NOR Flash memory mapped to virtual c1880000 AM29LV160DB: Found 2 x16 devices at 0x0 in 32-bit bank Amd/Fujitsu Extended Query Table at 0x0040 number of CFI chips: 1 cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. ns9360_map: using static partition definition Creating 3 MTD partitions on "AM29LV160DB": 0x00000000-0x00040000 : "U-boot" 0x00040000-0x00180000 : "kernel" 0x00180000-0x00400000 : "initrd" ns9360-ohci ns9360-ohci0: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usb 1-1: new full speed USB device using ns9360-ohci and address 2 hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver mice: PS/2 mouse device common for all mice i2c /dev entries driver NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: ext2sb->s_magic=e79b RAMDISK: ext2sb->s_inodes_count=e121f003 RAMDISK: ext2sb->s_blocks_count=e5903014 RAMDISK: ext2sb->s_r_blocks_count=e2433001 RAMDISK: ext2sb->s_free_blocks_count=e5803014 RAMDISK: cpu_to_le16(EXT2_SUPER_MAGIC)=ef53 RAMDISK: start_block=0 RAMDISK: Couldn't find valid RAM disk image starting at 0. Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Is there anything which I have missed out or done wrong? Regards

2 1

[U-Boot-Users] where to download the latest version of u-boot after 1.12 by http?
by zhuzhenhua 25 Jul '05

25 Jul '05

i can not download it by cvs,so is there a tarball to download?

3 3

[U-Boot-Users] u-boot crash on the first command 'help'
by Shawn Jin 25 Jul '05

25 Jul '05

Hi, I'm porting U-Boot to a ppc440 core based SoC. The system now doesn't have flash. So CFG_NO_FLASH and CFG_ENV_IS_NOWHERE are defined. After stucked in DDR mem initialization for a while (logic designers need to fix their bugs), I finally make U-Boot run on the system and the prompt is shown on the console. But the first command I typed causes u-boot to crash. The strange thing is that there is nothing in the call backtrace. Any hints to the cause? The chip is running on an emulator and the only modules u-boot brings up is UART and DDR. It may not be stable. So h/w still is more suspicious than u-boot itself. I wanna make sure this illeagal instruction exception isnot caused by u-boot. U-Boot 1.1.3 (Jul 22 2005 - 17:02:13) DRAM: 32 MB Top of RAM usable for U-Boot at: 02000000 Reserving 89k for U-Boot at: 01fe9000 Reserving 132k for malloc() at: 01fc8000 Reserving 112 Bytes for Board Info at: 01fc7f90 Reserving 48 Bytes for Global Data at: 01fc7f60 Stack Pointer at: 01fc7f48 New Stack Pointer is: 01fc7f48 Now running in RAM - U-Boot at: 01fe9000 Using default environment In: serial Out: serial Err: serial U-Boot relocated to 01fe9000 => ? ? - al NIP: 00000000 XER: 20000000 LR: 00000000 REGS: ffffff28 TRAP: 0700 DAR: FFFFFFFF MSR: 00029000 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00 GPR00: 00000000 00000018 BFFF8310 40120481 0000006C 00000001 00000001 01FCA055 GPR08: 00000010 1FCA0558 00000040 00000001 00000030 00000000 02004D00 02069000 GPR16: 00000000 00000000 00000000 00000000 00009000 01FC7C28 00000001 00000020 GPR24: 00000001 01FC7BA0 01FC7BA0 00000001 01FFCAF0 01FC7F60 0000000A 00000000 ** Illegal Instruction ** Call backtrace: 00000000 Program Check Exception Thanks a lot, -Shawn.

1 0

[U-Boot-Users] Rash Guard
by winnie 24 Jul '05

24 Jul '05

The products name : Rash Guard The price : USD5.00/pc (with shipping cost) The qty : 200pcs The size : S, M, L and XL http://hk.page.auctions.yahoo.com/hk/auction/1109185372?aucview=user Thanks, winnie

1 0

[U-Boot-Users] Interrupt initialization for ppc440
by Shawn Jin 23 Jul '05

23 Jul '05

Hi, IIRC, Interrupt usually doesn't have to be enabled on U-Boot. When looking into ppc440 code cpu/ppc4xx/interrupts.c, I noticed that uic0/1/2 are actually enabled for ppc440 targets. Is there any 440 chips using interrupts on U-Boot? Thanks, -Shawn.

2 2

[U-Boot-Users] Stuck relocating command table
by Gregg Nemas 22 Jul '05

22 Jul '05

I have been trying unsuccessfully to bring up u-boot on my PowerPC 440GP evaluation board. I am using the predefined configuration file for this board (EBONY.h). I have tried both the 1.1.2 release and the head CVS files, both with the same result. It displays the expected initial messages and then hangs after displaying the DRAM amount. I traced the code to find out where it is hanging. It makes it to board_init_r in board.c, and enters the loop in which u-boot is relocating the command table. It never gets out of this loop. One peculiar thing is that when I printed out the value of __u_boot_cmd_start and __u_boot_cmd_end just before the loop, they did not match what the u-boot.map file says they should be. The printed versions were __u_boot_cmd_start = 0x07faeed8 __u_boot_cmd_end = 0x07ff57f4 (difference 0x4691C) The u-boot.map versions are __u_boot_cmd_start = 0xfffa57f4 __u_boot_cmd_end = 0xfffa8ffc (difference 0x3808) The loop seems to be reading from the wrong flash locations because it is reading garbage. Can someone help me figure this out? Could it be the build tools? I am using gcc 3.3.6 and binutils 2.16.1. Are these okay for building u-boot? Thanks. Gregg

2 2