DAVE™ Forum Discussions

Check out the details from "Indonesia Robo Fest 2014 - Total prize of 60 Million Rupiah to be won!" event page. Show Less

Hi All,

I am wondering if there is an error in the "PWMSP002_SetPwmFreqAndDutyCycle" function when it calculates the timer value if concatenation is required. My PWMSP002 is configured for Edge Aligned Counting Mode and Symetric Compare Mode.

The function calculates the count to load into the CCU80_CC80.PRS and CCU80_CC81.PRS shadow registers for the required PWM period.

The calculation is actually performed by the "CCU8PWMLIB_lSetPwmFreqTimerConcat" function in the CCU8PWMLIB.c library (code snippet visible in screenshhots).

In the fist example below the MSB and LSB period counts are correct, the second example with a count greater than 65535 the counts seem wrong...

Example 1 (correct)
PwmTime = 65535
Call to CCU8PWMLIB_lSetPwmFreqTimerConcat

    Result
        MsbPeriodVal = 0x00
        LsbPeriodVal = 0xFFFF

Example 2 (incorrect ?)
PwmTime  = 65536
Call to CCU8PWMLIB_lSetPwmFreqTimerConcat

     Result
        MsbPeriodVal = 0x3
        LsbPeriodVal = 0x3FFF

Am I missing something ?

Any help would be greatly appreciated.

Best regards
Aaron Show Less

Hi All,

It seems the "PWMSP002_Start" function does not work correctly if 2 CCU8y timer slices are concatenated.

For example if the concatenated timer is preset with 0x1FFFE and the PWMSP002_Start function is called the timer counts up as follows....

0x1FFFE
0x1FFFF
0x10000
0x10001
,
,
,
0x1FFFF
0x20000

The high slice did not get incremented when the low slice rolled over the first time.

The following code presets the timer with a value and then waits for the timer to reach 0x20000 while incrementing a counter. The counter reports how many while loop iterations occurred.

// Initialise counter and preset timer
Iterations = 0;
PWMSP002_SetTimerVal(&PWMSP002_Handle2, Preset);

// Start timer and wait for timer to reach 0x20000
PWMSP002_Start(&PWMSP002_Handle2);
while(CCU80_CC81->TIMER < 0x2)
{
    Iterations ++;
};
// Read timer to confirm it reached 0x20000
TimerCount = CCU80_CC81->TIMER << 16 | CCU80_CC80->TIMER;

Here are the results of the while loop iterations...

Preset________While loop iterations
0x00000_______481522
0x03FFF_______411621
0x07FFF_______341719
0x0DC6C_______240764. NOTE : The CCU80 period counter is set to 0x2DC6C (CCU80_CC81.PR = 0x2, CCU80_CC81.PR = 0xDC6C)
0x0DC6D_______520382
0x10000________240762
0x1FFFF________240769 This is almost the same as the 0x10000 preset result suggesting the low slice rolled over twice before incrementing the high slice.

It seems that the problem occurs if the timer is set with a value which is higher than the low slice period even though the concatenated high and low slice period value is greater.

I am running the code on the XMC4500-F100x1024 Stepping Code AB.

Any comments would be most welcome.

Best regards
Aaron Show Less

SW that doesn’t require XMC specific configurations of peripherals or system resources like Clock, Systick, etc. can be added to a DAVE project as in any other IDE.
SW that configures chip resources can also be simply added to a DAVE project.

In order to avoid resource conflicts with the SW from DAVE Apps, the DAVE “Reserve Resource Group” feature can be used:
Go to: > DAVE > Select "Reserve Resource Group" > Input the resource group starting with a slash in the first free field (eg. /cpu/) in "Reserved resource group" window > Press "CTRL + SPACE" > All matched resource group options are listed > Select required resource group(s) (eg. /cpu/0/systick) > click “Solve and Save” --> All selected resource groups will be reserved

Details can be found in Help documentation:
Go to: > Help > Help contents > DAVE user manual > 6 Menu > 6.16 Reserve Resource Group Show Less

Hello,

my Dave3 Project refuses to link. Source of the error is USBBL001_Conf.c:

/*******************************************************************************
**  DAVE App Name : USBBL001       App Version: 1.0.12               
**  This file is generated by DAVE, User modification to this file will be    **
**  overwritten at the next code generation.                                  **
*******************************************************************************/

/*CODE_BLOCK_BEGIN[ADC002.c]*/

