No I2C/SPI routines for S32k14X could be found.
See here
Their superiors have no idea what the shell is thinking.
Conclusion: You have to install a bunch of unnecessary software yourself.
If you need to open a colleague's old project or an old project you wrote yourself, it's safer to just use the current version + RTM; otherwise, you might run into problems.
Just soy sauce
Hi@ lixia
S32K1 RTD 3.0.0QLP07 is not a complete RTD package; it simply adds support for some of the modules listed below.
Therefore, you cannot see the demo or select the RTD driver when creating a new project.
You should first install S32K1 RTD 3.0.0.Install this package again.
@CY9 CY9
Your answer is incorrect; it pertains to RTD and RTM 4.0.2.They are completely different drivers, and the two should not be confused.
You things:
After installing the new version of RTM, edited projects cannot be opened in the old RTM version.
You know the situation, right?
Therefore, it is not recommended to: [switch to a newer version], nor is it recommended to [use a different RTM version].
It's even suggested that you should never update the version and switch to a newer RTM!
That explanation makes sense!
Don't you understand, " I think you created all these questions "?
Hi@ CY9
The possible reason is that the RTM version pushed may be different for S32 DS installed at different times.
However, even if the pushed RTM version is different, you can still download different packages to choose to install different RTMs.
The rapid pace of version updates and the resulting compatibility issues have indeed caused confusion for users.
However, RTD and RTM 4.0.X are completely different drivers and should not be confused. S32 DS V3.4 is a very old version of IDE.
Hi@ CY9
That's true. If you use different versions, you'll need to install multiple S32 DS versions, and only one RTD version can be installed under each S32 DS IDE.
Installing different RTDs on a single IDE is not allowed and will result in an error. However, with S32 DS, you can install multiple RTDs without conflict.
This pot too: Re: [S32DS 3.5+RTM401] I don't know what this SHxT happened - NXP Community
Hi@ CY9
I see that you created these problems. If the engineer in charge hasn't resolved your issue, you can continue to comment.
The responsible engineer will continue to follow up.
Hi@ CY9
What I mean is that you created these two posts, and each post has a dedicated engineer responsible for following up. If your problem hasn't been resolved, you can continue to comment.
It's already a complete mess!
Even NXP's own employees don't understand which RTM version is paired with which S32DS...
Version 3.5, which hasn't been updated at all, already provides RTM401. They even claim RTM401 is only compatible with version 3.3... ~_~'?
If you yourselves, who touch the same people every day, don't even understand it...
How can you expect someone who only uses their S32DS once every three to five months to understand it!?
It's a mess~ Completely messy.....
I never mentioned this concept. However, RTD and RTM 4.0.X are completely different drivers.
I'm just reminding you: Keep using whatever version and RTM you used in previous projects! Use it until you're dead!
Even if the new version of RTM/S32DS has some new/useful features... DO NOT update!!! It will kill you.
My daily work report is just: Install S32DS... How deep is Wu Yu's knowledge?
Understood~
thank...
However, I don't think there will be a solution to these problems...
Because I have given up on v3.6.xAnd plans to remove v3.5 and reinstall v3.5+RTM.Go solve it~
And then... I'll never update again!
Egg-like...
Colleague A uses v3.4+ without RTM
Colleague B uses v3.4+RTM401
Colleague C uses v3.4+RTM402
Colleague D is using v3.4 + RTM403
...
How would you like to work together with others?