May 05, 2015
04:41 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 05, 2015
04:41 PM
Hello,
it seems to be impossible to use PIN 2.5 and 2.4 as Inputs with POSQE001.
We use XMC4400 F64x256 REV AA with different PCBs, PESQE001 quadrature encoder Mod3.
The Problem: Posif0 is not initialized(does not start), when PIN 2.5 and 2.4 are set in the Manual Pin Assignment.
Posifs registers remain unchanged, Posif0.PRUN is IDLE.
After having changed PIN 2.5 and 2.4 to PIN 1.3 and 1.2 the App works, but not for us, cause the Hardware uses PIN 2.5 and 2.4.
The Problem does not appear using the XMC 4500 Hexagon board, obviously this is a problem DAVE3.1.10-XMC4400.
I changed in the PESQE001.c file the Pinning to P2.4/2.5 (row 672-682), the POSIF starts but does not detect the incoming signals.
By the way:
The Resource Mapping Information table still shows PIN 1.3 and 1.2 instead of the PIN 2.5 and 2.4 when changes are made only in PESQE001.c file.
So what is true?
And what is the reason for this strange behaviour and- much more important - how can we solve this problems?
SBT
it seems to be impossible to use PIN 2.5 and 2.4 as Inputs with POSQE001.
We use XMC4400 F64x256 REV AA with different PCBs, PESQE001 quadrature encoder Mod3.
The Problem: Posif0 is not initialized(does not start), when PIN 2.5 and 2.4 are set in the Manual Pin Assignment.
Posifs registers remain unchanged, Posif0.PRUN is IDLE.
After having changed PIN 2.5 and 2.4 to PIN 1.3 and 1.2 the App works, but not for us, cause the Hardware uses PIN 2.5 and 2.4.
The Problem does not appear using the XMC 4500 Hexagon board, obviously this is a problem DAVE3.1.10-XMC4400.
I changed in the PESQE001.c file the Pinning to P2.4/2.5 (row 672-682), the POSIF starts but does not detect the incoming signals.
By the way:
The Resource Mapping Information table still shows PIN 1.3 and 1.2 instead of the PIN 2.5 and 2.4 when changes are made only in PESQE001.c file.
So what is true?
And what is the reason for this strange behaviour and- much more important - how can we solve this problems?
SBT
- Tags:
- IFX
3 Replies
Not applicable
May 06, 2015
12:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 06, 2015
12:13 AM
Hi SBT,
P2.5 and P2.4 are connected to POSIF1. The encoder mode is configured via PCONF.FSEL.
BR,
Zain
P2.5 and P2.4 are connected to POSIF1. The encoder mode is configured via PCONF.FSEL.
BR,
Zain
May 06, 2015
02:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 06, 2015
02:50 AM
Hi Zain,
you pointed me to the right direction.
POSIF(1) was unaffected also.
The problem is wrong Code here:
void POSQE001_Init(void)
{
status_t Status;
CCU4GLOBAL_Init();
/* Deassert the clock gating under SCU module to enable the Posif peripheral */
SET_BIT(SCU_CLK->CGATCLR0, SCU_CLK_CGATCLR0_POSIF0_Pos);
The App doesnt change POSIF0 to POSIF1 when Pin 2.4/2.5 is selected.
This is a Bug in Dave3.
I hope this will be fixed
Thank you.
SBT
you pointed me to the right direction.
POSIF(1) was unaffected also.
The problem is wrong Code here:
void POSQE001_Init(void)
{
status_t Status;
CCU4GLOBAL_Init();
/* Deassert the clock gating under SCU module to enable the Posif peripheral */
SET_BIT(SCU_CLK->CGATCLR0, SCU_CLK_CGATCLR0_POSIF0_Pos);
The App doesnt change POSIF0 to POSIF1 when Pin 2.4/2.5 is selected.
This is a Bug in Dave3.
I hope this will be fixed
Thank you.
SBT
Not applicable
May 11, 2015
12:34 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 11, 2015
12:34 AM