From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot & MonteJade start up
Date: Wed, 2 May 2007 07:16:39 +0200 [thread overview]
Message-ID: <200705020716.39394.sr@denx.de> (raw)
In-Reply-To: <7EDC24AB1ED682439657D3B7790609D390D7A2@deepthought.Elpro.local>
On Wednesday 02 May 2007 06:39, Jonathan Pratt wrote:
> I'm trying to get u-boot up and running on an Intel MonteJade (IXDPG425)
> board without much luck.
>
> I downloaded version 2.0 of the Npe code and placed it in the
> appropriate directory and the build worked fine. Getting it up and
> running on the board has proved more difficulat.
>
> I'm using a Macraigor USB wiggler to download to the FLASH. If anyone
> has done this successfully then I would appreciate some pointers as I'm
> not sure what I've done thus far is correct.
>
> As far as I understand it, the xscale starts up in little endian mode.
> The application is, however, big-endian. When I program the FLASH it
> appears to be big-endian, and I don't as yet understand where the
> transition from little endian occurs. The u-boot code in the current
> state doesn't go anywhere with no response from the serial port.
>
> Is there some pre-bootloader code which does the transition to
> big-endian?
No.
> If so, do I need to program this sepeartely? If not, where
> does the transition to big-endian occur and why does the code I see (in
> the srec file, for example) appear to start off big-endian?
Because it's compiled to be in big endian format. All IXP4xx U-Boot & Linux
implementations I know of are done in big endian mode.
> I can
> imagine ld getting pretty confused trying to link a little-endian
> snippet to a big-endian application.
I have to admit, that I don't know right now, where this big endian/little
endian change is made. Perhaps some boot-strapping pin? Not sure, would have
to look in the manual. Martijn? Could you jump in here?
For the 2 IXP4xx boards I used (ixdpg425 and pdnb3) I can say, that they "just
work" with the current U-Boot implementation in big endian mode. And here
definitely no pre-bootloader is required.
What exactly is your problem? Can you see where the U-Boot hangs with you
debugger? You are aware that the IXDPG425 port uses UART1 (and not UART0) for
console with 115200 baud.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
next prev parent reply other threads:[~2007-05-02 5:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 4:39 [U-Boot-Users] U-boot & MonteJade start up Jonathan Pratt
2007-05-02 5:16 ` Stefan Roese [this message]
2007-05-02 6:22 ` Jonathan Pratt
2007-05-09 7:17 ` [U-Boot-Users] IXP425 ethernet & NPE microcode Jonathan Pratt
2007-05-09 9:16 ` Eric BENARD
2007-05-09 9:52 ` Stefan Roese
2007-05-09 20:32 ` Jonathan Pratt
2007-05-09 22:37 ` Wolfgang Denk
2007-05-09 22:55 ` Jonathan Pratt
2007-05-09 23:16 ` David Hawkins
2007-05-10 1:50 ` Jonathan Pratt
2007-05-10 5:16 ` Stefan Roese
2007-05-10 9:04 ` Øyvind Repvik
2007-05-10 11:25 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2007-05-02 9:07 [U-Boot-Users] U-boot & MonteJade start up Martijn de Gouw
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=200705020716.39394.sr@denx.de \
--to=sr@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox