September 2005 - U-Boot

RE: [U-Boot-Users] Fail Safe: Redundant U-boot Images in Flash??? ?
by Eisenhut, Daniel (GE Healthcare) 24 Sep '05

24 Sep '05

> > > > > So what happens if the CRC is correct, but the new image has > > a > > > bug (functional ?) in it.... > > > > Then you should of tested your code before you released it. > > If the > > CRC passes, then it is the same as what you tested. > > > Famous last words. Sometimes corner cases are missed. I don't > know about you, but I realized a long time ago I am not perfect > and make mistakes. So what do you do when the hardware reboots > because of some unforseen proble? Just sit in a loop and reboot > forever? No, no one is perfect. But to imply that we should forgo implementing fail safes to protect against the power failing right as we are programming flash or flash becoming corrupt just because we might still have a bug in our code, is just plain foolish.

2 1

RE: [U-Boot-Users] Fail Safe: Redundant U-boot Images in Flash??? ?
by Eisenhut, Daniel (GE Healthcare) 23 Sep '05

23 Sep '05

> So what happens if the CRC is correct, but the new image has a > bug (functional ?) in it.... Then you should of tested your code before you released it. If the CRC passes, then it is the same as what you tested.

2 2

RE: [U-Boot-Users] Fail Safe: Redundant U-boot Images in Flash??? ?
by Roberts, John 23 Sep '05

23 Sep '05

>It is impossible - there is only one reset entry point. >How would you determine which image to boot? >What you typically do (assuming the hardware supports it) is to have >two banks of flash memory that can be swapped using some jumper or >switch or so. The code at the entry point needs to be small, reliable and never require an upgrade in the field. This code would run a CRC on the primary U-boot image to determine if it's safe to boot, upon CRC failure verify then run the backup image. For remote systems we need to resolve the issue of upgrade failure without human intervention - or perhaps remote human intervention. -John Roberts (Engineer, not Judge)

4 3

[U-Boot-Users] Fail Safe: Redundant U-boot Images in Flash????
by Roberts, John 23 Sep '05

23 Sep '05

Has anyone ever implemented duel U-boot images in flash as a fail safe mechanism? A primary U-boot image, and a backup U-boot image incase the primary image is invalid. I understand there needs to be a single boot point with verification to determine which image to boot from. Is there a mechanism already in U-boot that can do this? Any information is appreciated. (440gx) > -John Roberts > >

3 2

RE: [U-Boot-Users] Fail Safe: Redundant U-boot Images in Flash????
by Eisenhut, Daniel (GE Healthcare) 23 Sep '05

23 Sep '05

> Has anyone ever implemented duel U-boot images in flash as a > fail safe mechanism? A primary U-boot image, and a backup U-boot > image incase the primary image is invalid. > > I understand there needs to be a single boot point with > verification to determine which image to boot from. Is there a > mechanism already in U-boot that can do this? We're looking at doing something similar on an MPC860 with a first-stage U-Boot that just checksums and jumps to one of two second-stage U-Boot images that are stored in flash. This would allow us to update U-Boot in the field without risk of losing our bootloader and being left with a dead system. Of course, this assumes we keep the initial U-Boot very simple so that we can get away with never updating it. We haven't started working on it yet, just discussing at a high level. Might have some issues with vectors. Dan

2 1

[U-Boot-Users] AT91RM9200 Bits...
by Joe Grisso 23 Sep '05

23 Sep '05

Hello all, I was wondering who was working on the AT91RM9200 bits within the U-Boot CVS tree? I'm currently bringing up a new hardware platform and see where pieces could be streamlined. Some with code changes to the lowlevel_init.S file, and some with just simple variable changes. Going over the register init routine I found 3 registers that are written to (MC_PUIA, MC_PUP, MC_PUER) that are shown as reserved on the RM9200 datasheet and errata. Also, there's a definition to the SMC2_CSR which the atmel datasheet shows as SMC_CSR0. Bringing a lot of these #defines and whatnot in line with the datasheet would help folks that are new to U-Boot porting navigate everything easier. :-) Best Regards, Joe Grisso Detachment 3 Media, Ltd.

