Dear Aneesh,
In message 7f771c64c5c44208b24e38c75e159f28@DM2PR03MB415.namprd03.prod.outlook.com you wrote:
Sorry for the misleading statement. Yes, CONFIG_SYS_RAMBOOT is for booting from RAM directly and we have used it for the same purpose in the patch. Let me try and explain.
Mind the "directly" in this sentence, and no, you have not used it in this way.
What I meant is that for P1010 like platforms for normal (non-secure) boot in case of NAND, we don't use the CONFIG_SYS_RAMBOOT as we don't boot from RAM directly in this case.
You also do not boot directly from RAM in the secure case.
However in case of secure boot, even for NAND, we boot from RAM directly with boot ROM (ISBC) code copying the image from NAND to RAM. So in P1010RDB.h config file, for NAND Secure boot, we have
This is NOT a RAM boot. This is a completely normal boot process from NAND. You must not declare this as RAM booting, as it is NOT.
defined CONFIG_RAMBOOT_NAND and then further are enabling CONFIG_SYS_RAMBOOT for the same.
This is wrong. You have the ROM boot loader booting from NAND and not from RAM.
The name CONFIG_RAMBOOT_NAND is an oxymoron in itself (and it's undocumented as well). This should be fixed, as it makes no sense.
You cannot "RAM-boot form NAND" - you can always boot from a single boot device only - either NOR or NAND or SDCard or ... or RAM.
Best regards,
Wolfgang Denk