MTD Partitioning does not work.

Sorry for Crossposting but i think it better fits here.

Hello,

i have compiled a 3.1.5 Kernel for a TQM5200 Board.
But what i missed is the correct partitioning of the flash after the boot. Do i have to use another way as with Kernel 2.4.25?

With Kernel 2.4.25 i define the cmdline like:

Kernel command line: root=/dev/ram rw mtdparts=TQM5200-0:512k(u-boot),512k(env),2m(kernel),16m(ramfs1),5m(ramfs2),8m(jffs2) ip=192.168.0.50:192.168.0.133:::tqm5200:eth0:off panic=1 console=ttyS0,115200

=> Partitioning no Problem.

Following some informations of my Setup.

My actual U-Boot Parameters for mtdpart:

mtdids=nor0=TQM5200-0 mtdparts=mtdparts=TQM5200-0:512k(u- \
boot),512k(env),2m(kernel),16m(ramfs1),5m(ramfs2),8m(jffs2)

Output in U-Boot:

=> mtdpart

device nor0 <TQM5200-0>, # parts = 6
#: name size offset mask_flags

  0: u-boot              0x00080000    0x00000000    0
  1: env                 0x00080000    0x00080000    0
  2: kernel              0x00200000    0x00100000    0
  3: ramfs1              0x01000000    0x00300000    0
  4: ramfs2              0x00500000    0x01300000    0
  5: jffs2               0x00800000    0x01800000    0

active partition: nor0,0 - (u-boot) 0x00080000 @ 0x00000000

defaults:
mtdids : nor0=TQM5200-0
mtdparts:
mtdparts=TQM5200-0:512k(u-boot),512k(env),2m(kernel),16m(ramfs1),5m(ramfs2),8m(jffs2) =>

My Kernelconfig Section MTD:

CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_TESTS is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_OF_PARTS=y
# CONFIG_MTD_AR7_PARTS is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
CONFIG_MTD_ROM=y
# CONFIG_MTD_ABSENT is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PHYSMAP is not set
CONFIG_MTD_PHYSMAP_OF=y
# CONFIG_MTD_PLATRAM is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
# CONFIG_MTD_NAND is not set
# CONFIG_MTD_ONENAND is not set

#
# LPDDR flash memory drivers
#
# CONFIG_MTD_LPDDR is not set
# CONFIG_MTD_UBI is not set

Thanks in advance

Axel Beierlein

Dear Axel Beierlein,

No, you are off topic here. This is a Linux issue only.

U-Boot can just pass the boot arguments; the rest is a Linux thing.

Check your kernel boot messages if the name of the flash device is
really "TQM5200-0"; this is probably wrong. I guess it's more
something like "fc000000.flash" or so.

Best regards,

Wolfgang Denk

DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"God is a comedian playing to an audience too afraid to laugh."
- Voltaire