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

RE: [U-Boot-Users] configuring
by Peter Pearse 22 Jul '05

22 Jul '05

Dupas.External(a)infineon.com wrote: > -setenv bootargs "setenv bootargs root=/dev/mtdblock0 > mtdparts=armflash.0:0x65d000@0x2200000(cramfs) ip=none mem=128 > console=ttyAMA0 video=vc:1-2clcdfb:" > > my cramfs is in flash at address 0x341c0000 while the basis of my > flash memory is 0x34000000. mtdparts is size in bytes @offset from flash base so for 0x341c0000 it will be mtdparts=armflash.0:<some byte size>@0x1c0000(cramfs) The ARM boot monitor will show you the size: ARM Versatile/PB926EJ-S Boot Monitor Version: V2.0.1 Build Date: Nov 30 2004 Endian: Little > flash Flash> list images Flash Area Base 0x34000000 Address Name ------- ---- 0x34000000 u-boot 0x34040000 eabi26arm Flash> display image u-boot Name: u-boot Flash Address: 0x34000000 Load Address : 0x00000000 Entry Point : 0x00000000 Size : 79396 Bytes Blocks Used : 1 Flash> display image eabi26arm Name: eabi26arm Flash Address: 0x34040000 Load Address : 0x00000000 Entry Point : 0x00000000 Size : 2418640 Bytes Blocks Used : 10 Flash> Peter

1 0

[U-Boot-Users] configuring
by Dupas.External＠infineon.com 22 Jul '05

22 Jul '05

trying to boot linux2.6.12 with u-boot-1.1.3 on a ARM versatile board I am facing a difficulty . the kernel fails at init because i think of my ability to indicate the place where it can find the root file system. what is to be put in the bootargs? the error message is : Root-NFS : no NFS server available. please append a correct "root=" boot option Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(2,0) I have tried many commands all leading to the same error. -setenv bootargs "root=/dev/mtdblock0 mem=128M ether=27,0,0xfc800000,0xfc800010,eth0 mtdparts=versatile:0x5c0000@0x1c0000(cram fs) video=vc:1-2clcdfb:" -setenv bootargs "setenv bootargs root=/dev/mtdblock0 mtdparts=armflash.0:0x65d000@0x2200000(cramfs) ip=none mem=128 console=ttyAMA0 video=vc:1-2clcdfb:" my cramfs is in flash at address 0x341c0000 while the basis of my flash memory is 0x34000000. Anyone ? greetings thomas

3 2

[U-Boot-Users] u-boot.bin size below 50K
by Houda 21 Jul '05

21 Jul '05

Hi, I would like to know if it is at all possible to reduce the size of the u-boot to 50K or less? I've tried removing all the non-standard commands without going anywhere close to 50k! Is there a way to reduce it to very basic form? thanks, Hoda

4 4

[U-Boot-Users] Splash screen support for DbAu1100
by Martin Nichols 21 Jul '05

21 Jul '05

Hi All, Does anyone have a splash screen working on the AMD DbAu1100 board? What's involved in implementing this feature on new hardware? Regards, Martin. --------------------------------- How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo! Photos

2 3

[U-Boot-Users] Problem about "printf"!
by junping feng 21 Jul '05

21 Jul '05

I have tried it! But all the commands can't work. From the code,information printed in the serial interface should be as below: "...... DRAM: 16 MB FLASH: 16 MB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial => " But it displays only as below: "...... DRAM: 16 MB FLASH: 16 MB *** Warning - bad CRC, using default environment => " The information"In: serial Out: serial Err: serial" can't be printed. Why? > In message > <20050720143726.9858.qmail(a)web15704.mail.cnb.yahoo.com> > you wrote: > > My uboot can run now! Through serial,prompt"=>"can > be > > printed,but after input"help",it don't display > > commands of uboot. > > Does it work ith any command at all? For example, > does the board > reset when you ype "reset" ? > > > It seems as if uboot can't find the standard input > and > > output devices. > > What makes you think so? > > > > It display below: > > > > ...... > > DRAM: 16 MB > > FLASH: 16 MB > > *** Warning - bad CRC, using default environment > > => > > > > > > I find that function "printf" (in the > > /common/console.c) can't execute. WHY? Please > give me > > What makes you think so? > > > As below: > > > > #ifndef CFG_CONSOLE_INFO_QUIET > > /* Print informations */ > > printf ("In: "); > > if (stdio_devices[stdin] == NULL) { > > printf ("No input devices available!\n"); > > } else { > > printf ("%s\n", stdio_devices[stdin]->name); > > } > > > > printf ("Out: "); > > if (stdio_devices[stdout] == NULL) { > > printf ("No output devices available!\n"); > > } else { > > printf ("%s\n", stdio_devices[stdout]->name); > > } > > > > printf ("Err: "); > > if (stdio_devices[stderr] == NULL) { > > printf ("No error devices available!\n"); > > } else { > > printf ("%s\n", stdio_devices[stderr]->name); > > } > > #endif /* CFG_CONSOLE_INFO_QUIET */ > > I don't see any of the "No ??? devices available!" > error messages in > your display, so I don't understand why you think > this should be a > problem? > > > Which board is this on? And which version of U-Boot? > > 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 > Madness has no purpose. Or reason. But it may have > a goal. > -- Spock, "The Alternative Factor", stardate 3088.7 > __________________________________________________ 赶快注册雅虎超大容量免费邮箱? http://cn.mail.yahoo.com

1 0

