DAVE™ Forum Discussions
DAVE™
HelloI managed to get working UDP protocol with lwip app stack (ETH_LWIP, version 4.0.4) on Relax Kit.But when I build it as "Release" target, it doe...
Show More
Hello
I managed to get working UDP protocol with lwip app stack (ETH_LWIP, version 4.0.4) on Relax Kit.
But when I build it as "Release" target, it does not work. So I tried to simplify the program to isolate the problem.
Just now I have only two task blinking LED and a os timer. Nothing more.
1) In debug build:
LEDs are blinking and I can to ping the Relax kit.
2)In release build:
LEDs are blinking if the Ethernet cable is disconnected from Relax kit. When I connect the cable, Relax kit does not answer to ping.
Moreover after a while (let say 5s) program crashes - LED stop blinking.
Any idea what to try next? Show Less
I managed to get working UDP protocol with lwip app stack (ETH_LWIP, version 4.0.4) on Relax Kit.
But when I build it as "Release" target, it does not work. So I tried to simplify the program to isolate the problem.
Just now I have only two task blinking LED and a os timer. Nothing more.
1) In debug build:
LEDs are blinking and I can to ping the Relax kit.
2)In release build:
LEDs are blinking if the Ethernet cable is disconnected from Relax kit. When I connect the cable, Relax kit does not answer to ping.
Moreover after a while (let say 5s) program crashes - LED stop blinking.
Any idea what to try next? Show Less
DAVE™
Hi:I would like to watch the XMC_DEBUG message in DAVE debug console. I added a define "XMC_DEBUG_ENABLE" in preprocessor and enable semihosting in de...
Show More
Hi:
I would like to watch the XMC_DEBUG message in DAVE debug console.
I added a define "XMC_DEBUG_ENABLE" in preprocessor and enable semihosting in debug option.
But I don't see any debug message in my console.
Do I loss some setting for it?
Robin
Show Less
I would like to watch the XMC_DEBUG message in DAVE debug console.
I added a define "XMC_DEBUG_ENABLE" in preprocessor and enable semihosting in debug option.
But I don't see any debug message in my console.
Do I loss some setting for it?
Robin
Show Less
DAVE™
Today, we have released the first motor control examples package reflecting the new approach to develop and deliver better motor control support soft...
Show More
Today, we have released the first motor control examples package reflecting the new approach to develop and deliver better motor control support software for XMC controllers.
This first package is a BLDC example for DAVE v4, with 3 hall inputs running on the XMC1000 motor control kit.
The BLDC software included in the example allows configuration to different motors, power boards and XMC1300 HW usage. A respective comprehensive document in CHM format is included in the project.
An introduction is summarized in this PDF
The BLDC example is published on the Infineon web.
1. In the SW tab of the XMC1000 Motor Control kit, select - "DAVE™ Example Project 3 Hall Sensor based BLDC Motor Control Example for XMC1300 Series"
2. In the DAVE Example repository (download from DAVE and from a created web page -use keyword BLDC)
Regards,
Daryl Show Less
This first package is a BLDC example for DAVE v4, with 3 hall inputs running on the XMC1000 motor control kit.
The BLDC software included in the example allows configuration to different motors, power boards and XMC1300 HW usage. A respective comprehensive document in CHM format is included in the project.
An introduction is summarized in this PDF
The BLDC example is published on the Infineon web.
1. In the SW tab of the XMC1000 Motor Control kit, select - "DAVE™ Example Project 3 Hall Sensor based BLDC Motor Control Example for XMC1300 Series"
2. In the DAVE Example repository (download from DAVE and from a created web page -use keyword BLDC)
Regards,
Daryl Show Less
DAVE™
I find this macro ENABLE_CPU_CM_001_WORKAROUND in startup_XMC4500.S. Howerver, I could findout where the macro is defined. Is this macro defined for x...
Show More
I find this macro ENABLE_CPU_CM_001_WORKAROUND in startup_XMC4500.S. Howerver, I could findout where the macro is defined. Is this macro defined for xmc4500 step ac chip?
Show Less
DAVE™
Hello!I want to do a line follower robot, but I have a problem in Dave 4.2.4! How can i read the values of two QTR-1A Reflectance Sensor? I mean what ...
Show More
Hello!
I want to do a line follower robot, but I have a problem in Dave 4.2.4! How can i read the values of two QTR-1A Reflectance Sensor? I mean what the code should be? Please help me!!! Show Less
I want to do a line follower robot, but I have a problem in Dave 4.2.4! How can i read the values of two QTR-1A Reflectance Sensor? I mean what the code should be? Please help me!!! Show Less
DAVE™
WireShark file: (192.168.115.74 = XMC4500, 192.168.115.75 = PC)XMC4500 Hexagon Board with Ethernet/CAN/RS485 Interface CardDAVE 4.2.4DAVE Apps webserv...
Show More
WireShark file:
(192.168.115.74 = XMC4500, 192.168.115.75 = PC)
XMC4500 Hexagon Board with Ethernet/CAN/RS485 Interface Card
DAVE 4.2.4
DAVE Apps webserver example with CMSIS RTOS, lwIP (stack and simple file system) and netconn
connected with Ethernet/USB adapter, micro usb cable and SEGGER J-Link usb cable to a PC
After implementing the XMC4500 Relax Kit webserver example from the DAVE Apps (xmc4500_relaxkit_lwip_httpserver_netconn) with correct ethernet ports on the XMC 4500 Hexagon and the file system from lwIP I get TCP Resets and TCP Retransmissions.
The webserver works great if only one TCP port is in parallel use (I tested is with a small html page and one picture).
But, if there are two pictures included and the two HTTP Requests coming to the XMC in short time in a row, I get a reset for the second HTTP Request, so the second picture is not loaded from the webserver.
When they appear not in a row with a bit more time difference both pictures are loading.
1st try -> bad: WireShark line 5 to 82, small picture didn't load, both HTTP Requests appear in a row (line 31 and 32), XMC4500 answer second Request (for small image) with two (???) resets
2nd try -> good: WireShark line 83 to 169, both Requests don't appear in a row (line 104 and 118), both pictures loaded
3rd try -> bad: WireShark line 170 to 208, both Requests appear again in a row (line 196 and 197), now the huge picture didn't load cause attendant Request is second
... this behavior continues for about 20 page reloads, then I get TCP Retransmissions (beginning line 1622) and the page loading lasts a few seconds.
Maybe you guys have any idea what is the problem here.
Thanks for your help. Show Less
(192.168.115.74 = XMC4500, 192.168.115.75 = PC)
XMC4500 Hexagon Board with Ethernet/CAN/RS485 Interface Card
DAVE 4.2.4
DAVE Apps webserver example with CMSIS RTOS, lwIP (stack and simple file system) and netconn
connected with Ethernet/USB adapter, micro usb cable and SEGGER J-Link usb cable to a PC
After implementing the XMC4500 Relax Kit webserver example from the DAVE Apps (xmc4500_relaxkit_lwip_httpserver_netconn) with correct ethernet ports on the XMC 4500 Hexagon and the file system from lwIP I get TCP Resets and TCP Retransmissions.
The webserver works great if only one TCP port is in parallel use (I tested is with a small html page and one picture).
But, if there are two pictures included and the two HTTP Requests coming to the XMC in short time in a row, I get a reset for the second HTTP Request, so the second picture is not loaded from the webserver.
When they appear not in a row with a bit more time difference both pictures are loading.
1st try -> bad: WireShark line 5 to 82, small picture didn't load, both HTTP Requests appear in a row (line 31 and 32), XMC4500 answer second Request (for small image) with two (???) resets
2nd try -> good: WireShark line 83 to 169, both Requests don't appear in a row (line 104 and 118), both pictures loaded
3rd try -> bad: WireShark line 170 to 208, both Requests appear again in a row (line 196 and 197), now the huge picture didn't load cause attendant Request is second
... this behavior continues for about 20 page reloads, then I get TCP Retransmissions (beginning line 1622) and the page loading lasts a few seconds.
Maybe you guys have any idea what is the problem here.
Thanks for your help. Show Less
DAVE™
Today we released new versions of DAVE, DAVE SDK, Device Descriptions, and Device Support Pack.DAVE v4.2.8 and DAVE SDK v4.2.8Fix of an issues related...
Show More
Today we released new versions of DAVE, DAVE SDK, Device Descriptions, and Device Support Pack.
DAVE v4.2.8 and DAVE SDK v4.2.8
Further Details are described in the DAVE and DAVE SDK Release Note
Device Descriptions
A new version of the Device Description of the XMC1404 in QFN 40 package has been released to add missing pin options.
Further Details are described in the Release Note.
Device Support Pack v2.1.14
To correct in XMC4300 header file wrong offset address information of some peripheral. Please replace in exiting XMC4300 projects the old header file with the new header file versions (v1.0.4) provide in this Device Support Pack.
Further Details are described in the Release Note.
How to update:
When starting DAVE two update notifications will appear, one for the DAVE updated and one for the libraries update:. To install the updates click on the notifications and follow further instructions.
Alternatively the check for updates functionality can be used:
Press: -> Help -> Check for DAVE APP Updates (Device Description updates and Device Pack update)
Press: -> Help -> Check for Updates (DAVE update)
An updated zip file that includes all libraries for local installation / update of the local library store can be downloaded from here.
We also updated the separate XMC lib package with the correction of the XMC4300 header file as mention above.
For users of Keil/ ARM MDK: There is also a new update of the CMSIS PACK available. Plues use your Pack Installer to install the updates. Show Less
DAVE v4.2.8 and DAVE SDK v4.2.8
- Fix of an issues related to not correct solver results in case different versions of the same Devices Description are installed in the local library store.
- In SDK only the version has been adjusted to keep sync with DAVE.
Further Details are described in the DAVE and DAVE SDK Release Note
Device Descriptions
A new version of the Device Description of the XMC1404 in QFN 40 package has been released to add missing pin options.
Further Details are described in the Release Note.
Device Support Pack v2.1.14
To correct in XMC4300 header file wrong offset address information of some peripheral. Please replace in exiting XMC4300 projects the old header file with the new header file versions (v1.0.4) provide in this Device Support Pack.
Further Details are described in the Release Note.
How to update:
When starting DAVE two update notifications will appear, one for the DAVE updated and one for the libraries update:. To install the updates click on the notifications and follow further instructions.
Alternatively the check for updates functionality can be used:
Press: -> Help -> Check for DAVE APP Updates (Device Description updates and Device Pack update)
Press: -> Help -> Check for Updates (DAVE update)
An updated zip file that includes all libraries for local installation / update of the local library store can be downloaded from here.
We also updated the separate XMC lib package with the correction of the XMC4300 header file as mention above.
For users of Keil/ ARM MDK: There is also a new update of the CMSIS PACK available. Plues use your Pack Installer to install the updates. Show Less
DAVE™
Hello,the E_EEPROM_XMC4 app tries to copy a custom linker file when generating code. This fails in a very bad way when there are spaces in the project...
Show More
Hello,
the E_EEPROM_XMC4 app tries to copy a custom linker file when generating code. This fails in a very bad way when there are spaces in the project path. The problematic code is in E_EEPROM_XMC4/Templates/e_eeprom_xmc4/confc.tmpl. The issue is present in both version 4.04 and 4.06 of the app.
How to reproduce:
1. Change workspace to a path with spaces in it
2. Create new DAVE project
3. Add E_EEPROM_XMC4 app
4. Run Code Generation
5. Run compiler -> Compiler will fall over error output in "\Dave\Generated\E_EEPROM_XMC4\e_eeprom_xmc4_conf.c"
To see problem, replace "Dave\Generated\E_EEPROM_XMC4\e_eeprom_xmc4_conf.c" with this code:
To fix issue, replace line
by
Please get this passed on to the appropriate people if you can reproduce it, otherwise feel free to ask any questions!
Show Less
the E_EEPROM_XMC4 app tries to copy a custom linker file when generating code. This fails in a very bad way when there are spaces in the project path. The problematic code is in E_EEPROM_XMC4/
How to reproduce:
1. Change workspace to a path with spaces in it
2. Create new DAVE project
3. Add E_EEPROM_XMC4 app
4. Run Code Generation
5. Run compiler -> Compiler will fall over error output in "\Dave\Generated\E_EEPROM_XMC4\e_eeprom_xmc4_conf.c"
To see problem, replace "Dave\Generated\E_EEPROM_XMC4\e_eeprom_xmc4_conf.c" with this code:
package Model.APPS.E_EEPROM_XMC4.v4_0_6.Templates;
import Model.APPS.E_EEPROM_XMC4.v4_0_6.E_EEPROM_XMC4
import java.nio.file.*
out.print("""
/**
* @cond
***********************************************************************************************************************
*
* Copyright (c) 2016, 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).
***********************************************************************************************************************
*
* Change History
* --------------
*
* 2016-01-20:
* - Initial version
*
* @endcond
*
*/
/***********************************************************************************************************************
* HEADER FILES
**********************************************************************************************************************/
#include "e_eeprom_xmc4.h"
""");
String appInst = null
for (E_EEPROM_XMC4 EEPROM_Inst : appInstancesList ) {
appInst = EEPROM_Inst.getInstanceLabel()
String ld_file_name = daveEnv.project.selectedDevice.deviceId.deviceName.split("-")[0]+"x"+daveEnv.project.selectedDevice.deviceId.deviceName.split("x")[1]
def scriptDir = new File(getClass().protectionDomain.codeSource.location.path).getParentFile()
def projectDir = scriptDir.getParentFile().getParentFile().getParentFile().getParentFile().getParentFile().getParentFile()
try {
Files.delete(Paths.get(projectDir.path, "linker_script.ld"))
try {
Files.copy(Paths.get(scriptDir.path+"\\"+"linker_files", ld_file_name+".ld"), Paths.get(projectDir.path, "linker_script.ld"))
} catch (Exception e) {
println("#warning Could not copy from " + Paths.get(scriptDir.path+"\\"+"linker_files", ld_file_name+".ld") + " to " + Paths.get(projectDir.path, "linker_script.ld"))
}
}
catch (Exception e) {
println("#warning Could not delete " + Paths.get(projectDir.path, "linker_script.ld"))
}
out.println("""
E_EEPROM_XMC4_t ${appInst} =
{
.initialized = false
};
""");
}
To fix issue, replace line
def scriptDir = new File(getClass().protectionDomain.codeSource.location.path.toString()).getParentFile()
by
def scriptDir = new File(getClass().protectionDomain.codeSource.location.path.toString().replace("%20", " ")).getParentFile()
Please get this passed on to the appropriate people if you can reproduce it, otherwise feel free to ask any questions!
DAVE™
All examples that I have queried are for the Hexagon board, and are not operational on the Relax board. The Webserver Application for the Relax is op...
Show More
All examples that I have queried are for the Hexagon board, and are not operational on the Relax board. The Webserver Application for the Relax is operational, but when attempting to utilize only UDP and RTOS, I am unable to even ping the unit.
Please provide a fully operational example of UDP using this hardware. Very little documentation exists to understand if there is a subtle configuration issue that is causing the problem. Show Less
Please provide a fully operational example of UDP using this hardware. Very little documentation exists to understand if there is a subtle configuration issue that is causing the problem. Show Less
DAVE™
Dear,this is a question about SPI_MASTER of XMC4500,When select #73 (P1.10) to SCLKOUT pin, why can we never set 30MHz of 'Desired bus speed' ?Two fil...
Show More
Dear,
this is a question about SPI_MASTER of XMC4500,
When select #73 (P1.10) to SCLKOUT pin, why can we never set 30MHz of 'Desired bus speed' ?
Two files are attached for the reference.
Also we can set 30MHz when select #48 (P4.8) to SCLKOUT.
Is this a limitation of XMC4500 or DAVE ?
Best regards,
Kazunari Hayashi
TOMEN Electronics Corp. Show Less
this is a question about SPI_MASTER of XMC4500,
When select #73 (P1.10) to SCLKOUT pin, why can we never set 30MHz of 'Desired bus speed' ?
Two files are attached for the reference.
Also we can set 30MHz when select #48 (P4.8) to SCLKOUT.
Is this a limitation of XMC4500 or DAVE ?
Best regards,
Kazunari Hayashi
TOMEN Electronics Corp. Show Less