1 0

[U-Boot-Users] [PATCH] mips lds alignment bug
by Geoff Cleary 23 Sep '05

23 Sep '05

The following patch corrects a problem in (at least) the dbau1x0/u-boot.lds The bug only shows if the GOT requires alignment onto 16 byte boundary. In this case the _gp symbol is aligned, but the actual GOT section is not. *** u-boot_fix/board/dbau1x00/u-boot.lds 2005-09-23 13:38:13.126887305 -0400 --- u-boot/board/dbau1x00/u-boot.lds 2005-09-23 13:38:32.392077670 -0400 *************** *** 46,53 **** . = ALIGN(4); .sdata : { *(.sdata) } ! . = ALIGN(16); ! _gp = .; __got_start = .; .got : { *(.got) } --- 46,52 ---- . = ALIGN(4); .sdata : { *(.sdata) } ! _gp = ALIGN(16); __got_start = .; .got : { *(.got) } Geoff

1 0

[U-Boot-Users] " Configuring Flash on PPC405ep board"
by nreddy＠netenrich.com 23 Sep '05

23 Sep '05

Hi All, I need to know how to configure 8MB Flash on PPC405ep board. I already have 4MB flash on PPC405ep board working fine . I am using u-boot as my bootloader. Can anybody tell me what are the registers to be configured at Processor side(i am new to this register settings) or memory controller side. Please tell me the steps that i need to follow to write my own dirver(i may take existing driver as reference). Thanks in Advance, --Nagi

4 4

[U-Boot-Users] Hi all...
by Kiran Jammula 23 Sep '05

23 Sep '05

Hi, I am using Hms30c7202 from Hynix. I supports to serial ports. At the time of Booting U boot uses one seial port as console. How to use another serail pot while bootng. In /boards/serial.c there is only one seial port initialization is there.. Please help me in this.... Thanks in advance. Kiran Jammula. _________________________________________________________________ Stock Market Made Easy! http://www.sharekhan.com/campaign/OpenNewAccount.asp?ProdID=23&SrcID=59 Join Sharekhans FirstStep. learn the basics.

2 1

[U-Boot-Users] Boot Problem
by batsayan.das＠tcs.com 23 Sep '05

23 Sep '05

