September 2007 - U-Boot

[U-Boot-Users] u-boot init problem on ml403 (virtex-4) board
by Miroslaw Dach 28 Sep '07

28 Sep '07

Dear All, I am trying to use u-boot 1.2.0 on my avnet evaluation board (ml403 like with virtex-4 chip with built-in ppc405). My observation is as following: I am able to run linux v2.6.21 v2.6.22 v2.6.23 (zImage.elf) on my board. Linux always boots correctly. My board has 32 MB of RAM and 8 MB of Flash. Right now I run all of the software straight from RAM (by means of jtag). For couple of weeks I am dealing with u-boot with UART lite serial console. My observation is as following that u-boot does not always run properly. The u-boot crashes (or has some initialization problems) in most cases when I go through following steps: 1. I load Linux zImage.elf via jtag: XMD% dow zImage.elf section, .text: 0x00400000-0x004036c4 section, .data: 0x00404000-0x00505000 section, .bss: 0x00505000-0x0050719c Downloaded Program zImage.elf Setting PC with program start addr = 0x00400000 PC reset to 0x00400000, Clearing MSR Register XMD% run 2. Linux loads and boot always without any problems 3. Next I stop Linux and load u-boot via jtag XMD% dow u-bootXil section, .text: 0x00800000-0x0080e85c section, .resetvec: 0x00815050-0x00815054 section, .rodata: 0x0080e85c-0x00811027 section, .reloc: 0x00811100-0x00811770 section, .data: 0x00811770-0x00811c60 section, .data.rel: 0x00811c60-0x00811c8c section, .data.rel.local: 0x00811c8c-0x008120c4 section, .u_boot_cmd: 0x008120c4-0x00812364 section, .bss: 0x00812400-0x00815050 Downloaded Program u-bootXil Setting PC with program start addr = 0x00800100 PC reset to 0x00800100, Clearing MSR Register XMD% run ----------------------------------------------------------------- The output on the console is as following: ----------------------------------------------------------------- U-Boot 1.2.0 (Sep 25 2007 - 09:24:54) ### No HW ID - assuming ML403 DRAM: 32 MB Top of RAM usable for U-Boot at: 02000000 Reserving 84k for U-Boot at: 01fea000 Reserving 129k for malloc() at: 01fc9c00 Reserving 120 Bytes for Board Info at: 01fc9b88 Reserving 48 Bytes for Global Data at: 01fc9b58 Stack Pointer at: 01fc9b38 New Stack Pointer is: 01fc9b38 Now running in RAM - U-Boot at: 01fea000 Using default environment Bus Fault @ 0x01ff34dc, fixup 0x00000000 Machine check in kernel mode. Caused by (from msr): regs 01fc98f8 Data parity signal NIP: 01FF34DC XER: 00000000 LR: 01FF2F40 REGS: 01fc98f8 TRAP: 0200 DAR: 00000000 MSR: 00021000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00 GPR00: 00000000 01FC99E8 C01F3950 01AEA000 00000120 00000000 00000001 00000021 -------------------------------------------------------------------------- Sometimes u-boot dos not crash but it seems to be something wrong with board info: -------------------------------------------------------------------------- U-Boot 1.2.0 (Sep 24 2007 - 12:48:09) ### No HW ID - assuming ML403 DRAM: 32 MB Top of RAM usable for U-Boot at: 02000000 Reserving 83k for U-Boot at: 01feb000 Reserving 129k for malloc() at: 01fcac00 Reserving 120 Bytes for Board Info at: 01fcab88 Reserving 48 Bytes for Global Data at: 01fcab58 Stack Pointer at: 01fcab38 New Stack Pointer is: 01fcab38 Now running in RAM - U-Boot at: 01feb000 ˙ţď\In: ˙ţď\Err: U-Boot relocated to 01feb000 ### main_loop entered: bootdelay=3 ### main_loop: bootcmd="tftp 0x500000 uImage; bootm 0x500000" Hit any key to stop autoboot: 3 2 1 0 => bdinfo bd address = 0x0memstart = 0x00000000 memsize = 0x0flashstart = 0x00000000 flashsize = 0x00000000 flashoffset = 0x00000000 sramstart = 0x00000000 sramsize = 0x00000000 bootflags = 0xCprocfreq = 100 MHz plb_busfreq = 100 MHz ethaddr = 00:ţ:C:˙ď:D:0 IP addr = 129.129.144.83 baudrate = 9600 bps => md 01fcab88 100 01fcab88: ................ 01fcab98: ............. . 01fcaba8: ...S.P.F........ 01fcabb8: ......%.1.2.U-Bo 01fcabc8: ot 1.2.0........ 01fcabd8: ................ 01fcabe8: ................ 01fcabf8: ................ 01fcac08: ..r|bootargs=con 01fcac18: sole=ttyUL0,9600 01fcac28: root=/dev/nfs r 01fcac38: w nfsroot=129.12 01fcac48: 9.144.113:/opt/e 01fcac58: ldk41/ppc_4xx,tc 01fcac68: p ip=::::virtex 01fcac78: 4-mirek:eth0:dhc 01fcac88: p panic=1.bootcm 01fcac98: d=tftp 0x500000 01fcaca8: uImage; bootm 0x 01fcacb8: 500000.bootdelay 01fcacc8: =3.baudrate=9600 01fcacd8: .loads_echo=1.et 01fcace8: haddr=00:50:C2:4 01fcacf8: 6:D8:01.ipaddr=1 01fcad08: 29.129.144.83.se 01fcad18: rverip=129.129.1 01fcad28: 44.113.hostname= 01fcad38: virtex4-mirek.lo 01fcad48: adaddr=0x500000. 01fcad58: stdin=.stdout=.s 01fcad68: tderr=.......... 01fcad78: ................ ------------------------------------------------------------------------- When u-boot starts properly the output looks like below: ------------------------------------------------------------------------- U-Boot 1.2.0 (Sep 24 2007 - 12:48:09) ### No HW ID - assuming ML403 DRAM: 32 MB Top of RAM usable for U-Boot at: 02000000 Reserving 83k for U-Boot at: 01feb000 Reserving 129k for malloc() at: 01fcac00 Reserving 120 Bytes for Board Info at: 01fcab88 Reserving 48 Bytes for Global Data at: 01fcab58 Stack Pointer at: 01fcab38 New Stack Pointer is: 01fcab38 Now running in RAM - U-Boot at: 01feb000 Using default environment In: serial Out: serial Err: serial U-Boot relocated to 01feb000 ### main_loop entered: bootdelay=3 ### main_loop: bootcmd="tftp 0x500000 uImage; bootm 0x500000" Hit any key to stop autoboot: 3 2 1 0 => bdinfo bd address = 0x01FCAB88 memstart = 0x00000000 memsize = 0x02000000 flashstart = 0x00000000 flashsize = 0x00000000 flashoffset = 0x00000000 sramstart = 0x00000000 sramsize = 0x00000000 bootflags = 0xC1CB7D60 procfreq = 100 MHz plb_busfreq = 100 MHz ethaddr = 00:50:C2:46:D8:01 IP addr = 129.129.144.83 baudrate = 9600 bps ------------------------------------------------------------------------ I was trying to play with various u-boot parameters (CFG_ or CONFIG_ ) but I have never got it running reliably. My observation is also as following ACTION (jtag side): STATUS: load zImage.elf run runs properly (always) stop load u-boot run crashes (in most cases) stop load u-boot run runs properly (in most cases) stop load u-boot run runs properly (in most cases) stop Does somebody have some hints what could be wrong? Best Regards Mirek p.s. I attache to this e-mail my config file include/configs/ml403.h

