Post Go back to editing

SigmaStudio+ is used in dual-core mode

Thread Summary

The user is experiencing crashes with the ADSP-21593 dual-core setup when using complex SigmaStudio+ schematics with many input audio channels. The support team provided a modified 16CH in/out dual-core example and suggested checking for MIPS overshoot, but the user noted that the issue persists even with 16 channels and 60% CPU usage. The user also requested a real-time online schematic download example, which the support team confirmed is not supported in the lib integration example and suggested using the Demo/DemoUC example instead.
AI Generated Content
Category: Software
Product Number: SigmaStudio+ & ADSP21593
Software Version: SigmaStudio+ 2.1.0, CCES 2.12.0

Hi Sir,

I need to use 21593 dual-core + SigmaStudio+, but I can't find any instructions and routines. I created a dual-core application based on "C:\Analog Devices\SigmaStudioPlus-Rel2.1.0\Target\Examples\LibraryIntegration\ADSP-21593". I have created two separate schematics using SigmaStudio+ and can download them. I have found that it works only when the schematic is simple or there are few input audio channels, but when the schematic becomes complex and there are many input audio channels, it would crashes. The CCES always displays "A parity error has been detected."  I checked the memory usage and it doesn't seem to overflow

Please help, thank you!

   

LibIntegrationExample_Core1.map.xml
LibIntegrationExample_Core2.map.xml

Parents
  • Hi,

    Could you please share your schematic for analyzing this issue.

    Thanks

  • Hi Chiru & Sakthivel,

    Any updates for this issue?

    Our schematics were so complex that one core could not run well enough. We urgently needed to use 21593's dual core. Please give us useful help, thank you.

  • Hi Jonny,
    We will check and get back to you, since your schematic having 48 Input/40 Output channels we need to make some modifications to the schematic to test on evaluation boards.

    whether your simple schematic worked with 48 Input/40 Output channels configuration? 
    Is my understanding correct that you are facing issue only when using complex schematic with more modules?
    Any idea what your schematic MIPS is?
    Since your schematic block size is set to 16 there could be a possibility for MIPS overshoot when running with 48 Input/40 Output channels.     

  • Hi Sakthivel,

    1. The schematic of attachment can work normally

    2, I checked the MIPS and it didn't overshoot 

    3, Our project has 48 input  & 40 output channel. In my test on EV board only 16 input /16 output channel is actually used. The attachment has the related configuration of Sport port, and the unused channel is not connected to the data input/output port through SRU

    4. Because there are too many input and output channels, if the block size is set to 64, it will consume more memory, so I try to set it to 32 and 16

    5, The audio process is as follows:

    Core1 Sport In (48CH) -> Core1 SS+ -> Out to Core2 (40CH) -> Core2 In(40CH) - >  Core2 SS+ -> Out to Core1(40CH) -> Core1 Sport Out(40CH)

    Attached is my test schematic and part of the source code for your reference.

    6354.Test.zip

Reply
  • Hi Sakthivel,

    1. The schematic of attachment can work normally

    2, I checked the MIPS and it didn't overshoot 

    3, Our project has 48 input  & 40 output channel. In my test on EV board only 16 input /16 output channel is actually used. The attachment has the related configuration of Sport port, and the unused channel is not connected to the data input/output port through SRU

    4. Because there are too many input and output channels, if the block size is set to 64, it will consume more memory, so I try to set it to 32 and 16

    5, The audio process is as follows:

    Core1 Sport In (48CH) -> Core1 SS+ -> Out to Core2 (40CH) -> Core2 In(40CH) - >  Core2 SS+ -> Out to Core1(40CH) -> Core1 Sport Out(40CH)

    Attached is my test schematic and part of the source code for your reference.

    6354.Test.zip

Children
No Data

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.