The Intel® System Studio is a flexible complete software development studio which allows you to optimize Intel® Architecture based intelligent embedded systems and devices. It combines Eclipse* CDT integrated optimizing compiler solutions and signal and media processing libraries, whole platform power and performance tuning capabilities, in-depth memory and thread checking, instruction trace and data race detection enabled application debug, and the deep insight of a JTAG based system software debug solution.
This session will give an overview for the Intel® System Studio and introduce the key features which cover the following topics:
- Debugging with GDB* debugger with enhanced instruction trace and data race detection support, and Intel® JTAG Debugger with deep insight into processor architecture, flashing, and source level debug from EFI* to OS Kernel and to driver development
- Building with Intel® C++ Compiler in corss-build environment to extract the best performance for your embedded target.
- Tuning with Intel® Vtune Amplifier to find the performance hotspots, identify the architecture performance bottlenecks, analyze system power and frequency.
- Verifying with Intel® inspector to find the memory and threading issues for your embedded applications
Q: We have XDP Debug interface on our board. Is Intel® JTAG Debugger interface different?
A: The Intel® JTAG Debugger 3.0 provides Linux* hosted cross-debug solutions for software developers to debug the Linux* kernel sources and dynamically loaded drivers and kernel modules on Intel® Atom™ Processor based devices. It does so using the In-Target Probe eXtended Debug Port (ITP-XDP) on Intel® Atom™ Processor (N2xxx, D2xxx, E6xx, CE42xx, and CE 53xx) based platforms.
For more information, refer to Intel® System Studio Installation guide and Release Notes Intel® JTAG Debugger 3.0 : http://software.intel.com/sites/default/files/article/365160/jtag-release-install.pdf
Q: Does Intel System Studio support Menlow and Baytrail platforms?
A: Intel® System Studio 2013 supports Intel® Atom™ Z5xx series Processors(Menlow). The upcoming release of Intel® System Studio 2014 beta will support The Intel® Atom™ Processor E3xxx and Z3xxx code-named “Baytrail” from Windows* host with the Intel® ITP-XDP3 device.
Q: Do you have auto configuration option for connecting the target device? We are using American Arium which do not support auto configuration.
A: We do have script files for specific Intel® Atom™ based target boards which will set the environment variables and bring up the Intel® JTAG debugger GUI, provided you have connected either an Intel® ITP-XDP3 or Macraigor* usb2demon onto the target board.
Q: Our focus is primarily for board bringup and BIOS/ UEFI porting effort.
A: The Intel® JTAG Debugger included with Intel® System Studio supports BIOS/UEFI debugging. As UEFI code is usually compiler in Microsoft* COFF PDB format, our debugger relies on Microsoft Visual Studio* redistributables for symbol info resolution and thus the Windows* hosted version of the Intel® JTAG Debugger should be used.
Q: Is the mac probe available with the purchase of the System Studio?
A: Intel System Studio is just a software tools suite and NO hardware is shipped along with this product.To order the Intel® ITP-XDP3 device, please contact the Hibbert Group* at Intelvtg@hibbertgroup.com and request the VTG order form.
To order Macraigor* usb2Demon*, Go to http://www.macraigor.com/usbDemon.htm and select the Intel® Atom™ Processor target with the appropriate 24, 31 or 60 pin connector for your target device.
Q: What does SoC mean?
A: SoC - System on Chip, Please refer to http://www.intel.com/pressroom/kits/soc/ for more information.
Q: How to collect data from target device to host
A: Target board analysis can be done using Intel® VTune Amplifier, you have to setup SSH(Secured Shell) connection and the analysis data is automatically copied back onto the host machine. Please refer to the remote collection article for more details :
Q: Intel JTAG debugger can support for all the controller?
A: Intel® System Studio JTAG debugger supports only Intel® Atom x86 architecture as of today. With the 2014 release it will also support Intel® Core processors code-named “Haswell” and newer.
Q: Does Intel System studio supports GCC environment/GCC commands
A: Yes, Intel® System Studio tools are compatible with GCC compiled binaries and the Intel® C++ Compiler accepts GCC command-line options.
Q: Can we develop bare metal application on this studio. i.e target is not having any operating system
A: The build tools included with Intel® System Studio are targeted towards a variety of Embedded Linux* flavors like Yocto Project*, Wind River Linux*. The Intel® C++ Compiler relies on the presence of the GNU binutils. It is not intended for bare metal applications. You can however use the Intel® JTAG debugger to debug and analyze your bare metal code.
Q: What about Ivy bridge and Haswell support?
A: The build tools including the Intel® C++ Compiler already support the latest generation of Intel® Core processors. Optimiztaions will be further improved in future versions of Intel® System Studio. With Intel® System Studio 2014 we add support for the processor code-named “Haswell” in the analysis and system debug tools as well.
Q: Is The Studio Helpful In Developing Linux Drivers?
A: Yes, it can be used to build, optimize and debug Linux drivers and kernel moduels.
Q: What Do You Mean By SSH Connection?
Q: What Is Yocto Project?
A: Yocto Project* is a Linux* foundation open source framework for embedded Linux* development. It is Open Embedded compatible and provides reference OS builds as well as the setup and build environment to build your own compatible custom embedded Linux* - https://www.yoctoproject.org/
Q: Is Windriver ice JTAG supported?
A: No, as of now we are not supporting The Windriver ICE JTAG probe.
Q: If we want to implement our own load balancing mechanism, how we can bypass the Cilk auto load balancing?
A: Load balancing is done by default by Cilk Plus [Which is part of Intel compiler]. Since this is done by CILK runtime automatically, it is not advisable to change the behavior of this. However you can get the source of this runtime under GPL V3 license https://www.cilkplus.org/which-license.
Q: is this support all version of Linux? Like Fedora and Ubuntu.
A: We have validated and listed some of the supported Host and Target OS here http://software.intel.com/en-us/articles/intel-system-studio-system-requirements, You may want to ensure that the Linux kernel version is 2.6.32 or above.
Q: is trial version have limited code compilation?
A: The feature set of the evaluation version is identical to the commercial version, with the only limitation being the license expiration after 30days.
Q: is this studio support for C language programming or having other C Complier?
A: Intel C/C++ Compiler which is part of Intel® System Studio supports C/C++ language.
Q: How can you analyze multi core processing ?
A: Intel® System Studio’s VTune Amplifier for systems and Inspector for systems can be helpful to find the CPU usage on a Multi-core processor using concurrency analysis, threading analysis respectively.
Q: OpenMP will be supported for this compiler ?
A: No, OpenMP is not supported as a language extention by the Intel® C++ Compiler for Embedded Linux* OS included with Intel® System Studio. Pre-existing OpenMP based binaries and shared objects that rely on OpenMP runtimes will however be executed correctly. We areopen to considering the requests, If more developers are asking for OpenMP support in future.
Q: We observed a situation of 100% CPU usage, wanted to analyze the root cause
A: You can use Intel® VTune Amplifier for Systems.
Q: Does the studio software take care of cross compilation?
A: Yes, the Intel® C++ Compiler support sysroot and chroot based cross-build setups. For cross compilation using sysroot we offer a "-platform" compiler option on the host that already takes care of the cross build integration for multiple target Linux* OSs. The provided cross-build integration can also be used as a template for other cross-build environment. Please refer to the detailed procedure on cross compilation here:- http://software.intel.com/en-us/articles/using-intel-c-compiler-for-embedded-system