3 3

[U-Boot-Users] TEXT_BASE question
by robert lazarski 28 Sep '07

28 Sep '07

Hi all, I see that many boards use, and that TEXT_BASE is often defined in config.mk . In my 85xx case, I have: TEXT_BASE = 0xfff80000 However, some of my registers are using TEXT_BASE + DATA that don't seem right. In the bdi I get: ATUM>rd ivor15 ivor15 : 0x00000f00 3840 That seems out of range of my 4K stack before relocation, could that be a problem or am I simply reading this wrong? Thanks, Robert

2 2

[U-Boot-Users] gaon
by Jeegar blamey 28 Sep '07

28 Sep '07

Mining Sector --- Delta Mining UPDATE HOT SECTOR: Additional information on (O_T_C: D M X C) D M X C is expected to arrive soon. For those of you who currently own this company this will be great news. For those that don't currently own this company, you need to get in on this now. The company recently traded as high as .13 and with any significant news should be able to see (if not exceed) those prices again. Contact your broker now, don't miss this opportunity in D M X C!

1 0

[U-Boot-Users] make entry for creating new folder in standalone board
by nivas 28 Sep '07

28 Sep '07

Hi All, lam using u-boot-1.1.6 source(cpu-arm926ejs board-mcs8140(our standalone board). I want to create a new folder under my board(mcs8140) for some validation code. how to make entry for new folder and how to create a makefile in new folder? Please give me a solution for above problem. Srinivas Rao.Ch -- View this message in context: http://www.nabble.com/make-entry-for-creating-new-folder-in-standalone-boar… Sent from the Uboot - Users mailing list archive at Nabble.com.

3 2

[U-Boot-Users] Please help me!
by zxl 28 Sep '07

28 Sep '07

Hi: My u-boot can not start. DRAM: 64 MB Flash: 1 MB NAND: 64 MB *** Warning - bad CRC or NAND, using default environment It stop here. Please help me, thanks! Note: u-boot-1.1.6 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[U-Boot-Users] Fix missing DECLARE_GLOBAL_DATA_PTR on CONFIG_LPC2292 in serial
by Jean-Christophe PLAGNIOL-VILLARD 28 Sep '07

28 Sep '07

Hi, Fix missing DECLARE_GLOBAL_DATA_PTR on CONFIG_LPC2292 in serial Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj(a)jcrosoft.com> --- diff --git a/cpu/arm720t/serial.c b/cpu/arm720t/serial.c index 27eb73a..1b0e147 100644 --- a/cpu/arm720t/serial.c +++ b/cpu/arm720t/serial.c @@ -125,6 +125,8 @@ serial_puts (const char *s) #elif defined(CONFIG_LPC2292) +DECLARE_GLOBAL_DATA_PTR; + #include <asm/arch/hardware.h> void serial_setbrg (void) Best Regards Jean-Christophe PLAGNIOL-VILLARD

2 1

[U-Boot-Users] FPGA loading question
by E Robertson 27 Sep '07

27 Sep '07

Hi All, I've got a Spartan3E fpga I'm trying to program serially with a bin file. Is there any similar driver available to so this? I'm not sure if this is better done as a driver with embedded binary or as part of a hust script but the bin file embedded in the u-boot source. (I'm not sure if the latter is possible). Thanks.

