Issues regarding Conversion of *.tcf file to *.cfg file

Manju,
are you asking about the Outline view? If you are, can you click on the button "Show Configuration Results (Read Only)" in that view and expand all plus signs? Please post the picture of the view after you do that.

Hi Sasha,

Yes i am reffering to the outline view

When i am clicking on *.cfg file(Got after converting *.tcf file using XS conversion tool) i am unable to view the outline.

What my understanding is If i really converted to *.cfg file successfully, i should get all the configurations in the outline view but i am not getting that.

Thanks and Regards,

Manju

Manju,
are there any error messages anywhere? Have you opened Error Log and Problem views? Can you right-click on the project, clean and then rebuild, and then post the Console Window output?

Hi Sasha,

Sorry for the late reply.

I tried clean and then rebuilding the project, but still its not showing the statically configured modules.

Please find the attachment3617.mailbox_c2000.docx

Thanks,

Manju

Manju,
the attached file shows that there were some errors in the build. You'll have to fix these first before you try to open XGCONF succesfully. The conversion tool usually generates CFG scripts that can be used without changes, but there are cases when you need to edit the generated script to get a working configuration.

I see that there is an error at line 24, but the attached file does not show that line. Can you post the whole CFG script, or at least the first part of it including the line 24? Also, please post the console output, that's the tab in the same view as Problems (the tab with the error messages). I would like to see the configuro command line and the name of the platform you are using. The conversion tool also generates a platform package during the conversion process, and you have to use that platform for your SYS/BIOS project.

Hi Sasha,

Please find the attachment for the console o/p and the CFG script.

1643.Screenshot of the error.docx

I am using C2000 series.

XS command:

xs --xp "C:\ti\bios_6_33_04_39\packages" ti.bios.conversion -Dconfig.platform=ti.platforms.ezdsp28335 -c "C:\ti\xdctools_3_23_03_53\mailbox_c2000.cfg" --pr C:\ti\ccsv5\ccs_base --pn myplatform -i mailbox.tcf

The conversion tool generated a package and the same package i used in SYS/BIOS project.

Thanks,

Manju

From the conversion command line, it seems that you created a new platform "myplatform", which was then created in the directory C:\ti\ccsv5\ccs_base. That's the platform that you have to use in your project build. I see from the configuro command line that you are passing the option "-p mymailbox", which means that you are using the platform "mailbox". How did you get that platform? Can you try using "myplatform"?

Hi Sasha,

Actually in the configuro command line i used the "-p mailbox"  as the platform,

sorry for that mistake,the same generated platform we used for our SYS/BIOS project.

Thanks,

Manju

I am not sure I understand where did you make a mistake. Are you using now the same platform that was generated by the conversion tool and your configuration works, or you were using the same platform all along but your attached console output somehow shows different platform names?
Has your problem been solved?

Sasha,

I am using the same Platform package which i got after the configuro command.

My problem is not yet been solved its the same error as i have attached in my previous post.

Thanks,

Manju

Manju,
are you saying that the platforms 'mymailbox' and 'myplatform' are one and the same? Can you post Platform.xdc and Platform.xs files for that platform?

Sasha,

Yes,the platforms 'mymailbox' and 'myplatform' are one and same.

I have attached the package which was generated after the xs configuro command.

1738.mymailbox.rar

Thanks,

Manju

Manju,
I am not sure how you renamed the platform generated by the conversion tool without rebuilding the platform package. Anyway, the platform you posted does not contain the same memory objects that your script expects. The easiest way to fix it is to replace the name L47SARAM with LSARAM in your CFG script. The following lines

bios.L47SARAM.createHeap = true;
bios.L47SARAM.heapSize = 0x01f0;
bios.L47SARAM.enableHeapLabel = true;
bios.L47SARAM["heapLabel"] = "SEG0";
bios.MEM.MALLOCSEG = prog.get("L47SARAM");

should become

bios.LSARAM.createHeap = true;
bios.LSARAM.heapSize = 0x01f0;
bios.LSARAM.enableHeapLabel = true;
bios.LSARAM["heapLabel"] = "SEG0";
bios.MEM.MALLOCSEG = prog.get("LSARAM");

Try that and see if you can progress further. I am just guessing that L47SARAM and LSARAM represent the same physical memory object, but I can't be sure without seeing your original TCF script.