Have you solved this problem with bbram? I faced it too. But my problem is large
bbram array (approx size 10000 bytes)
Regards,
Serg
Have you solved it?
Started by ●April 25, 2012
Reply by ●April 26, 20122012-04-26
It seems when compiling for the RCM6700, by default the majority of the 32K
BBRAM (20K) is allocated for FAT file system buffers - even if you don't
use the FAT file system.
Have a look at the comments in the fatconfig.lib file for ways to remove or reduce the size of this allocation and free up some more BBRAM.
The amount you can free up will depend on whether you need the FAT support or not.
Regards,
Peter
--- In r..., sergej_r@... wrote:
>
> Have you solved this problem with bbram? I faced it too. But my problem is large bbram array (approx size 10000 bytes)
> Regards,
> Serg
>
Have a look at the comments in the fatconfig.lib file for ways to remove or reduce the size of this allocation and free up some more BBRAM.
The amount you can free up will depend on whether you need the FAT support or not.
Regards,
Peter
--- In r..., sergej_r@... wrote:
>
> Have you solved this problem with bbram? I faced it too. But my problem is large bbram array (approx size 10000 bytes)
> Regards,
> Serg
>
Reply by ●May 3, 20122012-05-03
If you are using the 6750 or 6760, the best solution is to use
_xalloc(&pAllocSize, 1, XALLOC_BB) for your persistent data. The full 1M of (BB)
static RAM is available.
Make sure you are using DC10.70, not 10.66, with this bug fix: "All memory orgs located in a battery-backable SRAM are now properly identified in memory_layout.lib as being BB, with regard to both xalloc usage and in the program's MAP file. In particular, the RCM6750/60's battery-backable external SRAM's memory org is now marked as BB."
--- In r..., "petermcs" wrote:
>
> It seems when compiling for the RCM6700, by default the majority of the 32K BBRAM (20K) is allocated for FAT file system buffers - even if you don't use the FAT file system.
>
> Have a look at the comments in the fatconfig.lib file for ways to remove or reduce the size of this allocation and free up some more BBRAM.
>
> The amount you can free up will depend on whether you need the FAT support or not.
>
> Regards,
> Peter
> --- In r..., sergej_r@ wrote:
> >
> > Have you solved this problem with bbram? I faced it too. But my problem is large bbram array (approx size 10000 bytes)
> > Regards,
> > Serg
>
Make sure you are using DC10.70, not 10.66, with this bug fix: "All memory orgs located in a battery-backable SRAM are now properly identified in memory_layout.lib as being BB, with regard to both xalloc usage and in the program's MAP file. In particular, the RCM6750/60's battery-backable external SRAM's memory org is now marked as BB."
--- In r..., "petermcs" wrote:
>
> It seems when compiling for the RCM6700, by default the majority of the 32K BBRAM (20K) is allocated for FAT file system buffers - even if you don't use the FAT file system.
>
> Have a look at the comments in the fatconfig.lib file for ways to remove or reduce the size of this allocation and free up some more BBRAM.
>
> The amount you can free up will depend on whether you need the FAT support or not.
>
> Regards,
> Peter
> --- In r..., sergej_r@ wrote:
> >
> > Have you solved this problem with bbram? I faced it too. But my problem is large bbram array (approx size 10000 bytes)
> > Regards,
> > Serg
>
