I have noticed that if I open a completely new work space estudio remembers that a sample project has been imported earlier and denies an import in the new fresh workspace.
That is not handy for upgrades which require the latest estudio and sdk like the current upgrade.
How is that issue be best addressed, a new SDK location for each independent project ?
Thanks
Ralph
update
It seems that this issue affects all sample projects even those I have not imported before.
I will try on a virgin machine to see if I can import according to the documentation.
Even when I completely uninstall estudio, delete all work spaces and reinstall estudio this problem remains
Let us know what kind of path is given as workspace.You could also try using "Existing Projects into Workspace" but uncheck "copy projects into workspace", or use "Projects from Folder or Archive".
please read the whole threat if you feel like answering
and you should know that importing "Existing Projects into Workspace" does NOT WORK. It has a bunch of unresolved identifiers as ALREADY MENTIONED EARLIER IN THIS THREAT
May be you come up with something that helps, I need a solution to follow the recommendation to always use the latest versions. I just starting a new project, so yes it would make sense to use the latest
Found no problems ...Then try using "Projects from Folder or Archive".Before "Dialog SDK project" import wizard implemented, I used it and it worked.
negative, not even the tiniest chance to get that working
anybody else having this problem? why its always me?
and not only on one machine, no, always on all my computers!
anyone needs a buck finder? hire me....
There are some cases even using empty workspace (such as with broken .project file).https://www.google.com/search?q=%22Some+projects+cannot+be+imported+because%22+eclipse+site:stackoverflow.com
here we go, so you are aware of that .project file is part of the sdk samples?
May be you try by cloning the REAL CURRENT github repo and see if you can replicate the issue?
So yes clean this up then
First, you should check workspace log (.metadata/.log) if any errors prevents from import.
here is what Renesas should fix ASAP
!SESSION 2025-05-28 10:57:34.081 ----------------------------------------------- eclipse.buildId=v25.4.1 java.version=21.0.6 java.vendor=Eclipse Adoptium BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86_64 -data C:\Users\ralph\e2_studio\waterwatch_II !ENTRY org.eclipse.ui 2 0 2025-05-28 10:57:37.144 !MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points. !SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.144 !MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core', id='com.renesas.cdt.managedbuilder.ui.commands.RenesasBuildOptionSettingsCommand', categoryId='com.renesas.cdt.quick.option.commands.category' !SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.144 !MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.deviceMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category' !SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.144 !MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.toolchainVersionMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category' !ENTRY org.eclipse.ui 2 0 2025-05-28 10:57:37.655 !MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points. !SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.655 !MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core', id='com.renesas.cdt.managedbuilder.ui.commands.RenesasBuildOptionSettingsCommand', categoryId='com.renesas.cdt.quick.option.commands.category' !SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.655 !MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.deviceMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category' !SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.655 !MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.toolchainVersionMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category' !ENTRY com.renesas.software.installer.ide 4 0 2025-05-28 10:57:38.583 !MESSAGE Unable to load product feature list !ENTRY org.eclipse.launchbar.core 2 0 2025-05-28 10:57:41.598 !MESSAGE Enablement expression is missing for config provider for com.renesas.cdt.dialogsdk.descriptorType
!SESSION 2025-05-28 10:57:34.081 -----------------------------------------------eclipse.buildId=v25.4.1java.version=21.0.6java.vendor=Eclipse AdoptiumBootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_USCommand-line arguments: -os win32 -ws win32 -arch x86_64 -data C:\Users\ralph\e2_studio\waterwatch_II!ENTRY org.eclipse.ui 2 0 2025-05-28 10:57:37.144!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.!SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.144!MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core', id='com.renesas.cdt.managedbuilder.ui.commands.RenesasBuildOptionSettingsCommand', categoryId='com.renesas.cdt.quick.option.commands.category'!SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.144!MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.deviceMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category'!SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.144!MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.toolchainVersionMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category'!ENTRY org.eclipse.ui 2 0 2025-05-28 10:57:37.655!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.!SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.655!MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core', id='com.renesas.cdt.managedbuilder.ui.commands.RenesasBuildOptionSettingsCommand', categoryId='com.renesas.cdt.quick.option.commands.category'!SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.655!MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.deviceMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category'!SUBENTRY 1 org.eclipse.ui 2 0 2025-05-28 10:57:37.655!MESSAGE Commands should really have a category: plug-in='com.renesas.cdt.core.ui', id='com.renesas.cdt.core.ui.commands.toolchainVersionMigrationCommand', categoryId='com.renesas.cdt.core.ui.commands.category'!ENTRY com.renesas.software.installer.ide 4 0 2025-05-28 10:57:38.583!MESSAGE Unable to load product feature list!ENTRY org.eclipse.launchbar.core 2 0 2025-05-28 10:57:41.598!MESSAGE Enablement expression is missing for config provider for com.renesas.cdt.dialogsdk.descriptorType
This is the log after a fresh workspace and import try
The newest record is at the bottom of the log.
any activities or feedback to solve that issue?
Hi Rales,Thank you for the reply.We have reported the issue internally.Unfortunately, from our side we are not able to replicate the issues you have reported.IF the e2 Studio team is able to reproduce the issue they will address it on the next e2 Studio release.Best Regards,OV_Renesas
About the import issue, restoring .project file from original SDK can be the solution.And "Projects from Folder or Archive" also may work with the same reason.
"Projects from Folder or Archive" allowed me to import a (just one) project into workspace, however with a bunch of issues. Not at all seamlessly.
one remaining issue is that I can't get rid of this message when starting a debug session and hence not debug. But still trying to get it to work.
However,I changed the target device at all places I know, it compiles and creates the folder for Debug_RAM_DA14531 and it loads the Debug_RAM_DA14531.elf file.Keep in mind that I work on a custom hardware using Jlink, which I successfully flashed with the simple_beacon in former SDK6 versions. I have now idea where the mess comes from in this new version.