public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot] Missing mtd device
@ 2012-05-23  9:57 Michael Moller
  2012-05-23 11:19 ` Wolfgang Denk
  2012-05-23 12:11 ` Gary Thomas
  0 siblings, 2 replies; 3+ messages in thread
From: Michael Moller @ 2012-05-23  9:57 UTC (permalink / raw)
  To: u-boot

Hi u-booters

I'm at my wit's end.  I really hope you can help.

I have tried updating the u-boot on a Davinci DM365 based board using
various versions of u-boot, including the latest from the git
repository.

After setting CROSS_COMPILE and configuring with
"make davinci_dm365evm_config", everything builds perfectly.

I then install TI's UBL and u-boot.bin to a Micron NAND flash
(MT29F16G08) using TI's sfh_DM36x.exe flashing utility. I set up the
u-boot environment and boot the kernel, which I compiled from TI's
DVSDK.

Everything boots up fine, except for access to the /dev/mtd? devices.
Also /proc/mtd exists but is empty of devices - it should show the
partitions of the flash chip. Further investigation reveals that the
davinci_nand driver simply returns from platform_driver_probe() with a
ENODEV "No such device" error.

What is the device that is missing, and why does it go missing when I
boot with this u-boot?  What makes some versions of u-boot activate this
device in the kernel and others not?  What is the mechanism by which
u-boot can do such a thing? It seems to be something other than simple
kernel command line parameters. How do I begin even looking for this
problem?

I hope you can help. Any pointers would be greatly appreciated.

Kind regards
Michael

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] Missing mtd device
  2012-05-23  9:57 [U-Boot] Missing mtd device Michael Moller
@ 2012-05-23 11:19 ` Wolfgang Denk
  2012-05-23 12:11 ` Gary Thomas
  1 sibling, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2012-05-23 11:19 UTC (permalink / raw)
  To: u-boot

Dear Michael Moller,

In message <1337767068.7635.38.camel@mmoller-desktop> you wrote:
> 
> Everything boots up fine, except for access to the /dev/mtd? devices.
> Also /proc/mtd exists but is empty of devices - it should show the
> partitions of the flash chip. Further investigation reveals that the
> davinci_nand driver simply returns from platform_driver_probe() with a
> ENODEV "No such device" error.

Sorry, but you are off topic here.  We can try to help with U-Boot
related questions, but this is Linux land.

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
Microsoft Multitasking:
                     several applications can crash at the same time.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] Missing mtd device
  2012-05-23  9:57 [U-Boot] Missing mtd device Michael Moller
  2012-05-23 11:19 ` Wolfgang Denk
@ 2012-05-23 12:11 ` Gary Thomas
  1 sibling, 0 replies; 3+ messages in thread
From: Gary Thomas @ 2012-05-23 12:11 UTC (permalink / raw)
  To: u-boot

On 2012-05-23 03:57, Michael Moller wrote:
> Hi u-booters
>
> I'm at my wit's end.  I really hope you can help.
>
> I have tried updating the u-boot on a Davinci DM365 based board using
> various versions of u-boot, including the latest from the git
> repository.
>
> After setting CROSS_COMPILE and configuring with
> "make davinci_dm365evm_config", everything builds perfectly.
>
> I then install TI's UBL and u-boot.bin to a Micron NAND flash
> (MT29F16G08) using TI's sfh_DM36x.exe flashing utility. I set up the
> u-boot environment and boot the kernel, which I compiled from TI's
> DVSDK.
>
> Everything boots up fine, except for access to the /dev/mtd? devices.
> Also /proc/mtd exists but is empty of devices - it should show the
> partitions of the flash chip. Further investigation reveals that the
> davinci_nand driver simply returns from platform_driver_probe() with a
> ENODEV "No such device" error.
>
> What is the device that is missing, and why does it go missing when I
> boot with this u-boot?  What makes some versions of u-boot activate this
> device in the kernel and others not?  What is the mechanism by which
> u-boot can do such a thing? It seems to be something other than simple
> kernel command line parameters. How do I begin even looking for this
> problem?
>
> I hope you can help. Any pointers would be greatly appreciated.

To be clear - you have used other versions of U-Boot on this board
that do properly report the NAND device?  If so, what version and
where did you get it?

I'd suspect that your board configuration is not causing the NAND
PINMUX to be set up correctly, hence Linux can't talk to the device.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-05-23 12:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-23  9:57 [U-Boot] Missing mtd device Michael Moller
2012-05-23 11:19 ` Wolfgang Denk
2012-05-23 12:11 ` Gary Thomas

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox