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.

Keystone II EMIF NOR Flash Boot vs. BOOTCOMPLETE Assertion

With the C66 selected as the boot master on a 66AK2Hx device, does the BOOTCOMPLETE signal get asserted by the RBL for bootmode set to EMIF NOR Flash?

  • The BCx bit in the BOOTCOMPLETE register indicate the boot complete status of the corresponding C66x CorePac. All BCx bits are sticky bits —
    that is, they can be set only once by the software after device reset and they will be cleared to 0 on all device resets. Boot ROM code is implemented such that each C66x CorePac sets its corresponding BCx bit immediately before branching to the predefined location in memory.


    This concept applies to all boot modes including EMIF NOR flash.

    Regards,
    Rahul

  • Thank you, Rahul.

    Do all BCx bits need to be set to assert BOOTCOMPLETE? That is, are they AND'ed together to generate the BOOTCOMPLETE signal? Since SPRUGY5C states that no return to the RBL is expected for the EMIF16 boot mode, is the user's EMIF16 executable responsible for setting the BCx bits? Is any example code available for doing this?

    Thanks and Best Regards,

    David
  • The ROM will set a bit for each core in the boot complete register as it reaches boot exit. The boot complete signal is the logical AND of all of these bits. So in sleep mode the bit is never set, unless you write the boot magic address and then run through the boot rom.

    So the boot complete bit is not set until the master boot core has finished, and then every other core is woken up.

    Regards,
    Rahul