DAVE™ Forum Discussions
DAVE™
A migration problem may occur if one or more DAVE Apps of the active project do not support the new target MCU device. The reason could be:a) The DAVE...
Show More
A migration problem may occur if one or more DAVE Apps of the active project do not support the new target MCU device. The reason could be:
a) The DAVE App has not yet been extended to support this new target device or new device step;
b) The new target device does not include a required peripheral (e.g. ETH module or USB module);
c) The new target device includes less peripheral instances than required;
d) The new target device does not included the manually assigned port pins.
For case a: This should be only an intermediate situation. The respective DAVE App should be updated soon.
For case b and c: The respective DAVE Apps have to be removed to fit the resources offered by the new target device.
For case d: The user has to manually assign port pins that are available in the new target device, or remove the critical manual pin assignment and let the solver search for a solution.
Details can be found in DAVE User Manual:
Go to: >Help>Help Contents>DAVE User Manual>App and Device Migration Show Less
a) The DAVE App has not yet been extended to support this new target device or new device step;
b) The new target device does not include a required peripheral (e.g. ETH module or USB module);
c) The new target device includes less peripheral instances than required;
d) The new target device does not included the manually assigned port pins.
For case a: This should be only an intermediate situation. The respective DAVE App should be updated soon.
For case b and c: The respective DAVE Apps have to be removed to fit the resources offered by the new target device.
For case d: The user has to manually assign port pins that are available in the new target device, or remove the critical manual pin assignment and let the solver search for a solution.
Details can be found in DAVE User Manual:
Go to: >Help>Help Contents>DAVE User Manual>App and Device Migration Show Less
DAVE™
Hi,I had try work with SPI and on that i configure the system to work with 3 devices ( LCD, ISOFACE OUT, ISOFACE IN) at the same time, but until now I...
Show More
Hi,
I had try work with SPI and on that i configure the system to work with 3 devices ( LCD, ISOFACE OUT, ISOFACE IN) at the same time, but until now I could not do it.
I can work with LCD and ISOFACE OUT at the same time, or with ISOFACE OUT and ISOFACE IN, but when i activates the three, the ISOFACE IN stops working in the good way. The function returns allways "0". What can i do to place all SPI devices working at the same time.
Another thing,
I had tried create a new program with GUI APP 002 in RTOS environment, but after add the APP GUISL002[1.0.0] , generate code.
then a added the GUI_Init() and compile the program and when i debug it ,the program crash "Insert_ExceptionHandler MemManage_Handler"
. What must be done to place it work?
Exists any configuration missing?
Which steps must I follow to correct this error?
The main.c
include //Declarations from DAVE3 Code Generation (includes SFR declaration)
int main(void)
{
// status_t status; // Declaration of return variable for DAVE3 APIs (toggle comment if required)
DAVE_Init(); // Initialization of DAVE Apps
GUI_Init();
while(1)
{
}
return 0;
}
Can anyone help me with this?
Luis Silva
Show Less
I had try work with SPI and on that i configure the system to work with 3 devices ( LCD, ISOFACE OUT, ISOFACE IN) at the same time, but until now I could not do it.
I can work with LCD and ISOFACE OUT at the same time, or with ISOFACE OUT and ISOFACE IN, but when i activates the three, the ISOFACE IN stops working in the good way. The function returns allways "0". What can i do to place all SPI devices working at the same time.
Another thing,
I had tried create a new program with GUI APP 002 in RTOS environment, but after add the APP GUISL002[1.0.0] , generate code.
then a added the GUI_Init() and compile the program and when i debug it ,the program crash "Insert_ExceptionHandler MemManage_Handler"
. What must be done to place it work?
Exists any configuration missing?
Which steps must I follow to correct this error?
The main.c
include
int main(void)
{
// status_t status; // Declaration of return variable for DAVE3 APIs (toggle comment if required)
DAVE_Init(); // Initialization of DAVE Apps
GUI_Init();
while(1)
{
}
return 0;
}
Can anyone help me with this?
Luis Silva
DAVE™
Can anyone advise me How to use Saturating instructions? (in XMC4500)Is there any application that could do work with Saturating instructions?Is there...
Show More
Can anyone advise me How to use Saturating instructions? (in XMC4500)
Is there any application that could do work with Saturating instructions?
Is there any manual or else description of Saturating instructions?
Thanks.
Best regards
Koumak Show Less
Is there any application that could do work with Saturating instructions?
Is there any manual or else description of Saturating instructions?
Thanks.
Best regards
Koumak Show Less
DAVE™
Is routing the ADCCH001 boundary flag to NVIC002 possible?The signal routing window provides a Boundary Flag for Result Regisert A signal option, but...
Show More
Is routing the ADCCH001 boundary flag to NVIC002 possible?
The signal routing window provides a Boundary Flag for Result Regisert A signal option, but does not provide a NVIC app option.
The Channel event signal option does provide a NVIC app option.
Please provide some guidance on this.
Thanks Show Less
The signal routing window provides a Boundary Flag for Result Regisert A signal option, but does not provide a NVIC app option.
The Channel event signal option does provide a NVIC app option.
Please provide some guidance on this.
Thanks Show Less
DAVE™
HelloI'm using the PWMSP001 to generate a special output and in my case it is necessary to set the output pin to high impedance. The library doesn't g...
Show More
Hello
I'm using the PWMSP001 to generate a special output and in my case it is necessary to set the output pin to high impedance. The library doesn't give me the opportunity to do this.
So my question is, is it possible to do this when the pin is used by the PWM?
Best regards,
Caro Show Less
I'm using the PWMSP001 to generate a special output and in my case it is necessary to set the output pin to high impedance. The library doesn't give me the opportunity to do this.
So my question is, is it possible to do this when the pin is used by the PWM?
Best regards,
Caro Show Less
DAVE™
The number of hardware breakpoints is supported by the debug unit of the CPU Cortex-M. For example, the Cortex-M4 in XMC4500 supports 5 HW breakpoints...
Show More
The number of hardware breakpoints is supported by the debug unit of the CPU Cortex-M. For example, the Cortex-M4 in XMC4500 supports 5 HW breakpoints.
There will an error message popping up if the HW breakpoints required is more than its support capacity.
In this case, you can use the SW breakpoints (Flash Breakpoints) which is an enhanced feature of J-Link. But you need to apply for an additional license from Segger in order to get this feature. Show Less
There will an error message popping up if the HW breakpoints required is more than its support capacity.
In this case, you can use the SW breakpoints (Flash Breakpoints) which is an enhanced feature of J-Link. But you need to apply for an additional license from Segger in order to get this feature. Show Less
DAVE™
This generated by Dave code writes the Data in to the Transfer Buffer FIFO for I2C communication:while(I2CRegs->TCSR & USIC_CH_TCSR_TDV_Msk) { ...
Show More
This generated by Dave code writes the Data in to the Transfer Buffer FIFO for I2C communication:
As one can see before writing in to the FIFO the polling of the TDV bit occures. But in this case the FIFO will never be loaded more then with one entry! Show Less
while(I2CRegs->TCSR & USIC_CH_TCSR_TDV_Msk)
{
;
}
I2CRegs->IN[0] = \
(((uint32_t)Data->TDF_Type << 😎 | Data->Data);
As one can see before writing in to the FIFO the polling of the TDV bit occures. But in this case the FIFO will never be loaded more then with one entry! Show Less
DAVE™
Given a use case where singular app instances need to be initialized independently at startup, or reinitialized during program execution what is the b...
Show More
Given a use case where singular app instances need to be initialized independently at startup, or reinitialized during program execution what is the best solution?
I have found that the order of execution within the DAVE_Init function is important when trying to implement the init functions independently, where they are needed in the application instead of at the beginning.
What is the best way to do this with the current code generated by DAVE? Show Less
I have found that the order of execution within the DAVE_Init function is important when trying to implement the init functions independently, where they are needed in the application instead of at the beginning.
What is the best way to do this with the current code generated by DAVE? Show Less
DAVE™
In order to get the current time from RTC, you need to enable RTC module 1st before calling "RTC001_Clock_GetTime()" API.The code sequence should be a...
Show More
In order to get the current time from RTC, you need to enable RTC module 1st before calling "RTC001_Clock_GetTime()" API.
The code sequence should be as followings:
1) DAVE_Init(); // RTC001_Init() will be called within DAVE_Init()
2) RTC001_Enable(); //defined in RTC001.c
3) RTC001_Clock_GetTime(); //call GetTime API
Details can be found in DAVE App Help documentation:
Go to: >Help>Help Contents>DAVE Apps>RTC001[1.0.28]>RTC001: RTC_Timer_RTC001App>API Documentation>RTC001_Clock_GetTime ()>Example of using "RTC001_Clock_GetTime ()" API function Show Less
The code sequence should be as followings:
1) DAVE_Init(); // RTC001_Init() will be called within DAVE_Init()
2) RTC001_Enable(); //defined in RTC001.c
3) RTC001_Clock_GetTime(); //call GetTime API
Details can be found in DAVE App Help documentation:
Go to: >Help>Help Contents>DAVE Apps>RTC001[1.0.28]>RTC001: RTC_Timer_RTC001App>API Documentation>RTC001_Clock_GetTime ()>Example of using "RTC001_Clock_GetTime ()" API function Show Less
DAVE™
Good morning,I have two DAVE projects:One making use of the POSQE001 app (which in turn has a dependency on CLK001/0)One making use of the SPI001 app ...
Show More
Good morning,
I have two DAVE projects:
One making use of the POSQE001 app (which in turn has a dependency on CLK001/0)
One making use of the SPI001 app (which in turn has a dependency on CLK001/0)
Both work satisfactorily.
I am now taking the POSQE001 project and adding the DAVE SPI001 app.
However, there appears to be a problem with the SPI app configuration: I set the desired baud rate on the SPI configuration to the value I require, but the parameters derived from this/CLK*, in conjunction with the CLK frequency are not recalculated and one shows in red (Step value) as an error.
* Real baud rate
Peripheral clock**
Divide factor
Step value
** This shows as 0.0000000, however in the CLK app frequency is 120 MHz. It would appear that the SPI app is not 'seeing' the CLK app's frequency.
Has anyone else experienced this problem and/or knows what I can do to resolve it?
Regards,
Steve
PS: I get this error when I first added the SPI app:
"Problem occurred while getting the plausibility result form the solver
Execution of solver query failed
The recently added app(s) will be removed !"
but when adding it the second time, no such error is report. I guess this is the underlying problem, but what on Earth does the error message mean? Anyone care to explain?
For information: I get the same error when adding the CAN app. Show Less
I have two DAVE projects:
One making use of the POSQE001 app (which in turn has a dependency on CLK001/0)
One making use of the SPI001 app (which in turn has a dependency on CLK001/0)
Both work satisfactorily.
I am now taking the POSQE001 project and adding the DAVE SPI001 app.
However, there appears to be a problem with the SPI app configuration: I set the desired baud rate on the SPI configuration to the value I require, but the parameters derived from this/CLK*, in conjunction with the CLK frequency are not recalculated and one shows in red (Step value) as an error.
* Real baud rate
Peripheral clock**
Divide factor
Step value
** This shows as 0.0000000, however in the CLK app frequency is 120 MHz. It would appear that the SPI app is not 'seeing' the CLK app's frequency.
Has anyone else experienced this problem and/or knows what I can do to resolve it?
Regards,
Steve
PS: I get this error when I first added the SPI app:
"Problem occurred while getting the plausibility result form the solver
Execution of solver query failed
The recently added app(s) will be removed !"
but when adding it the second time, no such error is report. I guess this is the underlying problem, but what on Earth does the error message mean? Anyone care to explain?
For information: I get the same error when adding the CAN app. Show Less