8. Getting Started
8.1. Installation Notes
SmartSnippets™ Toolbox supports 64-bit environments. SmartSnippets™ Studio installer contains SmartSnippets™ Toolbox application.
To use FTDI devices, the appropriate FTDI drivers need to be installed on the system. Just use the standard Windows
New hardware has been foundwizard to install them.
To use a Bluetooth dongle, the appropriate JLINK drivers need to be installed on the system. The latest drivers can be found at http://www.segger.com/jlink-software.html. To download them, please click on the
Downloadbutton under the
J-Link software & documentation pack for Windowssection. While installing these drivers, it is recommended that the Bluetooth dongle is NOT connected to the USB port.
If an error occurs while using the SPotA tool and trying to connect to the Bluetooth dongle, please make sure that the
Microsoft Visual C++ 2010 Redistributable Packagelibraries are installed at
C:\\Windows\\System32folder. Otherwise, please download and install the latest Redistributable libraries for Visual Studio 2010 from http://support.microsoft.com/kb/2019667/.
If the following error dialog appears, Java Simple Serial Connector library (JSSC), which is used by SmartSnippets™ Toolbox for serial communication, could not be loaded successfully. The reason is that none of the user home folder and user Temp folder is writable. JSSC library extracts to user home folder (or user Temp folder, if user home folder is not writable) the required DLLs for serial connection. The user can change the access rights of these folders or overwrite the default user folder location. In order to overwrite the default user home path, the user can use USER_HOME property. For example the user can set USER_HOME=C:/Users/_username_ or USER_HOME=C:\Users\_username_ at the properties file. File
properties.txtis inside SmartSnippets™ Toolbox workspace folder defined at installation.
8.2. Work Flow
This section is providing a guide to start using the SmartSnippets™ Toolbox, a proposed way of working with the tools available for the basic tasks during development. The following figure illustrates the basic flow to run a program from OTP on a DA1453x and DA14585/6 family chip.
 Dialog’s Development Board needs no configuration
 From this point on, application development and debugging is done, and OTP will be programmed
The user might experiment with the Power Profiler for optimizing the code as much as possible. This can take several iterations since the user can insert SW cursors (see Power Profiler software cursors ) to identify the code executions translated into current dissipation. As soon as it is completed, the programming of the code into the OTP might start so that the system is self-sustained. Upon OTP burning, the system can operate on a battery and realize complete power cycles e.g. active and sleep intervals. Please refer to Power Profiler about a detailed description of Power Profiler.
8.2.1. Device Selection
The first time SmartSnippets™ Toolbox is launched on a clean workspace the user will see the following:
At this point the target device is still unknown. No tools will be available until a device is selected or detected. The application has been launched with a default project (named ‘Default’) at which user settings will be saved. User can either use this default project or create a new project using the Project menu. Then the user is advised to either select Detect Device from the Board Menu or to manually select the device and the interfaces to be used from the Board Menu. Once a device is detected or manually selected the groups of tools supported for this device will be loaded at the ribbon.
SmartSnippets™ Toolbox saves user configurations (selected device, communication interfaces, tool specific settings) at the active project. If there any unsaved changes on application exit or when user switches to another project the user will be asked to save these changes. SmartSnippets™ Toolbox remembers the project that has been used in the last session and it will load by default the same project the next time the application is launched.
8.2.2. UART Port Configuration
If the connection between SmartSnippets™ and the board over the UART link is unstable try to change the latency time of the FTDI cable and set to some value below 10ms. User can configure the latency from the Device Manager. To open the Device Manager in Windows 10, the user can press the Windows button and type Device Manager in the search box. From the Device Manager expand Ports (COM & LPT). Right click on preferred port, click properties, select tab Port Settings and then advanced. In windows 8 COM & LPT is hidden. Go to View and select Show hidden devices. At Figure 22 you can see a screenshot of example settings.
8.3. Linux Support
8.3.1. Changing device permissions
When user adds a development board on a Linux system, new devices are created automatically on the OS. These devices should have read and write permission for all users. To avoid setting appropriate permissions every time SmartSnippets™ Toolbox is used, a rules file is provided which changes permissions to every “known” FTDI device. The file, named smartsnippets_studio_common_ftdi_devices.rules, contains a list of common vendor and product IDs and should be placed under /etc/udev/rules.d. If the user cannot find the VID-PID pair of the board used under this list, it is recommended that a new .rules file is created and copied to /etc/udev/rules.d folder.
8.3.2. Setting VID-PID pairs for Power Profiler
Except from changing permissions of connected devices, as described in the previous section, the user should also add the VID-PID pairs to the SmartSnippets™ Toolbox properties file, in order to work with Power Profiler. Due to incompatibility with FTDI Linux kernel module, SmartSnippets™ Toolbox needs to know the Vendor and Product ID of the connected devices, in order to unload FTDI kernel module, before using ftd2xx library. Power Profiler works with a default VID-PID pair: VID= 0x0403 and PID=0x6010. User can add extra VID-PID pairs in properties.txt file in the following way:
VID-PID pairs are created from properties starting with VID. (or vid.) and PID. (or pid.) and having common text after the first ‘.’.