[U-Boot-Users] PQ2FADS-ZU, was Code Warrior 8.14 + WireTAP + U-boot bootloader image ( Arabella 2 .0 C D-ROM "Linux for Motorola 82xx")

[VanBaren, Gerald (AGRE)]

> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net]On Behalf Of Alex
> Povolotsky
> Sent: Tuesday, September 07, 2004 1:00 PM
> To: wd at denx.de
> Cc: u-boot-users at lists.sourceforge.net
> Subject: [U-Boot-Users] Re: Code Warrior 8.14 + WireTAP + U-boot
> bootloader image ( Arabella 2 .0 C D-ROM "Linux for Motorola 82xx")
>
>
>
> Wolfgang,
>
> Your recommendation was well noted but at this point I want
> to avoid using u-boot image, compiled by myself from the source.
> At this point I want to use the "tried"/"tested" bootloader
> In my opinion, my question re usability of the u-boot
> bootloader images provided on the Arabella 2.0 CD-ROM "Linux
> for Motorola 82xx" is still worth to be asked/answered - this
> cdrom is "packaged" by the Freescale, when they ship the
> brand new board. Also FreeScale "packages" Code Warrior 8.14
> (with one month evaluation license) + WireTAP probe into the
> shipment.
>
> Do you yourself have the PQ2FADS_VR 66 MHz board (with the
> MPC8275 processor) by any chance (as well as Arabella 2.0
> CD-ROM "Linux for Motorola 82xx" ?) ?
>
> Thanks
> Alex,
>
> in message
> <20040907.084113.509.485968 at webmail14.lax.untd.com> you wrote:
> >
> >
> > Did any one on this list used elf bootloader for PQ2FADS_VR
> > 66 MHz board (with the MPC8275 processor) provided on the
> > Arabella 2.0 CD-ROM "Linux for Motorola 82xx" ?
>
> I already replied to your question on the etux  mailing  list.  There
> was  no  need to repost the very same question here. My hinto to post
> on u-boot-users was intended for _new_ questions.
>
> > While the programming of the flash seemingly completed without
> > errors -  however the resulted bootloader is not functional ... -
>
> I repeat my recommendation:
>
> Use the latest version of U-Boot (top of CVS tree).
> See http://sourceforge.net/projects/u-boot and
> http://www.denx.de/twiki/bin/view/DULG/Manual
>
> Best regards,
>
> Wolfgang Denk


I'm not answering the questions that were asked, but I figured a testimonial wouldn't hurt:

My configuration:
* PQ2FADS-ZU with a MPC8260
* BDI2000, MPC8280 configuration downloaded from denx.de
  * Remaps the IMMR from 0x0F000000 to 0xF0000000
  * Initializes SDRAM
* U-boot build top of the u-boot CVS tree (synced the week of 2004-09-12, I don't remember the exact date).

I had to change the BDI2000 JTAG clocking to 8MHz (JTAGCLOCK 1) from the default 16MHz (JTAGCLOCK 0) before the flash would program reliably.  With the 16MHz clock it would only program 1K+ and then have an error.

The board is booting with the (default) BCSR-supplied HRCW ((IMMR = 0x0F000000) == yech).  I cannot boot it with the BDI2000 plugged in, probably due to the HRCW.  If the BDI2000 is plugged in, u-boot starts to run and then the BDI2000 gets unhappy and resets the board.

ToDo:
* Change the J7 jumper to use flash for the HRCW
* Reconfigure u-boot to boot low (preferred configuration)
* Reconfigure the BDI2000 to...
  * Not move the IMMR (not necessary or desired with a flash HRCW)
  * Remove the SDRAM initialization (SDRAM init is poor practice)
* Get ethernet configured and running...
* Boot linux!

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.
******************************************