Integrate Non Autosar RTD 3.0.0 version with Example source code FlexCAN_Ip_Example_S32K34RTD 7.0.0

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

Integrate Non Autosar RTD 3.0.0 version with Example source code FlexCAN_Ip_Example_S32K34RTD 7.0.0

137 Views
sharathkumar2026
Contributor I

Is It Possible to Integrate Non Autosar RTD 3.0.0 version with (S32DS-36.8 version IDE) FlexCAN_Ip_Example_S32K34 _RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite

1. I need to integrate our Current UDS Application code with FlexCAN_Ip_Example_S32K34 _RTD_R23-11_7.0.1_D2603_DesignStudio source code 

2. I already added FreeRtos config into the RTD 7.0.0 does this support into  _RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite

0 Kudos
Reply
1 Reply

96 Views
PetrS
NXP TechSupport
NXP TechSupport

Hi,

This question seems related to your other thread regarding RTD 3.0.0 → RTD 7.x migration;
https://community.nxp.com/t5/S32K/Clarification-on-RTD-3-0-0-to-RTD-7-0-0-Migration-and-FreeRTOS/m-p...

For RTD 3.0.0 (non-AUTOSAR), please note:

  • RTD 3.0.0 already contains a number of demo/example projects (both AUTOSAR and non-AUTOSAR), which can be used as a reference for driver usage and project structure.
  • However, these examples are standalone and tightly coupled with their generated configuration (clocks, pins, peripherals), so they cannot be directly “plugged” into an existing project without alignment.
  • Integrating example source code into your application always requires manual adaptation of configuration and initialization.

From migration perspective:

  • There is no automatic migration tool between RTD versions.
  • Even when using *.mex import, configuration differences between RTD versions often lead to errors that must be resolved manually.
  • Recommended approach is to create a new project (especially when moving to RTD 7.x) and port the application incrementally.

The SW32K3 FreeRTOS 11.1.0 version 0.8.0 CD1 is intended to be used with SW32K3_S32M27x_RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite

BR, Petr

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2379534%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EIntegrate%20Non%20Autosar%20RTD%203.0.0%20version%20with%20Example%20source%20code%20FlexCAN_Ip_Example_S32K34RTD%207.0.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2379534%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EIs%20It%20Possible%20to%20Integrate%20Non%20Autosar%20RTD%203.0.0%20version%20with%20(S32DS-36.8%20version%20IDE)%20FlexCAN_Ip_Example_S32K34%20_RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20I%20need%20to%20integrate%20our%20Current%20UDS%20Application%20code%20with%20FlexCAN_Ip_Example_S32K34%20_RTD_R23-11_7.0.1_D2603_DesignStudio%20source%20code%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20I%20already%20added%20FreeRtos%20config%20into%20the%20RTD%207.0.0%20does%20this%20support%20into%26nbsp%3B%26nbsp%3B_RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2379941%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Integrate%20Non%20Autosar%20RTD%203.0.0%20version%20with%20Example%20source%20code%20FlexCAN_Ip_Example_S32K34RTD%207.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2379941%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EThis%20question%20seems%20related%20to%20your%20other%20thread%20regarding%20RTD%203.0.0%20%E2%86%92%20RTD%207.x%20migration%3B%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2FS32K%2FClarification-on-RTD-3-0-0-to-RTD-7-0-0-Migration-and-FreeRTOS%2Fm-p%2F2379535%2Fhighlight%2Ffalse%23M59186%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.nxp.com%2Ft5%2FS32K%2FClarification-on-RTD-3-0-0-to-RTD-7-0-0-Migration-and-FreeRTOS%2Fm-p%2F2379535%2Fhighlight%2Ffalse%23M59186%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EFor%20RTD%203.0.0%20(non-AUTOSAR)%2C%20please%20note%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ERTD%203.0.0%20already%20contains%20a%20number%20of%20demo%2Fexample%20projects%20(both%20AUTOSAR%20and%20non-AUTOSAR)%2C%20which%20can%20be%20used%20as%20a%20reference%20for%20driver%20usage%20and%20project%20structure.%3C%2FLI%3E%0A%3CLI%3EHowever%2C%20these%20examples%20are%20standalone%20and%20tightly%20coupled%20with%20their%20generated%20configuration%20(clocks%2C%20pins%2C%20peripherals)%2C%20so%20they%20cannot%20be%20directly%20%E2%80%9Cplugged%E2%80%9D%20into%20an%20existing%20project%20without%20alignment.%3C%2FLI%3E%0A%3CLI%3EIntegrating%20example%20source%20code%20into%20your%20application%20always%20requires%20manual%20adaptation%20of%20configuration%20and%20initialization.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EFrom%20migration%20perspective%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThere%20is%20no%20automatic%20migration%20tool%20between%20RTD%20versions.%3C%2FLI%3E%0A%3CLI%3EEven%20when%20using%20*.mex%20import%2C%20configuration%20differences%20between%20RTD%20versions%20often%20lead%20to%20errors%20that%20must%20be%20resolved%20manually.%3C%2FLI%3E%0A%3CLI%3ERecommended%20approach%20is%20to%20create%20a%20new%20project%20(especially%20when%20moving%20to%20RTD%207.x)%20and%20port%20the%20application%20incrementally.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThe%20SW32K3%20FreeRTOS%2011.1.0%20version%200.8.0%20CD1%20is%20intended%20to%20be%20used%20with%20SW32K3_S32M27x_RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite%3C%2FP%3E%0A%3CP%3EBR%2C%20Petr%3C%2FP%3E%3C%2FLINGO-BODY%3E