[U-Boot-Users] Problem about "printf"!
by junping feng 20 Jul '05

20 Jul '05

My uboot can run now! Through serial,prompt"=>"can be printed,but after input"help",it don't display commands of uboot. It seems as if uboot can't find the standard input and output devices. It display below: ...... DRAM: 16 MB FLASH: 16 MB *** Warning - bad CRC, using default environment => I find that function "printf" (in the /common/console.c) can't execute. WHY? Please give me a hand! Thanks! As below: #ifndef CFG_CONSOLE_INFO_QUIET /* Print informations */ printf ("In: "); if (stdio_devices[stdin] == NULL) { printf ("No input devices available!\n"); } else { printf ("%s\n", stdio_devices[stdin]->name); } printf ("Out: "); if (stdio_devices[stdout] == NULL) { printf ("No output devices available!\n"); } else { printf ("%s\n", stdio_devices[stdout]->name); } printf ("Err: "); if (stdio_devices[stderr] == NULL) { printf ("No error devices available!\n"); } else { printf ("%s\n", stdio_devices[stderr]->name); } #endif /* CFG_CONSOLE_INFO_QUIET */ ___________________________________________________________ 雅虎免费G邮箱－中国第一绝无垃圾邮件骚扰超大邮箱 http://cn.mail.yahoo.com/?id=77071

2 1

Re: [U-Boot-Users] bug in at91rm9200 interrupt.c [udelay()] ?
by Mirco Fuchs 20 Jul '05

20 Jul '05

Thank you for your fast reply, i didn't check the list archive on csb637 because i downloaded u-boot version 1.1.2 and thought that it was the newest version available - this thought was obvioulsy wrong ... But i did check the list now and i couldn't find any patch. The only entry i found was that there was a patch added (on 3.rd May) , but i couldn't find the patch itself. I also browsed the CVS Repository, but it seems that there is no folder csb637 in the /board directory. So what do i have to do to download the patch??? (Sorry if this question sounds stupid, but i'm new to this mailing list) best regards Mirco ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

3 2

[U-Boot-Users] lcd support for S1L50282F23K100 display for omap2420h4 board
by Elmaleh Aaron-CAE001 20 Jul '05

20 Jul '05

Hi, I'm looking if someone have a u-boot lcd support for the omap2420h4 lcd part #: S1L50282F23K100 . i could see that some boards have lcd support within u-boot , but unfortunatly none from TI... Regards, Aaron

1 0

[U-Boot-Users] Pb compiling u-boot
by Dupas.External＠infineon.com 20 Jul '05

20 Jul '05

I'm trying to port linux on an arm versatile board, currently I'm trying to create a loadable image of a recent u-boot. I've downloaded the latest release of u-boot on the site (I use the latest gcc provided by arm) and launched the compilation but an error occurred: I join the exact logs in attached file. <<log_u-boot_failure.doc>> It seems like the makefile is not valid (The start.o is not compiled...) Here is a final extract: DCONFIG_ARM -D__ARM__ -march=armv4t -I.. -Bstatic -T /home/dupas/linux/sources_u-boot/u-boot-1.1.2/board/versatile/u-boot.lds -Ttext 0x01000000 hello_world.c -o hello_world /home/dupas/linux/tool-chain/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.3 /../../../../arm-none-linux-gnueabi/bin/ld: cannot find cpu/arm926ejs/start.o collect2: ld returned 1 exit status make[1]: *** [hello_world] Erreur 1 make[1]: Leaving directory `/home/dupas/linux/sources_u-boot/u-boot-1.1.2/examples' make: *** [examples] Erreur 2 dupas@vlblnxs2:~/linux/sources_u-boot/u-boot-1.1.2$ Can anyone help me please? Greetings thomas

3 2

[U-Boot-Users] bug in at91rm9200 interrupt.c [udelay()] ?
by Mirco Fuchs 20 Jul '05

20 Jul '05

hello, i'm porting u-boot to the csb637 board from cogent. I think i found a bug in the udelay (); function in file interrupt.c (at91rm9200). Assume the following C code: ... start = get_timer(0); /* some code */ udelay(1500) // delay of about 1500us next = get_timer(start); ... what we expect is that the value of next holds the difference between next and start in milliseconds. This works fine without the udelay() function between the get_timer() function calls. But in udelay() the global variable timestamp is reset to zero and so there is no longer any relationship between next and start. The effect will be that any time measurements will fail. I allready looked in some other interrupt.c files, but the udelay() function is handled in a similar way. Maybe i'm wrong with my assumption, but i don't think so. I'm very interested in your answers. 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] (no subject)
by prabhu 20 Jul '05

20 Jul '05

1 0

[U-Boot-Users] CF 5282 fec.c
by Zachary Landau 20 Jul '05

20 Jul '05

> I'm new on U-Boot and work on a MCF5282 port. I have modify the cvs > source and U-Boot runs on my own MCF5282 board (I get a promt on serial > line). But i get "Tx not ready" and "Tx Timeout" messages for each > ethernet access. > I discover the fec.c, and find out that only 10MBit haft duplex is use. > Is there in implementation for full 100MBit use? Jens, Search the mailing list archives. There are multiple posts about 5282 ports, and some specifically about the fec. -- Zachary P. Landau <kapheine(a)gmail.com>

2 1

[U-Boot-Users] starting an initrd
by Greg Lindberg 20 Jul '05

20 Jul '05

