DAVE™ Forum Discussions

Sorry,

I'm new with Dave4 but I can't get the BMI-Button.

Thank you for help!

Bernd Show Less

Hello!

I know I can update the Apps via Help -> Check for DAVE APP Updates.

However, after updating to the latest Apps my projects are still using the old ones.

How can I tell Dave to use the latest ones instead?

Thanks! Show Less

Hi,

I'm writing an application using the USBD_VCOM library, a relax kit with the XMC4800 and a Windows10 PC.
All my drivers are up to date.

I need my application to write a menu (multiple selections through characters) on the screen through a text terminal and the COM port .
Something like:

const unsigned char ucMenu[] =
"\n\r"
"1 ... OPTION1\n\r"
"2 ... OPTION2\n\r"
"3 ... OPTION3\n\r"
"4 ... OPTION4\n\r"
"5 ... OPTION5\n\r"
"6 ... OPTION6\n\r"
"\n"
"your choice: ";

This must happen automatically after that the terminal (I'm using Putty) has been connected to the COM port generated by the microcontroller.

At the moment, this is the sequence:
- run the application
- run Putty
- send a character on the COM port generated through USB
AND ONLY HERE I CAN print the menu because if I send anything on the port before the app receives the first character, this is not displayed

So basically, whatever I is written before I run Putty is not displayed and I need to input a character for the uC to receive the first byte and understand that it can print something which will be seen.

I'd like to find a way to get my app to understand when Putty is connected.

Would it be possible?

Thanks and regards,
Ale Show Less

Hi all, I'm new to microcontroller programming.

I'm writing an app based on the USBD_VCOM library, running on XMC4800 Relax kit.
I'm using Putty and Windows10 as master for my USB-COM communication.

Looks like I can't open putty before I launch the debug session.
This makes sense and I believe has to do with the fact that the enumeration (and therefore the association of the COM number is carried out by "DAVE_Init(void)")
So if I don't launch the program, there is nothing for Putty to connect with.

My question is:
would it be possible open Putty first on the expected COM port (which is always the same) and only then start my application?


I'm happy to change my terminal sw should Putty be inadequate for any reason.

Thanks and regards,
Alessandro Show Less

Patch update, 2016, January, 25

Today we have released a plug-in update for DAVE v4.1.4
This plug-in update fixes a problem with the BMI functionality integrated in DAVE.
When changing the BMI (Boot Mode Index) setting in any XMC1000 microcontroller to the ASC BSL mode (device boot via a UART channel), in most of the cases the BMI was not set correctly; with the consequence that the device was not accessible any more. With the new DAVE CE plug-in this problem is fixed.

How to update:
Dave will provide an alert that an update is available, just accept this alert and follow further instructions.
The update can also be performed as follows:

• Press: -> Help -> Check for Updates
  
• Check the DAVE Code Engine Feature
  
• Press Next and follow further instructions
  
• 
  

Further details can be found in the Release Note.

To avoid other sporadic issue with getBMI() functionality, the latest JLink version V5.10h should be used. Show Less

After i installed J-link and Dave 4, when i try to debug i have this problem:

"J-Link GDB Server failed:
Could not connect to target. Please check if target is powered and if ribbon cable is plugged properly.

For more details, see the JLinkGDBServer.exe console."

I'm using a previous version 6.30e, but i had installed a newer version before and i had the same problem. Show Less

The stack size is defined in the linker script file.

The linker script file is created upon new project creation and has the extension *.ld.

Within the linker script file, there is a symbol “stack_size” that is set to 2048 Bytes by default. This value can be changed by the user. Show Less

For XMC4500, you should not make RAM partition by growing DSRAM_1_system as there is no physical memory address being mapped from 0x20010000 to 0x2FFFFFFF.
The linker will stop complaining. But any access starting from 0x20010000 will lead to a crash. Show Less