XDK110
BCDS
© Bosch Connected Devices and Solutions GmbH reserves all rights even in the event of industrial property rights. We reserve all rights of disposal such as
copying and passing on to third parties. BOSCH and the symbol are registered trademarks of Robert Bosch GmbH, Germany.
Note: Specifications within this document are subject to change without notice.
General Information Guide XDK110
!
Page
!
32
Reset/Reboot XDK
As outlined in Approach 3 in chapter 3.5.2, XDK can receive commands from XDK Workbench
over the virtual serial port. Commands are parsed and executed by the URU module in XDK SDK.
At the moment, XDK understands the following commands:
#reBoot$:
Reboot XDK and go into bootloader mode
#reSet$:
Reboot XDK and go into application mode
Sending these commands to XDK via the virtual serial port will either get XDK into bootloader
mode or restart XDK into application mode. When sending application data to XDK, please make
sure you do not use the reserved strings, as XDK might restart unexpectedly.
XDK Windows Driver
Unfortunately, the driver for CDC ACM devices in Microsoft Windows (which is also used by XDK)
misbehaves under certain circumstances. When a USB CDC ACM device is connected and the
respective port identifier is in use (by Tera Term for example) and then the device suddenly
disappears, the driver keeps the port identifier blocked. When the device reappears and the
identifier is still in use, the device will not be usable. To work around this issue, the port has to be
unused (e.g. by closing Tera Term) and the device has to be reconnected.
Note: Disappearing Device
Due to the design of XDK’s USB interface, reboot or resetting XDK as well as switching it off and
on again make the device disappear from Windows' perspective.
XDK Workbench works around this issue by closing the port identifier whenever XDK is
disappearing. However, third party applications usually will not do this. So, whenever XDK
disappears, please close your terminal session and restart it once XDK is available again.
The default path for the driver is
C:\XDK-Workbench\SDK\drivers_win32
.
Using a Serial Terminal
To communicate with XDK, a standard serial terminal application can be used. For example using
the third party Tera Term allows opening the virtual serial port of XDK and communicating with
XDK. Please make sure that XDK Workbench does not run when you want to communicate with
XDK with a third party program, as the two might interfere with each other. When working with
XDK, please also pay close attention to the problem outlined in chapter 3.6.1 “XDK Windows
Driver”.
To figure out what the port identifier of your XDK is, simply move your mouse over your XDK in
XDK Workbench. A mouseover as shown in the picture will show up and give you the "COMx"
identifier of your XDK.
