This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/DRA725: UBI partition in NAND boot

Part Number: DRA725

Tool/software: Linux

Hi all:

I have a UBI partition table in NAND flash (256MB). The BOOTINFO is at the top of the UBI table and the other 6 partitions are behind the BOOTINFO. 

I also put bootload(IPL) in NAND flash too. It locates at the beginning of the NAND flash(0x00000000h).

After Linux launch on, I use "ubiattach" tool to make NAND flash accessible. I reboot again, I found I can launch on. And I found the bootloader was damaged.

I retry again, I found the bootloader will be okay if I didn't attach UBI partition.

Is that because the UBI partition and the bootloader were overlapped?

SDK ver. : J6_03_02_00_03

Jacky Wu

  • Hi
    can you share details about the UBI partition and how they are described in the kernel (via device tree vs command line)
  • Hi Srirama Govindarajan:

    Thanks for your help.

    Here is my UBI table.

    My device tree

    And I did some research these few days. I found the root cause of this situation might be the device tree partition.

    Is that the device tree partition overlap the bootloader? Any suggestion? 

    Thanks again.

    Jackie

  • Hi
    You can refer to the illustrative partition mapping table described in the device tree definition file for DRA72x - under arch/arm/boot/dts/dra72-evm-common.dtsi

    I have attached the snippet with the definition below for quick reference - you need to ensure your allocation matches with the table described in the device tree file

    /* MTD partition table */
    /* All SPL-* partitions are sized to minimal length
    * which can be independently programmable. For
    * NAND flash this is equal to size of erase-block */
    #address-cells = <1>;
    #size-cells = <1>;
    partition@0 {
    label = "NAND.SPL";
    reg = <0x00000000 0x000020000>;
    };
    partition@1 {
    label = "NAND.SPL.backup1";
    reg = <0x00020000 0x00020000>;
    };
    partition@2 {
    label = "NAND.SPL.backup2";
    reg = <0x00040000 0x00020000>;
    };
    partition@3 {
    label = "NAND.SPL.backup3";
    reg = <0x00060000 0x00020000>;
    };
    partition@4 {
    label = "NAND.u-boot-spl-os";
    reg = <0x00080000 0x00040000>;
    };
    partition@5 {
    label = "NAND.u-boot";
    reg = <0x000c0000 0x00100000>;
    };
    partition@6 {
    label = "NAND.u-boot-env";
    reg = <0x001c0000 0x00020000>;
    };
    partition@7 {
    label = "NAND.u-boot-env.backup1";
    reg = <0x001e0000 0x00020000>;
    };
    partition@8 {
    label = "NAND.kernel";
    reg = <0x00200000 0x00800000>;
    };
    partition@9 {
    label = "NAND.file-system";
    reg = <0x00a00000 0x0f600000>;
    };
  • Hi
    Can you confirm if your issue has been resolved. If not please post your reply below