[U-Boot-Users] RE: Rattler Board Flash access Problem

[U-Boot-Users] RE: Rattler Board Flash access Problem

[Srivatsan]

Dear all,

      We are trying to port u-boot onto Rattler board(MPC8280). We had
done the relevant porting and but are unable to test the same due to the
problem mentioned below:

We are using BDI2000 to program the Rattler board. Our configuration
file for BDI2000 (which we had written) seems ok as we were able to
access the board using INFO, RES and also was able to dump the memory
starting from the PC (program counter). But when I tried to erase the
Flash, it erased for the first time. But subsequent erase is not
happening, it says

                        COP status is 0xAD
                        #PPC:unexpected response from target
                        Check running state failed
                        Target PVR is 0x0000 0000
                        Resetting target failed  

After this error I am unable to do anything with the board. Can anyone
give me some pointers for analyzing this problem? BDI2000 didn't have
support for AM29LV641D Flash chips so I had selected AM29F type chips.
Please do excuse me if this is off the topic but I thought some people
might have faced similar problems. Hence I had mailed to this group.
Please do help me out with this problem?

I can share the BDI2000 configuration file which we had modified.

Thanks.
srivats                           

[U-Boot-Users] RE: Rattler Board Flash access Problem

[Wolfgang Denk]

In message <000301c52a30$61255300$1269cb0a@bgcw301> you wrote:
> 
> We are using BDI2000 to program the Rattler board. Our configuration
> file for BDI2000 (which we had written) seems ok as we were able to
> access the board using INFO, RES and also was able to dump the memory
> starting from the PC (program counter). But when I tried to erase the
> Flash, it erased for the first time. But subsequent erase is not
> happening, it says

You probably erased the HRCW, and then power cycled the system.

> After this error I am unable to do anything with the board. Can anyone
> give me some pointers for analyzing this problem? BDI2000 didn't have

Check your hardware documentation how to enable the default processor
configuration to allow it to come up without a valid HRWC  in  flash.
There is probably some RSTCNF jumper or similar...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Life would be so much easier if we could  just  look  at  the  source
code.                                                   -- Dave Olson

[U-Boot-Users] RE: Rattler Board Flash access Problem

[Srivatsan]

Thanks Mr.Wolfgang. That input really helped us out.

But when we power up the target (MPC8280 based Rattler board), it is
getting continuous reset. Previously with the same configuration file it
wasn't so. Do we need to make any change in the configuration file?
Again Thanks for the input.

With Thanks and Best Regards,
C.R.Srivatsan

[U-Boot-Users] RE: Rattler Board Flash access Problem

[Wolfgang Denk]

In message <001001c52a45$8dbb4ea0$1269cb0a@bgcw301> you wrote:
> 
> But when we power up the target (MPC8280 based Rattler board), it is
> getting continuous reset. Previously with the same configuration file it
> wasn't so. Do we need to make any change in the configuration file?

How could I guess? I don't know your hardware,  I  don't  know  which
changes you made to port U-Boot to that hardware, I don't know if you
configured  the  BDI  correctly - I don't even know if you're talking
about the configuration file for the BDI2000 or for U-Boot...

Sorry...

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Power is danger.
	-- The Centurion, "Balance of Terror", stardate 1709.2

[U-Boot-Users] RE: Rattler Board Flash access Problem

[Srivatsan]

Thanks for your help Mr.Wolfgang.

The problem was in the BDI2000 configuration file. IMMR was not
reconfigured to 0x00000000 (I was using the default value). I am really
grateful to you for the support extended.

Regards,
C.R.Srivatsan

[U-Boot-Users] RE: Rattler Board Flash access Problem

[Jerry Van Baren]

Srivatsan wrote:
> Thanks Mr.Wolfgang. That input really helped us out.
> 
> But when we power up the target (MPC8280 based Rattler board), it is
> getting continuous reset. Previously with the same configuration file it
> wasn't so. Do we need to make any change in the configuration file?
> Again Thanks for the input.
> 
> With Thanks and Best Regards,
> C.R.Srivatsan

I assume you are saying that you were successful in asserting RSTCONF 
and programming the HRCW back in.
* Is it the _correct_ HRCW?  Do you know what it was previously?
* Did you _power cycle_ the board with RSTCONF deasserted? (the HRCW 
only is read on a _power cycle_)

My experience (not with the Rattler) is that boards don't run well with 
RSTCONF asserted.  In my experience, I assert RSTCONF, program the HRCW 
(and optionally u-boot), and then _power cycle_ the board.  At that 
point, the board should be functional enough to program u-boot (or 
whatever) into it, reset, and run.

gvb