/*******************************************************************************
 Copyright (c) 2014, Infineon Technologies AG                                 **
 All rights reserved.                                                         **
                                                                              **
 Redistribution and use in source and binary forms, with or without           **
 modification,are permitted provided that the following conditions are met:   **
                                                                              **
 *Redistributions of source code must retain the above copyright notice,      **
 this list of conditions and the following disclaimer.                        **
 *Redistributions in binary form must reproduce the above copyright notice,   **
 this list of conditions and the following disclaimer in the documentation    **
 and/or other materials provided with the distribution.                       **
 *Neither the name of the copyright holders nor the names of its contributors **
 may be used to endorse or promote products derived from this software without**
 specific prior written permission.                                           **
                                                                              **
 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"  **
 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE    **
 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE   **
 ARE  DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE   **
 LIABLE  FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR         **
 CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF         **
 SUBSTITUTE GOODS OR  SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS    **
 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN      **
 CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)       **
 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE   **
 POSSIBILITY OF SUCH DAMAGE.                                                  **
                                                                              **
 To improve the quality of the software, users are encouraged to share        **
 modifications, enhancements or bug fixes with Infineon Technologies AG       **
 dave@infineon.com).                                                          **
                                                                              **
********************************************************************************
**                                                                            **
**                                                                            **
** PLATFORM : Infineon XMC4000/XMC1000 Series                                 **
**                                                                            **
** COMPILER : Compiler Independent                                            **
**                                                                            **
** AUTHOR   : SSAM                                                              **
**                                                                            **
** MAY BE CHANGED BY USER [yes/no]: Yes                                       **
**                                                                            **
** MODIFICATION DATE : Jan 31, 2014                                           **
**                                                                            **
*******************************************************************************/

/**
 * @file ADC002.c
 *
 * @brief This file contains ADC002 App API definitions
 *
 * Change History:
 * Date         version      Details
 * 12-Dec-2012   1.0.6    Initial code added for XMC1000
 * 30-Jan-2013   1.0.8    App version changed
 * 24-Apr-2013   1.0.12   Ported to XMC4500 step AB
 *                        Source Result selection Feature added
 * 10-Jun-2013   1.0.14   1. Integer Parameter updated in manifest to support
 *                           PMSMFOCSL01 app.
 *                        2. In the Header comment section device name changed
 *                           to XMC1000
 *                        3. Source Result register selection feature disabled
 *                           due to header file update not available.
 * 27-Jun-2013   1.0.16   Source Result register selection feature removed to
 *                         simplify the app.
 * 10-Sep-2013   1.0.18   1. Arbitration slot enable(ASEN) code is moved to the
 *                         end of ADC002_lInit function.
 *                        2. Added support for the following devices under
 *                        XMC1200 and XMC1300 Series XMC1201, XMC1202, XMC1301.
 * 27-Sep-2013   1.0.20   ADC002_InitializeQueue api issue - the queue is not
 *                        created if interrupt is enabled is fixed.
 * 31-Oct-2013   1.0.22   '10 bit Fast compare mode' is made invisible in GUI
 *                        for standard conversion mode.
 * 30-Jan-2014   1.0.26   1. Error codes are added in various functions, that
 *                        can be logged with DBG002 App.
 *                        2. Bugfix for incorrect interrupt-clear in
 *                        ADC002_InitializeQueue API
 */
/**
 * @cond INTERNAL_DOCS
 */

... and so on, the whole code for ADC002.

Does the code generator cache the app code somewhere?
Is it possible to reset the code generator, delete caching directories or so? Show Less

Hiii,Please suggest me what are the considerations to take to calculate dutycycle of PWM,and which Dev APP to be used to run universal motor..


Thank you Show Less

Hi, I am Pilar.

I am trying to debug and RTOS project and I have seen a RTOS and RTOS Windows view in DAVE. But I cannot see anything.
Is it necessary to configure something? How can I configure?

Thank you. Show Less

Hi All,

My understanding of the "PWMSP002_SetTimerVal" function is it allows the timer to be set to a value such that the timer can be started part way through the period. This would allow the PWM signal to have a phase offset to other signals.

I've noticed it is possible to set he timer value greater than the period and I can't think why you would want to do that.

Would it make sense for the function to either truncate the timer value to the period or return an error ?

Best regards
Aaron Show Less

Hi All,

It seems the "PWMSP002_GetTimerRegsVal" App returns an incorrect TimerReg value if 2 timers are concatenated.

For example, the code below sets the timer to 0x1FFFF and reads the TimerReg value back incorrectly as 0xFFFF, the high 16 bits are missing.

Status = PWMSP002_SetTimerVal(&PWMSP002_Handle2, 0x1FFFF);
Status = PWMSP002_GetTimerRegsVal((PWMSP002_HandleType*)&PWMSP002_Handle2, &TimerVal);

Any comments or suggestions would be welcome.

Best regards
Aaron Show Less