I realize that this may be off-topic here, but I'm hoping that someone has some insight that will help me to figure out what the problem is. I'm running u-boot on a PXA255 based board, I've loaded u-boot in ram at 0xa1500000, the Linux kernel at 0xa0100000, compiled for 0xc0010000 (phy ram addresses get mapped from 0xa0000000 to 0xc0000000), and the ramdisk at 0xa1600000 to moved to 0xa1800000. I haven't tried to set up an environment yet, the board I'm working on is a temporary development board and that portion is going to change on the final board. The bootm command defaults to: bootm 0xa0100000 0xa1600000 Also, here is the command line that I'm passing to the Linux kernel: console=ttyS0,38400 initrd=0xa1800000,4096k root=/dev/ram init=/bin/sh Here is the output from running u-boot: U-Boot 1.1.3 (Jul 19 2005 - 10:37:00) U-Boot code: A1500000 -> A1513E40 BSS: -> A1515894 RAM Configuration: Bank #0: a0000000 32 MB Bank #1: a4000000 0 kB Bank #2: a8000000 0 kB Bank #3: ac000000 0 kB Flash: 32 MB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 ## Booting image at a0100000 ... Image Name: ARM-Linux-2.6 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 662900 Bytes = 647.4 kB Load Address: a0010000 Entry Point: a0010000 Verifying Checksum ... OK Uncompressing GZip'd Kernel Image ... OK ## Loading Ramdisk Image at a1600000 ... Image Name: ARM-Linux-2.6.initrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 1000261 Bytes = 976.8 kB Load Address: a1800000 Entry Point: a1800000 Verifying Checksum ... OK Starting kernel ... Linux version 2.6.12-RC4-InHand2 (greg@rh9dev) (gcc version 3.3.4) #62 Tue Jul 19 10:42:15 PDT 2005 CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE) CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Machine: InHand Electronics Fingertip3 initrd (0xa1800000 - 0xa1c00000) extends beyond physical memory - disabling initrd Memory policy: ECC disabled, Data cache writeback Memory clock: 99.53MHz (*27) Run Mode clock: 199.07MHz (*2) Turbo Mode clock: 199.07MHz (*1.0, inactive) Built 1 zonelists Kernel command line: console=ttyS0,38400 initrd=0xa1800000,4096k root=/dev/ram init=/bin/sh 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: 14720KB available (1110K code, 277K data, 68K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok Linux NoNET1.0 for Linux 2.6 JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. JFFS2: default compression mode: priority ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 4 RAM disks of 4096K size 1024 blocksize physmap flash device: 2000000 at 0 phys_mapped_flash: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x0031 Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled RedBoot partition parsing not available mtd: Giving out device 0 to phys_mapped_flash mice: PS/2 mouse device common for all mice i2c /dev entries driver Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Any help anyone can give me to point out to me what is happening and/or what I'm doing wrong would be greatly appreciated. Greg Wilson-Lindberg

2 2

[U-Boot-Users] Kernel Panic
by Will Haines 19 Jul '05

19 Jul '05

I am currently trying to boot an kernel with inital ramdisk using u-boot on an EP885C, but I am running into the following problem when I try to boot the kernel: Linux version 2.4.22 (wdhaine@prod-pci) (gcc version 3.3.3) #1 Mon Jul 18 12:45:35 EDT 2005 On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: console=ttyS0,9600 console=ttyS0 root=/dev/ram0 init=/linuxrc rw ... RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 8 devices) ... RAMDISK: Compressed image found at block 0 Freeing initrd memory: 466k freed Kernel panic: VFS: Unable to mount root fs on 01:00 I would think that this is purely a kernel problem; however, it did not crop up until I started using u-boot. As shown above, I have ramdisk support built into the kernel, and I am passing it a root device in the kernel command line, so this doesn't seem to be an FAQ type of problem. In order to get the kernel to run, I had to copy the ppcboot.h bd_t struct into my linux port and change the IMAP_ADDR to get the kernel to boot. I am thinking that somehow the bd_t struct changes could make the it impossible to use /dev/ram0 correctly. Other than that, I am stumped. Any help would be greatly apprectiated. Will Haines

4 9

Re: [U-Boot-Users] 2.6.12 with u-boot-1.1.2 on versatile
by Peter Pearse 19 Jul '05

19 Jul '05

Wolfgang Denk wrote: > In message <20050719073213.49786.qmail(a)web30712.mail.mud.yahoo.com> > you wrote: >> >> Thanks to Wolfgang Denk, Catalin Marinas, and Peter Pearse, I now >> have >> 2.6.12-rmk1 running with base.cramfs on the PB-ARM926EJ-S. The >> following documentation is for reference: > ... >> 4. Copy the uImage from flash to SDRAM: >> >> cp 0xbbccddee 0x7fc0 0x123456 > ... >> 6. Bootup >> >> bootm 0x7fc0 > > The "cp" step (4.) is redundant. Instead, just type "bootm > 0xbbccddee". > Not on Versatile, where we have not yet implemented CONFIG_HAS_DATAFLASH correctly. At present one must copy the kernel image into the load address before using bootm. I have this on my list of patches to make.... Peter

1 0

[U-Boot-Users] SDRAM initialization sequence!
by junping feng 19 Jul '05

19 Jul '05

