T1040 how to update vmalloc space

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

T1040 how to update vmalloc space

Jump to solution
2,230 Views
amoslin
Contributor I

We use t1040 and 256M nor flash, and we try to modify dts file for 256M nor flash.

We found the same question as bellow,

how to update vmalloc space in SDK 1.7

We try to modify kernel config, but linux kernel can't unpack rootfs image.

Log as attached.

Is there any problem?

Original Attachment has been moved to: t1040_vmalloc_failed.txt.zip

Labels (1)
0 Kudos
Reply
1 Solution
1,896 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Amos lin,

The problem is caused by your Kernel configuration, please configure "CONFIG_LOWMEM_SIZE=0x30000000". For PowerPC arch the Linux low memory size is configured as 0x30000000(768M), you specified a low memory space too small for Linux Kernel.


Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

View solution in original post

0 Kudos
Reply
4 Replies
1,896 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Amos li,

I built a Kernel image with the following Kernel configuration used to increase vmalloc space in Kernel, and verified it on T1040 platform, vmalloc space indeed increases after booting up the system by checking memory information.

Would you please provide your Kernel configuration?

# Advanced setup

#

CONFIG_ADVANCED_OPTIONS=y

# CONFIG_LOWMEM_SIZE_BOOL is not set

CONFIG_LOWMEM_SIZE=0x30000000

# CONFIG_LOWMEM_CAM_NUM_BOOL is not set

CONFIG_LOWMEM_CAM_NUM=3

# CONFIG_DYNAMIC_MEMSTART is not set

CONFIG_PAGE_OFFSET_BOOL=y

CONFIG_PAGE_OFFSET=0xa0000000

# CONFIG_KERNEL_START_BOOL is not set

CONFIG_KERNEL_START=0xa0000000

# CONFIG_PHYSICAL_START_BOOL is not set

CONFIG_PHYSICAL_START=0x00000000

CONFIG_PHYSICAL_ALIGN=0x04000000

CONFIG_TASK_SIZE_BOOL=y

CONFIG_TASK_SIZE=0xa0000000

CONFIG_NET=y


Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply
1,896 Views
amoslin
Contributor I

Hi Yiping,

Thank you for your reply.

configuration files as attached.

Amos

0 Kudos
Reply
1,897 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Amos lin,

The problem is caused by your Kernel configuration, please configure "CONFIG_LOWMEM_SIZE=0x30000000". For PowerPC arch the Linux low memory size is configured as 0x30000000(768M), you specified a low memory space too small for Linux Kernel.


Have a great day,
Yiping

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply
1,896 Views
amoslin
Contributor I

Hi Yiping Wang,

It worked, thank you for your help.

Amos

0 Kudos
Reply