CSEC support in RTD

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CSEC support in RTD

Jump to solution
362 Views
durga_choudhury
Contributor V

MCU: S32K148

Driver: RTD 3.0.0

IDE: S32DS 3.6.6

 

In the older, PE based SDK, there used to be driver support for CSEC and the examples had a CSEC example. In the newer RTD, I can neither find any kind of driver support nor a 'getting started' example. Any pointers in this regards?

0 Kudos
Reply
1 Solution
308 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

I recommend to always carefully read the release notes files.

Version 3.0.0 is initial version supporting  AUTOSAR R21-11 without Crypto drivers.

Package QLP01 should be installed on top of this version. It contains AUTOSAR R21-11 Crypto driver.

 

Version QLP02 is intended for customers who require Autosar version 4.4. This contain all the modules except Crypto. QLP03 contains Crypto module for Autosar 4.4 and it should be installed on top of QLP02.

 

Version QLP04 is another “base” installation (like initial 3.0.0 or QLP02) and the main difference is that it adds support for S32K116V, S32K118V and S32K144N 3.3V devices.

Version QLP06 just adds support for S32K142N 3.3V devices and it should be installed on top of QLP04.

 

All these details can be found in the release notes.

 

Regarding the installation – install only relevant packages. For example, version 3.0.0 and QLP01 on top of that. Or QLP02 and QLP03. Or QLP04 and QLP06. Don’t mix them together, always follow the instructions in the release notes files.

 

If you install, for example, QLP02 over 3.0.0, this is considered as upgrade and older version is removed. That’s the reason why you can’t see examples from older version.

 

If you need more version of RTD, recommended workaround is to install more instances of S32 Design Studio.

 

Regards,

Lukas

View solution in original post

0 Kudos
Reply
4 Replies
346 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @durga_choudhury 

There are a lot of differences between SDK and RTD. RTD strictly follows Autosar layout to meet Autosar specification and lower Ip layer (SDK-like) also needs to follow the layout. So, the Csec_Ip examples can be found in Crypto module.

However, the Crypto module is not available in 3.0.0. Sometimes the Crypto driver is not available in first initial release of new RTD and it is provided later in separate package. You can check section “2.5  Support and Driver Plugins Delivered” in release notes for each package. In case of S32K1 and RTD 3.0.0 R21-11, it’s necessary to install additional package S32K1_S32M24x Real-Time Drivers Version 3.0.0 QLP01 on top of 3.0.0 version. This version contains only the Crypto driver.

https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=SW32K1-RTD44-D

lukaszadrapa_0-1777448406406.png

 

lukaszadrapa_1-1777448413417.png

 

Regards,

Lukas

0 Kudos
Reply
332 Views
durga_choudhury
Contributor V

Hello @lukaszadrapa 

 

Thank you for the update. I visited the RTD update site you mentioned, and I found that a later version of the update, QPL06 than you you mentioned, QPL01, is available, and I tried to install it, as follows:

1. I downloaded SW32K1_S32M24x_RTD_R21-11_3.0.0_QLP06_D2603_DesignStudio_updatesite.zip

2. Opened the 'Update sites' in S32DS 3.6.6 and added the file in step 1 as the update site.

 

Now when I try to update the RTD, it fails like this:

durga_choudhury_0-1777473224922.png

 

And now my project is in a completely broken state. If I try to open the .mex file, I get this:

durga_choudhury_1-1777473292391.png

I am using the NXP gcc 10.2 toolchain, which, per the release notes, is the supported toolchain.

 

Help!

Tags (1)
0 Kudos
Reply
330 Views
durga_choudhury
Contributor V

I will add a few follow up questions here.

 

I uninstalled QPL06 and installed QPL01 instead, as was suggested by you. With that, my own code builds and now a CSEC IP is also available in the peripherals selection, so I can add it to my project (I have not used it yet, just added it to my project). I can also see some CSEC related example projects. However, most of the *original* example projects of RTD3.0.0 are now gone, please see the screen shot below. These projects were a great source of copy-pasting code to implement a specific logic in a peripheral. So two new questions, now:

 

1. Do these 'patches' (QPL<n>) need to be installed in succession? In other words, in order to be able to install QPL06, do I need to install QPL01..05 first, in that order?

 

2. When a new patch is installed, I can only get the examples that were part of that patch and the previous examples are gone? So if I want to keep them, maybe I should copy them somewhere before upgrading the QPL level?

 

durga_choudhury_0-1777478131400.png

 

0 Kudos
Reply
309 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

I recommend to always carefully read the release notes files.

Version 3.0.0 is initial version supporting  AUTOSAR R21-11 without Crypto drivers.

Package QLP01 should be installed on top of this version. It contains AUTOSAR R21-11 Crypto driver.

 

Version QLP02 is intended for customers who require Autosar version 4.4. This contain all the modules except Crypto. QLP03 contains Crypto module for Autosar 4.4 and it should be installed on top of QLP02.

 

Version QLP04 is another “base” installation (like initial 3.0.0 or QLP02) and the main difference is that it adds support for S32K116V, S32K118V and S32K144N 3.3V devices.

Version QLP06 just adds support for S32K142N 3.3V devices and it should be installed on top of QLP04.

 

All these details can be found in the release notes.

 

Regarding the installation – install only relevant packages. For example, version 3.0.0 and QLP01 on top of that. Or QLP02 and QLP03. Or QLP04 and QLP06. Don’t mix them together, always follow the instructions in the release notes files.

 

If you install, for example, QLP02 over 3.0.0, this is considered as upgrade and older version is removed. That’s the reason why you can’t see examples from older version.

 

If you need more version of RTD, recommended workaround is to install more instances of S32 Design Studio.

 

Regards,

Lukas

0 Kudos
Reply