-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Wolfgang Denk Sent: Friday, December 03, 2004 2:43 AM To: duo dong Cc: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] Questions of uImage on sbc8260 board

In message 20041203054507.79341.qmail@web54404.mail.yahoo.com you wrote:

...

The uImage is loaded onto RAM of sbc8260/ATM board. After starting the uImage, the msg shows:

[snip]

OK, so we finally got some U-Boot stuff here, and you are not completely off topic ;-)

...

Q1. Can the uImage build by using TQM8260_config can be used on sbc8260 board? If can not, which config I should use?

Of course you can build an uImage using the TQM8260 configuration. But this uImage will only be useful for TQM8260 boards. You must not assume that it might run on any other hardware.

Best regards,

Wolfgang Denk

Just to be totally complete, there is a sbc8260 target for u-boot, has been for years and works fine. A quick google search and eyeballing of the WindRiver brochure gives me the impression that the sbc8260 ATM board is a respin of the sbc8260 board with the ATM PHYs on-board (looks like the same memory configuration -- that is a biggie for getting u-boot running initially). I'm guessing that the sbc8260 target would be a MUCH better starting point than the TQM8260.

gvb

****************************************** The following messages are brought to you by the Lawyers' League of IdioSpeak:

****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************