Hi,I have a little problem with the uboot startup,the BDI2000 can program u-boot.bin into FLASH .My board is like the board MPC8260ADS.CPU is ppc8250. Board information can print through serial interface after the first initialization of board now. But when it run to the function relocate_code(in the /cpu/mpc8260/start.s),it don't run continually. Through LED on the board ,I find that it stops at the code below: in_ram: My SDRAM is samsang k4s643232f-tc60, total 16MBytes,two chips.Each is organzied as 4*512K*32bits. The link address is the SDRAM data sheet! http://www.samsung.com/Products/Semiconductor/DRAM/SDRAM/SDRAMcomponent/64M… Please check whether my SDRAM initialization sequence is correct! Thanks in advance! /* init sdram dimm */ printf("Now init 60x sdram dimm ...\n"); ramaddr = (uchar *)CFG_SDRAM_BASE; memctl->memc_mptpr = 0x1900; memctl->memc_psrt = 0x10; immap->im_memctl.memc_or2 = 0xFF003080; immap->im_memctl.memc_br2 = 0x00000041; memctl->memc_psdmr = 0x2869a452; *ramaddr = c; memctl->memc_psdmr = 0x0869a452; for (i = 0; i < 8; i++) *ramaddr = c; memctl->memc_psdmr = 0x1869a452; *ramaddr = c; memctl->memc_psdmr = 0x4069a452; *ramaddr = c; __________________________________________________ 赶快注册雅虎超大容量免费邮箱? http://cn.mail.yahoo.com

2 1

[U-Boot-Users] Mac Address communication to Linux
by Stage Iup - Fabrice & Frederic 19 Jul '05

19 Jul '05

Hi all i'm wondering something, i don't understand how can U-Boot communicate to an Embedded Linux. Can someone explain it to me please? -- With regards Frédéric Kwiatkowski -- IFOTEC Tél : 04 76 67 53 53

2 3

RE: [U-Boot-Users] 2.6.12 with u-boot-1.1.2 on versatile
by Shakthi Kannan 19 Jul '05

19 Jul '05

Hi, Thanks for your replies Peter Pearse and Catalin Marinas. 1. --- Peter Pearse <Peter.Pearse(a)arm.com> wrote: > I use > > <U-Boot dir>/tools/mkimage -A arm -O linux -T kernel > -C none -a 0x7fc0 > -e 0x8000 -n u-linux -d <Kernel dir>/arch/arm/Image > u-linux Worked like a charm! I then had to copy the kernel to SDRAM 0x7fc0 and boot it using: cp 0x36000000 0x7fc0 <kernel_size> bootm 0x7fc0 2. I then tried to use the base.cramfs filesystem provided in arm.com: http://www.arm.com/linux/linux_download.html I used mkimage to append a header and flashed it at 0x36200000. Copied the same to SDRAM, 0x04000000. I changed the bootargs values using setenv, but, was not sure as to what values I need to give. setenv bootargs root=/dev/mtdblock0 mtdparts=versatile:0x65d050@0x04000000(cramfs) ip=none mem=128M console=ttyAMA0 video=vc:1-2clcdfb: I then tried to boot the kernel with the ramdisk: bootm 0x7fc0 0x04000000 I got the following output: http://www.shakthimaan.com/downloads/session.log Why is it trying the floppy? Is it trying the external memory card? I did check the boot log to the 2.4.19-rmk6 kernel provided in the NOR flash, and it loaded ramdisk drivers etc. I have used the config-versatile-pb file as provided in arm.com site, which does not have support for ramdisk by default. I did try enabling ramdisk support, but, I ended up with the same output as above. The ramdisk by default is 4 MB in the kernel, but base.cramfs given in arm.com is 6 MB. I even tried changing the ramdisk size in kernel CONFIG to 8 MB, but, no change in the output. I'd appreciate any feedback for the above, and any help in getting the filesystem mounted, so I can start playing with the shell. Board: Versatile-PB-ARM926EJ-S Cross_compiler: 3.4.3 Kernel: 2.6.12 Thanks again for your help, K Shakthi -- proudly anti-micro$oft ------------------------------------------------------------ Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shaks(a)shakthimaan.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India ------------------------------------------------------------ ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

2 3

[U-Boot-Users] Undelivered Mail Returned to Sender
by MAILER-DAEMON＠glw.com 19 Jul '05

19 Jul '05

This is the Postfix program at host mail.glw.com. I'm sorry to have to inform you that the message returned below could not be delivered to one or more destinations. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the message returned below. The Postfix program <".aarons"@glw.com>: host public/lmtp[public/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown

1 0

[U-Boot-Users] flash erase problem for Intel TE28F640J3C
by me 19 Jul '05

19 Jul '05

Hi, I have a ATMEL AT91RM9200 board with u-boot 1.1.2 and Intel TE28F640J3C flash. I can burn u-boot image to flash when the board is booted from internal ROM. But I can't erase sector 1 of the flash when it is booted from external flash. Strangely, other sectors can be erased sucessfully expect the sector 1 which u-boot image will be located. I am sure that I unportect the sector 1 and I still get an erase timeout. BTW, I use CFI driver for Intel flash. Someone, can give me some light ?? Eric 憟單祥蝬脰楝餉店隞颱

1 0

[U-Boot-Users] Boot Delay 0 !!!
by Bharathi Subramanian 18 Jul '05

18 Jul '05

Hello All, Recently one of our unit's flash is got corrupted. Bcoz of that, one module is not started. So watch dog is rebooting the unit with-in 2 Sec after booting up. We thought of booting that unit in NFS and mount the JFFS Data partition for recovering the data file, address book, from that flash. Fortunately the boot delay is Zero. So we coun't do anything. Is there any trick to get the prompt ?? Bye :) -- Bharathi S

3 2

[U-Boot-Users] [id]cache_status looks at wrong bit for MPC8560
by Murray.Jensen＠csiro.au 18 Jul '05

18 Jul '05

Hi, the [id]cache_status functions in the MPC85xx start.S code look at the wrong bit in the L1CSRn registers for the MPC8560. I have a patch for it, but I was wondering if the code is wrong for all 85xx processors, or just the 8560. Rather than me downloading all the 85xx user manuals and checking the register bits (as I am only interested in 8560) I thought I would post here instead. If anyone knows for certain the code is correct or otherwise for other 85xx processors, please let me know. Cheers! Murray... -- Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763 Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853 Internet: Murray.Jensen(a)csiro.au To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference. The information contained in this e-mail may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this e-mail in error, please delete it immediately and notify Murray Jensen on +61 3 9662 7763. Thank you.

2 3

[U-Boot-Users] Configuration of u-boot for DM270 board
by Vipul Dashora 18 Jul '05

18 Jul '05

Hi All i m configuring u-boot bootloader for dm270. for this i have to initialize all memory settings for this i have done following settings in header file /*----------------------------------------------------------------------- * Physical Memory Map */ #define CONFIG_NR_DRAM_BANKS 1 /* we have 1 bank of DRAM */ #define PHYS_SDRAM_1 0x00900000 /* SDRAM Bank #1 */ #define PHYS_SDRAM_1_SIZE 0x01800000 /* 24 MB */ #define PHYS_FLASH_1 0x00100000 /* Flash Bank #1 */ #define PHYS_FLASH_SIZE 0x00800000 /* 8 MB */ #define CFG_FLASH_BASE PHYS_FLASH_1 /*----------------------------------------------------------------------- * FLASH and environment organization */ #define CFG_MAX_FLASH_BANKS 1 /* max number of memory banks */ #define CFG_MAX_FLASH_SECT 71 /* max number of sectors on one chip */ /* timeout values are in ticks */ #define CFG_FLASH_ERASE_TOUT (2*CFG_HZ) /* Timeout for Flash Erase */ #define CFG_FLASH_WRITE_TOUT (2*CFG_HZ) /* Timeout for Flash Write */ #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_ADDR (PHYS_FLASH_1 + 0x1C000)/* Addr of Environment Sector */ #define CFG_ENV_SIZE 0x4000 /* Total Size of Environment Sector */ what r the various registers of dm270 that i have to initialize to configure flash and SDRAM in memsetup.S any help will be highly appreciated Thanks and Regards Vipul Dashora

1 0

[U-Boot-Users] Re: how can I boot u-boot from 0x40000 in flash instead
by Ray Zhao 15 Jul '05

15 Jul '05

Thanks for the answers. I apologize that I did not make it clear. My board is a PXA270, it will, of cause, boot from 0x0000. But our customer has a tiny tiny boot loader which just generates some special data and save it in flash. (So they reserved the flash blocks from the 0x0000 to 0x40000.) Then it make PXA270 jump to the 0x40000 and run the real boot loader from there. We used blob and it works fine with kernel 2.4. But I am porting the new Linux 2.6 to the board and I decide to switch to u-boot. My understanding is that after the u-boot get the control, ie, the CPU jump to the first instruct of the u-boot code. u-boot will do some initialization on the CPU's cache to build a simple C environment and then copy part of itself from the flash into the cache and run from there to initial the memory controller etc. The code then will copy all (or the rest) the u-boot from the flash to the memory. My question is, in default, u-boot will copy itself from the 0x0000 (right?). How could I let it know that the u-boot is actually locates in the 0x40000. thanks, Ray > Ray Zhao wrote: > My board need keep the first 0x40000 flash for special purpose. Is it > easy to modify the u-boot to load itself from 0x40000 instead from the > 0x0000? Any help is appreciated. > > Ray > If your hardware supports it, probably. Otherwise no. Perhaps you > could tell us what your hardware is? >gvb >It's not U-Boot code what determines the boot address, but your >processor. So your real question is if you can teach your CPU to >start from a different reset vector. But sorry, we cannot answer this >here. >Best regards, >Wolfgang Denk -- --------------------------------------------------------------- Everything that has a beginning has an end.

2 3

[U-Boot-Users] 7xx/74xx cache question
by Richard Danter 15 Jul '05

15 Jul '05

Hi all, Further progress on my port. I can now write to flash! I noticed in lib_ppc/board.c board_init_r() that on e500 CPU's the unlock_ram_in_cache() function is called. The 7xx/74xx also locks the init RAM in the dcache, but nowhere is it unlocked. I tried calling unlock_ram_in_cache() from my board's misc_init_r() function, but this crashes U-Boot. As an experiment, I left the cache locked, but then ran the "dcache off" command from the shell. If I do printenv before turning the dcache off it is all OK, if I do it after then it crashes. With my debugger I can see that the gd data structure is garbage when env_get_char_memory() is called. But I thought all data was copied to the main sys RAM. Is there something else I need to do before/after calling unlock_ram_in_cache() so I can use the D-Cache as normal? Thanks Rich PS Calling icache_enable() from misc_init_r() seems to work fine.

3 5

[U-Boot-Users] initialize non-transparent PCI-to-PCI bridge
by CuiYW 15 Jul '05

15 Jul '05

