Oct 30, 2019
02:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 30, 2019
02:45 AM
Hello,
I have a problem with configuration of Port 33.8 to be the FSP output signal of SMU. I have followed the Aurix user manual and SafeTlib manual and i'm doing the following:
The Port 33.8 is configuration:
Pin Direction: Pin_Out
Initial mode: MODE_GPIO
Initial_Level: LEVEL_HIGH
Output Characteristic: OUT_PUSHPULL
Pad Level: CMOS_AUTOMOTIVE_LEVEL
SMU:
- SafeTlib is starting to execute the early-prerun test and prerun test
- the SMU_Init() is called before the prerun test with the default SMU configuration.
- by starting the MCAL, SMU_DeInit() is called
- then SMU_Init() with the required SMU configuration (ALM3_15, 16 are enabled with FSP enabled)
- Smu_SetupErrorPin() is called to config the Port33.8 to be as FSP of SMU.
- the behavior is: SMU_FSP[0] = high , Port 33.8 = high
in case of error injection ALM3_16, SMU_FSP[0] = low, Port 33.8 = high (no change)
- the Port 33.8 looks like it still as GPIO and not getting the FSP signal from the SMU. how to solve this problem ?
I have a problem with configuration of Port 33.8 to be the FSP output signal of SMU. I have followed the Aurix user manual and SafeTlib manual and i'm doing the following:
The Port 33.8 is configuration:
Pin Direction: Pin_Out
Initial mode: MODE_GPIO
Initial_Level: LEVEL_HIGH
Output Characteristic: OUT_PUSHPULL
Pad Level: CMOS_AUTOMOTIVE_LEVEL
SMU:
- SafeTlib is starting to execute the early-prerun test and prerun test
- the SMU_Init() is called before the prerun test with the default SMU configuration.
- by starting the MCAL, SMU_DeInit() is called
- then SMU_Init() with the required SMU configuration (ALM3_15, 16 are enabled with FSP enabled)
- Smu_SetupErrorPin() is called to config the Port33.8 to be as FSP of SMU.
- the behavior is: SMU_FSP[0] = high , Port 33.8 = high
in case of error injection ALM3_16, SMU_FSP[0] = low, Port 33.8 = high (no change)
- the Port 33.8 looks like it still as GPIO and not getting the FSP signal from the SMU. how to solve this problem ?
- Tags:
- aurix tc297
- IFX
- smu
6 Replies
Oct 30, 2019
04:55 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 30, 2019
04:55 AM
Which device you are using? Wish value contains SMU_PCTL when the error is triggered?
Oct 30, 2019
05:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 30, 2019
05:58 AM
I'm using Aurix TC297. the SMU_PCTL = 0x00F00083
Oct 30, 2019
06:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 30, 2019
06:03 AM
I have attached 3 screen shots for the SMU, EVR and Port33 registers
Oct 30, 2019
07:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 30, 2019
07:44 AM
Which value shows the P33_IN register? The register P33_OUT contains the static values which are driven if the pin configured as GPIO, this can be different from the real level on the pins if the pins is not configured as GPIO (e.g. in your case). To get the actual level on the pin itself you must check the Pxx_IN register.
Oct 30, 2019
09:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 30, 2019
09:18 AM
the P33_IN value of this pin 8 = low although the P33_OUT = high (see the attachment)
Oct 31, 2019
01:59 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 31, 2019
01:59 AM
Your P33.8 is low, when you measure the pin you will get the same result. Only the Pxx_IN register shows the actual state of the pin Independent of the I/O setting. P33_OUT is only the value which will be driven when the pin is configured as GPIO. Also when set a pin as GPIO with a weak drive level and you have a shortcut outside then the Pxx_OUT will show a 1 (which you will drive) but the pin itself is low also the Pxx_In will Show 0...