RE: [U-Boot-Users] quick gzip question/issue.

Robin,
I am assuming that you are using uClinux with 'romfs' as your rootfilesystem. If this is the case, you should create your 'uImage' with 'image.bin' and not 'linux.bin'. The 'linux.bin' is just the kernel and does not include the romfs image in it.Also noticed that u have given "root=/dev/mtdblock" as kernel command. Are you placing your 'romfs' image at that address ? Another point of note is your Flash memory space, which Iis just 4MB. I am assuming you are 'bootm' ing your image from Flash address.Is your uImage size bigger than that by any chance ?
-- Rupesh S
Robin Getz rgetz@blackfin.uclinux.org 04/15/05 04:21PM >>>
Wolfgang:
Sorry - I was not trying to make a bug report - just ask a quick question if anyone else had seen any issues with large (5.5Meg binary images) being turned into large (3Meg) gzip files.
Here is the full description (sorry for the previous typo):
make a kernel that includes a large file in the romfs (we are using mp3 file - so it is fairly uncompressible - not sure if this is the issue or not). When this mp3 is not included the romfs, uImages (and bootm) continue work OK.
to make the bin: bfin-elf-objcopy -O binary linux linux.bin
to creat the gzip: gzip -9 linux.bin
to create the uImage: (WORK_DIR)/u-boot_1.1.3/tools/mkimage -A Blackfin -O Linux -T kernel -C gzip -a 0x1000 -e 0x1000 -n "Bfin uClinux Kernel" -d linux.bin.gz uImage
I have three files linux (elf file) linux.bin (binary) and uImage (compressed)
CPU: ADSP BF533 Rev.: 0.3 Board: ADI BF533 Stamp board Support: http://blackfin.uclinux.org/ Richard Klingler richard@uclinux.net Clock: VCO: 497 MHz, Core: 497 MHz, System: 124 MHz SDRAM: 128 MB FLASH: 4 MB In: serial Out: serial Err: serial Net: SMC91111 at 0x20300300 I2C: ready Hit any key to stop autoboot: 0 ## Booting image at 20100000 ... Image Name: Blackfin Audio Created: 2005-04-12 19:53:31 UTC Image Type: Blackfin Linux Kernel Image (gzip compressed) Data Size: 2973852 Bytes = 2.8 MB Load Address: 00001000 Entry Point: 00001000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting Kernel at = 1000 Linux version 2.6.8.1 (dskocyp@linux) (gcc version 3.4.1) #2 Tue Apr 12 14:40:24 EDT 2005 Blackfin support (C) 2004 Analog Devices, Inc. ADSP-BF533 Rev. 0.3 uClinux/BF533 Blackfin uClinux support by LG Soft India (www.lgsoftindia.com Processor Speed: 497 MHz core clock and 124 Mhz System Clock Board Memory: 128MB Memory map: text = 0x001000-0x0d5bb4 data = 0x0e0364-0x1034b0 bss = 0x1034b0-0x112320 rootfs = 0x112320-0x5f5000 stack = 0x0e2000-0x0e4000 Command line: 'root=/dev/mtdblock0 rw' Instruction Cache Enabled Data Cache Enabled Built 1 zonelists Kernel command line: root=/dev/mtdblock0 rw Configuring Blackfin Priority Driven Interrupts PID hash table entries: 16 (order 4: 128 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Physical pages: 8000 Memory available: 123552k/130175k RAM, (40k init code, 850k kernel code, 199k data) Blackfin Scratchpad data SRAM: 4 KB Blackfin DATA_A SRAM: 16 KB Calibrating delay loop... 78.43 BogoMIPS Security Scaffold v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 (order: 0, 4096 bytes) NET: Registered protocol family 16 Blackfin DMA Controller for BF533 stamp_init registe the device resurce to system. Real Time Clock Driver v1.10e blackfin_dpmc_init Dynamic Power Management Controller: major=10, minor = 254 DPMC Driver v0.1 BlackFin BF533 serial driver version 2.00 With DMA Support ttyS0 at irq = 21 is a builtin BlackFin BF533 UART Enabling Serial UART Interrupts RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize EBIU Asynchronous memory setup. smc91x.c: v1.0, mar 07 2003 by Nicolas Pitre nico@cam.org EZ-LAN interrupt setup. eth0: SMC91C11xFD (rev 1) at 0x20300300 IRQ 27 [nowait] eth0: Ethernet addr: 00:e0:22:fe:01:0a Using cfq io scheduler uclinux[mtd]: RAM probe address=0x112320 size=0x7d0000 Creating 1 MTD partitions on "RAM": 0x00000000-0x007d0000 : "EXT2fs" uclinux[mtd]: set EXT2fs to be root filesystem Advanced Linux Sound Architecture Driver Version 1.0.4 (Mon May 17 14:31:44 2004 UTC). enable_irq(20) unbalanced from 000ddada enable_irq(12) unbalanced from 000ddae0 sport: ffc00800 dma rx: ffc00c40 tx: ffc00c80 enable_irq(10) unbalanced from 000ddb44 set register 13 to 0xd180 set register 0 to 0x0000 set register 12 to 0xc000 set register 2 to 0x23ff set register 3 to 0x33ff set register 4 to 0x43ff set register 5 to 0x53ff set register 6 to 0x63ff set register 7 to 0x73ff sport: bf53x_sport_set_multichannel( tdm_count=8 packed=1 ) sport: bf53x_sport_config_rx_dma( 00110320, 2, 32, 0x11 ) sport: bf53x_sport_config_tx_dma( 00110360, 2, 32, 0x11 ) channel masks set to 0123 = { 11 33 77 ff } ALSA device list: #0: Analog Devices AD1836A at SPI irq 20/12, SPORT0 rx/tx dma 1/2 irq 16/17/10 NET: Registered protocol family 2 IP: routing cache hash table of 1024 buckets, 8Kbytes TCP: Hash tables configured (established 8192 bind 16384) NET: Registered protocol family 1 NET: Registered protocol family 17 VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 40k freed (0xd6000 - 0xdf000) EXT2-fs error (device mtdblock0): ext2_check_page: bad entry in directory #173: rec_len is too small for name_len - offset6 Warning: unable to open an initial console. EXT2-fs error (device mtdblock0): ext2_check_page: bad entry in directory #174: unaligned directory entry - offset=0, inod1 Kernel panic: Attempted to kill init!
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

In message s264e329.041@EMAIL you wrote:
I am assuming that you are using uClinux with 'romfs' as your rootfilesystem. If this is the case, you should create your 'uImage' with 'image.bin' and not 'linux.bin'. The 'linux.bin' is just the kernel and does not include the romfs image in it.Also noticed that u have given "root=/dev/mtdblock"
And this is what is intended. It is one of the design goals of U-Boot to get rid of the need to bundle the Linux kernel and the root file system into one image.
Best regards,
Wolfgang Denk
participants (2)
-
Rupesh S
-
Wolfgang Denk