4,199
edits
Changes
m
TODO: Note that you cannot use stepin only stepover (all debug chapters) Categorize new tutorials
TODO: Explain that Eclipse only can build ARM projects How to manage the kernel modules on Linux
TODO: COde::Blocks or CodeBlocksHow do I edit my kernel command line
This guide can be helpful to learnt to develop Qt applications under IGEP Boards. Qt is a cross-platform application framework that is widely used for developing application software with a graphical user interface, and also used for developing non-GUI programs such as command-line tools and consoles for servers. You can get more information [http://qtdownload.nokiawavetlan.com/ here]SVV/Media/HTTP/FAAC-HE-AAC. aac
There are some requisites to follow this guide: outofthebox->ok
*[http://isee.biz/component/zoo/item/igep-virtual-machine-sdk-yocto IGEP SDK VM]: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 2.3 "Setting up and running the VM")<br> *[http://downloads.isee.biz/denzil/binary/qt4e-demo-image-igep00x0.tar.bz2 IGEP Qt Demo]: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card") and install qt4e-demo-image-igep00x0.tar.bz2 instead IGEP firmware. *[http://www.isee.biz/products/processor-boards/igepv2-board IGEPv2], [http://www.isee.biz/products/expansion-boards/product-igep-berlin IGEP BERLIN] or [http://www.isee.biz/products/expansion-boards/product-igep-paris IGEP PARIS] *MicroSD Card (at least 2Gbytes)<br>
== Download and install Qt demo image to a SD<br'''MP3DEC -> ==DEC MP3 (AUDIO ERRORS)'''
Once you have open IGEP SDK VM, launch a terminal and type: <pre>cd Desktop/wget http://downloads.isee.biz/denzil/binary/qt4e-demoFollowed README file from ISEE -imageIGEP DSP -igep00x0GST + DMAI Support Package 3.tar40.bz2 git clone git://git.isee.biz/pub/scm/igep-tools.gitcd igep-tools/scripts</pre> Insert a SD-Card media and use the igep-media-create script to copy the firmware to SD-Card media, required options are: 00
*--mmc <http:/dev/sdX>www.stephaniequinn.com/Music/Canon.mp3
unformated MMC Card gst-launch --gst-debug-level=2 filesrc location=Canon.mp3 ! TIAuddec1 codecName=mp3dec engineName=codecServer ! volume volume=0.25 ! alsasink sync=false
*--image <filename>'''Random fatal bit error'''
specify file used to create '''mp3-plugin doesn't resolve the bootable SD card. error'''
*--machine <machine>--
specify the machine. Options are igep0020, igep0030 or igep0032<br'''G711DEC -> DEC PCM uLAW (speech) (NOT TESTED)'''
For example, assuming the SD card device takes "/dev/sdf" and you have and IGEPv2 board '''G711ENC -> ENC PCM uLAW (igep0020speech), type: <pre>./igep-media-create --mmc /dev/sdf --machine igep0020 --image /home/jdoe/Desktop/qt4e-demo-image-igep00x0.tar.bz2</pre> This should give you a bootable SD-card<br> (NOT TESTED)'''
Qt demo image is a root filesystem build by Yocto that contains Qt embedded libraries, also this image has some Qt examples for testing purposes. '''AACLDDEC -> DEC AACLD (NOT TESTED)'''
This image doesn't have openssh and gdbserver, so we should install these packages to develop Qt applications. Open a shell prompt using serial communication ''WMA9 -> DEC WMA9 (IGEP SDK SOFTWARE MANUAL chapter 3.1 "Using serial mode"COMPILING ISSUES) and type the following commands: <pre>zypper refzypper in opensshzypper in gdbserver</pre> Now you can connect between IGEP and VM using SSH protocol:<br> <pre>ssh root@"IGEP IP for example: 192.168.5.1"</pre> == Using Qt Creator =='''
=== First Steeps<br'''ACCLCENC -> ===ENC AACLE (NOT TESTED)'''
==== Open Program:<br'''ACCHEENC -> ====ENC AACHE (NOT TESTED)'''
Go to Applications '''AACLDENC -> IGEP development -> Qt Creator<br> ENC AACLD (NOT TESTED)'''
{| border="1" width="200" cellspacing="1" cellpadding="1"|'''WMA8 -| [[Image:Openqtv2.png|331x249px]]<br> | [[Image:Qtopenedv2.png|331x249px]]<br>|}ENC WMA8 (NOT TESTED)'''
Copy your desired example from=== DM3730: /opt/QtSDK/Examples/4.7 to your desktop.<br> Decode a MP3 file (OK) (ADDED TO REPOSISTORIES)===
{| border="1" width="200" cellspacing="1" cellpadding="1"|-| [[Image:Qtcopyanexamplev2.png|496x373px]]|}'''under contruction'''
'''NOTE:''' some examples (like hellogl) cannot be compiled to ARM, for this How-to is used calculator example. Compiled gst-plugins-ugly using yocto tools
Open this example with Qt Creator, set Desktop target and use for each Qt Version one debug and one release - rpm -igst-plugins-ugly-0.*.rpm
{| border="1" width="757" cellspacing="1" cellpadding="1"|-| [[Image:Qtopenanexamplev2.png|250x188px]] | [[Image:Qtopenanexample2v2rpm -i libmad0-0.png|250x188px]] | [[Image:Qtopenanexample3v2*.png|250x188px]]|}rpm
'''<sup>Click to enlarge image</sup>'''- rpm -i gst-plugins-ugly-mad-0.*.rpm
To compile to ARM for IGEP go to Project use the following configuration at Projects field gst-> Build: launch --gst-debug-level=3 filesrc location=sample.ra ! rmdemux ! volume volume=0.25 ! alsasink
{| cellspacing="1" cellpadding="1" border="1" width="200"|-| [[Imagehttp:Qtarmconfigv2//www.png|496px]]|}superluminal.com/andalib/ra/listen.ra
'''<sup>Click to enlarge image</sup>''' gst-plugins-ugly-rmdemux-0.10.19-r1.armv7a.rpm
'''NOTElibgstsdp-0.10-0-0.10.36-r3.armv7a.rpm:''' Use Debug build if you want to debug later libgstsdp-0.10-0 libgstsdp-0.10.so.0
Compile withlibgstrtsp-0.10-0-0.10.36-r3.armv7a.rpm: Buildlibgstrtsp-0.10->Clean All and Build0 libgstrtsp->Build All (Ctrl+Shift+B)0.10.so. 0
==== Run Programs ===='''Error:'''
Once you compiled the program pass it from VM to IGEP via SSH, launch a terminal and type0: <pre>scp "pathtobinary" root@"IGEP IP for example00: 19200.168.5084839071 1550 0xa137b0 WARN rmdemux rmdemux.1"c:/home/root</pre> Get a remote shell prompt and run your program: <br> <pre>ssh root@"IGEP IP for example1012: 192.168.5.1"./"binary" "optionalgst_rmdemux_chain:arguments"</prermdemux0> {| cellspacing="1" cellpadding="1" border="1" width="200"|-| [[Image:Qtrunarmv2.jpg|496x373px]]|}Bogus looking header, unprintable FOURCC
'''0:00:00.085052695 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<suprmdemux0>Click to enlarge image</sup>''' Bogus looking header, unprintable FOURCC
'''NOTE0:''' You cannot use igep-remote-x program because Qt-demo image doesn't have X installed00:00.085540976 1550 0xa137b0 WARN rmdemux rmdemux.c:1057:gst_rmdemux_chain:<brrmdemux0> Unknown object_id .ra4
==== Debug Programs 0:00:00.085693564 ====1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, unprintable FOURCC
'''NOTE'''0: When you debug programs using Qt Creator "Step in" and "Step Out" are not supported00:00.085815634 1550 0xa137b0 WARN rmdemux rmdemux.c:1012:gst_rmdemux_chain:<rmdemux0> Bogus looking header, because dinamic libraries symbols are not loaded by gdb. unprintable FOURCC
Once you compiled the program pass it from VM to IGEP via SSH, launch a terminal and type0: <pre>scp "pathtobinary" root@"IGEP IP for example00: 19200.168085907187 1550 0xa137b0 WARN rmdemux rmdemux.5.1":/home/root</pre> Get a remote shell prompt and run gdbserverc: <pre>ssh root@"IGEP IP for example1057: 192.168.5.1"gdbserver "VM IP for example: 192.168.5.10":1000 "pathtobinary" "optional:armguments"</pre> Now use the followings steps to debug programgst_rmdemux_chain:<brrmdemux0> Unknown object_id RaTC
{| cellspacing="1" cellpadding="1" border="1" widthDM3730: Decode an AAC audio file (OK)==="200"|-| [[Image:Qtdebugx861v2.png|331x249px]] | [[Image:Qtarmdebug1v2.png|331x249px]]|-| [[Image:Qtarmdebug2v2.png|331x249px]] | [[Image:Qtarmdebug3v2.png|331x249px]]|}
Image 1: set breakpoints in your source code
Image 3: use the following configuration: faad2-2.7-r2.armv7a.rpmlibfaad2-2.7-r2.armv7a.rpmgst-plugins-bad-faad-0.10.23-r2.armv7a.rpm
*Debugger: /opt/poky/1'''maybe there are necessary more packages, compare actual gst-bad-recipe and add changes.2/sysroots/i686Necessary add faad2 recipe'''<pre>bitbake faad2 gst-pokysdkplugins-linuxbad</usr/bin/armv7apre><pre> rpm -vfpi faad2-neon2.7-pokyr2.armv7a.rpmrpm -linuxi libfaad2-gnueabi/arm-poky2.7-linux-gnueabi-gdb *Local executable: "pathtohostbinary" *Host and port: "IGEP IP for example: 192r2.168.5armv7a.1":1000 rpm*Architecture: arm *GNU target: armrpm -i gst-plugins-nonebad-linuxfaad-gnueabi *Sysroot: (empty)<br> *Location of debugging information: (empty) *Override host GDB start script: download [http://labs0.10.isee23-r2.biz/images/a/a1/Gdbinit_for_qt1.tararmv7a.bz2 gdbinit] file, uncompress to home folder and select it (/home/jdoerpm </gdbinit)<brpre>
'''NOTE:''' You cannot use igepgst-remotelaunch -x program because Qt-demo image doesn't have X installedgst-debug-level=3 filesrc location=sample.aac ! faad ! volume volume=0.<br>10 ! alsasink
==== Build Programs ====<pre>bitbake gst-ffmpeg</pre>
To compile to x86 go to Project use the following configuration at Projects field <pre>gst-> Build: launch -v filesrc location=sample.wma ! asfdemux ! decodebin ! audioconvert ! volume volume=0.25 ! alsasink </pre>
{| cellspacing="1" cellpadding="1" border="1" widthDM3730: Decode an OGG audio file (OK)==="200"|-| [[Image:Qtx86configv2.png|496px]]|}
'''NOTEhttp:''' Use Debug build if you want to debug later //upload.wikimedia.org/wikipedia/en/0/04/Rayman_2_music_sample.ogg
Compile with: Build->Clean All and Build->Build All (Ctrl+Shift+B).== Configure a static IP using the same private network range ==
==== Run Programs ===='''under construction'''
Use run button IGEP Firmware Yocto uses the following Ethernet network configuration (Ctrl+RIP addresses).
{| border="*eth0 − 192.168.5.1" width="200" cellspacing="1" cellpadding="1"|-| [[Image*eth0:Qtrunx86v20 − assigned via dhcp.png|496x373px]]|}
'''<sup>Click This Ethernet network configuration is really useful when you work using a Linux operating system like IGEP SDK Virtual Machine. Because you use eth0 device to enlarge image</sup>''' communicate easily with your board and eth0:0 device to get Internet acces using dhcp protocol.
==== Debug Programs ====But some scenarios this network configuration is not useful, for example: if you use a non-Linux operating system, connect to two IP private range interfaces is not simple. This How-to can be useful to
Set breakpoints in your source code (Make diagram one: IGEP and press debug button (F5Linux defualt communication. Diagram 2 IGEP and other SO alternative configuration)
{| border="1" widthigep.ini parameters ="200" cellspacing="1" cellpadding="1"|-| [[Image:Qtdebugx861v2.png|331x249px]] | [[Image:Qtdebugx862v2.png|331x249px]]|}
'''<sup>Click to enlarge image</sup>''' The kernel command line syntax is name=value1. These next parameters are supported in igep.ini since IGEP-X_Loader 2.4.0-2:
'''<sup>Click to enlarge image</sup>'''=== [kparams] ===
'''<sup>Click to enlarge image</sup>'''
Save all changes
== Using Code::Blocks ==
s
=== Build programs ===
s
=== Run programs ===
d
=== Debug programs ===
'''NOTE''': When you debug programs using CodeBlocks "Step into" and "Step out" are not supported, because dinamic libraries symbols are not loaded by gdb.
→DM3730: Decode an AAC audio file (OK)
= "CHECK ALL IN A NEW VIRTUAL MACHINE" TODO: =
= How to develop with Qt under IGEP = AUDIO DSP-ARM==
== Overview =Included (IGEP GST DSP):==='''AACHEDEC -> DEC AACHE (OK)'''
gst-launch --gst-debug-level=2 filesrc location= Requirements<br> sampleaache.m4a ! TIAuddec1 codecName=aachedec engineName=codecServer ! volume volume=0.25 ! alsasink sync==false
== Prepare Qt demo image =Not included (IGEP GST DSP):==='''ACCLCDEC -> DEC AACLE (NOT TESTED)'''
'''<sup>Click to enlarge image</sup>Problems adding codecs into igep-gst-dsp'''
==== Open an example:<br> ==DM3730==
'''<sup>Click to enlarge image</sup>does not have an accelerated audio decoder element'''
- gst-launch filesrc location=sample.mp3 ! mad ! volume volume== ARM Platform<br> ===0.25 ! alsasink
=== Build Programs <br> DM3730: Decode a RA or RM audio file (ERRORS)===
EXTRA_OECONF += "--disable-examples --disable-experimental --disable-sdl --disable-cdaudio --disable-directfb \ --with-plugins=musicbrainz,wavpack,ivorbis,mpegvideoparse,'''<sup>Click to enlarge image</sup>faad2''' --disable-vdpau --disable-apexsink \ --disable-orc"Install:
=== x86 Platform<br> = DM3730: Decode an WMA audio file (OK)====
'''<sup>Click to enlarge image</sup>Into repositories (base plugins):'''
gst-launch -v filesrc location=sample.ogg ! oggdemux ! vorbisdec ! audioconvert ! volume volume=0.25 ! alsasink
== BASE0033 CONNECTOR SUMMARY TABLE==
= Set up a NFS between IGEP Board and IGEP VM (check at prove it) == [kernel] ===
{| align="JUSTIFY" cellpadding= Overview "1" border="1" style="width: 900px; height: 240px;"|-| '''Parameter Name''' | '''Description''' | '''Default value''' | '''Comments'''|-| kaddress | Kernel copy address | =0x80008000 | Hex memory address|-| rdaddress | Ram Disk location address | =0x81600000 | Hex memory address;<br>disabled by defaultNetwork File System |-| serial.low | Serial number (NFSlow part) is a Distributed file system protocol originally developed by Sun Microsystems in 1984, allowing a user on a client Computer to access files over a network in a manner similar to how local storage is accessed| =00000001 | Numeric|-| serial. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call high | Serial number (ONC RPChigh part) system. The Network File System is an open standard defined in RFCs, allowing anyone to implement the protocol. More information [http://en.wikipedia.org/wiki/Network_File_System here].<br> | =00000000 | Numeric|-| revision | Revision ID | =0003 | Numeric|-| kImageName In IGEP Boards| Kernel, NFS protocol can be used to mount a whole rootfs partition located in a remote disk like Virtual Machine, this method can be useful for:<br> binary image name | =zImage *Your remote rootfs will not be limited by flash | Kernel or MicroSD storage.binary image name|-| kRdImageName | Kernel RAM Disk Image Name | - | Ram Disk image name*You can transfer binaries without using remote connections.|-*You can test other rootfs only editing igep.ini configuration file.| MachineID | Machine ID (kernel ID) {| cellspacing;IGEPv2<br>="1" cellpadding2344 | ;Module<br>="1" border="1" width2717<br>;Proton<br>="200"3203
|-
| [[Image:Nfs1 filesystem.pngMode | Boot Mode |331px]] ;Linux kernel<br>=kernel | ;Other image (like uboot)<br>[[Image:Nfs2 filesystem.png|331px]binary image]
|}
{| align="JUSTIFY" cellpadding= Requirements "1" border="1" style="width: 900px; height: 1095px;"|-| '''Parameter Name''' | '''Description''' | '''Default value''' There are some requisites to follow this guide: | '''Comments'''|-| buddy *[http:| Enable//isee.biz/component/zoo/item/igep-virtual-machine-sdk-yocto IGEP SDK VM]: follow the IGEPdisable expansion board support | SDK SOFTWAREIGEPv2 Expansion Board support<br>=igep0022 | USER MANUAL (chapter 2.3 "Setting up Berlin and running the VM")Paris Expansion Board support<br> *[http://downloads.isee.biz/denzil/binary/qt4e-demo-image-igep00x0.tar.bz2 IGEP Qt Demo] or [http://isee.biz/component/zoo/item/igep-firmware-yocto-1-2 IGEP Firmware]: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card") =base0010<br> *IGEP Board with Ethernet or Wifi connectionNew York Expansion<br>=ilms0015*MicroSD Card (at least 2Gbytes)|-| console == Set up NFS at VM ==| Setup the kernel console parameters | === Download and extract IGEP root filesystem ===ttyO2,115200n8 | -ISEE mantains two rootfs builded with Yocto tools: |-| earlyprintk *IGEP firmware: default software shipped in all IGEP Boards. It comes with some documentation and tools, so you need to uncompress again to extract rootfs| Enable early printk <pre>wget http://downloads.isee.biz/denzil/binary/igep_firmware| -yocto| -1.2.1|-1.tar.bz2 tar jxf igep_firmware-yocto-*.tar.bz2| mem cd igep_firmware-yocto-*| Setup the Board Memory Configuration sudo mkdir /srv/{your_rootfs_dir}| =430M sudo tar jxf demo| -image-sato-igep00x0.tar.bz2 |-C /srv/{your_rootfs_dir} </pre> *Qt demo: demo filesystem with Qt libraries and examples| boot_delay <pre>wget http://downloads.isee.biz/denzil/binary/qt4e-demo-image-igep00x0.tar.bz2 | Setup the boot delay sudo mkdir /srv/{your_rootfs_dir}| =0 sudo tar jxf qt4e| -demo|-image-igep00x0.tar.bz2 -C /srv/{your_rootfs_dir}</pre> === Configure NFS Server ===| mpurate | Setup ARM Processor Speed *Install nfs| -kernel| -server:<pre>sudo apt-get install nfs-kernel|-server </pre> *Make directory exports.d:<br>| loglevel <pre>sudo mkdir /etc/exports.d </pre> Edit /etc/exports file, add | Setup the following line and save the changes: loglevel <pre>/srv/{your_rootfs_dir} *(rw,sync,no_subtree_check,no_root_squash)</pre> | - Export NFS file system: | -<pre>sudo exportfs |-a</pre> '''NOTE: '''You can have as many rootfs as you want| debug | Enable kernel debug output == Set up NFS at IGEP Board ==| - | -=== MicroSD boot ===|-| fixrtc Configure igep.ini file located at boot partition:<br> | Fix RTC variable | - *Comment MMC boot:| -<pre>; --|- | nocompcache | Configure MMC boot ---nocompcache variable ;root| =/dev/mmcblk0p2 rw rootwait</pre> 1 *Add NFS configuration:| -<pre>; --- Configure NFS boot --|-ip=192.168.5| omapfb.1:192.168.5.10::255.255.255.0::eth0mode root=/dev/nfs| Configure frame bugger configuration nfsroot| =192.168.5.10dvi:/srv/{your_rootfs_dir}</pre> hd720-16@50 Save changes, plug MicroSD card and power up your IGEP.| ;Other configuration<br> =dvi:1280x720MR-16@60|-=== Flash boot<br> ===| vram | Configure Video RAM assigned to every frame buffer Boot IGEP with a MicroSD card without NFS support. | - <pre>mkdir /tmp/temp| -mount |-t jffs2 /dev/mtdblock1 /tmp/temp </pre> Now, mtdblock1 partition is mounted at /tmp/temp directory. Modify igep.ini located in: /tmp/temp/igep| omapfb.ini vram | Configure Video RAM assigned to every frame buffer *Comment JFFS2 FS boot:| - <pre>; -| -|- | omapfb.debug | Configure JFFS2 FS boot frame buffer debug output | -| -|-;root=/dev/mtdblock2| omapdss.debug ;rootfstype=jffs2</pre> | Configure DSS Video debug output *Add NFS configuration:| - <pre>; --- Configure NFS boot -| -|-ip=192.168.5| smsc911x.1:192.168.5.10::255.255.255.0::eth0mac0 root=/dev/nfs| Configure Board Ethernet Mac Address nfsroot| =192.168.5.10:/srv/{your_rootfs_dir}</pre> 0xb2,0xb0,0x14,0xb5,0xcd,0xde Save changes, power down | For IGEP, unplug MicroSD card and power up your boardBERLIN|-| smsc911x.mac1 | Configure Board Ethernet Mac Address | = Install and configure codeblocks for 0xb2,0xb0,0x14,0xb5,0xcd,0xdf | For IGEP devices BERLIN (under constructiononly with IGEP PROTON) =|-== Overview ==| smsc911x.mac | Configure Board Ethernet Mac Address Code::Blocks is a free and open source| =0xb2, cross-platform IDE which supports multiple compilers including GCC and MSVC. It is developed in C++ using wxWidgets as the GUI toolkit. Using a plugin architecture0xb0, its capabilities and features are defined by the provided plugins. Currently0x14, Code::Blocks is oriented towards C and C++. It can also be used for creating ARM0xb5, AVR0xcd, D0xde | For IGEPv2, DirectXIGEP PROTON, FLTK, Fortran, GLFW, GLUT, GTK+, Irrlicht, Lightfeather, MATLAB, OGRE, OpenGL, Qt, SDL, SFML, STL, SmartWin IGEP PARIS and wx programs and applications, although in some cases installing thirdIGEP BERLIN|-party SDKs or frameworks is necessary. More information [http://en.wikipedia.org/wiki/Codeblocks here]| ubi.<br> mtd | Fot UBI FS boot Code::Blocks is not installed by default in IGEP SDK VM, because Eclipse IDE is full integrated with IGEP Firmware. If you don't like Eclipse IDE or you want to use Code::blocks anyway this How| -to can be helpful to install, set up and use it.<br>| -== Requirements ==|-| root There are some requisites to follow this guide: | Configure root directory for MMC, NFS or UBI *[http://isee.biz/component/zoo/item/igep-virtual-machine-sdk-yocto IGEP SDK VM]: follow the IGEP| SDK SOFTWARE USER MANUAL (chapter 2.3 "Setting up and running the VM")For mmc memory<br> *[http:=/dev/isee.biz/component/zoo/item/igep-firmware-yocto-1-2 IGEP Firmware]: follow the IGEPmmcblk0p2 rw rootwait | SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card") For flash memory<br> =/dev/mtdblock2|-*IGEP Board | nfsroot *MicroSD Card (optional)| For NFS boot | - == Install Code::Blocks in VM ==| -<pre>sudo apt|-get install codeblocks codeblocks| rootfstype | For UBI FS boot | -contrib </pre> == Configure Code::Blocks ==| -|-=== Startup script ===| ip | For NFS boot Codeblocks startup script (Codeblocks.sh) will let you to load IGEP SDK YOCTO environtment variables to IDE. Don't execute this script if you want to compile with other environtment like x86.<br> | - <pre>cd Desktop/IGEP\ development/| -gedit Codeblocks.sh</pre> |-Copy this code to Codeblocks.sh | init <pre>#! /bin/bash| Assign init program source /opt/poky/1.2/environment| -setup| -armv7a|-vfp| musb_hdrc.debug | USB debug | -neon| -poky|-linux| musb_hdrc.use_dma | USB over network | -gnueabi exec codeblocks </pre> | -Give execute privileges to script: |-<pre>chmod a+x ~/Desktop/IGEP\ development/Codeblocks| libertas.shlibertas_debug | Configure libertas debug </pre> | - {| cellspacing="1" cellpadding="1" border="1" width="200"-
|-
| [[Image:Opencodeblocks1board.png|331px]]<br> ei485 | [[Image:Opencodeblocks2.png|331px]]<br>Enable/disable RS485 |} ;Enable RS485<br> === Add IGEP SDK Compiler and Debugger ===yes Follow the next instructions to add IGEP SDK| Yocto support: {| cellspacing="1" cellpadding="1" border="1" width;Disable RS485<br>="200"no
|-
| [[Image:Addsdkcodeblocks1board.pngmodem |250px]] Enable/disable GPRS modem | [[Image:Addsdkcodeblocks2.png|250px]] ;Enable modem (IGEPv2 Expansion)<br>=no | [[Image:Addsdkcodeblocks3.png|250px]] ;Enable modem (IGEPv2 Expansion)<br>=yes
|-
| [[Image:Addsdkcodeblocks4buddy.png|250px]] revision | Enable hardware buddy revision [[Image:Addsdkcodeblocks5.png|250px]A or B] | [[Image:Addsdkcodeblocks6.pngOnly for base0010<br>=A |250px]]Only for base0010<br>=B
|}