Post Go back to editing

What is the difference between init and preload?

I would like to know what the difference is between init and preload?

I have compared the init and preload projects from EE-387. I can't find a file difference only that main.c is excluded from the init build. Why is main.c excluded?

Parents
  • Hi,

    Our sincere apologies for the delayed response. Unfortunately, we missed this thread to address on time.

    Preload codes are equivalent to initcodes, but used during the debugging phase of development, whereas initcode is used for booting purpose.

    In most applications, the CGU and DMC initialization is only done once after the power-up. This can be done with the help of “preload” code (when loading the application via emulator) or “init” code (when loading the application via booting). The CCES installation provides the “preload” and “init” code sources and dxes for the default CGU/DMC settings which can be modified as per the customized system requirements.

    CCES 2.0.0 (and later) supports the concept of preload files for the ADSP-SC5xx processors.

    For more information,please refer in CCES help:
    CrossCore® Embedded Studio 2.x.x > Integrated Development Environment > Debugging Targets > Debugging ADSP-SC5xx SHARC+ and ARM Projects > About Preload Files

    CrossCore® Embedded Studio 2.x.x > Blackfin® Development Tools Documentation > Loader and Utilities Manual > Loader for ADSP-SC5xx/ADSP-215xx Multicore Processors > ADSP-SC5xx/ADSP-215xx Loader Collateral

    Regards,
    Nishanthi. V

Reply
  • Hi,

    Our sincere apologies for the delayed response. Unfortunately, we missed this thread to address on time.

    Preload codes are equivalent to initcodes, but used during the debugging phase of development, whereas initcode is used for booting purpose.

    In most applications, the CGU and DMC initialization is only done once after the power-up. This can be done with the help of “preload” code (when loading the application via emulator) or “init” code (when loading the application via booting). The CCES installation provides the “preload” and “init” code sources and dxes for the default CGU/DMC settings which can be modified as per the customized system requirements.

    CCES 2.0.0 (and later) supports the concept of preload files for the ADSP-SC5xx processors.

    For more information,please refer in CCES help:
    CrossCore® Embedded Studio 2.x.x > Integrated Development Environment > Debugging Targets > Debugging ADSP-SC5xx SHARC+ and ARM Projects > About Preload Files

    CrossCore® Embedded Studio 2.x.x > Blackfin® Development Tools Documentation > Loader and Utilities Manual > Loader for ADSP-SC5xx/ADSP-215xx Multicore Processors > ADSP-SC5xx/ADSP-215xx Loader Collateral

    Regards,
    Nishanthi. V

Children
No Data