Hi,
I am running CCS 5.1.0.09000. Until recently, I have been able to add new segments to my C66x platform using the Platform Wizard. I haven't had to do this for a while but today I tried to add a new segment. The wizard gave no errors, I clicked Finish, whereupon CCS built the platform with no errors. However, when I open the wizard again the new section has disappeared. I tried several times, with the same negative result.
A colleague has experienced the same problem. He tried changing the clock frequency. Strangely, he can see the change in his platform's xml file (using a diff) but it does not appear in the wizard.
Any idea why this is happening please?
BR
David
David,when you made a change, was there a window with a message "Success. Platform package built ..."? What's the version of XDCtools you are using?
In your platform package, there should be a file Platform.xdc. Can you check if your changes are reflected there? Also, which XML file were you checking for changes? I don't see any XML file that would contain clock info in my platforms. I am using 3.23.01.41.
If my reply answers your question please mark the thread as answered.
Sasha Slijepcevic David,when you made a change, was there a window with a message "Success. Platform package built ..."? What's the version of XDCtools you are using? In your platform package, there should be a file Platform.xdc. Can you check if your changes are reflected there? Also, which XML file were you checking for changes? I don't see any XML file that would contain clock info in my platforms. I am using 3.23.01.41.
Hi Sasha,
Thanks for your reply.
Yes, I get " Platform package ... built successfully ...". I am using XDCTools 3.22.4.46.
Yes the changes are reflected in Platform.xdc, but when I reopen the platform the change is not shown in the wizard. I then close the wizard and then can still see the change in the .xdc file. Very weird! The .java file is never modified.
I'm sorry, I was wrong to mention an xml file - it is the xdc file that changes.
Any thoughts please?
Best regards
David,I haven't seen that problem before, but if the java file in the directory 'package' is not rebuilt, your changes won't be reflected in your configuration. There is a workaround you can use until we figure out the cause of the problem. Open a command line window and go to the platform directory, where the file Platform.xdc is located.Type 'C:\ti\xdctools_3_22_04_46\xdc' (replace C:\ti with the actual installation directory on your computer).
Now, you should be able to use the platform in a configuration and see a new memory map being used.
Before you do all this, can you please zip up and post the whole platform directory in its current invalid state and post it here? I would like to replicate the behavior that you are seeing.
Thanks,Sasha
Hi Sasha
Please find attached the zipped platform folder 0412.evm6670_TML.zip as requested.
David,the package you attached is missing an important file from the directory package. The file is package.xdc.dep and it's automatically generated when the package is built. To recover from it, you'll have to open a command line window and type:C:\ti\xdctools_3_22_04_46\xdc.exe cleanC:\ti\xdctools_3_22_04_46\xdc.exe
After that, you will be able to load the platform, make the changes and save the new version of the platform.
Sasha Slijepcevic David,the package you attached is missing an important file from the directory package. The file is package.xdc.dep and it's automatically generated when the package is built. To recover from it, you'll have to open a command line window and type:C:\ti\xdctools_3_22_04_46\xdc.exe cleanC:\ti\xdctools_3_22_04_46\xdc.exe After that, you will be able to load the platform, make the changes and save the new version of the platform.
Thanks very much for your response, which has fixed my problem.
I would like to suggest that this is a bug. Shouldn't the platform wizard create the .dep file if it is missing?
The platform wizard simply runs gmake on the platform package. We could detect that some makefiles are missing when running gmake, but we decided not to try to recover from corrupted packages. There are too many failure modes to reliably detect them, and it's even harder to recover without completely cleaning and rebuilding. It also doesn't happen that often that some files from the directory 'package' are missing.That said, if this one particular use case turns out to be easy to detect and recover from, we will implement that fix.