Dear All,
I'm use RCM6710 and DC10.72A also define MAX_FIRMWARE_BINSIZE=0x8000
and ROOT_SIZE_4K=0x06.
If i'm compile get error out of variable data space.
Can anyone help me ?
Thanks.
Steve.
Posted by: S Sutikno
Error out of variable data space
Started by ●July 18, 2016
Reply by ●July 18, 20162016-07-18
hello,
ROOT_SIZE_4K=0x07
El 18 jul. 2016 12:16 AM, "S Sutikno s...@gmail.com [rabbit-semi]" <
r...> escribió:
> Dear All,
>
> I'm use RCM6710 and DC10.72A also define MAX_FIRMWARE_BINSIZE=0x8000
> and ROOT_SIZE_4K=0x06.
> If i'm compile get error out of variable data space.
> Can anyone help me ?
> Thanks.
> Steve.
ROOT_SIZE_4K=0x07
El 18 jul. 2016 12:16 AM, "S Sutikno s...@gmail.com [rabbit-semi]" <
r...> escribió:
> Dear All,
>
> I'm use RCM6710 and DC10.72A also define MAX_FIRMWARE_BINSIZE=0x8000
> and ROOT_SIZE_4K=0x06.
> If i'm compile get error out of variable data space.
> Can anyone help me ?
> Thanks.
> Steve.
Reply by ●July 18, 20162016-07-18
As Gustavo mentioned, you can increase ROOT_SIZE_4K to 7 and gain some more
space. Also, make sure you have "Separate Instruction & Data Space" enabled in
the compiler options.
You might want to check your MAP file to see what's taking up that root space. Consider moving any large globals you have into "far" memory. Dynamic C 10 is pretty good at working with far memory and not requiring you to copy things into root so you can use them.
-Tom
On Jul 17, 2016, at 8:16 PM, S Sutikno s...@gmail.com [rabbit-semi] wrote:
> Dear All,
>
> I'm use RCM6710 and DC10.72A also define MAX_FIRMWARE_BINSIZE=0x8000
> and ROOT_SIZE_4K=0x06.
> If i'm compile get error out of variable data space.
> Can anyone help me ?
> Thanks.
> Steve..
>
>
You might want to check your MAP file to see what's taking up that root space. Consider moving any large globals you have into "far" memory. Dynamic C 10 is pretty good at working with far memory and not requiring you to copy things into root so you can use them.
-Tom
On Jul 17, 2016, at 8:16 PM, S Sutikno s...@gmail.com [rabbit-semi] wrote:
> Dear All,
>
> I'm use RCM6710 and DC10.72A also define MAX_FIRMWARE_BINSIZE=0x8000
> and ROOT_SIZE_4K=0x06.
> If i'm compile get error out of variable data space.
> Can anyone help me ?
> Thanks.
> Steve..
>
>
Reply by ●July 22, 20162016-07-22
Thanks guys for your advice.
Stev
On Tue, Jul 19, 2016 at 3:55 AM, Tom Collins t...@tomlogic.com [rabbit-semi]
wrote:
> As Gustavo mentioned, you can increase ROOT_SIZE_4K to 7 and gain some
> more space. Also, make sure you have "Separate Instruction & Data Space"
> enabled in the compiler options.
>
> You might want to check your MAP file to see what's taking up that root
> space. Consider moving any large globals you have into "far" memory.
> Dynamic C 10 is pretty good at working with far memory and not requiring
> you to copy things into root so you can use them.
>
> -Tom
> On Jul 17, 2016, at 8:16 PM, S Sutikno s...@gmail.com [rabbit-semi]
> wrote:
>
> Dear All,
>
> I'm use RCM6710 and DC10.72A also define MAX_FIRMWARE_BINSIZE=0x8000
> and ROOT_SIZE_4K=0x06.
> If i'm compile get error out of variable data space.
> Can anyone help me ?
> Thanks.
> Steve..
>
Stev
On Tue, Jul 19, 2016 at 3:55 AM, Tom Collins t...@tomlogic.com [rabbit-semi]
wrote:
> As Gustavo mentioned, you can increase ROOT_SIZE_4K to 7 and gain some
> more space. Also, make sure you have "Separate Instruction & Data Space"
> enabled in the compiler options.
>
> You might want to check your MAP file to see what's taking up that root
> space. Consider moving any large globals you have into "far" memory.
> Dynamic C 10 is pretty good at working with far memory and not requiring
> you to copy things into root so you can use them.
>
> -Tom
> On Jul 17, 2016, at 8:16 PM, S Sutikno s...@gmail.com [rabbit-semi]
> wrote:
>
> Dear All,
>
> I'm use RCM6710 and DC10.72A also define MAX_FIRMWARE_BINSIZE=0x8000
> and ROOT_SIZE_4K=0x06.
> If i'm compile get error out of variable data space.
> Can anyone help me ?
> Thanks.
> Steve..
>
