[MinnowBoard] 4GB Ram need pcb rerouting?
Grigory V. Korotov
grinux at mail.ru
Fri Oct 28 12:05:45 UTC 2016
Hi David.
Thanks for assistance.
I tried this config. Nothing.
I think we should on first step get manual config working on original MBM2.
I also tried it on MBM2 with 4Gbit density
gVlvRefCodePkgTokenSpaceGuid.PcdDimmDensity|2 and also nothing.
I build debug version of fw and there is debug output:
MRC Parameters not valid. status is 8000000E
Set MRC paramaters for Customer Board. MRC parameters are patched by PCD.
DRAM_Speed is type 3, EccEnabled = 0
tCL = 11
tRP_tRCD = 11
tWR = 12
tWTR = 6
tRRD = 6
tRTP = 6
tFAW = 32
PROGRESS CODE: V51001 I0
POSTCODE=<0024>
MRC getting memory size from SeC ...
SeC Device ID: F18
SeC UMA Size Requested: 16384 KB
MRC SeCUmaSize memory size from SeC ... 10
MRC getting fTPM memory size from SeC ...
MRC SeCfTPMUmaSize memory size from SeC ... 0
PROGRESS CODE: V51002 I0
POSTCODE=<0025>
PROGRESS CODE: V51003 I0
POSTCODE=<0027>
Configuring Memory...
CheckMicrocodeRevision = 00000000, CpuId = 00030679
####: ConfigureMemory() Entry
Current function is McEnableHPET
Current function is ClearSelfRefresh
Current function is OemTrackInitComplete
Current function is ProgSFRVolSel
Current function is ProgDdrTimingControl
Current function is ProgBunit
Current function is ProgMpllSetup
Current function is ProgStaticDdrSetup
Current function is ProgStaticInitPerf
Current function is ProgStaticPwrClkGating
Current function is DUnitBlMode
Current function is ControlDDR3Reset
Current function is EnableVreg
Current function is ProgHmc
Current function is ProgReadWriteFifoPtr
Current function is ProgComp
Current function is SetIOBUFACT
Current function is ProgDdecodeBeforeJedec
Current function is PerformDDR3Reset
Current function is PreJedecInit
Current function is PerformJedecInit
Current function is SetDDRInitializationComplete
Current function is PerformJedecInit
Current function is DisableRank2RankSwitching
* Current function is MMRC_RcvnTrain
*fw hangs on last printed function.
Grigory
**
28.10.2016 9:23, Wei, David пишет:
>
> Hi,
>
> Could you try below configurations in the DSC file?
>
> #######################################################################################################
>
> #
>
> # Begin of MRC parameters
>
> #
>
> ## Memory Parameter Patchable.
>
> # FALSE - MRC Parameters are fixed for MinnowBoard Max<BR>
>
> # TRUE - MRC Parameters are patchable by following PCDs<BR>
>
> # @Prompt Memory Parameter Patchable.
>
> # @ValidList 0x80000001 | 0, 1
>
> gVlvRefCodePkgTokenSpaceGuid.PcdMemoryParameterPatchable|TRUE
>
> ## Memory Down or DIMM slot.
>
> # 0 - DIMM<BR>
>
> # 1 - Memory Down<BR>
>
> # @Prompt Enable Memory Down
>
> # @ValidList 0x80000001 | 0, 1
>
> gVlvRefCodePkgTokenSpaceGuid.PcdEnableMemoryDown|1
>
> ## The speed of DRAM.
>
> # 0 - 800 MHz<BR>
>
> # 1 - 1066 MHz<BR>
>
> # 2 - 1333 MHz<BR>
>
> # 3 - 1600 MHz<BR>
>
> # @Prompt DRAM Speed
>
> # @ValidList 0x80000001 | 0, 1, 2, 3
>
> gVlvRefCodePkgTokenSpaceGuid.PcdDramSpeed|3
>
> ## DRAM Type.
>
> # 0 - DDR3<BR>
>
> # 1 - DDR3L<BR>
>
> # 2 - DDR3U<BR>
>
> # 3 - DDR3All<BR>
>
> # 4 - LPDDR2<BR>
>
> # 5 - LPDDR3<BR>
>
> # 6 - DDR4<BR>
>
> # @Prompt DRAM Type
>
> # @ValidList 0x80000001 | 0, 1, 2, 3, 4, 5, 6
>
> gVlvRefCodePkgTokenSpaceGuid.PcdDramType|1
>
> ## Please populate DIMM slot 0 if only one DIMM is supported.
>
> # 0 - Disable<BR>
>
> # 1 - Enable<BR>
>
> # @Prompt DIMM 0 Enable
>
> # @ValidList 0x80000001 | 0, 1
>
> gVlvRefCodePkgTokenSpaceGuid.PcdEnableDimm0|1
>
> ## DIMM 1 has to be identical to DIMM 0.
>
> # 0 - Disable<BR>
>
> # 1 - Enable<BR>
>
> # @Prompt DIMM 1 Enable Type
>
> # @ValidList 0x80000001 | 0, 1
>
> gVlvRefCodePkgTokenSpaceGuid.PcdEnableDimm1|0
>
> ## DRAM device data width.
>
> # 0 - x8<BR>
>
> # 1 - x16<BR>
>
> # 2 - x32<BR>
>
> # @Prompt DIMM_DWIDTH
>
> # @ValidList 0x80000001 | 0, 1, 2
>
> gVlvRefCodePkgTokenSpaceGuid.PcdDimmDataWidth|1
>
> ## DRAM device data density.
>
> # 0 - 1 Gbit<BR>
>
> # 1 - 2 Gbit<BR>
>
> # 2 - 4 Gbit<BR>
>
> # 3 - 8 Gbit<BR>
>
> # @Prompt DIMM_Density
>
> # @ValidList 0x80000001 | 0, 1, 2, 3
>
> gVlvRefCodePkgTokenSpaceGuid.PcdDimmDensity|3
>
> ## DRAM device data bus width.
>
> # 0 - 8 bits<BR>
>
> # 1 - 16 bits<BR>
>
> # 2 - 32 bits<BR>
>
> # 3 - 64 bits<BR>
>
> # @Prompt DIMM_BusWidth
>
> # @ValidList 0x80000001 | 0, 1, 2, 3
>
> gVlvRefCodePkgTokenSpaceGuid.PcdDimmBusWidth|3
>
> ## Ranks Per DIMM or Sides Per DIMM.
>
> # 0 - 1 Rank<BR>
>
> # 1 - 2 Ranks<BR>
>
> # @Prompt DIMM_Sides
>
> # @ValidList 0x80000001 | 0, 1
>
> gVlvRefCodePkgTokenSpaceGuid.PcdRankPerDimm|0
>
> ## tCL.<BR><BR>
>
> # @Prompt tCL
>
> gVlvRefCodePkgTokenSpaceGuid.PcdTcl|11
>
> ## tRP and tRCD in DRAM clk - 5:12.5ns, 6:15ns, etc.
>
> # @Prompt tRP_tRCD
>
> gVlvRefCodePkgTokenSpaceGuid.PcdTrpTrcd|11
>
> ## tWR in DRAM clk.
>
> # @Prompt tWR
>
> gVlvRefCodePkgTokenSpaceGuid.PcdTwr|12
>
> ## tWTR in DRAM clk.
>
> # @Prompt tWTR
>
> gVlvRefCodePkgTokenSpaceGuid.PcdTwtr|6
>
> ## tRRD in DRAM clk.
>
> # @Prompt tRRD
>
> gVlvRefCodePkgTokenSpaceGuid.PcdTrrd|6
>
> ## tRTP in DRAM clk.
>
> # @Prompt tRTP
>
> gVlvRefCodePkgTokenSpaceGuid.PcdTrtp|6
>
> ## tFAW in DRAM clk.
>
> # @Prompt tFAW
>
> gVlvRefCodePkgTokenSpaceGuid.PcdTfaw|32
>
> Thanks,
>
> David Wei
>
> *From:*elinux-MinnowBoard
> [mailto:elinux-minnowboard-bounces at lists.elinux.org] *On Behalf Of
> *Grigory V. Korotov
> *Sent:* Wednesday, October 26, 2016 2:54 PM
> *To:* elinux-minnowboard at lists.elinux.org
> *Subject:* Re: [MinnowBoard] 4GB Ram need pcb rerouting?
>
> Hi David
> Thanks for answer.
> I just trying to get
> gVlvRefCodePkgTokenSpaceGuid.PcdMemoryParameterPatchable|TRUE config
> working on standart MBM2
> By now the following config was checked by me but not working on MBM2:
> *gVlvRefCodePkgTokenSpaceGuid.PcdMemoryParameterPatchable|TRUE
> gVlvRefCodePkgTokenSpaceGuid.PcdEnableMemoryDown|1
> gVlvRefCodePkgTokenSpaceGuid.PcdDramSpeed|1
> VlvRefCodePkgTokenSpaceGuid.PcdDramType|1
> gVlvRefCodePkgTokenSpaceGuid.PcdEnableDimm0|1
> gVlvRefCodePkgTokenSpaceGuid.PcdEnableDimm1|0
> gVlvRefCodePkgTokenSpaceGuid.PcdDimmDataWidth|1
> gVlvRefCodePkgTokenSpaceGuid.PcdDimmDensity|2
> gVlvRefCodePkgTokenSpaceGuid.PcdDimmBusWidth|3
> gVlvRefCodePkgTokenSpaceGuid.PcdRankPerDimm|0
> gVlvRefCodePkgTokenSpaceGuid.PcdTrpTrcd|7
> gVlvRefCodePkgTokenSpaceGuid.PcdTwr|8
> gVlvRefCodePkgTokenSpaceGuid.PcdTwtr|5
> gVlvRefCodePkgTokenSpaceGuid.PcdTrrd|6
> gVlvRefCodePkgTokenSpaceGuid.PcdTrtp|4
> gVlvRefCodePkgTokenSpaceGuid.PcdTfaw|28
>
> *My goal now is to get it working on MBM2.
> After that i'll try adjust config for working on higher density chips
> on my custom board.
> I just add higher density micron chips
> https://www.micron.com/parts/dram/ddr3-sdram/mt41k512m16ha-125?pc={00EED26F-83AE-4CE6-9A28-EB8B033361E8}
> And add some minor hw mods discussed here earlier. This is the DRAM
> schematic part:
>
> And this is E3800 part:
>
>
> As you can see i connected ODT1 CS1 CKE1 ZQ1 and A15 то CPU.
>
> 26.10.2016 5:14, Wei, David пишет:
>
> As Michael mentioned, there are total 17 parameters you need to change for your new memory. Those parameters are determined by your on-board memory chips layout and memory datasheet.
>
> You could send us the datasheet of your memory and also tell us how many memory chips are there on your board.
>
> Thanks,
>
> David Wei
>
> -----Original Message-----
>
> From: elinux-MinnowBoard [mailto:elinux-minnowboard-bounces at lists.elinux.org] On Behalf Of Grigory V. Korotov
>
> Sent: Tuesday, October 25, 2016 11:08 PM
>
> To:elinux-minnowboard at lists.elinux.org
> <mailto:elinux-minnowboard at lists.elinux.org>
>
> Subject: Re: [MinnowBoard] 4GB Ram need pcb rerouting?
>
> Hello again.
>
> So i have looked into PlatformPkgIA32.dsc and found all things you
>
> mentioned below.
>
> I just switched
>
> gVlvRefCodePkgTokenSpaceGuid.PcdMemoryParameterPatchable|TRUE and dont
>
> touched any other parameters to check that default values are working.
>
> But its not working, board wont boot.
>
> When a placed back
>
> gVlvRefCodePkgTokenSpaceGuid.PcdMemoryParameterPatchable|FALSE
>
> everything works fine.
>
> So i looking for valid MRC paramenetrs to make MBM2 working in standart
>
> configuration.
>
> Could someone help me?
>
> Thanks.
>
> 18.10.2016 17:58, Krau, Michael P пишет:
>
> In the release note of the Firmware, it provides instructions on how to change the PCD settings to change the memory configuration. The instructions start with (and I quote):
>
> 6. How to configure memory parameters for new custom platforms
>
>
>
> If you want to configure memory parameters for your own platform, the following steps must be done before building the source tree.
>
> (1) Open the platform DSC file, which is <MyWorkspace>/ Vlv2TbltDevicePkg/ PlatformPkgIA32.dsc or <MyWorkspace>/ Vlv2TbltDevicePkg/ PlatformPkgX64.dsc depending on your which CPU architecture you prefer to support.
>
> (2) Search in the platform DSC file for following PCDs. There are a total of 17
>
> PCDs for memory parameter configuration.
>
> Taking PCD "VlvRefCodePkgTokenSpaceGuid.PcdMemoryParameterPatchable|FALSE",
>
> for example, the string before "|" represents PCD name, while the string
>
> after "|" represents configurable PCD value.
>
> And the comment, which is above the PCD and marked by #, provides the
>
> usage of the PCD and valid selectable values.
>
> #######################################################################################################
>
> #
>
> # Begin of MRC parameters
>
> #
>
>
>
> .
>
> .
>
> .
>
> (end quote)
>
> I will note that the list of the settings available in the DSC file are much more inclusive to the list in the release notes. (also for space considerations, I have only provided you with the starting point in the release notes) The release notes were to point you in the right direction, the DSC provides all the available options. There is a PCD to set Memory configuration size, among other memory features.
>
> Thank you,
>
> Michael Krau
>
>
>
> -----Original Message-----
>
> From: elinux-MinnowBoard [mailto:elinux-minnowboard-bounces at lists.elinux.org] On Behalf Of Grigory V. Korotov
>
> Sent: Tuesday, October 18, 2016 4:01 AM
>
> To: MinnowBoard Development and Community Discussion<elinux-minnowboard at lists.elinux.org>
> <mailto:elinux-minnowboard at lists.elinux.org>
>
> Subject: Re: [MinnowBoard] 4GB Ram need pcb rerouting?
>
> Hello Berth-Olof,
>
> I got new version of my MBM based board with 4Gb ready hw mods. Thanks you again. At least it boots into uefi shell :) Could you please figure out point in uefi sources i should look into to get 4Gb config working? By now its only 2Gb available.
>
> Thanks
>
> 16.06.2016 12:23, Berth-Olof Bergman пишет:
>
> Yes, you need to do changes in UEFI sources.
>
> Best regards,
>
> B-O
>
> 16 juni 2016 kl. 10:10 skrev Grigory V. Korotov<grinux at mail.ru> <mailto:grinux at mail.ru>:
>
> So i just need to connect A15 and solder higher dencity chips?
>
> Should i do any changes in uefi sources?
>
> 16.06.2016 9:52, Berth-Olof Bergman пишет:
>
> It would be possible if DRAM A15 is connected, which it isn't on Minnowboard Max and Turbot. It would also be possible to use 8GB DRAM if channel 2 signals is connected. Our Minnowboard Quattro (4 cores) supports 1GB, 2GB, 4GB and 8 GB configurations. We also have an integrated nanoSSD on board, ranging from 8GB to 64GB.
>
> Best regards,
>
> B-O Bergman
>
> Winzent Technologies
>
> 16 juni 2016 kl. 08:45 skrev Grigory V. Korotov<grinux at mail.ru> <mailto:grinux at mail.ru>:
>
> Hi!
>
> Is it possible to replace currently used ddr3 chips by higher dencity chips without rerouting pcb to get total 4Gb of Ram?
>
> Thanks
>
> Grigory.
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
> _______________________________________________
>
> elinux-MinnowBoard mailing list
>
> elinux-MinnowBoard at lists.elinux.org
> <mailto:elinux-MinnowBoard at lists.elinux.org>
>
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>
>
>
> _______________________________________________
> elinux-MinnowBoard mailing list
> elinux-MinnowBoard at lists.elinux.org
> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elinux.org/pipermail/elinux-minnowboard/attachments/20161028/26d33e76/attachment-0001.html>
More information about the elinux-MinnowBoard
mailing list