Hello, I would like to boot the OMAP5912 board from u-boot. Memory layout is : FLASH : Starts from 0x0000 0000 (32MB) SDRAM: 0x1000 0000 to 0x1200 0000 (32 MB) I used the kernel Image with DHCP Support = ON. I copied the uImage at 0x0001 0000 and uRamdisk at 0x0010 0000 *********************LOG***************************** OMAP5912 OSK # tftp 10000000 uImage OMAP5912 OSK # cp.b 10000000 100000 b67e4 OMAP5912 OSK # imi 100000 ## Checking Image at 00100000 ... Image Name: Linux-2.4.20_mvl31-omap5912_osk Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 747428 Bytes = 729.9 kB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... OK OMAP5912 OSK # tftp 10000000 uRamdisk OMAP5912 OSK # cp.b 10000000 1000000 16f4eb OMAP5912 OSK # imi 1000000 ## Checking Image at 01000000 ... Image Name: Test Ramdisk Image Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 1504427 Bytes = 1.4 MB Load Address: 11000000 Entry Point: 11000000 Verifying Checksum ... OK OMAP5912 OSK # setenv bootargs mem=32M console=ttyS0,115200n8 root=/dev/rd/0 ramdisk_start=1000000 OMAP5912 OSK # print baudrate=115200 ethaddr=00:0E:99:02:06:7D bootdelay=10 bootfile=/tftpboot/omap/dhcp_uImage hostname=tqm stdin=serial stdout=serial stderr=serial filesize=16f4eb fileaddr=10000000 gatewayip=172.18.19.253 netmask=255.255.248.0 ipaddr=172.18.20.198 serverip=172.18.20.141 bootargs=mem=32M console=ttyS0,115200n8 root=/dev/rd/0 ramdisk_start=1000000 Environment size: 346/131068 bytes OMAP5912 OSK # bootm 100000 ## Booting image at 00100000 ... Image Name: Linux-2.4.20_mvl31-omap5912_osk Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 747428 Bytes = 729.9 kB Load Address: 10008000 Entry Point: 10008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux................................................... ...... ..... Backtrace: Function entered at [<c00c0fa8>] from [<c0049fc0>] r7 = 00000000 r6 = FFFFFFEA r5 = C03FA120 r4 = C03FA140 Function entered at [<c0049ef0>] from [<c0008ecc>] Function entered at [<c0008e68>] from [<c0009094>] r8 = 00000001 r7 = C018BD54 r6 = 00000000 r5 = C01874D4 r4 = 00000000 Function entered at [<c0009020>] from [<c001829c>] Function entered at [<c00181dc>] from [<c0018040>] r6 = C01B6728 r5 = C0176000 r4 = 00000000 Function entered at [<c001802c>] from [<c001bcac>] Code: 1a00002c e2522004 4282c004 4a00001b (e4913004) Kernel panic: Attempted to kill init! **************************LOG END*********************************** I also tried with => setenv bootargs root=/dev/ram rw => bootm 100000 1000000 But it also does not work, I think I made some mistake by passing the correct kernel parameter. What might be the correct bootargs value? The same uImage and uRamdisk works fine if the ramdisk image is mounted by NFS with the bootargs (setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=172.18.22.125:/mnt, nolock mem=30M) What am I missing? Now I tried with uImage without DHCP support which gives the following log ******LOG WITHOUT DHCP ************** OMAP5912 OSK # bootm 100000 1000000 ...... OMAP flash: using static partition definition Creating 5 MTD partitions on "omap-flash": 0x00000000-0x00020000 : "BootLoader" 0x00020000-0x00040000 : "Params" 0x00040000-0x00240000 : "Kernel" 0x00240000-0x01000000 : "Flash0 FileSys" 0x01000000-0x02000000 : "Flash1 FileSys" Linux Kernel Card Services 3.1.22 options: none NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 2048 bind 4096) IP-Config: Incomplete network configuration information. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.7 Ben Greear <greearb(a)candelatech.com> All bugs added by David S. Miller <davem(a)redhat.com> NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "nfs" or 02:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 02:00 ********************END*********************** What is the general rule to set bootargs? Batsayan Das Tata Consultancy Services Limited Mailto: batsayan.das(a)tcs.com Website: http://www.tcs.com Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

[U-Boot-Users] vmlinux kernel image(IN ELF BINARY format) for making uImage
by Swapnil Ashok Narkhede 21 Sep '05

21 Sep '05

Hi, I have several doubts. 1>> The README of U-boot says for generating uImage we have to get vmlinux image in ELF BINARY FORMAT. How do i know if the vmlinuz image that i have is in ELF BINARY format? 2>> I have a vmlinux image compiled from MontaVista Linux for COnsumer Edition. The size of this image is 28 MB but when i use this image in generating uImage the linux.bin that is genrated is of 1.7MB and after gzipping it and finally making uImage the uImage is of 775Kb. How is this possible? What is exactly happening out here? Is it a right way to pass MontaVista Kernel image to Uimage? Why is there so much of reduction in size? Please help me clear this concept Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

2 1

[U-Boot-Users] [PATCH] Fix bug in auto_update (trab board)
by Martin Krause 21 Sep '05

21 Sep '05

