• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 800 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/BEAGLEBK: NAND partition issue

Lior Yaron Benjamin
Prodigy 170 points
Part Number: BEAGLEBK
Other Parts Discussed in Thread: AM3352

Tool/software: Linux

Hi.
I used to use AM3352 GPMC NAND support over Var-Som board (from Variscite), and it all worked correctly. This board used kernel version 4.4.19

Now, I've switched to BeagleBone black, which uses 4.14.65, and the omap-nand support seems to be changed.

I managed to connect the NAND and have a correct identification phase (manufacture ID and stuff), but, it seems that the partitiong stage doesn't go well.... and no partition is created (I am trying to create the partitions through the device tree, and I copied the same paritions configurations that worked with the Var-Som board...

Could you please guide me how to have these partitions created?

here's my device-tree:

&am33xx_pinmux {
	bbcape_nand_flash_pins: bbcape_nand_flash_pins {
		pinctrl-single,pins = <
			0x00 (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad0.gpmc_ad0 */
			0x04 (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad1.gpmc_ad1 */
			0x08 (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad2.gpmc_ad2 */
			0x0c (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad3.gpmc_ad3 */
			0x10 (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad4.gpmc_ad4 */
			0x14 (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad5.gpmc_ad5 */
			0x18 (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad6.gpmc_ad6 */
			0x1c (MUX_MODE0 | PIN_INPUT_PULLUP)	/* gpmc_ad7.gpmc_ad7 */
			0x70 (MUX_MODE0 | PIN_INPUT_PULLUP )	/* gpmc_wait0.gpmc_wait0 */
			0x74 (MUX_MODE0 | PIN_OUTPUT_PULLUP)	/* gpmc_wpn.gpmc_wpn */
			0x7c (MUX_MODE0 | PIN_OUTPUT_PULLUP)	/* gpmc_csn0.gpmc_csn0  */
			0x90 (MUX_MODE0 | PIN_OUTPUT)		/* gpmc_advn_ale.gpmc_advn_ale */
			0x94 (MUX_MODE0 | PIN_OUTPUT)		/* gpmc_oen_ren.gpmc_oen_ren */
			0x98 (MUX_MODE0 | PIN_OUTPUT)		/* gpmc_wen.gpmc_wen */
			0x9c (MUX_MODE0 | PIN_OUTPUT)		/* gpmc_be0n_cle.gpmc_be0n_cle */
		>;
	};
};

&elm {
	status = "okay";
};

&gpmc {
  status = "okay";
	ranges = <0 0 0x01000000 0x10000000>;	/* address range = 16MB (minimum GPMC partition) */
  nand@0,0 {
    compatible = "ti,omap2-nand";
		reg = <0 0 4>;		/* device IO registers */
		pinctrl-names = "default";
		pinctrl-0 = <&bbcape_nand_flash_pins>;
		ti,nand-ecc-opt = "bch8";
		ti,elm-id = <&elm>;
		/* generic bindings */
		nand-bus-width = <8>;
		/* vendor specific bindings */
		gpmc,device-width = <2>;
		gpmc,sync-clk-ps = <0>;
		gpmc,cs-on-ns = <0>;
		gpmc,cs-rd-off-ns = <80>;
		gpmc,cs-wr-off-ns = <80>;
		gpmc,adv-on-ns = <0>;
		gpmc,adv-rd-off-ns = <80>;
		gpmc,adv-wr-off-ns = <80>;
		gpmc,we-on-ns = <20>;
		gpmc,we-off-ns = <60>;
		gpmc,oe-on-ns = <20>;
		gpmc,oe-off-ns = <60>;
		gpmc,access-ns = <40>;
		gpmc,rd-cycle-ns = <80>;
		gpmc,wr-cycle-ns = <80>;
		gpmc,wait-pin = <0>;
		gpmc,wait-on-read;
		gpmc,wait-on-write;
		gpmc,bus-turnaround-ns = <0>;
		gpmc,cycle2cycle-delay-ns = <0>;
		gpmc,clk-activation-ns = <0>;
		gpmc,wait-monitoring-ns = <0>;
		gpmc,wr-access-ns = <40>;
		gpmc,wr-data-mux-bus-ns = <0>;
		/* 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 0x00040000>;
		};
		partition@1 {
			label = "NAND.SPL.backup1";
			reg = <0x00040000 0x00040000>;
		};
		partition@2 {
			label = "NAND.SPL.backup2";
			reg = <0x00080000 0x00040000>;
		};
		partition@3 {
			label = "NAND.SPL.backup3";
			reg = <0x000c0000 0x00040000>;
		};
		partition@4 {
			label = "NAND.u-boot-spl-os";
			reg = <0x00100000 0x00080000>;
		};
		partition@5 {
			label = "NAND.u-boot";
			reg = <0x00180000 0x00100000>;
		};
		partition@6 {
			label = "NAND.u-boot-env";
			reg = <0x00280000 0x00040000>;
		};
		partition@7 {
			label = "NAND.u-boot-env.backup1";
			reg = <0x002c0000 0x00040000>;
		};
		partition@8 {
			label = "NAND.kernel";
			reg = <0x00300000 0x00700000>;
		};
		partition@9 {
			label = "NAND.file-system";
			reg = <0x00a00000 0x1f600000>;
		};
	};
};

Thanks.

  • 0
    TI__Guru**** 393215 points
    Hi,

    The latest Linux SDK release by TI is kernel v4.14.40. If you are using the Debian image which comes with BBB boards, this is not supported by TI, and you should direct your questions to www.beagleboard.org
  • 0 in reply to Biser Gatchev-XID
    Prodigy 170 points

    Thanks for your reply.

    Comparing omap2.c files between the two versions, seems to be identical, handling the partitions, so I guess the same issue would appear there.
    Is there any documentation for tha changes in omap2.c partitions creation between 4.4 to 4.14?

  • 0 in reply to Lior Yaron Benjamin
    Prodigy 170 points

    Now looking at v4.14.40 again, I see that the MTD partition is identical .

    In  omap_nand_probe (file: driver/mtd/nand/omap2.c), the partitions are created in second phase scan, by calling:

    #define mtd_device_register(master, parts, nr_parts)	\
	mtd_device_parse_register(master, NULL, NULL, parts, nr_parts)

    	err = nand_scan_tail(mtd);
	if (err)
		goto return_error;


	if (dev->of_node) //
		mtd_device_register(mtd, NULL, 0);
	else
		mtd_device_register(mtd, pdata->parts, pdata->nr_parts);

    While on earlier version:

    	if (nand_scan_tail(mtd)) {
		err = -ENXIO;
		goto return_error;
	}

	if (dev->of_node) {
		ppdata.of_node = dev->of_node;
		mtd_device_parse_register(mtd, NULL, &ppdata, NULL, 0);

	} else {
		mtd_device_register(mtd, pdata->parts, pdata->nr_parts);
	}

    Since mtd_device_parse_register was not changed dramtatically, it seems that the exact of_node for the partition creation, is missing.
    What am I missing?

  • 0 in reply to Lior Yaron Benjamin
    TI__Mastermind 30726 points
    What failure are you seeing? Why do you say the partitions are not being created?

    The am335x-evm.dtb file shipped in the kernel/arch/arm/boot/dts has a good example for NAND. The timing parameters may need to be optimized for your specific situation.

    One thing I notice as a difference between the two is that your pinctrl is inside the NAND node, while the example puts this inside the GPMC node.

    I hope this is helpful.
  • 0 in reply to RonB
    Prodigy 170 points

    Hi Ron.

    Thanks for you reply.
    I already overcome the issue. It wasn't a failure, it was just a part of code that I expected to be executed, to create partitions over external NAND, that was not executed.
    Apparently, I missed some defines in the .config file, that I was sure are enabled with the NAND itself (CONFIG_MTD_CMDLINE_PARTS & CONFIG_MTD_OF_PARTS)

    Thanks again.