Help! The proven apps don’t work after migration from DSP/BIOS 4.90 to 5.33 and 5.41

Hi General Polar,

Can you also attach the projects that you have migrated?  I would like to compare them.

General Polar said:

I repeated the migration procedure for the proven demonstrations, including

Which migration procedure are you following? Is this coming from the integration workshop document? (apologies ahead of time ... but the software versions and hardware you are working on are very old and I am going to need to refresh my memory a bit here :)

General Polar said:

4. The example Chapter - 5 EDMA is not working under CCS3.3 and co-delivered DSP/BIOS 5_33_05: there is no output audio signal.
5. The example Chapter - 5 EDMA is not working under CCS4.2 and co-delivered DSP/BIOS 5_41_10_36: there is no output audio signal.

when you upgraded your CCS, in addition to upgrading your DSP/BIOS, it also installed newer versions of Code Generation Tools (compiler), XDC Tools and drivers.  Can you tell me the versions of these other tools that you have in CCS 3.3 and 4.2?  (you can find this by looking under help->about and then opening the component manager. The component manager allows you to see the available tools that CCS can use, as well as which ones are currently used (those will have a check mark next to them).

Thanks,

Steve

Hi Steve

OK, I’ve attached the already named project „Chapter5 – EDMA“ migrated to CCS3.3.

Steven Connell said:

Which migration procedure are you following?

For the CCS3.3 projects the cdb->tcf conversion procedure is automated, I simply used it.
For the CCS4.2 I have to use the cdb2tcf utility manually.

For the CCS3.3 they are:
            CCS     3.3.81.11
             IDE     5.98.0.393
            CGT     6.1.15
   DSP/BIOS     5.33.01
            XDC     3.00.06
      SD Emu     3.03.30

For the CCS4.2 they are:
            CCS     4.2.4.00033
             IDE     4.0.0.201106061600
            CGT     7.0.5
   DSP/BIOS     5.41.10.36
            XDC     3.20.08.88
      SD Emu     4.2.3.02

Thanks,

GP

GP,

What is the file "EDMA_project.tcf"? Is this the configuration you are using for your project?

I noticed that several speeds are different in EDMA_project.cdb (which is generated as a result of EDMA_project.tcf).  See the below screen shot of the difference report.

I suspect that in your original .cdb file, these speeds were the same as those on the left hand side in the screen shot.  I suspect the values on the right hand side are coming out of the dsk6416 platform file.

I also noticed that the c6416.cdb has different memory segments defined.

Did you try to use the c6416.tcf file?

Steve

7506.report.html

Hi Steve,

Steven Connell said:

What is the file "EDMA_project.tcf"? Is this the configuration you are using for your project?

Sorry Steve, I've forgot to notice about. The file produced after automatic conversion of the original c6416.cdb file is the c6416.tcf. EDMA_project.tcf I've built myself from scratch. Unfortunately the both of variants are not working.

Steven Connell said:

I also noticed that the c6416.cdb has different memory segments defined.

Thanks

GP

General Polar said:

I don't see any differences in memory segments in the report. What a tool did you use for this?

I just diffed the two map files.  Please see the below screen shot:

7002.mapdiff.html

General Polar,

I think at this point the best bet would be to try a process of elimination, in order to determine which component is causing a problem.  Since there are several variables that have changed between upgrades, I think you should try changing each of these variables one at a time.

Let's start with this problem:

General Polar said:

4. The example Chapter - 5 EDMA is not working under CCS3.3 and co-delivered DSP/BIOS 5_33_05: there is no output audio signal.

            CCS     3.3.81.11
             IDE     5.98.0.393
            CGT     6.1.15
   DSP/BIOS     5.33.01
            XDC     3.00.06
      SD Emu     3.03.30

I suggest as a first step, to build the app in CCS 3.3 using the same components as you used in CCS3.1 with DSP/BIOS 4.90 (not sure what other components were in original working example.

So, for example start with:

A) Only CCS variable changed:

           CCS     3.3.81.11
            CGT     (same version as CCS 3.1 working case)
   DSP/BIOS     (same version as CCS 3.1 working case)
            XDC     (same version as CCS 3.1 working case)
      SD Emu     (same version as CCS 3.1 working case)

B) If the program works with the above change, then try changing CGT:

           CCS     3.3.81.11
            CGT     6.1.15
   DSP/BIOS     (same version as CCS 3.1 working case)
            XDC     (same version as CCS 3.1 working case)
      SD Emu     (same version as CCS 3.1 working case)

C) If the above works, then try moving the BIOS version forward:

           CCS     3.3.81.11
            CGT     6.1.15
   DSP/BIOS     5.33.01
            XDC     (same version as CCS 3.1 working case)
      SD Emu     (same version as CCS 3.1 working case)

D) ... And so on ...

This will allow you to see which of the variables is the cause of the problem.

Steve

Hi Steve,

Steven Connell said:

I think at this point the best bet would be to try a process of elimination, in order to determine which component is causing a problem.  Since there are several variables that have changed between upgrades, I think you should try changing each of these variables one at a time.

Steven Connell said:

I suggest as a first step, to build the app in CCS 3.3 using the same components as you used in CCS3.1 with DSP/BIOS 4.90 (not sure what other components were in original working example.

thanks, good idea. But following my logic, I would begin from a working example – using CCS3.1 and updating every component step-by-step. This way I have fewer problems with potential backwards compatibility issues and accessibility of old CCS3.1 components.  I can’t download e.g. the CGT and DSP/BIOS versions lower than 5.1.6 and 5.20, having in the CCS3.1 5.1.0 and 4.90.02.10 correspondingly.

I’m only on one point not sure: whether the CCS3.1 will be upwards compatible with the DSP/BIOS 5.33, since DSP/BIOS 4.90 and 5.33 have different CSL connections mechanisms?

GP

General Polar said:

using CCS3.1 and updating every component step-by-step.

sure, that method of eliminating variables should work just as well.

General Polar said:

I can’t download e.g. the CGT and DSP/BIOS versions lower than 5.1.6 and 5.20, having in the CCS3.1 5.1.0 and 4.90.02.10 correspondingly.

I don't think you need to download anything.  It sounds like you have all of the necessary versions of BIOS and CGT, however you would just need to make sure you are pointing to the correct versions from your CCSv 3.1 build environment.

General Polar said:

I’m only on one point not sure: whether the CCS3.1 will be upwards compatible with the DSP/BIOS 5.33, since DSP/BIOS 4.90 and 5.33 have different CSL connections mechanisms?

As far as I know, BIOS 5.33 should work in CCSv3.1.