Oct 22, 2013
05:56 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 22, 2013
05:56 AM
Hi,
It seems that function "status_t PWMSP001_SetTimerVal (const PWMSP001_HandleType *HandlePtr, uint32_t TimerVal) " dont work well.
I am tried this function (during timer was stopped), but there is no way how set the timer start value. (with Relax Lite Kit)
Can some help me?
Thanks
Regards
Koumak
It seems that function "status_t PWMSP001_SetTimerVal (const PWMSP001_HandleType *HandlePtr, uint32_t TimerVal) " dont work well.
I am tried this function (during timer was stopped), but there is no way how set the timer start value. (with Relax Lite Kit)
Can some help me?
Thanks
Regards
Koumak
- Tags:
- IFX
6 Replies
Oct 23, 2013
01:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 23, 2013
01:38 AM
For changing of the timer starting value from default "0" to "other value".
Yes. You should use the PWMSP001_SetTimerVal.
However, there is a bug. The CCU4 is still in "Idle set" mode.
Thus, there is no reaction when Timer = value.
Please try out the following code.
DAVE_Init(); // Initialization of DAVE Apps
CCU40->GIDLC |= 0x10F;
PWMSP001_SetTimerVal((PWMSP001_HandleType*)&PWMSP001_Handle0, 500);
PWMSP001_Start(&PWMSP001_Handle0);
Yes. You should use the PWMSP001_SetTimerVal.
However, there is a bug. The CCU4 is still in "Idle set" mode.
Thus, there is no reaction when Timer = value.
Please try out the following code.
DAVE_Init(); // Initialization of DAVE Apps
CCU40->GIDLC |= 0x10F;
PWMSP001_SetTimerVal((PWMSP001_HandleType*)&PWMSP001_Handle0, 500);
PWMSP001_Start(&PWMSP001_Handle0);
Oct 23, 2013
03:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 23, 2013
03:04 AM
Thanks
with CCU40->GIDLC |= 0x10F; it working
with CCU40->GIDLC |= 0x10F; it working
Not applicable
Oct 23, 2013
03:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 23, 2013
03:07 AM
Not applicable
Aug 19, 2014
01:33 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 19, 2014
01:33 AM
Hi Sophia,
Does this problem affect the PWMSP002 too ?
Thank you
Best regards
Aaron
Does this problem affect the PWMSP002 too ?
Thank you
Best regards
Aaron
Not applicable
Aug 20, 2014
01:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 20, 2014
01:23 AM
Hi Sophia,
My own tests have confirmed that the problem also applies to the PWMSP002 App as well.
As a work around I am using the following code to set the 4 "Idle clear" bits in the CCU80 before calling the "PWMSP002_SetTimerVal" function...
Does another eTicket need to be raised ?
Thanks
Best regards
Aaron
My own tests have confirmed that the problem also applies to the PWMSP002 App as well.
As a work around I am using the following code to set the 4 "Idle clear" bits in the CCU80 before calling the "PWMSP002_SetTimerVal" function...
CCU80->GIDLC |= CCU8_GIDLC_CS3I_Msk | CCU8_GIDLC_CS2I_Msk | CCU8_GIDLC_CS1I_Msk | CCU8_GIDLC_CS0I_Msk;
Does another eTicket need to be raised ?
Thanks
Best regards
Aaron
Not applicable
Aug 20, 2014
07:48 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 20, 2014
07:48 PM
Hi Aaron,
Yes, you are right. However, it is not necessary to raise another eTicket as all relevant cases have been addressed in the internal request.
Best regards,
Sophia
Yes, you are right. However, it is not necessary to raise another eTicket as all relevant cases have been addressed in the internal request.
Best regards,
Sophia