4 6

[U-Boot-Users] Looking for Help booting Kernel
by Nick Droogh 27 Sep '07

27 Sep '07

Hi, I am trying to boot the latest kernel for a MPC5200B based board from DENX. I built the latest UBoot which seems to run fine on my board. With the new uboot, my same environment variables, I can still boot my old kernel. U-Boot 1.3.0-rc2-dirty (Sep 24 2007 - 08:08:49) CPU: MPC5200 v1.2, Core v1.1 at 462 MHz Bus 132 MHz, IPB 132 MHz, PCI 33 MHz Board: MyBoard MPC5200 Controller I2C: 343 kHz, ready DRAM: 128 MB FLASH: 64 MB In: serial Out: serial Err: serial Net: FEC ETHERNET IDE: Bus 0: not available Type "run net_nfs" to mount root filesystem over NFS Hit any key to stop autoboot: 0 Using FEC ETHERNET device TFTP from server 192.168.100.102; our IP address is 192.168.100.11 Filename 'uImage'. Load address: 0x200000 Loading: ################################################################# ############################################# done Bytes transferred = 1612360 (189a48 hex) ## Booting image at 00200000 ... Image Name: Linux-2.6.19.2 Created: 2007-09-21 8:11:59 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1612296 Bytes = 1.5 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK id mach(): done MMU:enter MMU:hw init MMU:mapin MMU:setio MMU:exit setup_arch: enter setup_arch: bootmem arch: exit Linux version 2.6.19.2 (nick@nick_lnx) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) \ #5 Fri Sep 21 04:11:50 EDT 2007 Zone PFN ranges: DMA 0 -> 32768 Normal 32768 -> 32768 early_node_map[1] active PFN ranges 0: 0 -> 32768 Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/nfs rw nfsroot=192.168.100.102:/opt/eldk/ppc_6xx \ ip=192.168.100.11:192.168.100.102:192.168.100.102:255.255.255.0:\ MyBoard:eth0:off console=ttyPSC0,115200 panic=1 PID hash table entries: 512 (order: 9, 2048 bytes) I-pipe 1.5-00: pipeline enabled. Console: colour dummy device 80x25 ... and the kernel runs fine. With the latest kernel from Denx, I get the following: U-Boot 1.3.0-rc2-dirty (Sep 24 2007 - 08:08:49) CPU: MPC5200 v1.2, Core v1.1 at 462 MHz Bus 132 MHz, IPB 132 MHz, PCI 33 MHz Board: MyBoard MPC5200 Controller I2C: 343 kHz, ready DRAM: 128 MB FLASH: 64 MB In: serial Out: serial Err: serial Net: FEC ETHERNET IDE: Bus 0: not available Type "run net_nfs" to mount root filesystem over NFS Hit any key to stop autoboot: 0 => boot Using FEC ETHERNET device TFTP from server 192.168.100.102; our IP address is 192.168.100.11 Filename 'uImage'. Load address: 0x200000 Loading: ################################################################# ################## done Bytes transferred = 1212323 (127fa3 hex) ## Booting image at 00200000 ... Image Name: Linux-2.6.23-rc6-gea60adb5-dirty Created: 2007-09-26 9:53:02 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1212259 Bytes = 1.2 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Is there anything special I need to pass to the kernel for setting up the console on the MPC5200B? I had to change ttyS0 to ttyPSC0 for the old console to work. Is there anything I need to enable inside the kernel? The kernel command line is: root=/dev/nfs rw nfsroot=192.168.100.102:/opt/eldk/ppc_6xx \ ip=192.168.100.11:192.168.100.102:192.168.100.102:255.255.255.0:\ MyBoard:eth0:off console=ttyPSC0,115200 panic=1 Many thanks, Nick

