Fw: Re: ColdFire 5307 start up problem using CS1 with byte access

I also tried without BSTR BSTW:
$1DA0 # D0 MOV D0 CSCR1 A0) W. MOV
it works the same way

----- Original Message -----
From: "Leon Wagner" <leon_at_forth.com>
To: <swiftx_at_forth.com>
Sent: 15-Oct-04 14:17
Subject: [swiftx] Re: ColdFire 5307 start up problem using CS1 with byte
access

> Are you really sure you want BSTR and BSTW?
>
> > -----Original Message-----
> > From: swiftx-bounce_at_forth.com [mailto:swiftx-bounce_at_forth.com]On Behalf
> > Of Jacek Myzyk
> > Sent: Thursday, October 14, 2004 13:23
> > To: swiftx_at_forth.com
> > Subject: [swiftx] ColdFire 5307 start up problem using CS1 with byte
> > access
> >
> >
> > Hello,
> >
> > I'm using Motorola MCF5307 with SwiftX ColdFire 2.04.5
> >
> > instead of dynamic ram with CS1 I am using static ram,
> > everything was fine ( for last 4 years) when ram chip was 16 bit with
> > no byte access
> >
> > now I have new CPU board with 16 bit ram which has two pins for
> > byte access,
> > BE0 96/5307 is connected to BHE# of ram
> > BE1 98/5307 is connected to BLE# of ram
> >
> > in start.f I changed
> > $1DC0 # D0 MOV D0 CSCR1 A0) W. MOV \ no byte access
> > to
> > $1DF8 # D0 MOV D0 CSCR1 A0) W. MOV \ with byte access
> >
> > and ColdFire does not start, unless I put the two ram pins to GND
> > for initial start up defined in start.f
> > and then I allow connection ( mentioned above) just before my
> > software starts
> > to run - in this case everything is ok, I have both 16bit & 8bit access
> >
> > I am not sure at this moment if this is software or hardware issue.
> >
> > Service request to Motorola ( Freescale) did not help
> >
> > Did anybody encounter that problem ?
> >
> > Thanks
> >
> > Jacek Myzyk
> >
> > Gem Systems Inc.
> >
> >
> >
> >
> >
> > ----------------------------------------------------------------------
> > swiftx_at_forth.com The SwiftX programming discussion email list
> > To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
> > For list command help, send subject "help" to swiftx-request_at_forth.com
> > Message archives are located at http://www.forth.com/archive/swiftx
> > ----------------------------------------------------------------------
> > This list is a forum for SwiftX users. For product support and bug
> > reports, please send email to support_at_forth.com
> > ----------------------------------------------------------------------
> >
> >
> ----------------------------------------------------------------------
> swiftx_at_forth.com The SwiftX programming discussion email list
> To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
> For list command help, send subject "help" to swiftx-request_at_forth.com
> Message archives are located at http://www.forth.com/archive/swiftx
> ----------------------------------------------------------------------
> This list is a forum for SwiftX users. For product support and bug
> reports, please send email to support_at_forth.com
> ----------------------------------------------------------------------
>

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Fri Oct 15 2004 - 11:50:55 PDT