DAVE™ Forum Discussions
DAVE™
Hi everybodyI have a issue in DAVE debug.My code free run is okay in debug mode, yesterday.butToday, this code can't free running in debug mode.when I...
Show More
Hi everybody
I have a issue in DAVE debug.
My code free run is okay in debug mode, yesterday.
but
Today, this code can't free running in debug mode.
when I free run my code in debug mode, always jump to it (following picture)
Please, I need your help & support it.
Show Less
I have a issue in DAVE debug.
My code free run is okay in debug mode, yesterday.
but
Today, this code can't free running in debug mode.
when I free run my code in debug mode, always jump to it (following picture)
Please, I need your help & support it.
Show Less
DAVE™
Dear Community!The goal of this post to help you in case you have faced with the came problem I did. Namely when using Davefor compile, Eclipse hangs ...
Show More
Dear Community!
The goal of this post to help you in case you have faced with the came problem I did. Namely when using Dave
for compile, Eclipse hangs up for minutes saying is waiting for background activities to complete.
This happens both during build/clean.
The reason for this:
The default build command is like this: "${ARM_GCC_HOME}/bin/make" --output-sync
When I remove the addtitional flags resulting this:
"${ARM_GCC_HOME}/bin/make" ,
then building and cleaning running flawless.
Note that the above described problem does not occurs always, but it can be quite easily demonstrated.
I'd ask also the developers of the IDE to consider removing these switched, since I'am concerned if the are really needed.
Version:DAVE-IDE-4.4.2-64Bit
Have a nice day! Show Less
The goal of this post to help you in case you have faced with the came problem I did. Namely when using Dave
for compile, Eclipse hangs up for minutes saying is waiting for background activities to complete.
This happens both during build/clean.
The reason for this:
The default build command is like this: "${ARM_GCC_HOME}/bin/make" --output-sync
When I remove the addtitional flags resulting this:
"${ARM_GCC_HOME}/bin/make" ,
then building and cleaning running flawless.
Note that the above described problem does not occurs always, but it can be quite easily demonstrated.
I'd ask also the developers of the IDE to consider removing these switched, since I'am concerned if the are really needed.
Version:DAVE-IDE-4.4.2-64Bit
Have a nice day! Show Less
DAVE™
Today we published new versions of DAVE, DAVE APPs, XMC Lib, Device Descriptions, and Device Support Pack.DAVE v4.4.2New features:Board selection opti...
Show More
Today we published new versions of DAVE, DAVE APPs, XMC Lib, Device Descriptions, and Device Support Pack.
DAVE v4.4.2
New features:
Download New DAVE v4.4.2
Download DAVE 4.4.2 release note
The SDK for DAVE v4.4.2 will be released later.
DAVE APPs
25 DAVE APPs have been updated (fixing of issues, adding new features, update)
CCU4_SLICE_CONFIG, CCU8_SLICE_CONFIG, CLOCK_XMC1, CMSIS_DSP, CMSIS_RTOS_RTX, CRC_SW, DAC_LUT, E_EEPROM_XMC4, ECAT_SSC, ETH_LWIP, FATFS, FREERTOS, GLOBAL_POSIF, GLOBAL_SCU_XMC1, GLOBAL_SCU_XMC4, HTTP_SERVER, I2C_MASTER, I2C_SLAVE, PMSM_FOC, PWM_BC, PWM_SVM, RTC, SPI_MASTER, UART_CONFIG, VADC_GLOBAL_CONFIG
Contributed DAVE APPs
2 DAVE APPs have been updated: SEGGER_RTT, UCPROBE
Download release note (contains also the changes of the contributed DAVE APPs)
Please note, a user action is required when migrating an existing project to the new version of the UART_CONFIG APP (described in the release note).
DAVE Device Description
The device descriptions for the XMC1400 series and the XMC4300 series have been updated with missing connectivity and alternate function options.
Download release note
DAVE Device Pack v2.2.2
Update to XMC Lib v2.1.18
Update to CMSIS 5.2.0
Support for new devices added
Board Support added (can only be us along with DAVE v4.4.2 and not with earlier DAVE version)
Updates of CMSIS startup and system files
Download release note
Download the complete library update sites as zip file for DAV 4.4.2 (is already included when downloading the new DAVE 4.4.2 version).
Download the complete library store for DAVE v4.3.2 and older Versions (without board support schemes).
XMC Lib v2.1.18
15 XMC Libs are updated:
Common, CAN, CCU4, CCU8, DMA, ETH_MAC, FCE, FLASH, GPIO, I2C, MATH, UART, USIC, SCU, VADC
Download release note
Download XMC Lib v 2.1.18 package
The current web sites of DAVE are not full updated, this will happen within the next couple of day.
Also the CMSIS PACKs for XMC100 and XMC4000 have been updated.
They can be directly updated from the web using the PACK installer in the respective tools.
Or can be downloaded separately as PACK files:
XMC1000 PACK
XMC4000 PACK Show Less
DAVE v4.4.2
New features:
- Board selection option introduced.
- Library store default path is moved to DAVE package
- DAVE package is upgraded from Eclipse Luna to Neon package
- Please note that DAVE 4.4.2 is coming as zip file without installer (details in the installation instructions
Download New DAVE v4.4.2
Download DAVE 4.4.2 release note
The SDK for DAVE v4.4.2 will be released later.
DAVE APPs
25 DAVE APPs have been updated (fixing of issues, adding new features, update)
CCU4_SLICE_CONFIG, CCU8_SLICE_CONFIG, CLOCK_XMC1, CMSIS_DSP, CMSIS_RTOS_RTX, CRC_SW, DAC_LUT, E_EEPROM_XMC4, ECAT_SSC, ETH_LWIP, FATFS, FREERTOS, GLOBAL_POSIF, GLOBAL_SCU_XMC1, GLOBAL_SCU_XMC4, HTTP_SERVER, I2C_MASTER, I2C_SLAVE, PMSM_FOC, PWM_BC, PWM_SVM, RTC, SPI_MASTER, UART_CONFIG, VADC_GLOBAL_CONFIG
Contributed DAVE APPs
2 DAVE APPs have been updated: SEGGER_RTT, UCPROBE
Download release note (contains also the changes of the contributed DAVE APPs)
Please note, a user action is required when migrating an existing project to the new version of the UART_CONFIG APP (described in the release note).
DAVE Device Description
The device descriptions for the XMC1400 series and the XMC4300 series have been updated with missing connectivity and alternate function options.
Download release note
DAVE Device Pack v2.2.2
Update to XMC Lib v2.1.18
Update to CMSIS 5.2.0
Support for new devices added
Board Support added (can only be us along with DAVE v4.4.2 and not with earlier DAVE version)
Updates of CMSIS startup and system files
Download release note
Download the complete library update sites as zip file for DAV 4.4.2 (is already included when downloading the new DAVE 4.4.2 version).
Download the complete library store for DAVE v4.3.2 and older Versions (without board support schemes).
XMC Lib v2.1.18
15 XMC Libs are updated:
Common, CAN, CCU4, CCU8, DMA, ETH_MAC, FCE, FLASH, GPIO, I2C, MATH, UART, USIC, SCU, VADC
Download release note
Download XMC Lib v 2.1.18 package
The current web sites of DAVE are not full updated, this will happen within the next couple of day.
Also the CMSIS PACKs for XMC100 and XMC4000 have been updated.
They can be directly updated from the web using the PACK installer in the respective tools.
Or can be downloaded separately as PACK files:
XMC1000 PACK
XMC4000 PACK Show Less
DAVE™
I discovered an issue, while creating a binary image to flash on the xmc4800 with my runtime software in it.DAVE generates a binary image with missing...
Show More
I discovered an issue, while creating a binary image to flash on the xmc4800 with my runtime software in it.
DAVE generates a binary image with missing bites
It is certainly a bug, we added the missing bytes (highlighted), after checking for them while debugging.
Adding those, the CPU will boot, while without them it isn't working at all.
Is there a way to avoid this? Is it known?
Show Less
DAVE generates a binary image with missing bites
It is certainly a bug, we added the missing bytes (highlighted), after checking for them while debugging.
Adding those, the CPU will boot, while without them it isn't working at all.
Is there a way to avoid this? Is it known?
Show Less
DAVE™
I have a project which was working flawlessly. I added some DAVE Apps, imported their configuration from another projet. Then, when I generate code, t...
Show More
I have a project which was working flawlessly. I added some DAVE Apps, imported their configuration from another projet.
Then, when I generate code, this error message appears: "Failed to generate code for the following templates, check problems view", template name is xmc_eschwc.tmpl, APP name is ECAT_SSC.
the Problems, Problems Detail and Console views are empty, is there some other place to look into? I exported the Collect Problem Data log files and there is this exception:
!ENTRY DAVE CE 4 0 2018-03-19 11:56:23.415
!MESSAGE
***START of Exception Info***
C:\Workspaces\DAVE-4.3-64Bit\WS_2016_09_02\XMC4800_EtherCat_CiA402%20-3\Dave\Model\APPS\ECAT_SSC\v4_0_6\Templates\Infineon_XMC_ECAT_SSC_Config.xml
sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
java.nio.file.Files.copy(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)
org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88)
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
Model.APPS.ECAT_SSC.v4_0_6.Templates.xmc_eschwc.run(xmc_eschwc.tmpl:24)
com.ifx.davex.ce.core.codegeneration.GroovyTemplateEngine$Mywritable.writeTo(GroovyTemplateEngine.java:104)
com.ifx.davex.ce.core.codegeneration.GroovyTemplateEngine$Mywritable.toString(GroovyTemplateEngine.java:112)
com.ifx.davex.ce.core.codegeneration.CodeGenerationEngine.generateContents(CodeGenerationEngine.java:97)
com.ifx.davex.ce.core.codegeneration.FileProviderCTemplate.writeToFile(FileProviderCTemplate.java:318)
com.ifx.davex.ce.core.codegeneration.FileProviderCTemplate.generateFile(FileProviderCTemplate.java:177)
com.ifx.davex.ce.core.codegeneration.FileProviderCTemplate.provide(FileProviderCTemplate.java:97)
com.ifx.davex.ce.core.codegeneration.CodeGenerationManager.generate(CodeGenerationManager.java:520)
com.ifx.davex.ce.core.codegeneration.CodeGenerationManager.access$0(CodeGenerationManager.java:510)
com.ifx.davex.ce.core.codegeneration.CodeGenerationManager$CodeGenCallble.call(CodeGenerationManager.java:145)
java.util.concurrent.FutureTask.run(Unknown Source)
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)
***END of Exception Info***
After removing the new Apps the generating error persists, but I can clean and rebuild my project.
Any idea?
Thanks. Show Less
Then, when I generate code, this error message appears: "Failed to generate code for the following templates, check problems view", template name is xmc_eschwc.tmpl, APP name is ECAT_SSC.
the Problems, Problems Detail and Console views are empty, is there some other place to look into? I exported the Collect Problem Data log files and there is this exception:
!ENTRY DAVE CE 4 0 2018-03-19 11:56:23.415
!MESSAGE
***START of Exception Info***
C:\Workspaces\DAVE-4.3-64Bit\WS_2016_09_02\XMC4800_EtherCat_CiA402%20-3\Dave\Model\APPS\ECAT_SSC\v4_0_6\Templates\Infineon_XMC_ECAT_SSC_Config.xml
sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
java.nio.file.Files.copy(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324)
org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)
org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88)
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45)
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
Model.APPS.ECAT_SSC.v4_0_6.Templates.xmc_eschwc.run(xmc_eschwc.tmpl:24)
com.ifx.davex.ce.core.codegeneration.GroovyTemplateEngine$Mywritable.writeTo(GroovyTemplateEngine.java:104)
com.ifx.davex.ce.core.codegeneration.GroovyTemplateEngine$Mywritable.toString(GroovyTemplateEngine.java:112)
com.ifx.davex.ce.core.codegeneration.CodeGenerationEngine.generateContents(CodeGenerationEngine.java:97)
com.ifx.davex.ce.core.codegeneration.FileProviderCTemplate.writeToFile(FileProviderCTemplate.java:318)
com.ifx.davex.ce.core.codegeneration.FileProviderCTemplate.generateFile(FileProviderCTemplate.java:177)
com.ifx.davex.ce.core.codegeneration.FileProviderCTemplate.provide(FileProviderCTemplate.java:97)
com.ifx.davex.ce.core.codegeneration.CodeGenerationManager.generate(CodeGenerationManager.java:520)
com.ifx.davex.ce.core.codegeneration.CodeGenerationManager.access$0(CodeGenerationManager.java:510)
com.ifx.davex.ce.core.codegeneration.CodeGenerationManager$CodeGenCallble.call(CodeGenerationManager.java:145)
java.util.concurrent.FutureTask.run(Unknown Source)
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)
***END of Exception Info***
After removing the new Apps the generating error persists, but I can clean and rebuild my project.
Any idea?
Thanks. Show Less
DAVE™
When trying to run a sample code for the 24v shield I keep getting the followingError in services launch sequenceLaunching command [/JLinkGDBServerCL....
Show More
When trying to run a sample code for the 24v shield I keep getting the following
Error in services launch sequence
Launching command [/JLinkGDBServerCL.exe -if swd -device XMC1100-T038x0064 -endian little -speed auto -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0] failed.
Launching command [/JLinkGDBServerCL.exe -if swd -device XMC1100-T038x0064 -endian little -speed auto -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0] failed.
Cannot run program "/JLinkGDBServerCL.exe": Launching failed
When debugging it.
Following the steps for setup from this page
https://www.infineon.com/dgdl/Infineon-24V_ProtectedSwitchShield_with_Profet+24V_for_Arduino_UsersManual_10.pdf-UM-v01_00-EN.pdf?fileId=5546d46255dd933d0156074933e91fe2
Any help would be greatly appreciated. Show Less
Error in services launch sequence
Launching command [/JLinkGDBServerCL.exe -if swd -device XMC1100-T038x0064 -endian little -speed auto -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0] failed.
Launching command [/JLinkGDBServerCL.exe -if swd -device XMC1100-T038x0064 -endian little -speed auto -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0] failed.
Cannot run program "/JLinkGDBServerCL.exe": Launching failed
When debugging it.
Following the steps for setup from this page
https://www.infineon.com/dgdl/Infineon-24V_ProtectedSwitchShield_with_Profet+24V_for_Arduino_UsersManual_10.pdf-UM-v01_00-EN.pdf?fileId=5546d46255dd933d0156074933e91fe2
Any help would be greatly appreciated. Show Less
DAVE™
Hello, i have a problem. Dave 4.2.2 shuts down in iSystem debug mode (in GDB SEGGER ... debug mode no problems). I can see iSystem debug mode just for...
Show More
Hello, i have a problem. Dave 4.2.2 shuts down in iSystem debug mode (in GDB SEGGER ... debug mode no problems). I can see iSystem debug mode just for a few seconds 1-2. I have also dave 3 + iSystem but I don't use them at the same time. So it is a problem with eclipse perspective mode with iSystem.
Show Less
DAVE™
I just tried to upgrade the apps in my project. I went from DAVE 4.2.8 to 4.4.2. For I2C_MASTER I got this warning:tx pin WARNING Hardware connecti...
Show More
I just tried to upgrade the apps in my project. I went from DAVE 4.2.8 to 4.4.2. For I2C_MASTER I got this warning:
tx pin WARNING Hardware connection has been removed in new version of APP: I2C_MASTER_0
I2C_MASTER went from v4.1.12 to v4.1.26. Since there never was a tx pin, what could this possibly mean? Oh yes, the program doesn't work anymore.
Randy Show Less
tx pin WARNING Hardware connection has been removed in new version of APP: I2C_MASTER_0
I2C_MASTER went from v4.1.12 to v4.1.26. Since there never was a tx pin, what could this possibly mean? Oh yes, the program doesn't work anymore.
Randy Show Less
DAVE™
New to DAVE and uP programing.. How do I display the value of a variable in the Debugger? For example, the Value of an A to D conversion.Is there...
Show More
New to DAVE and uP programing.. How do I display the value of a variable in the Debugger?
For example, the Value of an A to D conversion.
Is there some code I need to add to the program itself? At the moment I am using the XMC relax kit.
Regards,
Rick Show Less
For example, the Value of an A to D conversion.
Is there some code I need to add to the program itself? At the moment I am using the XMC relax kit.
Regards,
Rick Show Less
DAVE™
Hi all, we developed a board with two infineon CPUs, one XMCC4800 144x2048, one XMC 4500 144x1024. We have a JTAG connector linked to both the CPUs bu...
Show More
Hi all, we developed a board with two infineon CPUs, one XMCC4800 144x2048, one XMC 4500 144x1024.
We have a JTAG connector linked to both the CPUs but in the debugger i couldn't find the target to debug.
I mean, i created a new project with just a simple PWM on P1.3, and i want to debug it targetting the XMC4500 to see if the board is working, and i will to the same on the XMC4800.
How can i achieve this?
Here is the JTAG configuration
Show Less
We have a JTAG connector linked to both the CPUs but in the debugger i couldn't find the target to debug.
I mean, i created a new project with just a simple PWM on P1.3, and i want to debug it targetting the XMC4500 to see if the board is working, and i will to the same on the XMC4800.
How can i achieve this?
Here is the JTAG configuration
Show Less