Skip to contentSkip to conversation

X-loader / U-Boot query

DISCUSSION Gary Thomas 6 participants 11 messages Oct 8, 2009

lore
Share & tools
lore
#0 lore raw

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

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 4 lines

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

Quoted 8 lines

* 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

#3 lore raw
In reply to Adam Machalek
Quoted 10 lines · Adam Machalek

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??

Quoted 21 lines
Quoted 20 lines · Gary Thomas

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

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#2 lore raw
In reply to Gary Thomas

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

Quoted 20 lines · Gary Thomas

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

#4 lore raw
Quoted 10 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Adam Machalek
Sent: Thursday, October 08, 2009 9:47 AM
To: Gary Thomas
Cc: [email protected]
Subject: Re: X-loader / U-Boot query

The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c

Quoted 9 lines

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

#5 lore raw
Quoted 12 lines · Nishanth
Quoted 12 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Adam Machalek
Sent: Thursday, October 08, 2009 9:47 AM
To: Gary Thomas
Cc: [email protected]
Subject: Re: X-loader / U-Boot query

The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c

Function do_sdrc_init()

Quoted 8 lines
Quoted 7 lines

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...

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#6 lore raw
Quoted 27 lines

-----Original Message-----
From: Gary Thomas [mailto:[email protected]]
Sent: Thursday, October 08, 2009 10:17 AM
To: Menon, Nishanth
Cc: Adam Machalek; [email protected]
Subject: Re: X-loader / U-Boot query

Quoted 19 lines · Nishanth
Quoted 19 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Adam Machalek
Sent: Thursday, October 08, 2009 9:47 AM
To: Gary Thomas
Cc: [email protected]
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);
Quoted 5 lines
Quoted 1 line

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

#7 lore raw
In reply to Gary Thomas
Quoted 30 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Gary Thomas
Sent: Thursday, October 08, 2009 10:17 AM
To: Menon, Nishanth
Cc: Adam Machalek; [email protected]
Subject: Re: X-loader / U-Boot query

Quoted 19 lines · Nishanth
Quoted 19 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Adam Machalek
Sent: Thursday, October 08, 2009 9:47 AM
To: Gary Thomas
Cc: [email protected]
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);
Quoted 6 lines
Quoted 1 line

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

#8 lore raw
Quoted 31 lines · Khasim
Quoted 31 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Gary Thomas
Sent: Thursday, October 08, 2009 10:17 AM
To: Menon, Nishanth
Cc: Adam Machalek; [email protected]
Subject: Re: X-loader / U-Boot query

Quoted 20 lines · Nishanth
Quoted 10 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Adam Machalek
Sent: Thursday, October 08, 2009 9:47 AM
To: Gary Thomas
Cc: [email protected]
Subject: Re: X-loader / U-Boot query

The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c

Quoted 9 lines

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

Quoted 8 lines
Quoted 5 lines

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?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#9 lore raw
Quoted 51 lines

-----Original Message-----
From: Gary Thomas [mailto:[email protected]]
Sent: Thursday, October 08, 2009 11:10 AM
To: Syed Mohammed, Khasim
Cc: [email protected]
Subject: Re: X-loader / U-Boot query

Quoted 30 lines · Khasim
Quoted 30 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Gary Thomas
Sent: Thursday, October 08, 2009 10:17 AM
To: Menon, Nishanth
Cc: Adam Machalek; [email protected]
Subject: Re: X-loader / U-Boot query

Quoted 19 lines · Nishanth
Quoted 19 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Adam Machalek
Sent: Thursday, October 08, 2009 9:47 AM
To: Gary Thomas
Cc: [email protected]
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);
Quoted 7 lines
Quoted 6 lines
Quoted 1 line

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.

Quoted 1 line
Quoted 7 lines
Quoted 1 line

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

#10 lore raw
In reply to Gary Thomas
Quoted 7 lines · Gary Thomas

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

Quoted 7 lines

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.

Quoted 1 line

* Is there a better place to ask/discuss these questions?

Yes. U-Boot list. It was already mentioned in this thread.

Cheers

Dirk