hi, all I am porting U-boot to custom cpci board (MPC8540 based). On the board, we use Intel non-transparent PCI-to-PCI bridge 21555 to isolate MPC8540 from system, and MPC8540 is connected to secondary pci bus of 21555. Because no srom is connected to 21555, we configure 21555 using mpc8540 (implemented in U-boot). After system starts up, mpc8540 can find and access 21555, but system card can not find and configure it(such as BAR0, BAR1). If we delay booting of system card(boot mpc8540 firstly), system card can find and configure 21555 successfully. How to fixthe problem? Could you please give me a hand? Best Regards, Cui

2 1

[U-Boot-Users] AMD29LV800T in 16bit mode x4 devices (64bit bus)
by Richard Danter 15 Jul '05

15 Jul '05

Hi, Is there a driver that supports this flash within U-Boot? I can't see one, but want to make sure I didn't miss it before I reinvent the wheel! Thanks Rich

2 3

[U-Boot-Users] 440SP
by Morten Ebbell Hestnes 15 Jul '05

15 Jul '05

Hi, I want to use U-Boot as bootloader for a board using AMCC 440SP. A similar question where asked 2004-09-09. See bellow. Is there anyone how have ported U-Boot from 440GX to 440SP? Is there anyone working with U-Boot for a board using the PPC440SP? Thanks in advance, Morten *********************************************************** From: Stefan Roese <stefan@es...> RE: 440SP evaluation board 2004-09-09 00:25 Hi Gary, > We have received an AMCC(IBM)440SP evaluation board > that has PIBS > as > the bootloader. We would like to use U-Boot. Is there anyone > working with U-Boot on this particular evaluation board? Sorry, we are not. But a port for the PPC440GP/GX exists and it should be pretty easy to generate a 440SP port from here (OCOTEA is the PPC440GX eval board from IBM/AMCC). Best regards, Stefan ***********************************************************

1 0

[U-Boot-Users] U-Boot+CSB637
by subramanian mohankumar 15 Jul '05

15 Jul '05

Hi I am new entry to U-Boot users list. We are using CSB637 board for our project. We plan to use U-Boot as bootloader since it is easy to port for our custom made board in future. Has anybody used u-boot for CSB637. If so what changes i need to do in u-boot code.please help. We tried to download u-boot1.1.2 to CSB637 board but it is not responding after message "Downlaoding U-boot...". please reply. regards Mohan ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

2 3

[U-Boot-Users] Console garbage
by Will Haines 14 Jul '05

14 Jul '05

The recent u-boot port to the EP88xC is getting closer and closer to working, but I am still having the problem that there is no coherent console output. The code to print to console is executing, but I either get no output or garbage. When I step through with the BDI, I get error messages like: serial_puts (s=0x1 <Address 0x1 out of bounds>) at serial.c:200 I have changed static struct serial_device *serial_devices = NULL; static struct serial_device *serial_current = NULL; to static struct serial_device *serial_devices __attribute__ ((section (".data"))) / = NULL; static struct serial_device *serial_current __attribute__ ((section (".data"))) / = NULL; in common/serial.c as suggested by Yuli Barcohen, but to no avail. Does anyone have any other ideas? Thank you, everyone. Will Haines

1 0

[U-Boot-Users] how can I boot u-boot from 0x40000 in flash instead of 0x0000
by Ray Zhao 14 Jul '05

14 Jul '05

My board need keep the first 0x40000 flash for special purpose. Is it easy to modify the u-boot to load itself from 0x40000 instead from the 0x0000? Any help is appreciated. Ray -- --------------------------------------------------------------- Everything that has a beginning has an end.

3 2

[U-Boot-Users] Activating hush shell
by Andreas Engel 14 Jul '05

14 Jul '05

Hi, I'm trying to switch from the old shell to hush on a custom ARM board with u-boot 1.1.2 by just defining CFG_HUSH_PARSER and CFG_PROMPT_HUSH_PS2 in the config file. However, u-boot now doesn't really wait for user input, but endlessly prints its console prompt. Before digging deeper into the problem with a debugger: do I need to do anything else beyond just enabling hush? Andreas

2 2

[U-Boot-Users] gdb debug!
by junping feng 14 Jul '05

14 Jul '05

