[U-Boot] how big is the NOR flash on 85xx boards?
I was wondering if we can see how big the NOR flash is on the XES & TQM boards.
thanks.
- k
On Mon, 2009-08-10 at 14:07 -0500, Kumar Gala wrote:
I was wondering if we can see how big the NOR flash is on the XES & TQM boards.
XES's 85xx and 86xx boards should all have U-Boot located in a NOR flash that is either 64MB or 128MB. Sector sizes are generally 128KB.
Out of curiosity, how does XES and TQM's flash size affect what Freescale does for its reference platforms? XES's preference would be to maintain the current 512KB size to maintain continuity with documentation, programming scripts, fdts, etc.
Would it be possible to trim down some of the enabled config options in the larger Freescale boards? The XPedite5370 (mpc8572-based board) has quite a few features enabled, and it has a lot of room to spare:
text data bss dec hex filename 307948 26920 37384 372252 5ae1c u-boot
Best, Peter
Dear Kumar Gala,
In message F424A9E6-AFF8-40F0-B134-92031A12568E@kernel.crashing.org you wrote:
I was wondering if we can see how big the NOR flash is on the XES & TQM boards.
Including the old MPC8xx? They usually have 4 or 8 MB NOR.
Anything else usually has 32...128 MB.
If I remember correctly, there are configurations of the TQM8548 with 4 GB NOR flash - no kidding.
Why do you ask?
Best regards,
Wolfgang Denk
On Aug 10, 2009, at 2:48 PM, Wolfgang Denk wrote:
Dear Kumar Gala,
In message <F424A9E6-AFF8-40F0- B134-92031A12568E@kernel.crashing.org> you wrote:
I was wondering if we can see how big the NOR flash is on the XES & TQM boards.
Including the old MPC8xx? They usually have 4 or 8 MB NOR.
Anything else usually has 32...128 MB.
If I remember correctly, there are configurations of the TQM8548 with 4 GB NOR flash - no kidding.
Why do you ask?
I'm asking this just see if we bump up in size if it should be to 768k or 1M. While this doesn't directly impact the TQM or XES boards I just wanted to get a sense of how much flash people are putting on boards today to see if 1M is a burden or in the noise w/regards to the size of things.
My desire is if we support a different size on 8536DS that its a size other boards would be ok with if they needed to grow.
- k
Dear Kumar Gala,
In message 07DA25C3-1F4F-431E-BF8A-61C11CD4113B@kernel.crashing.org you wrote:
I'm asking this just see if we bump up in size if it should be to 768k or 1M. While this doesn't directly impact the TQM or XES boards I just wanted to get a sense of how much flash people are putting on boards today to see if 1M is a burden or in the noise w/regards to the size of things.
So far we have many systems that are well below 256 kB. 512 kB al- ready seems to a a LOT for just a boot loader. Yes, features like UBI and graphics support cost a price, but these are still non-standard, right?
My desire is if we support a different size on 8536DS that its a size other boards would be ok with if they needed to grow.
I think this is only a Freescale internal issue.
Best regards,
Wolfgang Denk
On Aug 10, 2009, at 4:25 PM, Wolfgang Denk wrote:
Dear Kumar Gala,
In message <07DA25C3-1F4F-431E- BF8A-61C11CD4113B@kernel.crashing.org> you wrote:
I'm asking this just see if we bump up in size if it should be to 768k or 1M. While this doesn't directly impact the TQM or XES boards I just wanted to get a sense of how much flash people are putting on boards today to see if 1M is a burden or in the noise w/regards to the size of things.
So far we have many systems that are well below 256 kB. 512 kB al- ready seems to a a LOT for just a boot loader. Yes, features like UBI and graphics support cost a price, but these are still non-standard, right?
My desire is if we support a different size on 8536DS that its a size other boards would be ok with if they needed to grow.
I think this is only a Freescale internal issue.
And thus my desire is to just disable BEDBUG as its not something we really use and its anywhere near correct for e500. I'm not even sure how it got enabled. Its also a little weird in that its enabled based on having PCI enabled:
#if defined(CONFIG_PCI) #define CONFIG_CMD_PCI #define CONFIG_CMD_BEDBUG #define CONFIG_CMD_NET #define CONFIG_CMD_SCSI #define CONFIG_CMD_EXT2 #endif
- k
participants (3)
-
Kumar Gala -
Peter Tyser -
Wolfgang Denk