4 Replies Latest reply on Nov 16, 2020 9:53 PM by MoTa_728816

    How can we avoid symbol corruption with UDB I2S?

    MoTa_728816

      Hi,

       

      We need to add another I2S component.

      So I followed the KBA229971

      Import UDB-based I2S Component in a PSoC 6 MCU Project (PSoC Creator) – KBA229971

       

      And I could manage to generate an I2S v2.70 in UDB

      001-original.JPG

       

      But as I don't want to corrupt this project, I duplicated the project using Copy and Paste

      002-copy_1.JPG

      Then I tried to rename the project something else

      003-renaming_copy_1.JPG

       

      After the project was renamed, the symbol of I2S component does not seem to be happy.

      004-symbol_broken.JPG

       

      I think that probably I missed something in the KBA or some additional protection/modification is required for the component.

       

      Could someone teach us how to avoid or fix this problem?

       

      moto

        • 1. Re: How can we avoid symbol corruption with UDB I2S?
          DheerajK_81

          Hello MoTa_728816,

           

          Since the project contains additional components like the UDB Based I2S, when you copy and paste the project, you would have received the following prompt:

           

          Please click "Yes". The component should work correctly without any problems. Let me know your observations

           

          Regards,

          Dheeraj

          • 2. Re: How can we avoid symbol corruption with UDB I2S?
            MoTa_728816

            Dear Dheeraj-san,

             

            Thank you very much for your answer.

            I have tried the following to confirm the result.

             

            (1) Started the previous project

            Note: This symbol was corrupted in my previous post, but somehow it recovered...

            010-Original.JPG

            (2) I copied the project

            011-Copy.JPG

            (3) I pasted the project

            012-Paste.JPG

            (4) Here, the dialog window you mentioned appeared.

            I answered "Yes"

            014-Yes-to_the_dialog.JPG

            (5) The project was duplicated OK.

            015-Procect_Copy_01.JPG

            (6) I renamed the project

            016-Rename.JPG

            (7) Now I get the symbol corrupted.

            017-Renamed.JPG

             

            (8) In my previous trials, I removed the corrupted project(s) to avoid corrupting other projects and the workspace.

            But this time I quitted PSoC Creator at this point.

             

            Then I got dialog asking if modified files should be saved.

            I selected "Yes"

            018-save-before-quit.JPG

            (9) I restarted PSoC Creator with same workspace and got the following dialog

            I selected "Yes"

            019-Restarting-the-creator-dilaog.JPG

             

            (10) Now the symbol which seemed to be corrupted at the step (7) seems to be OK.

            020-symbol-recovered.JPG

             

            So, my current conclusion is that after renaming the project,

            (9) type dialog must be presented and some internal process needs to be done.

            which does not take place automatically while I keep PSoC Creator running,

            but by restarting PSoC Creator, that dialog (and/or the service) will be invoked.

             

            This is not very elegant, but as far as with this knowledge/work around IMHO, this is acceptable.

            It would be nice, if the dialog also will be invoked when project renaming takes place, though.

            Or, I wonder if there is a way to explicitly start that dialog from PSoC Creator?

             

            Best Regards,

            17-Nov-2020

            Motoo Tanaka

            • 3. Re: How can we avoid symbol corruption with UDB I2S?
              DheerajK_81

              Hello MoTa_728816,

               

              That's a good observation. Thanks for the feedback. I will pass this on to the software team for evaluation.

               

              Glad to hear that the issue is resolved.

               

              Regards,

              Dheeraj

              • 4. Re: How can we avoid symbol corruption with UDB I2S?
                MoTa_728816

                Dear Dheeraj-san,

                 

                Since the first response could be misleading,
                I marked the last response as Correct Answer

                so that others will read the whole story.

                 

                Best Regards,

                17-Nov-2020

                Motoo Tanaka

                1 of 1 people found this helpful