Hi,I have some question on gdb-debugger with BDI2000.My board is like MPC8260ADS,ppcboot version is 2.0.0. I have programed ppcboot.bin into flash with BDI2000. After power on board ,information printed is below: PPCBoot 2.0.0 (Jul 10 2005 - 11:54:35) Rewin Tech :fengjunping && huangjianzhong MPC8260 Reset Status: External Soft, External Hard MPC8260 Clock Configuration - Bus-to-Core Mult 5x, VCO Div 2, 60x Bus Freq 20-60 , Core Freq 100-300 - dfbrg 0, corecnf 0x0b, busdf 5, cpmdf 1, plldf 0, pllmf 2 - vco_out 199999998, scc_clk 49999999, brg_clk 49999999 - cpu_clk 166666665, cpm_clk 99999999, bus_clk 33333333 CPU: MPC8260 (Rev 14, Mask unknown [immr=0x0064,k=0x002d]) at 166.666 MHz Board: Motorola MPC8260ADS I2C: ready DRAM: 16 MB (stop here!) Then ,cpu hangs! When I debug source code with gdb,I am troubled with the problem below: I don't know where is wrong! [root@localhost root]# cd ./ppcboot [root@localhost ppcboot]# ppc-linux-gdb ppcboot GNU gdb Yellow Dog Linux (5.2.1-4b_4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i386-redhat-linux --target=ppc-linux"... (gdb) target remote 192.168.1.108:2001 Remote debugging using 192.168.1.108:2001 0xff812568 in crc32 (crc=1165264316, buf=0xff845760 '?' <repeats 200 times>..., len=239780) at crc32.c:166 166 DO8(buf); (gdb) b cpu_init_f Breakpoint 1 at 0xff803be8: file cpu_init.c, line 118. (gdb) cont Continuing. warning: Cannot insert breakpoint 1: Error accessing memory address 0xff803be8: Unknown error 4294967295. (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) n Program not restarted. (gdb) c Continuing. Program received signal SIGSTOP, Stopped (signal). 0x00000800 in ?? () (gdb) Below is the configure file for BDI2000. ; bdiGDB configuration file for myppc8250 board ; ---------------------------------------------- ; [INIT] ; init core register WREG MSR 0x00000000;clear MSR WM32 0xF00101A8 0xF0000000 ;IMMR : internal space @ 0xF0000000 WM32 0xF0010004 0xFFFFFFC3 ;SYPCR: disable watchdog WM32 0xF0010C80 0x00000001 ;SCCR : normal operation WM32 0xF0010000 0x02600000 ;SIUMCR ; init memory controller WM32 0xF0010104 0xFF800836 ;OR0: Boot Rom 8 WM32 0xF0010100 0xFF801001 ;BR0: Flash @0xFF800000 WM32 0xF0010114 0xFF003080 ;OR2: SDRAM 16M,each chip organzied 512K*32bits*4banks,total two chips. WM32 0xF0010110 0x00000041 ;BR2: SDRAM @0x0000000 ; init SDRAM Init (PPC bus) WM16 0xF0010184 0x1900 ;MPTPR WM8 0xF001019C 0x10 ;PSRT WM32 0xF0010190 0x2869A452 ;PSDMR: Precharge all banks WM8 0x00000000 0xFF ;Access SDRAM WM32 0xF0010190 0x0869A452 ;PSDMR: CBR Refresh WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM32 0xF0010190 0x1869A452 ;PSDMR: Mode Set WM8 0x00000000 0xFF ;Access SDRAM WM32 0xF0010190 0x4069A452 ;PSDMR: enable refresh, normal [TARGET] CPUTYPE 8260 ;the CPU type (603EV,750,8240,8260) JTAGCLOCK 0 ;use 16 MHz JTAG clock BOOTADDR 0xFFF00100 ;boot address used for start-up break ;WORKSPACE 0x00000000 ;workspace in target RAM for fast download BDIMODE AGENT ;the BDI working mode (LOADONLY | AGENT | GATEWAY) BREAKMODE HARD ;SOFT or HARD, HARD uses PPC hardware breakpoints ;STEPMODE HWBP ;TRACE or HWBP, HWPB uses a hardware breakpoint VECTOR CATCH ;catch unhandled exceptions DCACHE NOFLUSH ;data cache flushing (FLUSH | NOFLUSH) ;MMU XLAT ;translate effective to physical addressa ;PTBASE 0x000000F0 ;here is the pointer to the page table pointers POWERUP 5000 ;start delay after power-up detected in ms [HOST] IP 192.168.1.10 FILE /tftpboot/ppcboot FORMAT ELF LOAD MANUAL ;load code MANUAL or AUTO after reset DEBUGPORT 2001 PROMPT MPC8260> ;new prompt for Telnet [FLASH] CHIPTYPE STRATAX16 ;Flash type (Intel E28F128J3A120) CHIPSIZE 0x800000 ;The size of one flash chip in bytes(16MB) BUSWIDTH 16 ;The width of the flash memory bus in bits ;WORKSPACE 0x00000000 ;workspace in SDRAM FORMAT BIN 0x0 FILE /tftpboot/ppcboot.bin ERASE 0xFF800000 CHIP ;erase whole chip [REGS] DMM1 0xF0000000 ;Internal Memory Map Base Address FILE reg8260.def Now, many people are still using ppcboot, please help me! Thanks in advance!! ___________________________________________________________ 雅虎免费G邮箱－No.1的防毒防垃圾超大邮箱 http://cn.mail.yahoo.com/?id=77072

3 2

[U-Boot-Users] PCI PNP
by C.Gillan＠ecit.qub.ac.uk 14 Jul '05

14 Jul '05

I am trying to understand the role of the the hash define CONFIG_PCI_PNP in the context of building a card (8540 based) with a PCI interface such that it will sit inside an Intel PCI runing Linux. I see several examples of PCI usage in the U-Boot source code but its not clear whether any of these correspond to my situation. Recently the PN62 was mentioned on this list - it is such a card ? Where can I find more documentation on it ? My guess is that the PNP code is only used when the 8540 is acting as a "master" and configuring devices that are an "extension" to it on the PCI bus. In my case, I am expecting the Intel PC's motherboard BIOS to configure the PCI controller on my 8540. So, all I need to do, I think, is configure the ATMUs to map PCI addresses into 8540 Ocean addresses ? Thanks in advance, Charles Gillan Inst. for Elect. Comms and Info. Technology (ECIT) Queen's University Belfast N. Ireland BT3 9DT

2 1

[U-Boot-Users] 2.6.12 with u-boot-1.1.2 on versatile
by Shakthi Kannan 14 Jul '05

14 Jul '05

