boring
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ Development Tools 12.5.0.202606022100 (org.eclipse.cdt.feature.group 12.5.0.202606022100)
Missing requirement: GDB Common 7.2.500.202603111352 (org.eclipse.cdt.gdb 7.2.500.202603111352) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ Development Tools 12.5.0.202606022100 (org.eclipse.cdt.feature.group 12.5.0.202606022100)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.gdb.feature.group [12.5.0.202603111352,12.5.0.202603111352]
Cannot satisfy dependency:
From: C/C++ Common GDB Support 12.5.0.202603111352 (org.eclipse.cdt.gdb.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.gdb [7.2.500.202603111352,7.2.500.202603111352]
Cannot complete the install because one or more required items could not be found.
Software being installed: Remote Services 12.5.0.202603111352 (org.eclipse.remote.feature.group 12.5.0.202603111352)
Missing requirement: Eclipse Remote Development documentation plug-in 12.5.0.202603111352 (org.eclipse.remote.doc.isv 12.5.0.202603111352) requires 'osgi.bundle; org.eclipse.help [3.10.500,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: Remote Services 12.5.0.202603111352 (org.eclipse.remote.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.remote.doc.isv [12.5.0.202603111352,12.5.0.202603111352]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ Development Tools 12.5.0.202606022100 (org.eclipse.cdt.feature.group 12.5.0.202606022100)
Missing requirement: GDB Common 7.2.500.202603111352 (org.eclipse.cdt.gdb 7.2.500.202603111352) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ Development Tools 12.5.0.202606022100 (org.eclipse.cdt.feature.group 12.5.0.202606022100)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.gdb.feature.group [12.5.0.202603111352,12.5.0.202603111352]
Cannot satisfy dependency:
From: C/C++ Common GDB Support 12.5.0.202603111352 (org.eclipse.cdt.gdb.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.gdb [7.2.500.202603111352,7.2.500.202603111352]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ Development Platform 12.5.0.202606022100 (org.eclipse.cdt.platform.feature.group 12.5.0.202606022100)
Missing requirement: C/C++ Development Tools Core Native Utilities 6.6.200.202603111352 (org.eclipse.cdt.core.native 6.6.200.202603111352) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ Development Tooling Native Utilities 12.5.0.202606022100 (org.eclipse.cdt.native.feature.group 12.5.0.202606022100)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.core.native [6.6.200.202603111352,6.6.200.202603111352]
Cannot satisfy dependency:
From: C/C++ Development Platform 12.5.0.202606022100 (org.eclipse.cdt.platform.feature.group 12.5.0.202606022100)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.native.feature.group [12.5.0.202606022100,12.5.0.202606022100]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ GCC Cross Compiler Support 12.5.0.202603111352 (org.eclipse.cdt.build.crossgcc.feature.group 12.5.0.202603111352)
Missing requirement: CDT GCC Cross Compiler Support 1.3.800.202603111352 (org.eclipse.cdt.build.crossgcc 1.3.800.202603111352) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ GCC Cross Compiler Support 12.5.0.202603111352 (org.eclipse.cdt.build.crossgcc.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.build.crossgcc [1.3.800.202603111352,1.3.800.202603111352]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ Development Tooling Native Utilities 12.5.0.202606022100 (org.eclipse.cdt.native.feature.group 12.5.0.202606022100)
Missing requirement: C/C++ Development Tools Core Native Utilities 6.6.200.202603111352 (org.eclipse.cdt.core.native 6.6.200.202603111352) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ Development Tooling Native Utilities 12.5.0.202606022100 (org.eclipse.cdt.native.feature.group 12.5.0.202606022100)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.core.native [6.6.200.202603111352,6.6.200.202603111352]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ Common GDB Support 12.5.0.202603111352 (org.eclipse.cdt.gdb.feature.group 12.5.0.202603111352)
Missing requirement: GDB Common 7.2.500.202603111352 (org.eclipse.cdt.gdb 7.2.500.202603111352) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ Common GDB Support 12.5.0.202603111352 (org.eclipse.cdt.gdb.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.gdb [7.2.500.202603111352,7.2.500.202603111352]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ Memory View Enhancements 12.5.0.202603111352 (org.eclipse.cdt.debug.ui.memory.feature.group 12.5.0.202603111352)
Missing requirement: Debug Core Memory 0.2.300.202512020204 (org.eclipse.cdt.debug.core.memory 0.2.300.202512020204) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ Memory View Enhancements 12.5.0.202603111352 (org.eclipse.cdt.debug.ui.memory.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.debug.core.memory [0.2.300.202512020204,0.2.300.202512020204]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ GNU Toolchain Build Support 12.5.0.202603111352 (org.eclipse.cdt.gnu.build.feature.group 12.5.0.202603111352)
Missing requirement: GCC support for CDT Build Core 2.1.800.202512020204 (org.eclipse.cdt.build.gcc.core 2.1.800.202512020204) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ GNU Toolchain Build Support 12.5.0.202603111352 (org.eclipse.cdt.gnu.build.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.build.gcc.core [2.1.800.202512020204,2.1.800.202512020204]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ GDB Hardware Debugging 12.5.0.202603111352 (org.eclipse.cdt.debug.gdbjtag.feature.group 12.5.0.202603111352)
Missing requirement: Eclipse GDB Hardware Debug Core Plug-in 10.8.500.202512020204 (org.eclipse.cdt.debug.gdbjtag.core 10.8.500.202512020204) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ GDB Hardware Debugging 12.5.0.202603111352 (org.eclipse.cdt.debug.gdbjtag.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.debug.gdbjtag.core [10.8.500.202512020204,10.8.500.202512020204]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ GNU Toolchain Debug Support 12.5.0.202603111352 (org.eclipse.cdt.gnu.debug.feature.group 12.5.0.202603111352)
Missing requirement: C/C++ Development Tools Launching Support 11.0.300.202603111352 (org.eclipse.cdt.launch 11.0.300.202603111352) requires 'osgi.bundle; org.eclipse.ui.ide [3.22.600,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ GNU Toolchain Debug Support 12.5.0.202603111352 (org.eclipse.cdt.gnu.debug.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.launch [11.0.300.202603111352,11.0.300.202603111352]
Cannot complete the install because one or more required items could not be found.
Software being installed: C/C++ DSF GDB Debugger Integration 12.5.0.202603111352 (org.eclipse.cdt.gnu.dsf.feature.group 12.5.0.202603111352)
Missing requirement: GDB DSF Debugger Integration Core 7.3.100.202601271447 (org.eclipse.cdt.dsf.gdb 7.3.100.202601271447) requires 'osgi.bundle; org.eclipse.core.runtime [3.34.0,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: C/C++ DSF GDB Debugger Integration 12.5.0.202603111352 (org.eclipse.cdt.gnu.dsf.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.cdt.dsf.gdb [7.3.100.202601271447,7.3.100.202601271447]
Cannot complete the install because one or more required items could not be found.
Software being installed: Remote Services 12.5.0.202603111352 (org.eclipse.remote.feature.group 12.5.0.202603111352)
Missing requirement: Eclipse Remote Development documentation plug-in 12.5.0.202603111352 (org.eclipse.remote.doc.isv 12.5.0.202603111352) requires 'osgi.bundle; org.eclipse.help [3.10.500,4.0.0)' but it could not be found
Cannot satisfy dependency:
From: Remote Services 12.5.0.202603111352 (org.eclipse.remote.feature.group 12.5.0.202603111352)
To: org.eclipse.equinox.p2.iu; org.eclipse.remote.doc.isv [12.5.0.202603111352,12.5.0.202603111352]
Hello @CY9,
Could you share what package, updatesite, RTD or plugin you are trying to install?
From the error log, I can see you are trying to install CDT 12.5.0, however, latest S32DS release supports Eclipse 2023-12 framework, CDT 11.4, and Java17.
Have you tried to update only through the S32DS Updates and Extensions interface?
Best regards,
Julián
Hello @CY9,
I apologize if S32DS and general environment gave you too many issues. By your other post, I can see you are looking to use RTM 4.0.2, which is not supported by S32DS 3.6.10.
Instead, as my colleague Robin suggested, you must install:
- S32 Design Studio 3.4
- S32K1xx Service Pack 1
With this, you should be able to see S32K1XX RTM. In my case, I use RTM 4.0.3:
Otherwise, if you use S32DS 3.6.10, you must use Real-Time Drivers (RTD). S32SDK has been deprecated and replaced by RTD package, which also provides examples and drivers for low level (IP) and high level (MCAL).
I apologize for the inconveniences while trying to install S32SDK.
Best regards,
Julián
「 ... RTM 4.0.2, which is not supported by S32DS ... 」
That's another question:
How do a newbie know that [Which RTM is supported/NOT supported by which version of S32DS] !??
AND:
How Do I open/import a old Project that made by RTM xx , in new version os S32DS !??
I can *NOT* open&import old project created by S32DS v3.5+RTM402 on new S32DS v6.0.10 ...
There is no motivation to upgrade to the new version. ..... understand !?
I will use S32DS 3.5 FOREVER... no matter how smart/advanced is your new S32DS 4.0/99.0 ... if you don't solve this problem :
```
$ grep -ni "RTM" .* * 2>/dev/null
.project:35: <locationURI>s32sdk_s32k1xx_rtm_402/rtos/osif/doxygen/osif.dox</locationURI>
.project:40: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/drivers/src/adc/doxygen/adc_driver.dox</locationURI>
.project:45: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/clock/doxygen/clock_manager.dox</locationURI>
.project:50: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/crc/doxygen/crc.dox</locationURI>
.project:55: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/edma/doxygen/edma_driver.dox</locationURI>
.project:60: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/flash/doxygen/flash_driver.dox</locationURI>
.project:65: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/flexcan/doxygen/flexcan_driver.dox</locationURI>
.project:70: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/ftm/doxygen/ftm_driver.dox</locationURI>
.project:75: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/ftm/doxygen/ftm_pwm_driver.dox</locationURI>
.project:80: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/interrupt/doxygen/interrupt.dox</locationURI>
.project:85: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/drivers/src/lptmr/doxygen/lptmr.dox</locationURI>
.project:90: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/drivers/src/lptmr/doxygen/lptmr_driver.dox</locationURI>
.project:95: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/lpuart/doxygen/lpuart_driver.dox</locationURI>
.project:100: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/drivers/src/pdb/doxygen/pdb.dox</locationURI>
.project:105: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/drivers/src/pdb/doxygen/pdb_driver.dox</locationURI>
.project:110: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/pins/doxygen/pins.dox</locationURI>
.project:115: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/drivers/src/trgmux/doxygen/trgmux_driver.dox</locationURI>
.project:120: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/pal/src/adc/doxygen/adc_pal.dox</locationURI>
.project:125: <locationURI>s32sdk_s32k1xx_rtm_402/platform/pal/src/can/doxygen/can_pal.dox</locationURI>
.project:130: <locationURI>S32SDK_S32K1XX_RTM_4.0.2/platform/pal/src/pwm/doxygen/pwm_pal.dox</locationURI>
.project:135: <locationURI>s32sdk_s32k1xx_rtm_402/platform/pal/src/timing/doxygen/timing_pal.dox</locationURI>
.project:140: <locationURI>s32sdk_s32k1xx_rtm_402/platform/pal/src/uart/doxygen/uart_pal.dox</locationURI>
.project:145: <locationURI>s32sdk_s32k1xx_rtm_402/platform/drivers/src/clock/S32K1xx/doxygen/clock_S32K1xx.dox</locationURI>
Project_S32DS35_118.mex:6: <mcu_data>s32sdk_s32k1xx_rtm_402</mcu_data>
```
I know RTM402 is *NOT* supported by S32DS3.5 ..... after I HAD ALREADY CREATE lots of project for my job for a long time.....
But I can *NOT* rollback RTM402 back to RTM401 =_="
And When I install RTM402 on S32DS3.5, your RTM/S32DS v3.5 NEVER block/alarm me because it's *NOT* supported... ← That's the most annoying thing.
Hello ,
RTM 4.0.2 is quite old and not pushed by NXP anymore. The easiest way to know which SW is supported is to refer to the release notes. For example, since RTM 4.0.2 was released with S32 Design Studio v3.4 S32K1 Service Pack 1, you should consider using only the version advertised with the SDK (S32DS v3.4 for RTM 4.0.2). SDK/RTD compatibility:
| SDK/RTD | S32DS Version |
|---|---|
| SDK RTM 4.0.1 | v3.3 only |
| SDK RTM 4.0.2 | v3.4 only |
| SDK RTM 4.0.3 | v3.4 only |
| RTD 2.0.x | v3.5 |
| RTD 3.0.0 | v3.6.1+ |
When trying to import a project made by older SW (RTM xxx), I simply suggest using the same IDE + SW versions used to developed (e.g. S32DS 3.4 + RTM 4.0.2), instead of updating to newer RTD.
And When I install RTM402 on S32DS3.5, your RTM/S32DS v3.5 NEVER block/alarm me because it's *NOT* supported... ← That's the most annoying thing.
SDK/RTD installation is done through S32DS Extensions and Updates. This usually blocks unsupported versions. You can see if you try to install SDK in v3.5+ this message appears:
When installing SW through "Help > Install New Software", eclipse bypasses all of S32DS Extensions and Updates' restrictions. I suggest not installing the software directly, unless you are certain it is compatible.
As my colleague Robin answered in this other post: 回复： [S32DS 3.5+RTM401] I don't know what this SHxT happened - NXP Community, if you are trying to use S32K1 SDK RTM 4.0.1, S32DS 3.3 is recommended instead. This depends on which SW you are trying to install.
I apologize for the inconveniences.
Best regards,
Julián
Could you install a brand new S32DS v3.5 on a brand new PC/VM ?
That's my screenshot on brand new install S32DS v3.5 !! *NOT* v3.3/v3.4 !!
It's support S32K1xx_RTM 401 already !!!
-- Filter keyword: "RTM" :
And install it without any warning/alert !
You can confirm it by yourself...
So, your list below is INCORRECT !!
| SDK RTM 4.0.1 | v3.3 only |
and, make all ppl confused... understand !?
Hi @CY9,
I understand you are using S32DS 3.5 with RTM 4.0.1. Even if the SDK can be installed without warnings or errors, it is not recommended to install S32K1 SDK 4.0.x in S32DS v3.5+.
What I meant by sharing the compatibility table was that each SDK RTM 4.0.x release specifies which S32DS version it was developed and tested with, and that is the only combination for which we guarantee full compatibility with no issues. SDK RTM 4.0.1 was developed and validated with S32DS v3.3, and the last 4.0.x version (RTM 4.0.3) was validated with S32DS v3.4. There are currently no plans to integrate S32SDK S32K1XX 4.0.x into S32DS v3.5 or above.
From RTM 4.0.1 release notes:
Best regards,
Julián
