DAVE™ Forum Discussions
text.format{('custom.tabs.no.results')}
Sort by:
DAVE™
I was grubbing around in my project looking at typedefs to find out if stddef.h and stdbool.h were included anywhere. I found ./Dave/Generated/inc/LI...
Show More
I was grubbing around in my project looking at typedefs to find out if stddef.h and stdbool.h were included anywhere. I found ./Dave/Generated/inc/LIBS/types.h in which are the following lines:
#include "stdint.h"I noticed a yellow box to the left of the second line so I hovered my mouse over it and it says Unresolved inclusion: "stddef.h". Neither of these files is in the same directory as types.h, so why don't they both have the same indication? Why are the filenames in quotes instead of <...>? Show Less
#include "stddef.h"
DAVE™
Let me start by saying that I am a total noob to the world of Infineon, XMC, Eclipse, and DAVE. With that in mind...I'm trying to develop an applicat...
Show More
Let me start by saying that I am a total noob to the world of Infineon, XMC, Eclipse, and DAVE. With that in mind...
I'm trying to develop an application (using DAVE 3 and XMC 2Go). After studying the datasheet I must confess that I am confused about the data buffering and additional FIFO capabilities of the USIC. I see no need for the I2C master to be interrupt-driven and would just as soon use a polling method. This way the I2C master can loop through its duties (in no paticular hurry) while the SPI slave can interrupt this process at any time and demand data or upload some configuration parameters, etc. The DAVE apps API documentation is not stellar and the example projects are minimalistic, at best, with no error handling or real purpose.
I guess I'm looking for some real-world expertise and guidance on configuring and structuring this application. Anyone? Show Less
I'm trying to develop an application (using DAVE 3 and XMC 2Go). After studying the datasheet I must confess that I am confused about the data buffering and additional FIFO capabilities of the USIC. I see no need for the I2C master to be interrupt-driven and would just as soon use a polling method. This way the I2C master can loop through its duties (in no paticular hurry) while the SPI slave can interrupt this process at any time and demand data or upload some configuration parameters, etc. The DAVE apps API documentation is not stellar and the example projects are minimalistic, at best, with no error handling or real purpose.
I guess I'm looking for some real-world expertise and guidance on configuring and structuring this application. Anyone? Show Less
DAVE™
Hi,I´m doing a project with the IO004 App and the USBD_VCOM App. When i try to solve the project i get about 25 errors: "Failed to start solver. Pleas...
Show More
Hi,
I´m doing a project with the IO004 App and the USBD_VCOM App. When i try to solve the project i get about 25 errors: "Failed to start solver. Please check whether selected device is installed."
The resource of most of the errors are apps, that i don´t use in my project, like "PWMSP001, PWMSP002, IO003, USBVC001" etc. I don´t know why this happens. Nevertheless i can debug my code but it does not work like it should.
What can I do to solve this Problems?
Lukas Show Less
I´m doing a project with the IO004 App and the USBD_VCOM App. When i try to solve the project i get about 25 errors: "Failed to start solver. Please check whether selected device is installed."
The resource of most of the errors are apps, that i don´t use in my project, like "PWMSP001, PWMSP002, IO003, USBVC001" etc. I don´t know why this happens. Nevertheless i can debug my code but it does not work like it should.
What can I do to solve this Problems?
Lukas Show Less
DAVE™
How can I get the device description for XMC4108-F64K64 AB?The current Dave3 Version only offers XMC4108-Q48K64 AB.Any Patch/Workaround available?
Show More
How can I get the device description for XMC4108-F64K64 AB?
The current Dave3 Version only offers XMC4108-Q48K64 AB.
Any Patch/Workaround available? Show Less
The current Dave3 Version only offers XMC4108-Q48K64 AB.
Any Patch/Workaround available? Show Less
DAVE™
Hello,some Dave3 produced code:/********************************************************************************* DAVE App Name : USBBL001 App ...
Show More
Hello,
some Dave3 produced code:
!?
BR,
Daniel
P.S.: no parallel build, no ccache Show Less
some Dave3 produced code:
/*******************************************************************************
** 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[FATFS003_Conf.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 : App Developer **
** **
** MAY BE CHANGED BY USER [yes/no]: Yes **
** **
** MODIFICATION DATE : Jan 25, 2014 **
** **
*******************************************************************************/
/*******************************************************************************
** Author(s) Identity **
********************************************************************************
** **
** Initials Name **
** ---------------------------------------------------------------------------**
** SK App Developer **
*******************************************************************************/
/**
* @file FATFS003_Conf.c
*
* @App Version FATFS003 <1.0.8>
*
* @brief Configuration file generated based on UI settings
* of FATFS003 App
*
* Revision History
* 13 Sep 2012 v1.0.0 Initial version
* 22 Jul 2013 v1.0.2 Ported for XMC4400/4200 Devices and Related SW IDs
* are added.
* XMC4500 Series AB Step Supported.
* Defect ID25204 "Fatfs not working with RTOS with
* default settings" is fixed.
* 29 Nov 2013 v1.0.4 Supported XMC1000 Devices and Related SW IDs are added.
*
* 25 Jan 2014 v1.0.6 Supported latest version of FatFs module R0.09b
*
*
*/
/*******************************************************************************
** INCLUDE FILES **
*******************************************************************************/
#include "../../inc/FATFS002/ffconf.h"
#include
/*****************************************************************************
DUMMY DEFINTIONS OF DEBUG LOG MACROS
*****************************************************************************/
/*These definitions are included here to avoid compilation errors,
since the DBG002 app is not part of the project. All the macros are defined
as empty*/
#ifndef _DBG002_H_
#define DBG002_RegisterCallBack(A,B,C)
#define DBG002_I(e)
#define DBG002_IG(e,g)
#define DBG002_IH(e,h)
#define DBG002_IP(e,p)
#define DBG002_IGH(e,g,h)
#define DBG002_IGP(e,g,p)
#define DBG002_IHP(e,h,p)
#define DBG002_IGHP(e,g,h,p)
#define DBG002_N(e)
#define DBG002_NG(e,g)
#define DBG002_NH(e,h)
#define DBG002_NP(e,p)
#define DBG002_NGH(e,g,h)
#define DBG002_NGP(e,g,p)
#define DBG002_NHP(e,h,p)
#define DBG002_NGHP(e,g,h,p)
#define DBG002_ID(e)
#define DBG002_IS(e)
#define DBG002_ISG(e,g)
#define DBG002_SAFETY_CRITICAL(groupid,messageid,length,value)
#define DBG002_CRITICAL(groupid,messageid,length,value)
#define DBG002_ERROR(groupid,messageid,length,value)
#define DBG002_WARNING(groupid,messageid,length,value)
#define DBG002_INFO(groupid,messageid,length,value)
#define DBG002_TRACE(groupid,messageid,length,value)
#define DBG002_FUNCTION_ENTRY(GID, Status)
#define DBG002_FUNCTION_EXIT(GID, Status)
#define DBG002_MESSAGEID_LITERAL
#endif/* End of definitions of dummy Debug Log macros*/
/*******************************************************************************
** Global Variable Definitions **
*******************************************************************************/
#if _FS_REENTRANT
/** Create 4 Mutex instances for each volume/logical drives. Only four
* primary-partitions can be mounted. Extended partition is not supported.
*/
FATFS002_MutexInfoType FATFS002_MutexInfo[FATFS002_MAX_LOGICAL_DRIVES];
/* Mutex definations */
osMutexDef(Drive0Mutex1);
osMutexDef(Drive1Mutex2);
osMutexDef(Drive2Mutex3);
osMutexDef(Drive3Mutex4);
osMutexDef(MutexToProtect);
volatile osMutexId FATFS002_MutexProtectId;
volatile status_t Status;
#endif
/*******************************************************************************
** Public Function Definitions **
*******************************************************************************/
/* This functions creates mutex for the file system. Since Fatfs doesn't supports
* extended partition feature, only 4 logical partitions can be created.
*/
void FATFS002_Init()
{
#if _FS_REENTRANT
/* Drive0 Mutex 1 */
FATFS002_MutexInfo[0].MutexId = osMutexCreate (osMutex(Drive0Mutex1));
if (/* !N_DBG*/(NULL == FATFS002_MutexInfo[0].MutexId ))
{
Status = FATFS002_MUTEX_CREATE_FAILED;
DBG002_ERROR(DBG002_GID_FATFS002, DBG002_MESSAGEID_LITERAL, 4, &Status);
}
FATFS002_MutexInfo[1].MutexId = osMutexCreate (osMutex(Drive1Mutex2));
if (/* !N_DBG*/(NULL == FATFS002_MutexInfo[1].MutexId ))
{
Status = FATFS002_MUTEX_CREATE_FAILED;
DBG002_ERROR(DBG002_GID_FATFS002, DBG002_MESSAGEID_LITERAL, 4, &Status);
}
FATFS002_MutexInfo[2].MutexId = osMutexCreate (osMutex(Drive2Mutex3));
if (/* !N_DBG*/(NULL == FATFS002_MutexInfo[2].MutexId ))
{
Status = FATFS002_MUTEX_CREATE_FAILED;
DBG002_ERROR(DBG002_GID_FATFS002, DBG002_MESSAGEID_LITERAL, 4, &Status);
}
FATFS002_MutexInfo[3].MutexId = osMutexCreate (osMutex(Drive3Mutex4));
if (/* !N_DBG*/(NULL == FATFS002_MutexInfo[3].MutexId ))
{
Status = FATFS002_MUTEX_CREATE_FAILED;
DBG002_ERROR(DBG002_GID_FATFS002, DBG002_MESSAGEID_LITERAL, 4, &Status);
}
FATFS002_MutexProtectId = osMutexCreate (osMutex(MutexToProtect));
... [shortened] ...
!?
BR,
Daniel
P.S.: no parallel build, no ccache Show Less
DAVE™
I am using the GUISL001 app to put out strings on the HMI board's OLED display. After code generation the GUILC001 App (v1.0.6) causes build errors. ....
Show More
I am using the GUISL001 app to put out strings on the HMI board's OLED display. After code generation the GUILC001 App (v1.0.6) causes build errors.
In fact, I am using IO004 Handle19 for the OLED_CMD pin. Thus, the definition in GUILC001.c
was generated erroneously.
Show Less
../Dave/Generated/src/GUILC001/GUILC001.c:190:3: error: 'IO004_Handle9' undeclared (first use in this function)
In fact, I am using IO004 Handle19 for the OLED_CMD pin. Thus, the definition in GUILC001.c
#define GUILC001_IOHandle (IO004_Handle9)
was generated erroneously.
Show Less
DAVE™
How to change permanently background of editor when opening file belonging to inactive DAVE project?
DAVE™
Found an easy way to cause a Debugger Crash with the following signature.Simply create a C++ object and define a global variable. Enter the Debugge...
Show More
Found an easy way to cause a Debugger Crash with the following signature.
Simply create a C++ object and define a global variable. Enter the Debugger. Before even starting the app, attempt to display the global variable in the .cpp file. Crashes every time.
This should be fixed ASAP for anyone wanting to use C++ on your platform
Problem signature:
Problem Event Name: APPCRASH
Application Name: taskingdebugger.exe
Application Version: 1.29.0.0
Application Timestamp: 52f0c42a
Fault Module Name: libcifcarm_1.dll
Fault Module Version: 1.91.0.0
Fault Module Timestamp: 52f0c4c7
Exception Code: c0000005
Exception Offset: 000315f7
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt Show Less
Simply create a C++ object and define a global variable. Enter the Debugger. Before even starting the app, attempt to display the global variable in the .cpp file. Crashes every time.
This should be fixed ASAP for anyone wanting to use C++ on your platform
Problem signature:
Problem Event Name: APPCRASH
Application Name: taskingdebugger.exe
Application Version: 1.29.0.0
Application Timestamp: 52f0c42a
Fault Module Name: libcifcarm_1.dll
Fault Module Version: 1.91.0.0
Fault Module Timestamp: 52f0c4c7
Exception Code: c0000005
Exception Offset: 000315f7
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt Show Less
DAVE™
Hello, I am trying to access the DAVE User Manual, most of the Figures are blank and when I tried to Search, the indexing is now frozen at 38%. Is the...
Show More
Hello,
I am trying to access the DAVE User Manual, most of the Figures are blank and when I tried to Search, the indexing is now frozen at 38%.
Is there a PDF of the manual available? Any other help?
Thanks in advance,
Kevin Show Less
I am trying to access the DAVE User Manual, most of the Figures are blank and when I tried to Search, the indexing is now frozen at 38%.
Is there a PDF of the manual available? Any other help?
Thanks in advance,
Kevin Show Less
DAVE™
Hi Infineon,as far as I see at the moment it's not possible to program an external flash at EBU (at actual project: Spansion S29AL016J) via tasking de...
Show More
Hi Infineon,
as far as I see at the moment it's not possible to program an external flash at EBU (at actual project: Spansion S29AL016J) via tasking debugger. On Altium website, the user guide of the Tasking VX-toolset for ARM V5.0 describes on page 283 a version of the Tasking debugger, which offers this possibility. Please are any plans to add this version to a future release of Dave?
Best regards,
Wolfgang Show Less
as far as I see at the moment it's not possible to program an external flash at EBU (at actual project: Spansion S29AL016J) via tasking debugger. On Altium website, the user guide of the Tasking VX-toolset for ARM V5.0 describes on page 283 a version of the Tasking debugger, which offers this possibility. Please are any plans to add this version to a future release of Dave?
Best regards,
Wolfgang Show Less