Bug 87631 - Wrong SDRAM size for IXDP425 Evaluation Board
Wrong SDRAM size for IXDP425 Evaluation Board
Status: CLOSED NOTABUG
Product: eCos
Classification: Retired
Component: HAL (Show other bugs)
CVS
xscale Linux
medium Severity medium
: ---
: ---
Assigned To: Mark Salter
Jonathan Larmour
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-31 08:31 EST by Lutz Jänicke
Modified: 2007-04-18 12:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-04-02 05:17:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lutz Jänicke 2003-03-31 08:31:41 EST
Description of problem:
The SDRAM size of the IXDP425 Evaluation Board is 128MByte instead of the
256MByte currently configured, see hal/arm/xscale/ixdp425/current/include/ixdp425.h:

#define SDRAM_SIZE                         0x10000000  // 256MB

Version-Release number of selected component (if applicable):
CVS

How reproducible:


Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:
Comment 1 Mark Salter 2003-04-01 19:35:48 EST
http://developer.intel.com/design/network/products/npfamily/ixdp425.htm
shows that the board has 256MB. My board has 256MB. Is there a 128MB
model? Are all four SDRAM positions populated on your board? In any
case, if there are 128MByte boards out there, some runtime code to size
memory would be nice. I can't do it, though as I don't have a 128MByte
board.
Comment 2 Lutz Jänicke 2003-04-02 05:17:41 EST
I studied once more the documentation.
My value (128MB) was around since the very first preliminary software version we
received from Intel. This has long since been corrected but never made it to our
files.
256MB and therefore Redboot is correct.

Sorry for any confusion caused,
       Lutz

Note You need to log in before you can comment on or make changes to this bug.