In the imx6ul-evk,Why is the boot partition so large?

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

In the imx6ul-evk,Why is the boot partition so large?

1,115 Views
zhangbin_eos
Contributor III

The BSD is fsl-yocto-L4.1.15_2.0.0

In the u-boot env 

mtdparts=gpmi-nand:64m(boot),16m(kernel),16m(dtb) .....

Why is the boot partition so large? And then I fix it to be :

mtdparts=gpmi-nand:16m(boot),16m(kernel),16m(dtb) .....

When I use mfgtool to burn uboot, kobs-ng tell me :

mtd: bootstream too large

Can I change the size of boot partition ? How should I do ?

Labels (2)
0 Kudos
7 Replies

977 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Hi,

The partitions are defined in "include/configs/mx6ul_14x14_evk.h" file, CONFIG_MFG_NAND_PARTITION .

If you want to change the partitions,  changing CONFIG_MFG_NAND_PARTITION

Ex :

      #define CONFIG_MFG_NAND_PARTITION "mtdparts=gpmi-nand:64m(boot),16m(kernel),16m(dtb),50m(rootfs), -(data) "

And you also need generated u-boot.imx in "Firmware" folder of MFG tool.

Hope this can do help for you

Have a nice day

Rita

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

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos

977 Views
zhangbin_eos
Contributor III

Hi,Rita

Thank you response.

I fix the partitions as 

mtdparts=gpmi-nand:16m(boot),16m(kernel),16m(dtb) .....

Then I get errors when I writing with MFG tool,I want to know . If I want to change "64m (boot)" to "16m (boot)", what should I do?

0 Kudos

977 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Which error you meet ? Could you show it ?

0 Kudos

977 Views
zhangbin_eos
Contributor III

just like 

root@imx6ulevk:/nandflash# kobs-ng init -v u-boot.imx
MTD CONFIG:
chip_0_device_path = "/dev/mtd0"
chip_1_device_path = "(null)"
search_exponent = 2
data_setup_time = 80
data_hold_time = 60
address_setup_time = 25
data_sample_time = 6
row_address_size = 3
column_address_size = 2
read_command_code1 = 0
read_command_code2 = 48
boot_stream_major_version = 1
boot_stream_minor_version = 0
boot_stream_sub_version = 0
ncb_version = 3
boot_stream_1_address = 0
boot_stream_2_address = 0
u-boot.imx: verifying using key '00000000000000000000000000000000'
u-boot.imx: is a valid bootstream for key '00000000000000000000000000000000'
mtd: use new bch layout raw access mode
mtd: opening: "/dev/mtd0"
NFC geometry :
ECC Strength : 40
Page Size in Bytes : 8762
Metadata size : 10
ECC Chunk Size in byte : 1024
ECC Chunk count : 8
Block Mark Byte Offset : 7692
Block Mark Bit Offset : 0
====================================================
mtd: opened '/dev/mtd0' - '(null)'
mtd: bootstream too large
mtd_init failed!

0 Kudos

977 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

https://community.nxp.com/thread/324550 

You can refer to this thread. Hope this can do some help for you.

0 Kudos

977 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

You can try to modify the mksdcard.sh.tar.

0 Kudos

977 Views
zhangbin_eos
Contributor III

i used nandflash 

0 Kudos