Example_S32K344_decouple_RTD400_Ip_C40_DS35

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

Example_S32K344_decouple_RTD400_Ip_C40_DS35

Example_S32K344_decouple_RTD400_Ip_C40_DS35

*******************************************************************************************************
* Detailed Description:
* DCF Record decouples CM7_0 and CM_1 on S32K344
* Find first available location in UTEST.
* By default, first available address is 0x1B000768U
*
* NOTE: There is a bug in the RTD version.
* Change FLS_MAX_VIRTUAL_SECTOR to 528 in C40_Ip_Cfg.h
* ------------------------------------------------------------------------------
* Test HW: : S32K344EVB-Q257
* MCU: : S32K344
* Project : RTD AUTOSAR 4.7
* Platform : CORTEXM
* Peripheral : S32K3XX
* Dependencies : none
* Autosar Version : 4.7.0
* Autosar Revision : ASR_REL_4_7_REV_0000
* Autosar Conf.Variant :
* SW Version : 4.0.0
* Build Version : S32K3_RTD_4_0_0_P20_D2403_ASR_REL_4_7_REV_0000_20240315
*******************************************************************************************************

Attachments
Comments

Hello, @danielmartynek 
I have a few questions and notes:
1) Is it aplicable for s32k358?
2) In the main.c line 33:
     * By default, first available address is 0x1B000780U
I suppose it should be 0x1B000768U according to description

3) in the main.c lines 115 and 116:
    DCF_record[0] = 0x00000100; /* DCF Control Word */
    DCF_record[1] = 0x00100004; /* DCF Data Word, LOCKSTEP = 0 */

I think the comments are incorrect and the first one should be DCF data word and the second DCF control word

4) in the main.c line 116:
 DCF_record[1] = 0x00100004;

is the parity bit missing here and it actually must be 0x00100006 to match parity with DCF_record[0] = 0x00000100; ? 

Hello @dmitry_buchynski,

Thanks for the feedback.

It has been fixed.

 

Regards,

Daniel

%3CLINGO-SUB%20id%3D%22lingo-sub-1866329%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EExample_S32K344_decouple_RTD400_Ip_C40_DS35%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1866329%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%0A%3CP%3E*******************************************************************************************************%3CBR%20%2F%3E*%20Detailed%20Description%3A%3CBR%20%2F%3E*%20DCF%20Record%20decouples%20CM7_0%20and%20CM_1%20on%20S32K344%3CBR%20%2F%3E*%20Find%20first%20available%20location%20in%20UTEST.%3CBR%20%2F%3E*%20By%20default%2C%20first%20available%20address%20is%200x1B000768U%3CBR%20%2F%3E*%3CBR%20%2F%3E*%20%3CSTRONG%3ENOTE%3A%3C%2FSTRONG%3E%20%3CSTRONG%3EThere%20is%20a%20bug%20in%20the%20RTD%20version.%3C%2FSTRONG%3E%3CBR%20%2F%3E*%3CSTRONG%3E%20Change%20FLS_MAX_VIRTUAL_SECTOR%20to%20528%20in%20C40_Ip_Cfg.h%3C%2FSTRONG%3E%3CBR%20%2F%3E*%20------------------------------------------------------------------------------%3CBR%20%2F%3E*%20Test%20HW%3A%20%3A%20S32K344EVB-Q257%3CBR%20%2F%3E*%20MCU%3A%20%3A%20S32K344%3CBR%20%2F%3E*%20Project%20%3A%20RTD%20AUTOSAR%204.7%3CBR%20%2F%3E*%20Platform%20%3A%20CORTEXM%3CBR%20%2F%3E*%20Peripheral%20%3A%20S32K3XX%3CBR%20%2F%3E*%20Dependencies%20%3A%20none%3CBR%20%2F%3E*%20Autosar%20Version%20%3A%204.7.0%3CBR%20%2F%3E*%20Autosar%20Revision%20%3A%20ASR_REL_4_7_REV_0000%3CBR%20%2F%3E*%20Autosar%20Conf.Variant%20%3A%3CBR%20%2F%3E*%20SW%20Version%20%3A%204.0.0%3CBR%20%2F%3E*%20Build%20Version%20%3A%20S32K3_RTD_4_0_0_P20_D2403_ASR_REL_4_7_REV_0000_20240315%3CBR%20%2F%3E*******************************************************************************************************%3C%2FP%3E%0A%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1987126%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20Example_S32K344_decouple_RTD400_Ip_C40_DS35%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1987126%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F220939%22%20target%3D%22_blank%22%3E%40dmitry_buchynski%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3EThanks%20for%20the%20feedback.%3C%2FP%3E%0A%3CP%3EIt%20has%20been%20fixed.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3ERegards%2C%3C%2FP%3E%0A%3CP%3EDaniel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1985447%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20Example_S32K344_decouple_RTD400_Ip_C40_DS35_v1%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1985447%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F160001%22%20target%3D%22_blank%22%3E%40danielmartynek%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EI%20have%20a%20few%20questions%20and%20notes%3A%3CBR%20%2F%3E1)%20Is%20it%20aplicable%20for%20s32k358%3F%3CBR%20%2F%3E2)%20In%20the%20main.c%20line%2033%3A%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%20*%20By%20default%2C%20first%20available%20address%20is%200x1B000780U%3CBR%20%2F%3EI%20suppose%20it%20should%20be%26nbsp%3B%3CSPAN%3E0x1B000768U%20according%20to%20description%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E3)%20in%20the%20main.c%20lines%20115%20and%20116%3A%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20DCF_record%5B0%5D%20%3D%200x00000100%3B%20%2F*%20DCF%20Control%20Word%20*%2F%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20DCF_record%5B1%5D%20%3D%200x00100004%3B%20%2F*%20DCF%20Data%20Word%2C%20LOCKSTEP%20%3D%200%20*%2F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20think%20the%20comments%20are%20incorrect%20and%20the%20first%20one%20should%20be%20DCF%20data%20word%20and%20the%20second%20DCF%20control%20word%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E4)%20in%20the%20main.c%20line%20116%3A%3CBR%20%2F%3E%26nbsp%3BDCF_record%5B1%5D%20%3D%200x00100004%3B%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eis%20the%20parity%20bit%20missing%20here%20and%20it%20actually%20must%20be%200x00100006%20to%20match%20parity%20with%26nbsp%3BDCF_record%5B0%5D%20%3D%200x00000100%3B%20%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
No ratings
Version history
Last update:
‎11-04-2024 07:52 AM
Updated by: