解决“向FLASH烧写cramfs文件系统出错：Image not a multiple of 528 bytes

向FLASH烧写cramfs文件系统出错：
vivi> net flash root
Found block size = 0x006fc000
Erasing... ... done
Writing... Image not a multiple of 528 bytes
... failed
retlen = 7319552, ret = -1

方法：

 

要烧cramfs文件系统必需把分区的flag改为0

先删除root分区

part del root

再重新创建root分区,flag设置为0

part add root 0x200000 0x200000 0 (红色的为flag)

 

 

 

A load command is loading binaries to the flash or the ram.

Usage:

load <media_type> [ <partname> | <addr> <size> ] <x|y|z>

<media_type>

    This argument is where to load. Availabe values are *flash* and *ram*.

[ <partname> ] or [ <addr> <size> ]

    This arguement determines location where to load a binary. If you
    want to use pre-defined mtd partiton informations, just type a
    partition name. Otherwise you specify an address and a size.

<x|y|z>

    This arguement determines the file transfer protocol. I shy that the
    vivi only supprot xmodem curruntly. So, Available value is "x".

For exampe, you load zImage to flash memroy.

vivi > load flash kernel x

or you specify an address and a size.

vivi > load flash 0x80000 0xc0000 x

 

      3.2.2. part command

The vivi has mtd partiton informations for the vivi. This informatin not
related to mtd partition informations of mtd device drivers. The vivi
uses partition informations when load a binary, boot the linux kernel,
erase flash memroy, etc...

Avalilable commands are:

Display mtd partition informations.

part show

Add a new mtd partition.

part add <name> <offset> <size> <flag>

<name>

    is name of a new mtd partiton.

<offset>

    is offset in the mtd device.

<size>

    is a size of a mtd parition.

<flag>

    is flags of a mtd parition. Available valuse are JFFS2, LOCKED,
    and BONFS.

Delete a mtd partiton.

part del <partname>

Reset mtd partitions to default values.

part reset

Save paramter valuse and mtd parition informations to flash permanently.

part save

 

      3.2.3. param command

The vivi has some parameter values. For example, the "boot_delay"
paramter determines how long wait keystroek when the vivi is in the
autoboot mode. I'm sorry that this feature is in progress. So all listed
parameter is not available.

Here, I give several tips for you.

If you change the "linxu command line",

vivi> param set linux_cmd_line "you wish.."

If you want to see paramters,

vivi> param show

If you want to wait a long time when recevie file via xmodem,

vivi> param set xmodem_initial_timeout 3000000

If you want to boot imediately when a hardware reset,

vivi> param set boot_delay 100000

 

      3.2.4. boot command

A boot command is boot the linux kernel which is stored in the flash
memroy or ram. Usage:

boot <media_type> [ <partname> | <addr> <size> ]

<media_type>

    This argument is where to store the linux kernel image. Availabe
    values are ram, nor and smc.

[ <partname> ] or [ <addr> <size> ]

    This arguement determines location where to store the linux kernel.
    If you want to use pre-defined mtd partiton information, just type a
    partition name. Otherwise you shuld specify an address and a size.

Note that all argument is optional. If you omit all argument (just type
boot), all arguments is parsing from pre-defined mtd parititon
information called "kernel" For example,

vivi> boot

the vivi read the linux kernel binary from the "kernel" mtd parititons.

vivi> boot nor 0x80000

the vivi read the linux kernel binary form the nor flash memory. the
offset is 0x80000 and the size is default value (0xc0000).

Ocassionally, you want to test the kernel on the ram (not store kernel
to flash). you can do it on the vivi On the SA-1110 based machine,

vivi> load ram 0xc0008000 x
vivi> boot ram

On the S3C2410 based machine,

vivi> load ram 0x30008000 x
vivi> boot ram

On the PXA-240 based machine,

vivi> load ram 0xA0008000 x
vivi> boot ram

the vivi boot the linux kernel from the ram.

 

      3.2.5. flash command

A flash comamnd manages the flash memory. If you want to erase flash
memory,

flash erase [ <partname> | <offset> <size> ]