S32 Design Studio for ARM v 2.2

[durga_choudhury]

Is S32 Design Studio for ARM v 2.2 still maintained? When I launch it or click on 'Help -> S32 DS Extensions and Updates' it pops up a window saying 'operation in progress' and just hangs (until I click 'Cancel' to close the window).

[durga_choudhury]

Thank you for your clarification. I do have a follow up question, however. As I mentioned, our current project is based on S32 DS for ARM v2.2 and in this IDE it builds fine. As expected, it does not build on S32DS for S32 because of the SDK incompatibility.

As you mentioned, this porting has to be done manually.

Before I delve into this porting, which I expect will take some effort, I wanted, as a stepping stone, to see if I can upgrade to S32DS v3.4 where I believe the auto migration will still work (is my understanding correct?)

I installed v 3.4 IDE and it says 'Processors are not defined for this product'. Yet it seems all the components are already installed, as shown in the screenshot. What am I missing?

[_Leo_ · Accepted solution]

Kindly create a separate post for this new query. Thank you for your understanding.

[_Leo_]

Thank you for your interest in our products and for contributing to our community.

S32 Design Studio for ARM v 2.2 is no longer maintained, instead of that, we recommend use newer version of S32 Design Studio for S32 Platform with newer version of RTD for the device you are using.

What you can do is go to Help -> S32 DS Extensions and Updates and uncheck the following box:

It will take a while to open the first time, but on the next launch it will not open automatically.

I hope this information is helpful.

Best regards,
Leonardo

[durga_choudhury]

Thank you for the suggestion and also solving the mystery of 'why it is hanging'. I do agree with you that the only way out is forward.

However, our device, which has a large number of field deployments, started on the S32DS for ARM and is using the SDK that comes with it. I was told that the SDK has now been superseded by the 'Real time drivers', and that the later has no compatibility with the former and also, (worse) that any porting has to be done manually.

Can you please say if the above is correct? If there is a way to automatically, or at least in a somewhat templated sort of way, to replace the SDK calls with the RTD calls, I can do that quickly. This is the reason we are holding off on the migration.

[_Leo_]

Your understanding is correct - any porting has to be done manually.