DAVE™ Forum Discussions

I often arrange the 'S/W App Connectivity View' block diagram to be logical and clear so I can easily find each App and see the links between them (DAVE often overlays the Apps).

But when a change is made to the block diagram (for example adding an App or Editing a label) the diagram is re-drawn.

It would be really nice if DAVE didn't re-draw the diagram, this could be an optional setting.

Thank you very much
Aaron Show Less

I often need multiple instances of an App in my project and generally their configuration is identical apart from I/O pin allocation.

It would be really nice if it were possible to select an App in the 'S/W App Connectivity View' and paste it as a new instance so that the settings within the original instance are carried across to the new instance.

Thank you very much
Aaron Show Less

The Hexagon Development Kit uses the XMC4500-F144x1024-AA and my final target pcb uses the XMC4500-F100x1024-AB.

Unfortunately both seem to be missing from the list of supported devices in the 'USBVC001' v1.0.10 and 'NVIC002' v1.0.12.

I suspect the devices are missing from most other Apps too.

Will these devices be added or are they actually supported even though they are not listed.

Any help and advice will be much appreciated.

Aaron Show Less

I need to output a PWM signal on the XMC4500-F100 pin P5.1 (CCU81.OUT32) .

Unfortunately, P5.1 is not listed within the pin assignment list of the CCU8 PWM Apps (PWMMP001 and PWMSP002).

Is there a way around this ?

Maybe I could configure a PWM App to generate interrupts on the rising and falling edges and within the interrupt control the P5.1 pin directly. My PWM frequency is only 1KHz so interrupt overhead would not be a problem.

Any help and advise would be greatly appreciated.

Aaron Show Less

The XMC4500 reference manual (Table 25-10 ) defines the following pins...

P14.12 34 J1 23 AN/DIG_IN
P14.13 33 H4 22 AN/DIG_IN
P14.14 32 H3 21 AN/DIG_IN
P14.15 31 H2 20 AN/DIG_IN

This seems to indicate that pins P14.12 - P14.15 can be used as digital inputs. However the IO004 v1.0.16 App does not seem to allow pins P14.12 - 15 to be selected on the 'Manual Pin Assignment' dialog.

Will this feature be added or is the reference manual incorrect ?

Thank you in advance
Aaron

Show Less

I have just upgraded DAVE and found the 'USBVC001_VCOMSerial_Example1' App has been changed from the xmc4500 AA step device to the AB step device.

This means the example no longer runs on my Hexagon Development Kit which is fitted with an AA step MCU.

I appreciate I can create a new xmc4500 AA step project and merge the latest example code into it but this is time consuming.

My questions are...

• Have all the examples been converted to AB step ?
  
• Is there a plan to offer Hexagon kit processor module upgrades ?
  
• Is there another solution for running the new examples on AA step Hexagon kits without manually merging the latest examples into a new project ?
  

Thank you for any help and advice.

Aaron Show Less

I have just updated my code to use the latest 'USBVC001' App (1.0.10) instead of an older version (1.0.2). This App calls the 'NVIC_SCU001' App.
However, I get the following build error....

../Dave/Generated/src/NVIC_SCU001/NVIC_SCU001.c: In function 'SCU_0_IRQHandler':
../Dave/Generated/src/NVIC_SCU001/NVIC_SCU001.c:262:17: error: 'NVIC_SCU001_OSCSITRIM' undeclared (first use in this function)
../Dave/Generated/src/NVIC_SCU001/NVIC_SCU001.c:262:17: note: each undeclared identifier is reported only once for each function it appears inmake: *** [Dave/Generated/src/NVIC_SCU001/NVIC_SCU001.o] Error 1

I have checked the file "../Dave/Generated/src/NVIC_SCU001/NVIC_SCU001.c" and found it to be an old version (Nov 20, 2011) instead of version (Jan 21 2013) as used in the latest "USBVC001_VCOMSerial_Example1".

The 'S/W App Connectivity View' shows the 'NVIC_SCU001' App to be version 1.0.12 in both my code and the 'USBVC001_VCOMSerial_Example1'.

I have re-generated the code and tried 'Clean project', 'Build All' but still get the error.

Is there a method for ensuring the source code for all App's is re-created using the latest version ?

Thank you for any help
Best regards
Aaron

Show Less

Hello.

Our company recently decided to switch from the phased-out TI Stellaris LM3S series uC to the XMC4500

Setting up the Dave3 IDE and starting testing on the Hexagon card has been a breeze, and we have found Dave APPs for all our needs except for the Quadrature module.
Have I overlooked it, or is it missing?

We want to use the phase A&B signals from an absolute encoder. The only APP I find is for brush-less DC motor control.

Cheers Show Less

I am using GPIO macros in my project. The macros are defined in GPIO.H.

I manually placed a copy of the GPIO.H file into my project from C:\DAVE-3.1\Examples\EasyStart\XMC4000\XMC4500\144Pin

However I need to switch between the 144 pin and 100 pin xmc4500 but the GPIO.H files for each device are different.

So I would like to omit the GPIO.H file from my project and let DAVE locate the correct file depending on the MCU selected.

Doing things this way also means I always get the latest version of GPIO.H when I build.

Is there a way to do this ?

Any help would be greatly appreciated.

Aaron Show Less