MobileRead Forums - View Single Post

knc1 · 09-26-2012, 03:45 AM

@ixtab: See the part where the DCD is set to null so that the built-in DCD is used from i.ROM?
You most likely have to download the DCD and perhaps the CSF needed to enable the DRAM before downloading and executing the "client" part of the communications code.
(or, a U-Boot configured to init the DRAM when it starts up - - what you have found sounds like your downloading U-Boot into the SoC i.RAM).

Sign-for and download the application note: AN3996.pdf from the Freescale site.
Its one of their free documents that you have to sign-for (limited distribution).
You might also want the source code to the R170_ATK_STD bundle; that plus the part number of the DRAM chip should let you find the "magic numbers"

09-26-2012, 03:45 AM	#233
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	@ixtab: See the part where the DCD is set to null so that the built-in DCD is used from i.ROM? You most likely have to download the DCD and perhaps the CSF needed to enable the DRAM before downloading and executing the "client" part of the communications code. (or, a U-Boot configured to init the DRAM when it starts up - - what you have found sounds like your downloading U-Boot into the SoC i.RAM). Sign-for and download the application note: AN3996.pdf from the Freescale site. Its one of their free documents that you have to sign-for (limited distribution). You might also want the source code to the R170_ATK_STD bundle; that plus the part number of the DRAM chip should let you find the "magic numbers" Last edited by knc1; 09-26-2012 at 03:51 AM.