Project

General

Profile

No unzip in MityArm uboot?

Added by Anonymous over 11 years ago

Hi,

We are running the critical link u-boot version(below) on the MityArm and it appears that there is not a unzip command available. The reason we need it is that the StarterWare image we are running is over 3Mbytes in size and we need to reduce it. We were testing the bootm command with a uncompressed StarterWare image that had the mkimage run on it (the checksum ran correctly, but it would hang when it went to execute it.) 
Is the u-boot image to old to have unzip in it or is there a known problem in running bootm from this version?

Thanks,
John Conover

U-Boot 2011.09-00000-g045cda5 (Jul 12 2012 - 16:03:00)
arm-arago-linux-gnueabi-gcc (GCC) 4.5.3 20110311 (prerelease)
GNU ld (GNU Binutils) 2.20.1.20100303


Replies (4)

RE: No unzip in MityArm uboot? - Added by Michael Williamson over 11 years ago

You will probably need to rebuild it and enable the optioncommand by adding a CMD_XXX (CMD_ZIP? would need to check) to the board header file.

Many options / features of u-boot may not be enabled in our default u-boot application in order to keep the image size under control.

-Mike

RE: No unzip in MityArm uboot? - Added by Anonymous over 11 years ago

Where is the board header file?

Thanks,
John C.

RE: No unzip in MityArm uboot? - Added by Jonathan Cormier over 11 years ago

In the file include/configs/mityarm335x.h you need to insert

#define CONFIG_CMD_UNZIP

RE: No unzip in MityArm uboot? - Added by Anonymous over 11 years ago

Thanks Jonathan,

I added #define CONFIG_CMD_UNZIP to the file, rebuilt u-boot and burned it into NAND. So I was able to do the following 
from a u-boot prompt and our application runs:

mw.b 0x8C100000 0x00 2E274
sf probe 0:0
sf read 8C100000 410000 2E274
unzip 8c100040 80000000
-----Uncompressed size: 3595909 = 0x36DE85
go 80000000

Our only problem with this is that we still have to CRC manually when if we could use bootm, it would be automatic.
When we tried bootm on the same image we get the following output, but it just hangs after that:
mw.b 0x8C100000 0x00 2E274
sf probe 0:0
sf read 8C100000 410000 2E274
U-Boot# bootm 8c100000
  1. Booting kernel from Legacy Image at 8c100000 ...
    Image Name: AIRtrac image
    Image Type: ARM U-Boot Standalone Program (gzip compressed)
    Data Size: 188980 Bytes = 184.6 KiB
    Load Address: 80000000
    Entry Point: 80000000
    Verifying Checksum ... OK
    Uncompressing Standalone Program ... OK
Is there anything obvious we are doing that looks incorrect? The mkimage is very straight forward.

mkimage -A arm -O u-boot -T standalone -C gzip -a 0x80000000 -e 0x80000000 -n "AIRtrac image" -d AIRtracEmbedded.bin.gz airtrac.img

Any help is greatly appreciated,
John C.

    (1-4/4)
    Go to top
    Add picture from clipboard (Maximum size: 1 GB)