Hello David

I try the mac file
http://casper.berkeley.edu/svn/trunk/roach/production/test_software/roach_testing/macraigor_macros/loadram_rinit_auto.mac
it works.
But the ROACH can't complete the whole uboot process.
The screen only shows the message as follows:
---------------------------------------------------------------------------------------------------
U-Boot 2008.10-svn2226 (Aug  7 2009 - 16:06:44)

CPU:   AMCC PowerPC 440EPx Rev. A at 660 MHz (PLB=165, OPB=82, EBC=82 MHz)
      No Security/Kasumi support
      Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
      32 kB I-Cache 32 kB D-Cache
Board: Roach
I2C:   ready
DTT:   1 is 30 C
DRAM:  (spd v1.2)  1 GB
---------------------------------------------------------------------------------------
What's happened?

Regards C-H Cheng



----- Original Message ----- From: "David George" <[email protected]>
To: "C-H Cheng" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, September 16, 2009 6:31 PM
Subject: Re: [casper] PowerPC U-Boot Configuration


Hi.
Hello
I had erased/corrupted the flash memory during updating and I used OCD
commander to program PPC's uboot over USBWiggler. Of course I had the
macro(program.mac), too.
I follow the web page:
http://casper.berkeley.edu/wiki/ROACH_Bringup#PowerPC_U-Boot_Configuration

When I execute the OCD commander with macro, OCD commander show me a
lot of messages and the last line is "word 0x71000ffc = 0x4bfff004".
Then, OCD commander stop working....
It looks like you have the correct macro - you would typically get that
macro from the roach production files at:
http://casper.berkeley.edu/svn/trunk/roach/production/test_software/roach_testing/macraigor_macros/loadram_rinit_auto.mac

The final command that the macro runs is 'exit', which closes OCD
commander. So OCD commander closing unexpected is a feature not a bug!
Once OCD commander quits you should start seeing activity on the serial
port. Wait a while (more than 10s I think) until a character starts
repeating (it looks like an S in hyperterminal). When this happens you
are ready to transfer. Use XMODEM (not YMODEM) to xfer the u-boot.bin
file. You'll find the latest file in:
http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/uboot/

You should have uboot running after the xmodem transfer completes.

Cheers.

--
David George
Digital Design Engineer
Karoo Array Telescope
Tel:     +27 21 531-7282
Fax:     +27 21 531-9761
Email:   [email protected]
Web: www.ska.ac.za


Reply via email to