Greetings! System details: Board: Versatile-ARM926Ej-S Cross-toolchain: 3.4.3 Linux kernel: 2.6.12 u-boot: 1.1.2 I have been able to successfully cross-compile u-boot, program it to NOR flash, and run it from the SDRAM. I have also cross-compiled the kernel to create the vmlinux file. I have used the config file provided in arm.com site for this board: http://www.arm.com/linux/linux_download.html I then created uImage using: # arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin # gzip linux.bin # ./mkimage -A arm -O linux -T kernel -C gzip -a 0xc0008000 -e 0xc0008000 -n "Linux Kernel Image" -d linux.bin.gz uImage The uImage is programmed at 0x36000000 in NOR flash. But, When I try to run the kernel from u-boot it hangs at the following: ## Booting image at 36000000 ... Image Name: Linux kernel image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1112206 Bytes = 1.1 MB Load Address: c0008000 Entry Point: c0008000 Uncompressing Kernel Image ... OK Starting kernel ... When I looked through the debugger (Lauterbach), it hung at a virtual address inside panic.c. If anyone can tell me as to what I am doing wrong, and how I can get the kernel up and running on this board, it will be really helpful. Thanks, K Shakthi -- proudly anti-micro$oft ------------------------------------------------------------ Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shaks(a)shakthimaan.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India ------------------------------------------------------------ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 6

[U-Boot-Users] [PATCH] sinclude board specific make fragment
by Murray.Jensen＠csiro.au 14 Jul '05

14 Jul '05

This patch "sinclude"s (i.e. it is allowed not to exist) a make fragment from the board specific subdirectory, to allow a port to have board or platform specific targets (which may or may not be added to ALL var - see previous patch). for example - install, or in the case of my 8560 based board, I build a separate file image of the "boot page". Cheers! Murray... -- Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763 Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853 Internet: Murray.Jensen(a)csiro.au To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference. The information contained in this e-mail may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this e-mail in error, please delete it immediately and notify Murray Jensen on +61 3 9662 7763. Thank you.

2 6

[U-Boot-Users] CF 5282 fec.c
by Jens Scharsig 13 Jul '05

13 Jul '05

Hello I'm new on U-Boot and work on a MCF5282 port. I have modify the cvs source and U-Boot runs on my own MCF5282 board (I get a promt on serial line). But i get "Tx not ready" and "Tx Timeout" messages for each ethernet access. I discover the fec.c, and find out that only 10MBit haft duplex is use. Is there in implementation for full 100MBit use? regards Jens Scharsig Internet: http://www.bus-elektronik.de

1 0

[U-Boot-Users] Problem about sdram initialization！
by junping feng 13 Jul '05

13 Jul '05

Hi,I have a little problem with the ppcboot startup,the BDI2000 can program ppcboot.bin into FLASH .Board information can print through serial interface after the first initialization of board now. But when it run to the function relocate_code(in the /cpu/mpc8260/start.s),it don't run continually. Through LED on the board ,I find that it stops at the code below: addi r0, r10, in_ram - _start + EXC_OFF_SYS_RESET mtlr r0 blr in_ram: The size of SDRAM size is 16MB,flash is 8MB,CPU is MPC8250,and my costum board is like the board MPC8260ADS.Othe infomation with my board is below: CLKIN:33M MPTPR:0x10 PSRT:0x1900 BR2(control SDRAM): 0x0000 0041 OR2:0xFF80 3080 PSDMR: 0x2869 A452 0x0869 A452 0x1869 A452 0x4069 A452 SIUMCR：0x0A20 0000 Please give me a hand. Thanks in advance! __________________________________________________ 赶快注册雅虎超大容量免费邮箱? http://cn.mail.yahoo.com

3 2

RE: [U-Boot-Users] Problem about sdram initialization!
by Nghiem, Tien 13 Jul '05

13 Jul '05

Hi, The ppcboot is a very old version of the bootloader. Why don't you use the lastest version of the u-boot: u-boot-1.1.2? Tien -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of junping feng Sent: Wednesday, July 13, 2005 7:47 AM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] Problem about sdram initialization! Hi,I have a little problem with the ppcboot startup,the BDI2000 can program ppcboot.bin into FLASH .Board information can print through serial interface after the first initialization of board now. But when it run to the function relocate_code(in the /cpu/mpc8260/start.s),it don't run continually. Through LED on the board ,I find that it stops at the code below: addi r0, r10, in_ram - _start + EXC_OFF_SYS_RESET mtlr r0 blr in_ram: The size of SDRAM size is 16MB,flash is 8MB,CPU is MPC8250,and my costum board is like the board MPC8260ADS.Othe infomation with my board is below: CLKIN:33M MPTPR:0x10 PSRT:0x1900 BR2(control SDRAM): 0x0000 0041 OR2:0xFF80 3080 PSDMR: 0x2869 A452 0x0869 A452 0x1869 A452 0x4069 A452 SIUMCR：0x0A20 0000 Please give me a hand. Thanks in advance! __________________________________________________ 赶快注册雅虎超大容量免费邮箱? http://cn.mail.yahoo.com

1 0

[U-Boot-Users] Side-effects when adding debug output
by "Häpe, Sebastian, HRD/AB" 13 Jul '05

13 Jul '05

Hi everybody! I have a little problem with u-boot and I don't know if I am the reason for it. It's the following: I want to add some extra output to the functions do_bootm and do_bootm_linux because I have problems with the kernel parameters. So i added a few printf's to the functions mentioned above. The things that happen now, I do not understand: Parameters of called functions (e.g. like the "int argc" parameter) suddenly change to random values. How could that be caused? Has it something to do with the stack (overflow or undefined behaviour when using "printf")? Or should I use any other function for creating output? (instead of using the BDI2k) Greetings, Sebastian

2 1