Post Go back to editing

ADZS-SC573-EZLITE observations and questions

Category: Software
Product Number: ADSP-SC573
Software Version: CCES 3.0.3

Following up on an earlier "getting started" question. I'm attempting to use the demo project to get some basic audio processing working.

Using CCES 3.0.3 I built and loaded the application from C:\Analog Devices\SigmaStudioPlus-Rel2.4.0\Target\Examples\DemoUc\ADSP-SC57x. As expected, this performs an audio passthrough between the coax inputs and outputs.

Using SigmaStudio+ 2.4.0, I opened the "Example for ADSP-SC5xx Dual SH Core Demo uC application". The first issue I had was that the download verification failed. I probed the SPI lines from the USBi and discovered that the MISO and MISO lines were being pulled low by the EZLITE. The cause was a bug in the demo CCES project: The SoftConfig (which uses TWI to enable/disable I/O configurations on the EZLITE board) had pushbuttons 1 and 2 enabled. This conflicted with the SPI1 MOSI/MISO signals. Altering the SoftConfig to disable the pushbuttons allowed the download to succeed.

  

/*
U48 Port A U48 Port B

7--------------- ~FLG3_LOOP | 7--------------- Not Used
| 6------------- ~FLG2_LOOP | | 6------------- Not Used
| | 5----------- ~FLG1_LOOP | | | 5----------- Not Used
| | | 4--------- ~FLG0_LOOP | | | | 4--------- AD2410_MASTER_SLAVE
| | | | 3------- ~LEDs_EN | | | | | 3------- ~ENGINE_RPM_OE
| | | | | 2----- ~PUSHBUTTON1_EN | | | | | | 2----- ~THUMBWHEEL_OE
| | | | | | 1--- ~PUSHBUTTON2_EN | | | | | | | 1--- ~ADAU1977_FAULT_RST_EN
| | | | | | | 0- ~PUSHBUTTON3_EN | | | | | | | | 0- ~ADAU1977_EN
| | | | | | | | | | | | | | | | |
N N N N Y N N N | X X X Y N Y N Y ( Active Y or N )
1 1 1 1 0 1 1 1 | 1 1 1 1 1 0 1 0 ( value being set )
*/
{ 0x12u, 0xF7u }, { 0x13u, 0xFAu },

Now that I'm able to download schematics, I'm trying to get the demo canvas working. I've made the following changes to the SigmaStudio project:

  • Changed the target processor to "ADSP-SC573"
  • Configured the DXE files for the SHARC cores
  • Set the CCES version to v3.0.3

After compile/link/download, the audio passthrough completely stops working. Should this demo be expected to work "out of the box" or do I need to perform SPORT configuration changes or other alterations to the project? Perhaps you have an existing SigmaStudio project that is known to work with the SC573 demo?

Some other general questions:
 - Why are the DXE files necessary for SigmaStudio? Is this so the memory map can be obtained, or some other reason?
 - Are you aware that building the CCES demo app with the "Debug" profile doesn't work? The SHARC1 core asserts following the "adi_ss_fw_Init" call. Guessing this is an optimization issue.
 - Presuming I can get the demo working, what would be your recommended "next steps" for integrating SigmaStudio with an existing CCES project's audio path? Just looking for some general direction.

Many thanks!

Parents
  • Hi,

    When it comes to the ADSP-SC573 DemoUc example, the application, by default, is designed for audio module tuning using the EZLITE on-board push buttons (for Mute Enable/Disable and Filter Enable/Disable). However, if you want to perform tuning from the SigmaStudio+ UI, as you mentioned, you need to disable the push buttons in the softconfig file and use the Link-Compile-Connect option from the UI.

    If you want to test this application in Debug mode, you will need to regenerate the source files (please refer to the Microcontroller Mode Support [Analog Devices Wiki] link for steps to regenerate source files), since the existing ones were generated using the “Release” mode DXEs available with the installation package as reference.

    All the example applications (Demo, DemoUc, and LibraryIntegration) provided with the installation package can be run straight out of the box in Release mode. Except for DemoUc (which requires regeneration of source files in Debug mode), the Demo and LibraryIntegration examples can be run as-is in either Release or Debug mode.

    If you just want to run an existing example and test the SigmaStudio+ functionality on the ADSP-SC573 board, you can use the Demo application available at the installation path: "C:\Analog Devices\SigmaStudioPlus-Relx.x.x\Target\Examples\Demo\ADSP-SC57x\ADSP-SC573". Run the application in CCES (in either Release or Debug mode). The application will wait for the SMAP information from the SigmaStudio+ UI. Specify the DXE path in the SS+ schematic settings, and upon downloading the schematic to the target using the USBi, audio output can be observed and runtime tuning can also be performed.
    Please refer to the Load Application using CCES [Analog Devices Wiki] -> ADSP-SC573 / ADSP-SC584 / ADSP-SC589 / ADSP-SC594 Target section for more details on running the ADSP-SC573 Demo application.

    "Why are the DXE files necessary for SigmaStudio? Is this so the memory map can be obtained, or some other reason?"
    -> Please refer to the Global Memory Map (GMAP) and Schematic Memory Map (SMAP) sections in the System Integration [Analog Devices Wiki] link to understand more about why DXEs are required for SigmaStudio+.

    Let us know if you face any further issues after checking out the Demo application.

Reply
  • Hi,

    When it comes to the ADSP-SC573 DemoUc example, the application, by default, is designed for audio module tuning using the EZLITE on-board push buttons (for Mute Enable/Disable and Filter Enable/Disable). However, if you want to perform tuning from the SigmaStudio+ UI, as you mentioned, you need to disable the push buttons in the softconfig file and use the Link-Compile-Connect option from the UI.

    If you want to test this application in Debug mode, you will need to regenerate the source files (please refer to the Microcontroller Mode Support [Analog Devices Wiki] link for steps to regenerate source files), since the existing ones were generated using the “Release” mode DXEs available with the installation package as reference.

    All the example applications (Demo, DemoUc, and LibraryIntegration) provided with the installation package can be run straight out of the box in Release mode. Except for DemoUc (which requires regeneration of source files in Debug mode), the Demo and LibraryIntegration examples can be run as-is in either Release or Debug mode.

    If you just want to run an existing example and test the SigmaStudio+ functionality on the ADSP-SC573 board, you can use the Demo application available at the installation path: "C:\Analog Devices\SigmaStudioPlus-Relx.x.x\Target\Examples\Demo\ADSP-SC57x\ADSP-SC573". Run the application in CCES (in either Release or Debug mode). The application will wait for the SMAP information from the SigmaStudio+ UI. Specify the DXE path in the SS+ schematic settings, and upon downloading the schematic to the target using the USBi, audio output can be observed and runtime tuning can also be performed.
    Please refer to the Load Application using CCES [Analog Devices Wiki] -> ADSP-SC573 / ADSP-SC584 / ADSP-SC589 / ADSP-SC594 Target section for more details on running the ADSP-SC573 Demo application.

    "Why are the DXE files necessary for SigmaStudio? Is this so the memory map can be obtained, or some other reason?"
    -> Please refer to the Global Memory Map (GMAP) and Schematic Memory Map (SMAP) sections in the System Integration [Analog Devices Wiki] link to understand more about why DXEs are required for SigmaStudio+.

    Let us know if you face any further issues after checking out the Demo application.

Children
No Data