Opened 5 years ago

Closed 5 years ago

Last modified 20 months ago

#11918 closed defect (fixed)

Nanya/Micron 2Gb DRAM doesn't work

Reported by: wad Owned by: Quozl
Priority: normal Milestone:
Component: ofw - open firmware Version: 1.75-C1
Keywords: XO-1.75 Cc: wad, quozl, wmb@…
Blocked By: Blocking:
Deployments affected: Action Needed: never set
Verified: no


When testing the latest 2Gb DD3 die from Nanya (NT5CB256M8GN-CG), which is also shipped as Micron's MT4J256M8HX-15E, memory errors prevented a current OFW from booting.

Further examination showed that our existing memory timing is not valid for those parts. Per JEDEC JESD-79-3D ( ), 2Gb parts are allowed to have a longer tRFC than used by our current timing.

We haven't seen a problem with already qualified 2Gb parts, but those will probably be EOL'd soon in favor of newer dies.

I suggest that CForth's memory configuration code be changed to include conditional setting of register 0xd0000060 to 0x64660404 (instead of 0x646602C4) when configuring 1GB of memory.

This value meets the JEDEC requirements, and has been tested to work with the Nanya memory. It appears both Micron test boards had rework problems, and haven't been tested yet.

Before releasing this modification, we should test with all qualified 2Gb parts. It is expected, however, that even 1Gb parts should work with this more conservative timing.

Change History (13)

comment:1 Changed 5 years ago by wad

Just a clarification that 2Gb DDR3 parts are used in all XO-1.75 laptops which have 1GB of memory loaded.

comment:2 Changed 5 years ago by wmb@…

  • Action Needed changed from code to test in build
  • Owner changed from wmb@… to Quozl

Fixed by git commit ead02cb. Barely-tested so far. It seems to do the right thing on a 512 MiB machine. Test version at scp

comment:3 Changed 5 years ago by Quozl

Testing in progress, two 1GB and two 512MB machines.

diag-mode test /memory many

... and a counter.

comment:4 Changed 5 years ago by Quozl

  • Cc wmb@… added

Passed 730 cycles on 1GB, and 1475 cycles on 512MB, looks good.

Tested q4d16mk with os14, it doesn't boot, but q4d16 boots fine, perhaps something in q4d16mk? Tested q4d16je which is using the same git commit ead02cbe, no symptom. Will test runin with that over the weekend.

comment:5 Changed 5 years ago by Quozl

Is in Q4D17.

comment:6 Changed 5 years ago by Quozl

  • Milestone changed from 11.3.1 to 1.75-firmware

Runin testing of Q4D17 and 11.3.1 is in progress.

Runin testing of Q4D17 and 12.1.0 os14 is too unstable to give me confidence with this change, so it is ongoing.

(Pulling this ticket out of the 11.3.1 milestone since that release has been just completed, and the firmware is loaded before the software download by manufacturing.)

comment:7 Changed 5 years ago by Quozl

Runin test of Q4D17 and 11.3.1 passed 24-hours fine.

comment:8 Changed 5 years ago by Quozl

Q4D18 memtest

  • in progress on SKU200X3, overnight, 486 cycles.
  • in progress on SKU201, overnight, 555 cycles.
  • in progress on four units by Chia-Hsiu, (one Micro, three Nanya), overnight passed,

Runin test of Q4D17 and 11.3.1 passed 48-hours fine.

Chia-Hsiu plans to put four units in runin test over weekend.

comment:9 Changed 5 years ago by Quozl

Q4D18 memtest

  • completed SKU201, 1184 cycles, over 24-hours,
  • completed SKU200X3, over 24-hours, but evidence lost, need to retest.

comment:10 Changed 5 years ago by Quozl

Runin test of Q4D17 and 11.3.1 passed 72-hours fine, completed.

comment:11 Changed 5 years ago by greenfeld

Is this ticket safe to close?

comment:12 Changed 5 years ago by Quozl

  • Action Needed changed from test in build to never set
  • Resolution set to fixed
  • Status changed from new to closed

Thinks so. I've not seen problems yet with it.

comment:13 Changed 20 months ago by Quozl

  • Milestone 1.75-firmware deleted

Milestone 1.75-firmware deleted

Note: See TracTickets for help on using tickets.