MTD partitions

MTD partitions

[Tim Chen]

Hi,
I'm trying to add MTD NAND partitions to my OMAP850 based board.

I saw NAND partitions information in arch/arm/mach-omap1/board-h3.c,
But after some survey, I found *.c files in drivers/mtd/maps, there're
also files containing MTD partitions information.
What file should I add MTD partitions information to?
Files in arch/arm/mach-omap1/ or drivers/mtd/maps?

Thanks.

-- 
--
Regards,
Tim.

Re: MTD partitions

[David Brownell]

On Wednesday 12 March 2008, Tim Chen wrote:
> What file should I add MTD partitions information to?
> Files in arch/arm/mach-omap1/ or drivers/mtd/maps?

Platform data in .../mach-omap1/board-$(MYBOARD).c should
give default partition data to the relevant NAND driver.

- Dave

Re: MTD partitions

[Tim Chen]

Thanks, David,
I added the MTD partition information to board-($MYBOARD).c,
But kernel didn't show any MTD partition information during booting.
If I have to create the MTD partitions using MTD commands in u-boot first?
My u-boot is old, no MTD support, if that's the case, I'll port the
newer u-boot, then try again.
Thanks.

On Wed, Mar 12, 2008 at 6:16 PM, David Brownell <david-b@pacbell.net> wrote:
> On Wednesday 12 March 2008, Tim Chen wrote:
>  > What file should I add MTD partitions information to?
>  > Files in arch/arm/mach-omap1/ or drivers/mtd/maps?
>
>  Platform data in .../mach-omap1/board-$(MYBOARD).c should
>  give default partition data to the relevant NAND driver.
>
>  - Dave
>
>



-- 
--
Regards,
Tim.

Re: MTD partitions

[Tim Chen]

Hi David,
Solved,
Finally, I checked out a new GIT tree, the previous I used is
linux-2.6.23-rc3-omap1(might be quite old).
As you said, I modified the board-(MYBOARD).c file.

Also, The NAND flash part is  the Samsung K5E1212ACB MCP(64MB NAND
flash/64MB DDR), as the IDs shown below,

NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit
)
Scanning device for bad blocks
Bad eraseblock 753 at 0x00bc4000
Bad eraseblock 1007 at 0x00fbc000
Bad eraseblock 1112 at 0x01160000
Bad eraseblock 1281 at 0x01404000
Bad eraseblock 1948 at 0x01e70000
Bad eraseblock 2158 at 0x021b8000
Bad eraseblock 2328 at 0x02460000
Bad eraseblock 2941 at 0x02df4000
Creating 5 MTD partitions on "omapnand.0":
0x00000000-0x00010000 : "xloader"
mtd: Giving out device 0 to xloader
0x00010000-0x00050000 : "bootloader"
mtd: Giving out device 1 to bootloader
0x00050000-0x00080000 : "params"
mtd: Giving out device 2 to params
0x00080000-0x00280000 : "kernel"
mtd: Giving out device 3 to kernel
0x00280000-0x04000000 : "filesystem"
mtd: Giving out device 4 to filesystem


On Thu, Mar 13, 2008 at 12:19 PM, David Brownell <david-b@pacbell.net> wrote:
> On Wednesday 12 March 2008, you wrote:
>  > I added the MTD partition information to board-($MYBOARD).c,
>  > But kernel didn't show any MTD partition information during booting.
>
>  That means you didn't connect something correctly.  Is the right
>  platform device present?  Is its driver loaded?  Is it successfully
>  probing?  Did you enable partitions?  You can enable MTD debug to
>  see most of that.
>
>
>
>  > If I have to create the MTD partitions using MTD commands in u-boot first?
>  > My u-boot is old, no MTD support, if that's the case, I'll port the newer
>  > u-boot, then try again.
>
>  That would only matter if you're trying to boot from e.g. a JFFS2
>  partition using u-boot.  Or, depending on what you mean, load the
>  kernel from flash.
>
>  What you need to do first is make sure that the kernel sees the
>  flash chip, and then make sure the partition info is used.
>
>
>
>



-- 
--
Regards,
Tim.