How to change the 25MHz crystal input for SHARC

Hi,

    I use SC573 processor and CCES 2.8.2, since I want to generate 48KHz sample rate, I use 24.576MHz crystal  instead of 25MHz crystal, so it seem that my project need to be modified.

    I find the init code in the CCES installation directory, the path is "C:\Analog Devices\CrossCore Embedded Studio 2.8.2\SHARC\ldr\init_code\SC57x_Init", there are two projects named sc573_init_Core0 and sc573_preload_Core0, my questions are list below

    1. What's deffirences between the init code and preload code? What should I use in my project?

    2. How to modify the init code or preload code to match the 24.576MHz crystal?

    3. Besides the init code, Is there any other attentions in my own project when I change the crystal?

    Thanks!

Parents
  • +1
    •  Analog Employees 
    on Dec 31, 2020 12:42 PM 2 months ago

    Hi,

    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 theADSP-SC5xx processors, which are equivalent to init codes, but used during the debugging phase of development.

    I would recommend you to refer the below FAQ for more information about how to create/modify the preload program and .ld file for the custom target on ADSP-SC5XX:
    FAQ: Preload code customization
    https://ez.analog.com/dsp/sharc-processors/adsp-sc5xxadsp-215xx/w/documents/5045/faq-preload-code-customization


    Also refer the below CCES help path:
    CrossCore® Embedded Studio> Integrated Development Environment > Debugging Targets > Debugging ADSP-SC5xx SHARC+ and ARM Projects > About Preload Files

    Regards,
    Anand Selvaraj.

Reply
  • +1
    •  Analog Employees 
    on Dec 31, 2020 12:42 PM 2 months ago

    Hi,

    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 theADSP-SC5xx processors, which are equivalent to init codes, but used during the debugging phase of development.

    I would recommend you to refer the below FAQ for more information about how to create/modify the preload program and .ld file for the custom target on ADSP-SC5XX:
    FAQ: Preload code customization
    https://ez.analog.com/dsp/sharc-processors/adsp-sc5xxadsp-215xx/w/documents/5045/faq-preload-code-customization


    Also refer the below CCES help path:
    CrossCore® Embedded Studio> Integrated Development Environment > Debugging Targets > Debugging ADSP-SC5xx SHARC+ and ARM Projects > About Preload Files

    Regards,
    Anand Selvaraj.

Children
No Data