Post Go back to editing

Unable to Process "Butterworth / Chebyshev Filter" and "2nd Order Index Selectable" module in Sigma Studio Plus

Category: Software
Software Version: CCES-2.9.1, Sigma Studio+-2.1.0

Hi Team,


I have a source code integrated with the Sigma Studio Plus functionality along with our decoders (referred the ADSP21569 LibIntegrationExample code). In the adi_ss_app.ldf only SSn code segments is mapped to L1 memory remaining all segments are mapped to L3 segment due to memory constrains.

At runtime, while debugging with "Filter-> IIR -> High Order Filters -> Butterworth / Chebyshev Filter" and "Filter-> IIR ->Lookup -> 2nd Order Index Selectable" module in SS+ GUI the code gets halt at adi_ss_schematic_process function and unable to process further. I haven't faced issues with any other modules in SS+ Schematic.

As per our understanding these two modules are taking Data48 in the memory (referred in SS+ GUI Memory window).

Let me know this issue is related to extended precision memory mapping, if related is there any specification for using the extended precision memory segment.

Kindly help us to overcome this issue.

Thanks,

Sundari

  • are mapping State and parameter all memory sections mapped to L3?

  • Yes, other than SSN code (Code A) remaining all memory sections are mapped in L3 memory.

    At runtime, while debugging with "Filter-> IIR -> High Order Filters -> Butterworth / Chebyshev Filter" and "Filter-> IIR ->Lookup -> 2nd Order Index Selectable" module in SS+ GUI the code gets halt at adi_ss_schematic_process function and unable to process further. (refer the below image)

     


    Thanks,

    Sundari

  • Are you facing this issue in design mode application or only in deployment mode? 
    are facing this issue even in testing only with this particular module  using L1 or only in L3?

    Please try enabling cache memory when you are using L3 memory. 
    Please let us know if you are facing issue even after enabling cache.

  • Ques1: Facing this issue in both Design and Deployment mode.
    Ques2,3: The module Data and Param memory section are mapped in L3 and its a cache memory region.

  • I tried mapping the extended precision memory segment in L1 block3 segment. As I have decoder contents and the data buffers mapped in L1 block 3, I still faced the same issue.
    Then tried to map only the extended precision memory segment in L1block 3 by moving all other decoder and data contents to some other memory I can sort out this issue.

    Is there any limitation to place the extended precision memory segment in separate block without any decoder contents and data buffers? 
    I have the requirement to map the extended precision in L3 is there any memory segments that support extended precision (Data 48)?

    Note: When moving the extended precision memory segment to "L3" Butterworth/ chebyshev Filter and 2nd order Index Selectable is not working, but other modules are working fine.

  • We set the memory as per your requirement itself and tried it, but we didn't face any issue as you mentioned.

    Based on your requirement, you are only keeping the SSn Code segments in L1 and moved the rest of the data and parameters to L3 memory.

    We believe you made the following changes in SigmaStudioPlus schematic section map settings (Host side) as shown below:

    Section Map Settings

    By keeping Code Memory section in Code (L1) itself and moving all other State Memory Sections to State C (L3).

    The only change you have to do in target side is in adi_ss_app.ldf file as shown below for Parameter memory mapping:

    Parameter memory mapping

    Increase the size of the block by varying the _Block2_L1_space_length based on your requirement (please consider the value 10240 as an example alone).

    By making the above changes, we were able to process the schematic containing both Butterworth/Chebyshev Filter and 2nd Order Index Select modules.

  • Hi,

    Thanks for your response.

    PCM streams are working fine even without any modification, facing issue with Decoder streams only.
    As per your above response I still can't solve the issue.

    In my code I have few decoder contents and sport DMA buffer mapped in Block3.I have tried few more modifications and have few observations.

    Observation 1: Mapped the Extended precision memory segment in "Block3" L1 memory.
    Moved the Sport DMA buffer to "Block2" L1 memory. The Butterworth/ chebyshev Filter and 2nd order Index are working fine with all decoder streams.

    Note: Code breaks when the extended precision and sport DMA buffers are mapped in "Block3" L1 memory.

    Observation 2: Mapped the Extended precision memory segment in L3 memory.
    Moved the Sport DMA buffer to Block2 L1 memory. The Butterworth/ chebyshev Filter and 2nd order Index are working but noisy output with all decoder streams.

    Note: Code breaks when the extended precision is mapped in L3 memory and sport DMA buffers are mapped in "Block3" L1 memory.

    Ques1: Is there any other changes has to be done to get proper output while mapping the extended precision segment in L3?
    Ques2: Is there any limitation that Sport DMA buffer should not be mapped in "Block3" L1 memory while using extended precision?


    Kindly help me to sort this issue.

    Thanks,

    Sundari

  • SigmaStudio can't process the encoded streams. You need to decode the streams and send PCM data to SigmaStudio schematic processing.

  • Hi,

    As per my code I have decoders for processing the streams.
    I have already mentioned before, that in my source code I have integrated the Sigma Studio Plus functionality along with our decoders.
    At runtime, while debugging with "Butterworth / Chebyshev Filter" and "2nd Order Index Selectable" module in SS+ GUI, the code gets halt at "adi_ss_schematic_process function" and unable to process further.

    I haven't faced issues with any other modules in SS+ Schematic with Decoder Streams and PCM streams.

    Consider the above-mentioned observations and help me to sort the issue.

    Thanks,

    Sundari

  • Could you please try increasing the stack memory allocated for your application and let me know the status?