LAUNCHXL-F280039C: TIDM_02002 with DSP tms320F28004x migrating to tms320F280039C

Hi,

Can you tell us more about the errors shown in CCS?

Best,

John

this is the error

llibc.a

>> Compilation failure
makefile:164: recipe for target 'clllc_F28004x.out' failed
error #16004-D: file "C:/Users/Reta/workspace_v11/clllc_F28004x/libraries/SFO/SFO_v8_fpu_lib_build_c28_driverlib_eabi.lib<SFO_v8_fpu_lib_build_c28_driverlib.obj>" has a Tag_VCU attribute value of "1" that is different than one previously seen ("3"); combining incompatible files
"../device/f28004x_flash_lnk.cmd", line 89: warning #10068-D: no matching section
error #10010: errors encountered during linking; "clllc_F28004x.out" not built
gmake[1]: *** [clllc_F28004x.out] Error 1
gmake: *** [all] Error 2
makefile:160: recipe for target 'all' failed

**** Build Finished ****

Hi,

Can you list out all the changes that you made? did you also change linker command file?

Best,

John

only I switch that device for another in this section in sysconfig 

you can download the aplication in the in the resourse explorer

that is the aplication I have anothe that already try but is showing diferent error

Hi Arturo,

You are using the 4.01.00.00 version of the Digital Power SDK? If you trying to migrate the project to TMS320F28003x, there are a few steps you will need to take.

1. You will need to create an entirely new project designed for TMS320F28003x device, this can be taken from the C2000Ware SDK (there should be a copy of this in the Digital Power SDK) at the folder driverlib>f28003x>examples>pinmux

2. You will need to go into the CCS properties of this project, go to the SysConfig settings under Build, and entirely remove the device, part, and package flags.

3. Next you will want to copy all of the source files from the CLLLC project over to the new project.

4. Finally, you can then use the SWITCH button within the SysConfig GUI. This will migrate all settings over to TMS320F28003x, but you may need to resolve any errors that show up.

Please follow this procedure and let me know if there are any other questions. We are also releasing a video shortly that provides the step-by-step process of the procedure I just described.

Regards,

Peter

I was doing each step and is showing this errors

Hi Arturo,

At what part of the sysconfig migration process did you receive this error? What changes have you made so far to produce this error? 

Can you go in the project properties and show me what SysConfig version you are using?

Regards,

Peter

this was at the stage of opening the sysconfig after having copied it as the video says, could you please do that exercise because I think this case is very different from the one in the video and it gives us problems that are not in the video and that the video It turned out a very simple example to be able to translate it as shown

Could you please transfer the TIDM-2002 (CLLLC) project that is for the F28004x card to the F28003x and it will show you the same error that I have when doing it

thanks in advance

this is the project that I am triyng to tralate to TMS320F280039C if you see in the image you can se where como from the project and original DSP is TMS320F280049C

Hi Arturo,

Thank you for the clarification. I didn't realize the syscfg file in the TIDM-02002 project used a specific PowerSuite SysConfig file. In that case, you will need to make the changes directly in the original CLLLC project by deleting the F28004x-specific files (device, targetconfig, libraries, etc.) and replacing them with F28003x files (which you can directly copy over from the empty_sysconfig_100pz project you imported).

This is definitely more complex than what was shown in the guide, but let me know if you run into any issues.

Regards,

Peter

I can't to translate this example because is showing error and maybe if you could do the translate will show the same errors becuse I was triying to made the adjust and still showing errors  because the tms320f280049 has the block of PGA and the tms320f280039C doesn't has that block

Hi Arturo,

For the missing PGA block, you should be able to bypass the error by removing it from the configuration in tms320f280039C. I will let John comment additionally on the migration for the reference design

Regards,

Peter

I already did a new projject and is showing this errors

I already add the target but has this errors

the problem is that how can I to know where is the error because the software not sending to the lineof that error 

Note that the all arguments other than '--help' and '--version' may also be
specified via the script with an embedded @cliArgs comment directive.
E.g. // @cliArgs -d MSP432P401R

If an argument is embedded in a script and explicitly specified via the CLI
then precedence is given to the CLI arguments. Additionally, specifying
"--board" or "--device" on the CLI will override any "--board" and "--device"
arguments specified in the script.

subdir_rules.mk:23: recipe for target 'build-1729859375' failed
Invalid argument '--product': No product with name "powerSUITE" and version "3.00.00.00" found
gmake: *** [build-1729859375] Error 1
gmake: Target 'all' not remade because of errors.

Hi Arturo,

The error is saying that you don't have a 3.00.00.00 version of powerSUITE in your CCS project. Can you go into your CCS project properties and see what version you are using? If one isn't selected, you can manually add the powerSUITE product to your CCS project.

Regards,

Peter

Hi Arturo,

I reached out to a colleague and this is the info I was given

"If the user is trying to port one of the DP SDK SysConfig projects. They will need to make several changes to the project besides the typical SysConfig files.

There’s a file named solution.js that is included in the projects. This file specifies the device number, PWM switching frequency & clock values (eCAP, SysClock, etc.).

The user will need to update the values in that file that are unique for the device. In addition to the other device related changes to driverlib, DSP libs, etc."

Regards,

Peter