[PATCH] Fix bug in auto_update (trab board) Exclude image header from image size calculation (for firmware.img), because the image header is not stored to FLASH. Signed-off-by Martin Krause <martin.krause(a)tqs.de> --- CHANGELOG entry: * Fix bug in auto_update (trab board) Patch by Martin Krause, 16 Sep 2005 board/trab/auto_update.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) 4111a69f46a7a264564a413521599d907a463b93 diff --git a/board/trab/auto_update.c b/board/trab/auto_update.c --- a/board/trab/auto_update.c +++ b/board/trab/auto_update.c @@ -296,7 +296,7 @@ au_check_header_valid(int idx, long nbyt /* recycle checksum */ checksum = ntohl(hdr->ih_size); /* for kernel and app the image header must also fit into flash */ - if (idx != IDX_DISK) + if ((idx != IDX_DISK) && (idx != IDX_FIRMWARE)) checksum += sizeof(*hdr); /* check the size does not exceed space in flash. HUSH scripts */ /* all have ausize[] set to 0 */ Regards, Martin TQ-Systems GmbH Mühlstraße 2, Gut Delling, 82229 Seefeld Tel. +49 (8153) 93 08-157, Fax +49 (8153) 93 08-7157 martin.krause(a)tqs.de www.tq-group.com

2 1

[U-Boot-Users] [PATCH] computation of framebuffer palette for 8bpp lcd bitmaps
by Francesco Mandracci 21 Sep '05

21 Sep '05

-- This patch is a bug fix. -- Description on the bug: using 8 bits/pixel framebuffer, all (splashscreen) bitmaps with palette colors whose RGB components differ in the 5 high bits in the blue byte and/or in the 6 high bits in the green byte do not display correctly. -- How my patch fixes this bug: computing correctly the palette entries. The C code fills a 16bit palette entry with 3 RGB bytes in the form RRRR RGGG GGGB BBBB [....|....|....|....] masks: (R,G,B) (0xf800, 0x07e0, 0x001f) fedc ba98 7654 3210 The used bits are the highest 5 bits for the red and blue bytes and the 6 high bits for the green byte. This did not change neither in PowerPC nor in PXA in all cvs.sf.net revisions I've found. The computation may be either: colreg = ((red & 0xf8) << 8) /* [RRRR|Rrrr|....|....] */ | ((green & 0xfc) << 3) /* [....|.GGG|GGGg|g...] */ | ((blue & 0xf8) >> 3); /* [....|....|...B|BBBB]bbb. */ or: colreg = ((red << 8) & 0xf800) | ((green << 3) & 0x07e0) /* versus " << 4" */ | ((blue >> 3) & 0x001f); /* versus " >> 0" */ I choose the latter form because it's the way you adopted. -- A way of demonstrating that the patch actually fixes something is simply displaying such a bitmap (either splashscreen or simply as argument to "bmp display"). For instance obtaining a 640x480 8 bpp bitmap from http://www.dreamvideo.it/video/immagini/monoscopio.jpg: the original code displays greys as yellowish and blues as rubbish, while the patched code displays everything correctly. -- (no new features) -- CHANGELOG entry * Corrected the computation of framebuffer palette for 8bpp lcd bitmaps Patch by Francesco Mandracci, 16 Sep 2005 -- CREDITS entry N: Francesco Mandracci E: francesco.mandracci(a)primaelectronics.com P: ID=0xF6B25635 P: Fingerprint=4059 B2F9 E987 105D 00C8 3DEA 848C F56A F6B2 5635 D: Hacking PXA270 -- (no new board) -- (no new configuration options) -- The patch itself: ------------------------------------------------------------------- Index: common/lcd.c =================================================================== RCS file: /cvsroot/u-boot/u-boot/common/lcd.c,v retrieving revision 1.5 diff -p -u -r1.5 lcd.c --- common/lcd.c 4 Jul 2005 00:03:16 -0000 1.5 +++ common/lcd.c 16 Sep 2005 13:07:00 -0000 @@ -638,8 +638,8 @@ int lcd_display_bitmap(ulong bmp_image, bmp_color_table_entry_t cte = bmp->color_table[i]; ushort colreg = ( ((cte.red) << 8) & 0xf800) | - ( ((cte.green) << 4) & 0x07e0) | - ( (cte.blue) & 0x001f) ; + ( ((cte.green) << 3) & 0x07e0) | + ( ((cte.blue) >> 3) & 0x001f) ; #ifdef CFG_INVERT_COLORS *cmap = 0xffff - colreg; ------------------------------------------------------------------- -- (single file) -- (single modification) -- ok for all boards -- modifications are at the minimum -- thinking that the memory footprint is affected in a reasonably way -- in order to respect the 40Kb size limit I'm not sending the very bitmap file Ciao Francesco Mandracci

2 1

[U-Boot-Users] how to modify u-boot to run in ram?
by zhuzhenhua 21 Sep '05

21 Sep '05

if i have a brom in chip which will load the u-boot to sdram and jump to run it,how to modify the lds file and gcc options to support it?

2 1

[U-Boot-Users] A question about the raminit in u-boot
by FCG WANG Baohua 21 Sep '05

21 Sep '05

Dear All: I have a question about the u-boot: I use a 128M board, the u-boot is OK, but when I changed the same config board, except the ram changed to 256M, it crashed when going into relocate_code() in board.c, and not going into board_init_r(), I had changed in mpc8260ADS.c initdram(), from 128 to 256, and changed the BR2 registers in mpc8260ADS.h. What's the other need to be changed? thanks!

2 1

[U-Boot-Users] mx21ads patch
by Livio Tenze 21 Sep '05

21 Sep '05

Hi all!! I am trying to use the mx21ads patch for the u-boot-1.1.3 but I have some problems in configuring the ethernet adapter cs8900: when I properly set the related definitions /* * CS8900 Ethernet drivers */ #define CONFIG_DRIVER_CS8900 1 /* we don't have a CS8900 on-board */ #define CS8900_BASE 0x15000300 #define CS8900_BUS16 1 /* the Linux driver does accesses as shorts */ an error occurs at the compile-time (unreferenced cs8900_get_enetaddr or something similar). How can I correctly set the ethernet adapter? May you help me? Thanks in advance! Livio

2 1

[U-Boot-Users] ssi.h file missing on uBoot 1.1.3
by garumuga＠sahasrasolutions.com 20 Sep '05

20 Sep '05

Hi, We had downloaded the uBoot 1.1.3 version on Linux kernel 2.6.11 running on Intel Pentium machine. While we were trying to compile the uBoot module with the target board as AMD, we are getting an error message stating that "ssi.h: No such file or directory" and the compilation fails. Can someone please let us know any possible solutions for overcoming this problem? Thanks Govind

2 1

[U-Boot-Users] Installing U-Boot on target via USB/serial using U-Boot commands
by Goswami Jigisha-ejg014 19 Sep '05

19 Sep '05

Hello, I want to find out if U-Boot can be installed on my new target (with no bootloader previously installed) via serial or USB interface using U-Boot commands? I read the U-Boot manual that- if no bootloader is previously installed on the target, a BDM or JTAG interface and can be used. However I want to find out if only U-Boot can be used to install itself over serial or USB interface. Can anyone help here? (I have disabled HTML but if it still appears, I apologize for that) Thanks in advance. Jigisha Goswami

3 3

[U-Boot-Users] How can ich configure xf86-emulator for PPC-440GX in u-boot?
by Roberto Pavon Sierra 19 Sep '05

19 Sep '05

Hi, can someone help me? i need to configurate on my custom board ppc440GX a x86 BIOS-emulator in u-boot to init a ATI Radeon M6 card, i know that the Amigaone board hat this function, but ich don´t know how can i configure it? Best Regards, Roberto Pavón

1 0

[U-Boot-Users] Large-page NAND support
by Hoda 19 Sep '05

19 Sep '05

Is there a version of the u-boot that has large-page NAND support? Thanks, Hoda

2 1

[U-Boot-Users] ATI Radeon M6-C16h for PPC 440GX
by Roberto Pavon Sierra 19 Sep '05

19 Sep '05

Hello, i´m using on my custom board with PPC 440GX a ATI M6 Mobility Radeon with kernel 2.6.12. Now i have to initialize the ati and configure the kernel to support it. I don´t have the BIOS of ATI for PPC and i like to simulate this BIOS with U-boot. How can i configure the U-boot for ATI to initialize or how can i write the programm for ATI- EEPROM BIOS? must i install a XF86-Simulator on my board? Roberto Pavon

2 1

[U-Boot-Users] Patch to cmd_eeprom.c
by Li, Aubrey 19 Sep '05

19 Sep '05

Dear Wolfgang, I have submitted a patch about cmd_eeprom.c, Could you please take a look and give me some suggestions? Thanks -Aubrey

2 1

[U-Boot-Users] Help about "Bad Magic Number" (XIP kernel is not booting)
by ravi.aloor＠wipro.com 19 Sep '05

19 Sep '05

Hello, I am working on ARMVersatile 926EJS application board. I am using NOR Flash with boot monitor. I am trying to boot kernel from the flash, as it is an XIP kernel. I have 3 doubts as explained below. Switch Settings: S1-1 to S1-8 Off S4-1 On and S4-2 to S4-4 Off After kernel configuration, .config file contains the following two CONFIG_ entries: CONFIG_XIP_KERNEL=y CONFIG_XIP_PHYS_ADDR=0x34060000 Doubt #1 -------- "The DENX U-Boot and Linux Guide (DULG) for TQM8xxL" document suggests to use CONFIG_XIP_VIRT_ADDR. But I didn't use CONFIG_XIP_VIRT_ADDR. Because I was asked to work with above two CONFIG_ entries only. CONFIG_XIP_VIRT_ADDR is really necessary? The areas and images available are as shown below on NOR flash: Flash> list areas Base Area Size Blocks Block Size ---- --------- ------ ---------- 0x34000000 64M 512 128K Flash> list images Flash Area Base 0x34000000 Address Name ------- ---- 0x34000000 boot_monitor.axf 0x34040000 u-boot 0x34060000 linux 0x341E0000 selftest.axf 0x34260000 cramfs 0x349E0000 symbian 0x356E0000 mmc2flash.axf Flash> Used mkimage utility and created kernel image as XiPImage.pcd. Details about XiPImage.pcd are as shown below. I also copied it to /tftpboot/ directory. I want to put XiPImage.pcd in the address range 0x34060000 and 0x341DFFFF. bash-3.00$ ../../../../../build/bin/mkimage -A arm -O Linux -T kernel -C none -a 0x34060000 -e 0x34060040 -n xipImage-2.6.10-pcd -d xipImage XiPImage.pcd Image Name: xipImage-2.6.10-pcd Created: Mon Sep 19 13:11:40 2005 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2175788 Bytes = 2124.79 kB = 2.07 MB Load Address: 0x34060000 Entry Point: 0x34060040 bash-3.00$ bash-3.00$ ../../../../../build/bin/mkimage -l XiPImage.pcd Image Name: xipImage-2.6.10-pcd Created: Sun Sep 18 19:20:09 2005 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2175788 Bytes = 2124.79 kB = 2.07 MB Load Address: 0x34060000 Entry Point: 0x34060040 bash-3.00$ cp XiPImage.pcd /tftpboot/ bash-3.00$ I erased linux range from 0x34060000 to 0x341DFFFF. Flash> erase range 0x34060000 0x341DFFFF Flash> run u-boot Versatile # setenv serverip 10.200.136.7 Versatile # setenv ipaddr 10.200.136.28 Versatile # setenv bootfile XiPImage.pcd Versatile # tftpboot Using MAC Address 00:02:F7:00:10:77 TFTP from server 10.200.136.7; our IP address is 10.200.136.28 Filename 'XiPImage.pcd'. Load address: 0x7fc0 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################### done Bytes transferred = 2175852 (21336c hex) Versatile # Versatile # iminfo ## Checking Image at 00007fc0 ... Image Name: xipImage-2.6.10-pcd Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2175788 Bytes = 2.1 MB Load Address: 34060000 Entry Point: 34060040 Verifying Checksum ... OK Versatile # I checked whether any image is already there at flash address 0x34060000 even after erasing. Versatile # iminfo 0x34060000 ## Checking Image at 34060000 ... Bad Magic Number Versatile # Doubt #2 -------- I got "Bad Magic Number". Means, nothing useful information is there. Am I right? I copied XIP kernel from SDRAM to flash address 0x34060000 Versatile # cp.b 0x7fc0 0x34060000 0x21336c Versatile # iminfo 0x34060000 ## Checking Image at 34060000 ... Bad Magic Number Versatile # Kernel uses NFS mounted root file system. Versatile # setenv bootargs root=/dev/nfs rw nfsroot=10.200.136.7:/wrlinux/testscheduler/stage/boards/arm-versatile2/ rootfs console=ttyAMA0 mem=128M ip=10.200.136.28:10.200.136.7::255.255.255.0:arm-versatile:eth0:off Versatile # bootm 0x34060000 ## Booting image at 34060000 ... Bad Magic Number Versatile # Doubt #3 -------- Kernel is not booting. Because of "Bad Magic Number". Suggestion please, what could be wrong? Thank you, Ravi

1 0

[U-Boot-Users] Issue regarding entry point address
by Swapnil Ashok Narkhede 18 Sep '05

18 Sep '05

Excerpts from previous posts Query > Using the uImage in RAM, when > i try to execute it using bootm from > the RAM. i get the following output > > o/p>>> > SWAP$ bootm 0xa0800000 ^^^^^^^^^^^^^^^^^^^^^^^^ > ## Booting image at a0800000 ... > Image Name: Linux Kernel Image > Image Type: ARM Linux Kernel Image (gzip compressed) > Data Size: 771905 Bytes = 753.8 kB > Load Address: a0800000 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Reply >>Download address and load address must differt at by least the size >> of the uncompressed kernel size. The difference between the compressed and uncompressed image is 40 bytes. So i tried to load the image at 0xa0800000 and tried to give entry point address as 0xa0800040 but then i get BAD MAGIC ERROR. Which means there is not proper image at that address (or rather, that is not the proper start of the image file). So how do i look up for the proper load address and entry point address. As per the CFG_LOAD_ADDR parameter in /include/configs/pxa255idp.h load address should be 0xa0800000 but how do i figure out,what is my entry point address. Please help me resolve this error. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

2 1

[U-Boot-Users] setenv handeling on OSK
by Carl Blair 17 Sep '05

17 Sep '05

Hi I am having similar problems with the osk to Jean-Marc 2005-09-14 01:38. I also used an = in setenv ie. setenv ipaddr=192.168.1.21. then I tried using tftpboot ie. tftpboot 0x10000000 u-boot.bin with u-boot.bin in the /tftpboot dir on the host.I get the error, ERROR 'ipaddr' not set I saw something about not using the = sign so I set the env variables again. All changed accordingly except ipaddr, which now has two entries. Still tftpboot does not work. I am going to use the flash recovery utility, but was wondering 1.) is this normal operation or is this just the factory installed u-boot operation? 2.) is there any way of removing environment variables? OMAP5912 OSK # printenv baudrate=115200 bootcmd=bootm 0x100000 bootfile=uImage bootdelay=10 ethaddr=00-0E-99-02-06-46 ipaddr=192.168.1.21 severip=0 ipaddr=192.168.1.11 stdin=serial stdout=serial stderr=serial netmask=255.255.254.0 serverip=192.168.1.6 bootargs=console=ttyS0,115200n8 noinitrd rw ip=off root=/dev/mtdblock4 mem=30 Any advice would be much appreciated :) _________________________________________________________________ Sell your car for $9 on carpoint.com.au http://www.carpoint.com.au/sellyourcar

2 1