Re: X-loader / U-Boot query
Gary Thomas wrote: I have a new board - OMAP 3530 with 512MB DRAM & NAND I've build X-loader and U-Boot for it and it mostly comes up. The sources I used (based on recommendations from the BeagleBoard pages) were: http://git.gitorious.org/x-load-omap3/mainline.git git://git.denx.de/u-boot.git I had to make a small change to get it to recognize the larger NAND FLASH device. The problem I have now is that it's only seeing 1/2 (256MB) of the available DRAM. * Does anyone know how to get it to see all 512MB? Not exactly on how to see all 512MB. But while we switched U-Boot Beagle to support 256MB instead of 128MB we did what is in http://git.mansr.com/?p=u-boot;a=shortlog;h=refs/heads/old Maybe the top ~10 commits from Mans there could help you. * Is there a better place to ask/discuss these questions? Yes. U-Boot list. It was already mentioned in this thread. Cheers Dirk -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: X-loader / U-Boot query
> -Original Message- > From: Gary Thomas [mailto:g...@mlbassoc.com] > Sent: Thursday, October 08, 2009 11:10 AM > To: Syed Mohammed, Khasim > Cc: linux-omap@vger.kernel.org > Subject: Re: X-loader / U-Boot query > > On 10/08/2009 09:54 AM, Syed Mohammed, Khasim wrote: > > > > > >> -Original Message- > >> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > >> ow...@vger.kernel.org] On Behalf Of Gary Thomas > >> Sent: Thursday, October 08, 2009 10:17 AM > >> To: Menon, Nishanth > >> Cc: Adam Machalek; linux-omap@vger.kernel.org > >> Subject: Re: X-loader / U-Boot query > >> > >> On 10/08/2009 09:14 AM, Menon, Nishanth wrote: > >>>> -Original Message- > >>>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > >>>> ow...@vger.kernel.org] On Behalf Of Adam Machalek > >>>> Sent: Thursday, October 08, 2009 9:47 AM > >>>> To: Gary Thomas > >>>> Cc: linux-omap@vger.kernel.org > >>>> Subject: Re: X-loader / U-Boot query > >>>> > >>>> The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c > >>>> > >>>> Function do_sdrc_init() > >>>> > >>>> There is an assumption that the RAM size on each CS is maximum of 128M. > >>>> See this line: > >>>> > >>>> writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | > >>>> RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | > >>>> DEEPPD | DDR_SDRAM,&sdrc_base->cs[cs].mcfg); > >>>> > >>> This discussion should really be taken to u-boot mailing list. Yes, any > >> additional patches would be good to have.. > >> > >> Where is that list?? I did ask this question in the original > >> email... > >> > > Sorry, I have not seen all the thread. Are you using x-loader? Then your > DDR configuration happens in x-loader and not in u-boot as it skips it. In > that case your question should be on x-loader and this is the right list to > discuss the same. > > > > If you use u-boot for RAM configuration then you should be on NOR flash. > > I'm definitely using x-loader (followed by U-Boot). > > Where is this set in X-loader? Is there any guidance for > using the larger DRAM devices? > I have tried upto 256MB on beagleboard, http://gitorious.org/x-load-omap3/mainline/commit/c0bc8cc7005abad65be07b0c64901bcfaff71971 See the DDR configuration. I think others have tried for 512MB on other OMAP3 devices I don't know about the source location for the same. Regards, Khasim -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: X-loader / U-Boot query
On 10/08/2009 09:54 AM, Syed Mohammed, Khasim wrote: -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Gary Thomas Sent: Thursday, October 08, 2009 10:17 AM To: Menon, Nishanth Cc: Adam Machalek; linux-omap@vger.kernel.org Subject: Re: X-loader / U-Boot query On 10/08/2009 09:14 AM, Menon, Nishanth wrote: -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Adam Machalek Sent: Thursday, October 08, 2009 9:47 AM To: Gary Thomas Cc: linux-omap@vger.kernel.org Subject: Re: X-loader / U-Boot query The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c Function do_sdrc_init() There is an assumption that the RAM size on each CS is maximum of 128M. See this line: writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | DEEPPD | DDR_SDRAM,&sdrc_base->cs[cs].mcfg); This discussion should really be taken to u-boot mailing list. Yes, any additional patches would be good to have.. Where is that list?? I did ask this question in the original email... Sorry, I have not seen all the thread. Are you using x-loader? Then your DDR configuration happens in x-loader and not in u-boot as it skips it. In that case your question should be on x-loader and this is the right list to discuss the same. If you use u-boot for RAM configuration then you should be on NOR flash. I'm definitely using x-loader (followed by U-Boot). Where is this set in X-loader? Is there any guidance for using the larger DRAM devices? -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: X-loader / U-Boot query
> -Original Message- > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > ow...@vger.kernel.org] On Behalf Of Gary Thomas > Sent: Thursday, October 08, 2009 10:17 AM > To: Menon, Nishanth > Cc: Adam Machalek; linux-omap@vger.kernel.org > Subject: Re: X-loader / U-Boot query > > On 10/08/2009 09:14 AM, Menon, Nishanth wrote: > >> -Original Message- > >> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > >> ow...@vger.kernel.org] On Behalf Of Adam Machalek > >> Sent: Thursday, October 08, 2009 9:47 AM > >> To: Gary Thomas > >> Cc: linux-omap@vger.kernel.org > >> Subject: Re: X-loader / U-Boot query > >> > >> The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c > >> > >> Function do_sdrc_init() > >> > >> There is an assumption that the RAM size on each CS is maximum of 128M. > >> See this line: > >> > >> writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | > >>RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | > >>DEEPPD | DDR_SDRAM,&sdrc_base->cs[cs].mcfg); > >> > > This discussion should really be taken to u-boot mailing list. Yes, any > additional patches would be good to have.. > > Where is that list?? I did ask this question in the original > email... > Sorry, I have not seen all the thread. Are you using x-loader? Then your DDR configuration happens in x-loader and not in u-boot as it skips it. In that case your question should be on x-loader and this is the right list to discuss the same. If you use u-boot for RAM configuration then you should be on NOR flash. Regards, Khasim -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: X-loader / U-Boot query
> -Original Message- > From: Gary Thomas [mailto:g...@mlbassoc.com] > Sent: Thursday, October 08, 2009 10:17 AM > To: Menon, Nishanth > Cc: Adam Machalek; linux-omap@vger.kernel.org > Subject: Re: X-loader / U-Boot query > > On 10/08/2009 09:14 AM, Menon, Nishanth wrote: > >> -Original Message- > >> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > >> ow...@vger.kernel.org] On Behalf Of Adam Machalek > >> Sent: Thursday, October 08, 2009 9:47 AM > >> To: Gary Thomas > >> Cc: linux-omap@vger.kernel.org > >> Subject: Re: X-loader / U-Boot query > >> > >> The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c > >> > >> Function do_sdrc_init() > >> > >> There is an assumption that the RAM size on each CS is maximum of 128M. > >> See this line: > >> > >> writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | > >>RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | > >>DEEPPD | DDR_SDRAM,&sdrc_base->cs[cs].mcfg); > >> > > This discussion should really be taken to u-boot mailing list. Yes, any > additional patches would be good to have.. > > Where is that list?? I did ask this question in the original > email... Please see [1] and the specific list [2] and also see [3] Regards, Nishanth Menon Ref: [1] http://www.google.com/search?sourceid=navclient&ie=UTF-8&rlz=1T4GGLL_enUS306US306&q=u-boot+mailing+list [2] http://lists.denx.de/mailman/listinfo/u-boot [3] http://www.denx.de/wiki/U-Boot -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: X-loader / U-Boot query
On 10/08/2009 09:14 AM, Menon, Nishanth wrote: -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Adam Machalek Sent: Thursday, October 08, 2009 9:47 AM To: Gary Thomas Cc: linux-omap@vger.kernel.org Subject: Re: X-loader / U-Boot query The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c Function do_sdrc_init() There is an assumption that the RAM size on each CS is maximum of 128M. See this line: writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | DEEPPD | DDR_SDRAM,&sdrc_base->cs[cs].mcfg); This discussion should really be taken to u-boot mailing list. Yes, any additional patches would be good to have.. Where is that list?? I did ask this question in the original email... -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: X-loader / U-Boot query
> -Original Message- > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > ow...@vger.kernel.org] On Behalf Of Adam Machalek > Sent: Thursday, October 08, 2009 9:47 AM > To: Gary Thomas > Cc: linux-omap@vger.kernel.org > Subject: Re: X-loader / U-Boot query > > The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c > > Function do_sdrc_init() > > There is an assumption that the RAM size on each CS is maximum of 128M. > See this line: > > writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | > RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | > DEEPPD | DDR_SDRAM, &sdrc_base->cs[cs].mcfg); > This discussion should really be taken to u-boot mailing list. Yes, any additional patches would be good to have.. Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: X-loader / U-Boot query
The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c Function do_sdrc_init() There is an assumption that the RAM size on each CS is maximum of 128M. See this line: writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | DEEPPD | DDR_SDRAM, &sdrc_base->cs[cs].mcfg); Adam Gary Thomas wrote: I have a new board - OMAP 3530 with 512MB DRAM & NAND I've build X-loader and U-Boot for it and it mostly comes up. The sources I used (based on recommendations from the BeagleBoard pages) were: http://git.gitorious.org/x-load-omap3/mainline.git git://git.denx.de/u-boot.git I had to make a small change to get it to recognize the larger NAND FLASH device. The problem I have now is that it's only seeing 1/2 (256MB) of the available DRAM. * Does anyone know how to get it to see all 512MB? * Is there a better place to ask/discuss these questions? A cursory look around did not point to anything fresh (most of the web pages & Wikis I looked are are _years_ old) Thanks for any help/pointers -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: X-loader / U-Boot query
On 10/08/2009 08:46 AM, Adam Machalek wrote: The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c Function do_sdrc_init() There is an assumption that the RAM size on each CS is maximum of 128M. See this line: writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY | RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 | DEEPPD | DDR_SDRAM, &sdrc_base->cs[cs].mcfg); Thanks, I had already found this. What I was _hoping_ was that someone had already fixed this for the larger devices... When I get it figured out, how/where do I pass the info so the next guy doesn't get stuck here as well?? Gary Thomas wrote: I have a new board - OMAP 3530 with 512MB DRAM & NAND I've build X-loader and U-Boot for it and it mostly comes up. The sources I used (based on recommendations from the BeagleBoard pages) were: http://git.gitorious.org/x-load-omap3/mainline.git git://git.denx.de/u-boot.git I had to make a small change to get it to recognize the larger NAND FLASH device. The problem I have now is that it's only seeing 1/2 (256MB) of the available DRAM. * Does anyone know how to get it to see all 512MB? * Is there a better place to ask/discuss these questions? A cursory look around did not point to anything fresh (most of the web pages & Wikis I looked are are _years_ old) Thanks for any help/pointers -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: X-loader / U-Boot query
The problem I have now is that it's only seeing 1/2 (256MB) of the available DRAM. Please refer sdrc_init() in u-boot/board/omap3530beagle/mem.c . SDRC_MCFG register has definition for SIZE and CS settings. Refer [1] for details about SDRC configurations. [1]http://focus.ti.com/pdfs/wtbu/SWPU114Q_PrelimFinal_EPDF_03_05_2009.pdf Regards, Shankar * Does anyone know how to get it to see all 512MB? * Is there a better place to ask/discuss these questions? A cursory look around did not point to anything fresh (most of the web pages & Wikis I looked are are _years_ old) Thanks for any help/pointers -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
