- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software:
I am working on a CCS project that needs to run on both TMS320F2800135 and TMS320F280039C. To achieve this, I have included all the necessary files for both ICs and manually switch between them by:
.ccxml file.While switching from TMS320F2800135 to TMS320F280039C, there are no build errors, but the program does not appear to be running:
Checked Target Configuration:
.ccxml file is active in targetConfigs.Modified Linker Command Files:
2800135_generic_ram_lnk.cmd when switching to TMS320F280039C.280039_generic_ram_lnk.cmd instead.Checked SysConfig & DriverLib Dependencies:
syscfg is updated to match the selected IC.Debugging Observations:
Any guidance on this issue would be greatly appreciated!
Hello,
Program execution appears to be stuck.
Can you provide more details on this? What is the state of the device when executing the migrated code?
Registers do not update in real-time unless the program is manually halted.
Did you enable "Continuous Refresh" in the registers view?
Are there additional project settings required in CCS to switch between TMS320F2800135 and TMS320F280039C dynamically?
The C2000 Migration Report Generation Tool may be helpful. You can view the register, device interconnect, and function level changes when migrating from F280013x to F28003x.
Should any modifications be made in the startup files or memory configurations?
Did you update the project to use the f28003x_codestartbranch.asm file in the device folder as well?
Best,
Matt
Hi,
Can you check the linker's "File Search Path in the project properties to see if the device support files are included?
You can also try migrating the syscfg file itself -- it will migrate the configuration settings from F2800135 to F280039C automatically for you. Please note that it cannot be undone, so save a copy in case migration fails.
Best,
Matt
Okay, the device files are getting generated now, but I am getting the below debugging error while trying to debug it, can you help me with this
Hi,
The device is stuck in the ITRAP ISR. Can you try to step through the code to see what line triggers this to occur?
Best,
Matt
Just before the device_init() statement it is getting stuck and throwing this debugging error, so how to resolve this error. I've attached the registers window screenshot as well.
It is from the sysconfig as you can see the location of device.c file at the right hand side of the image. Now, how to get rid of that error
Hi,
Did you follow this step in the FAQ to configure the default RAM linker command file? It doesn't seem the linker command file (syscfg/device_cmd.cmd) was properly generated.
In the linker command file configuration, please make sure to set the following:
Best,
Matt
Hi Devesh,
You will need to have two different build configurations for F28003x and F280013x devices respectively.
You can create a new build configuration by right-clicking the project and navigating to Build Configurations > Manage
Then you can include/exclude the respective syscfg files by right-clicking the intended file and selecting "Exclude from build". CCS will remember your project settings per build configuration so they won't be lost when changing between device builds.
Best,
Matt
These are the files that I've in my project folder, where I'm using two target config file and changing them depending on which IC I'm using.
I'm selecting the IC from build manage option, which excludes the unnecessary syscfg files from itself. It's working fine with F280013x and not giving error but on switching to F28003x, it is providing me those sysctl compilation errors
I'm getting these errors in specific files from the board.c and device.c file generated from sysconfig as they are present in the syscfg folder. Now, please give me some valuable suggestion from which I can use my project for F28003x IC as well just by using migration.
Hi,
It looks like the device support header files for F28003x aren't being included in the build.
Two things to check:
You can also try manually linking the necessary device support header files, they're located at: C2000Ware_5_04_00_00\device_support\f28003x\headers
Best,
Matt