2 2

Re: [U-Boot-Users] Problem with Lite5200 DDR configuration
by Txema Lopez 27 Sep '07

27 Sep '07

Prakash Palanisamy, TLS-Chennai wrote: > Hi, > > We are using u-Boot in Lite5200B with DDR. We compiled the u-Boot with > “ icecube_5200_DDR_LOWBOOT_config” option and flashed the image in to > flash at * 0xFF800000 * . > > The problem we are facing is, > > The image is *booting* only if we flash the image in *both (0xFF800000 > and 0xFF000000) places*. The reset vector for the two configurations > (icecube_5200_LOWBOOT & icecube_5200_DDR_LOWBOOT) are same. > > We have tried by writing different images in these locations and found > that the booted image is the one which is flashed in 0xFF800000. But > if erase the image at 0xFF000000, it is not booting. > The Lite5200B has two banks of 16Mbtes flash, so if you flashed U-Boot in the 0xFF800000 you are putting it in the meddle of the flash, nor in theLOWBOOT location, nor in the HIGH boot location. When you flash a new U-Boot in the 0xFF000000 the system starts from this location but I think there is a jump to the U-Boot flashed in the 0xFF800000 because your TEXT_BASE ( the address reference for the linker) in U-Boot is 0xFF800000. The correct address for the LOWBOOT in the Lite5200B is 0xFF000000. Best Regards, Txema.

1 0

[U-Boot-Users] Problem with Lite5200 DDR configuration
by Prakash Palanisamy, TLS-Chennai 27 Sep '07

27 Sep '07

Hi, We are using u-Boot in Lite5200B with DDR. We compiled the u-Boot with "icecube_5200_DDR_LOWBOOT_config" option and flashed the image in to flash at 0xFF800000. The problem we are facing is, The image is booting only if we flash the image in both (0xFF800000 and 0xFF000000) places. The reset vector for the two configurations (icecube_5200_LOWBOOT & icecube_5200_DDR_LOWBOOT) are same. We have tried by writing different images in these locations and found that the booted image is the one which is flashed in 0xFF800000. But if erase the image at 0xFF000000, it is not booting. In the README for Icecube is as follows ------------------------------------------------------------------------ --- Build target Flash address | BDI "go" command | Reset Vector ------------------------------------------------------------------------ --- Lite5200 0xFFF00000 | 0xFFF00100 | 0xFFF00100 Lite5200_LOWBOOT 0xFF000000 | 0xFF000100 | 0x00000100 Lite5200_LOWBOOT08 0xFF800000 | 0xFF800100 | 0x00000100 icecube_5200 0xFFF00000 | 0xFFF00100 | 0xFFF00100 icecube_5200_LOWBOOT 0xFF000000 | 0xFF000100 | 0x00000100 icecube_5200_LOWBOOT08 0xFF800000 | 0xFF800100 | 0x00000100 icecube_5200_DDR 0xFFF00000 | 0xFFF00100 | 0xFFF00100 icecube_5200_DDR_LOWBOOT 0xFF800000 | 0xFF800100 | 0x00000100 icecube_5200_DDR_LOWBOOT08 0xFF800000 | 0xFF800100 | 0x00000100 ------------------------------------------------------------------------ --- Can any one help me to find out the issue? Thanks & Regards, P.Prakash DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. -----------------------------------------------------------------------------------------------------------------------

1 0