[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [microblaze-uclinux] external ram not executing code



Hi,

      We are using the OPB_EMC.

       Attached is the MHS file, and the UCF file.

      The engineer said to let you know that we are Not using CE, (we are
using CEN), and we aren't using BEN.  (Chip Enable, Chip Enable Not, Byte
Enable Not).

      If we write a byte to external memory, we blow away 24 bits of data
at that long word location. Same way with 16 bits, we blow away the long
word.

      I'm now at a point where I have to rely on others for "eyewitness"
accounts, it can get murky due to that.  I'm trying to boil down to most
useful information.

      Thanks for the help!

wade
(See attached file: system.mhs)(See attached file: system.ucf)




                                                                           
             "Kristian                                                     
             Chaplin"                                                      
             <kristian.chaplin                                          To 
             @xilinx.com>              <microblaze-uclinux@itee.uq.edu.au> 
             Sent by:                                                   cc 
             owner-microblaze-         "Kristian Chaplin"                  
             uclinux@itee.uq.e         <kristian.chaplin@xilinx.com>       
             du.au                                                 Subject 
                                       RE: [microblaze-uclinux] external   
                                       ram not executing code              
             05/19/2005 12:41                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             microblaze-uclinu                                             
             x@itee.uq.edu.au                                              
                                                                           
                                                                           




Hello Wade,

I'm not quite sure what you are seeing here.

I assume if the hardware is SRAM, you are using the OPB_EMC.

What do you mean by it only being 32-bits wide for data?  Can you write
8,
16 and 32-bit data values into and out of it?

As the ram is available on the data and instruction side of the bus, you
can
 perform some memory test functions.  Please tell us what you find.

Also it might be useful to paste in the MHS file for the system, so we
can
check the EMC parameters.

Best regards

Kris


--
------------------------------------------------------------------------
----
/ /\/ Kris Chaplin
\ \   Applications Engineer - Embedded Processors
/ /   Xilinx Europe
\_\/\ +44 (0)870-7356-563

-----Original Message-----
From: owner-microblaze-uclinux@itee.uq.edu.au
[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of
Wade.Maxfield@precision-es.com
Sent: 19 May 2005 16:53
To: microblaze-uclinux@itee.uq.edu.au
Subject: [microblaze-uclinux] external ram not executing code


    My hardware guy is having problems getting external Static Ram to
execute code for the Microblaze.  Internal block ram does fine.

    As I understand it now, the ram is enabled both for program space
and
data space.  However, it appears to only be 32 bits wide for data
(although
it is 2 16 bit wide ram devices).

    Any suggestions what to look for?

thanks!
wade





***CONFIDENTIALITY NOTICE***
This communication (and any attachment) is confidential.  It should only be
read by the person(s) to whom
it is addressed.  If you have received this communication in error, please
notify the sender by reply and delete this communication.
*****************************************
***CONFIDENTIALITY NOTICE***
This communication (and any attachment) is confidential. It should only be
read by the person(s) to whom
it is addressed.  If you have received this communication in error, please
notify the sender by reply and delete this communication.
*****************************************

Attachment: system.mhs
Description: Binary data

Attachment: system.ucf
Description: Binary data