From: Ian Jeffray <ijeffray@a2etech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] EMAC failure and SPI support for TI DaVinci DM365
Date: Tue, 23 Feb 2010 14:59:02 +0000 [thread overview]
Message-ID: <4B83ED36.6060207@a2etech.com> (raw)
Hi guys,
This question may be mostly directed to Sandeep Paulraj, the TI
tree maintainer, but is also observed in the mainline...
I've had great success with U-Boot on many ADI BF5xx devices, but I'm
having considerably less fun with the TI DM365.
I've a DM365EVM board - the stock U-Boot binary from the PSP 3.10
distribution from TI works ok, but has no SPI ('sf') support, so I
need to build that in for starters (ultimately we're designing a
custom board with only SPI flash - no NAND).
My problem is that even building the 2009.11 release, the current
mainline revision (ie 2010.02 prerelease), or the u-boot-ti mainline,
the EMAC fails and instantly reboots the board... with no mods made
to U-Boot... just a build out of the box fails this way:
git clone git://git.denx.de/u-boot-ti.git
cd u-boot-ti
make davinci_dm365evm_config
make
...then flash on to my board using the sfh_DM36x.exe utility with the
UBL from the PSP 3.10 distribution... and boot up...
> DM36x initialization passed!
> TI UBL Version: 1.50
> Booting Catalog Boot Loader
> BootMode = NAND
> Starting NAND Copy...
> Valid magicnum, 0xA1ACED66, found in block 0x0000001A.
> DONE
> Jumping to entry point at 0x81080000.
>
> U-Boot 2009.11-00988-g2a6e256 (Feb 23 2010 - 13:50:13)
>
> I2C: ready
> DRAM: 128 MB
> NAND: 2048 MiB
> (snipped out lots of nand BBT details here from this email)
> *** Warning - bad CRC or NAND, using default environment
>
> Net:
> Hit any key to stop autoboot: 0
> DM365 EVM # dhcp
> DM36x initialization passed!
> TI UBL Version: 1.50
> Booting Catalog Boot Loader
As you can see, as soon as I "dhcp", the board is rebooting. The same
happens if I set "ipaddr" and "netmask" then attempt a tftp or ping.
My expectation was that this stuff would work fine out of the box and
clearly isn't for me -- I hope this is just something I'm doing wrong
here and that someone is able to confirm that the code's kosher and
maybe pointers as to what I could have done wrong?
I do notice that the "Net: " line above has no further detail, wheras
the TI PSP binary version says "Ethernet PHY: GENERIC @ 0x00"
(I've not managed to get a 2009.03 build of my own to run on DM365
to compare yet... that's the version TI supplied as binary somehow)
My second question is about the DaVinci SPI flash support in U-Boot.
I've replaced the 64K SPI flash on the DM365EVM with a larger part,
which works just fine from my self-build Linux kernel, so I know the
device itself is fine. All attempts to utilise this from U-Boot
are failing. I realise the SPI DaVinci SPI flash driver is rather
new - wondering what the expectations of this driver are in terms of
stability and testing?
Many thanks for all the great work by everyone on the U-Boot project;
It's certainly been an invaluable asset for us on Blackfin and I hope
we'll be able to get it playing nicely on DaVinci too!
Thanks,
Ian.
next reply other threads:[~2010-02-23 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 14:59 Ian Jeffray [this message]
2010-02-23 20:14 ` [U-Boot] EMAC failure and SPI support for TI DaVinci DM365 Paulraj, Sandeep
2010-02-23 21:19 ` Ian Jeffray
2010-02-24 9:20 ` Nick Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B83ED36.6060207@a2etech.com \
--to=ijeffray@a2etech.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.