# Error while accessing le\_data connection API in WP85xx legato application project **URL:** \ **Category:** Legato Linux distribution (Yocto project)\ **Created:** [March 8, 2017, 7:48am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380 "2017-03-08T07:48:27Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forum.legato.io/u/rups)\ **Post date:** [March 8, 2017, 7:48am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/1 "2017-03-08T07:48:27Z")
Hi, I am having mangOH board with WP85xx series. I have created legato application project in that, I am trying to use le\_dataConnection API but it is giving error as below: Error: Function ‘le\_data\_TryConnectService’ could not be resolved Type ‘le\_data\_RequestObjRef\_t’ could not be resolved my source code : ``` extern "C"{ #include "legato.h" #include "interfaces.h" } extern "C" { COMPONENT_INIT { LE_INFO("Initializing component started."); le_result_t res; le_data_RequestObjRef_t ref; res = le_data_TryConnectService(); } } ``` I have check all current bindings and services available with mangOH device , details as below: ``` root@swi-mdm9x15:~# sdir list BINDINGS .sdirTool -> .sdirTool .LogClient -> .LogClient .LogControl -> .LogControl .le_sup_ctrl -> .le_sup_ctrl .le_sup_wdog -> .le_sup_wdog .le_cfg -> .le_cfg .le_cfgAdmin -> .le_cfgAdmin .le_update -> .le_update .le_updateCtrl -> .le_updateCtrl .le_appRemove -> .le_appRemove .le_instStat -> .le_instStat .le_appInfo -> .le_appInfo .le_appProc -> .le_appProc .appSmack -> .appSmack .logFd -> .logFd .le_fwupdate -> .le_fwupdate .avcDaemon.avcDaemon.le_cfg -> .le_cfg .avcDaemon.avcDaemon.le_appInfo -> .le_appInfo .avcDaemon.appCfg.le_cfg -> .le_cfg .avcDaemon.avcAppUpdate.le_update -> .le_update .avcDaemon.avcAppUpdate.le_instStat -> .le_instStat .avcDaemon.avcAppUpdate.le_appRemove -> .le_appRemove .avcDaemon.avcAppUpdate.le_sup_ctrl -> .le_sup_ctrl .avcDaemon.avcAppUpdate.le_appInfo -> .le_appInfo .avcDaemon.avcAppUpdate.le_cfg -> .le_cfg .cellNetService.cellNetService.le_sim -> .le_sim .cellNetService.cellNetService.le_mrc -> .le_mrc .cellNetService.cellNetService.le_cfg -> .le_cfg .dcsDaemon.dataConnectionService.le_mdc -> .le_mdc .dcsDaemon.dataConnectionService.le_mrc -> .le_mrc .dcsDaemon.dataConnectionService.le_sim -> .le_sim .dcsDaemon.dataConnectionService.le_cellnet -> .le_cellnet .dcsDaemon.dataConnectionService.le_cfg -> .le_cfg .gpioService.sysfsGpio.le_cfg -> .le_cfg .modemDaemon.modemDaemon.le_cfg -> .le_cfg .modemDaemon.modemDaemon.le_pm -> .le_pm .posDaemon.posDaemon.le_cfg -> .le_cfg .secStore.appCfg.le_cfg -> .le_cfg .secStore.secStoreDaemon.le_appInfo -> .le_appInfo .secStore.secStoreDaemon.le_update -> .le_update .smsInboxService.smsInboxService.le_sim -> .le_sim .smsInboxService.smsInboxService.le_sms -> .le_sms .smsInboxService.smsInboxService.le_cfg -> .le_cfg .cm.cm.le_cfg -> .le_cfg .cm.cm.le_data -> .le_data .cm.cm.le_mrc -> .le_mrc .cm.cm.le_mdc -> .le_mdc .cm.cm.le_sim -> .le_sim .cm.cm.le_sms -> .le_sms .cm.cm.le_info -> .le_info .cm.cm.le_adc -> .le_adc .cm.cm.le_temp -> .le_temp .cm.cm.le_ips -> .le_ips .cm.cm.le_rtc -> .le_rtc .fwupdate.fwupdate.le_fwupdate -> .le_fwupdate .gnss.gnss.le_gnss -> .le_gnss .gnss.gnss.le_pos -> .le_pos .gnss.gnss.le_posCtrl -> .le_posCtrl .pmtool.pmtool.le_ulpm -> .le_ulpm .pmtool.pmtool.le_bootReason -> .le_bootReason .pmtool.pmtool.le_pm -> .le_pm .secstore.secstore.secStoreAdmin -> .secStoreAdmin .voiceCallService.voiceCallService.le_mcc -> .le_mcc .voiceCallService.voiceCallService.le_audio -> .le_audio .wifi.wifi.le_wifiClient -> .le_wifiClient .wifi.wifi.le_wifiAp -> .le_wifiAp .wifiApTest.wifiApTestComponent.le_wifiAp -> .le_wifiAp .wifiClientTest.wifiClientTestComponent.le_wifiClient -> .le_wifiClient .wifiWebAp.wifiWebApComponent.le_wifiAp -> .le_wifiAp DemoApplication.LogClient -> .LogClient DemoApp2.LogClient -> .LogClient SERVICES .sdirTool (protocol ID = 'sdirTool', max message size = 268 bytes) .logFd (protocol ID = '117ace8de217d75449a4c9698a82d4a9', max message size = 1104 bytes) .LogClient (protocol ID = 'LogControlProtocol', max message size = 300 bytes) .LogControl (protocol ID = 'LogControlProtocol', max message size = 300 bytes) .le_cfg (protocol ID = '8a26e6c5c2c76df02e412df515bd9f71', max message size = 1604 bytes) .le_cfgAdmin (protocol ID = '8732700875243b723b2ffcd56f807ae9', max message size = 1104 bytes) .le_update (protocol ID = 'aa0702b2ee62b2e6b86f1b71708b329e', max message size = 1104 bytes) .le_appRemove (protocol ID = '00c84606e1c1359c8fff5a3e96f4eff0', max message size = 1104 bytes) .le_instStat (protocol ID = '0948327abc5d498775520952fe46cf5c', max message size = 1104 bytes) .le_updateCtrl (protocol ID = '06d0977d4bb4d01afda6237bd33c0b9c', max message size = 1104 bytes) .le_sup_ctrl (protocol ID = 'fa6bf8cc16759825710163005fdfbe9e', max message size = 1104 bytes) .le_sup_wdog (protocol ID = '097fbccd0328ad2605764aecdd9339bc', max message size = 1104 bytes) .le_appInfo (protocol ID = 'f92de62899eb1ab8e72119f371ac3fb7', max message size = 1104 bytes) .le_appProc (protocol ID = 'a39440605262ba21c1ad7f777ffc885b', max message size = 1104 bytes) .le_wdog (protocol ID = '389c20913bdeb5d3928d55f3852135b3', max message size = 1104 bytes) .le_atClient (protocol ID = 'e02481d04f4b91a87b46b5ae8468b7e6', max message size = 1104 bytes) .le_pm (protocol ID = 'd4432c316b20d70444f61e31f53f03e7', max message size = 1104 bytes) .le_ulpm (protocol ID = '0396910cefbe1c3cb64549056dee1dfa', max message size = 1104 bytes) .le_bootReason (protocol ID = '7d55f7e527797be860b5666644f27973', max message size = 1104 bytes) .le_atServer (protocol ID = 'b95fb6329638c9229f619e0396d97c6a', max message size = 1104 bytes) .le_fwupdate (protocol ID = '7c948360e1df2b6ba4a92c34f9e6c335', max message size = 1104 bytes) .le_wifiClient (protocol ID = 'da0707db4fe4d07b1340d39e73eaf032', max message size = 1104 bytes) .le_wifiAp (protocol ID = '4ff3f438efca01cdc1878a61cd15932c', max message size = 1104 bytes) .le_secStore (protocol ID = '8b8edad7c68f1db9dd23ab6aa7286bc1', max message size = 8504 bytes) .secStoreAdmin (protocol ID = 'ea2df07974fddb1e29ff0ea75b056fd0', max message size = 8504 bytes) .le_gpioPin2 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin6 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin7 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin8 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin13 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin21 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin22 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin23 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin24 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin25 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin32 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin33 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin38 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin39 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin40 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin41 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_gpioPin42 (protocol ID = '53b428577c18e3558699d57262acfc23', max message size = 1104 bytes) .le_info (protocol ID = 'b95387f00f48c76d024c6d9d0f66b852', max message size = 1104 bytes) .le_sms (protocol ID = 'd26b22be0fe85bc15a90af10f7d8a763', max message size = 1104 bytes) .le_mrc (protocol ID = '74bd62afd4fc83a23e68a6e7230749f7', max message size = 1104 bytes) .le_sim (protocol ID = '5003e8cf806c2137854dd150a6a8b2ff', max message size = 1104 bytes) .le_mdc (protocol ID = 'f51d46d0916e8217f8268ebd7f42baa0', max message size = 1104 bytes) .le_mcc (protocol ID = '777c0b73990426b4607a00221c9bbd8a', max message size = 1104 bytes) .le_ecall (protocol ID = 'b1c201a17a0c2c920d3ca6449baee6b8', max message size = 1104 bytes) .le_ips (protocol ID = '56c5cba5a7432bfef2993f23fb20e301', max message size = 1104 bytes) .le_temp (protocol ID = 'edbdcab7bd9a0b21a45e3c14571e0142', max message size = 1104 bytes) .le_antenna (protocol ID = '1d182864820df39d84fc4ec67565256f', max message size = 1104 bytes) .le_riPin (protocol ID = '4e9952e2bf63425cef9166d475f6c589', max message size = 1104 bytes) .le_adc (protocol ID = '2fd8e9f3f6c6312b50eba80126dcee6b', max message size = 1104 bytes) .le_rtc (protocol ID = 'b8ff65055120e98365784481d667b417', max message size = 1104 bytes) .le_audio (protocol ID = 'e370edc833f30f7a5ea29bf604784811', max message size = 1104 bytes) .le_cellnet (protocol ID = 'af28a0c754f2f70de5f8943e05b85ee8', max message size = 1104 bytes) .le_avc (protocol ID = '2126873cd01b248f604738094b3b302f', max message size = 1104 bytes) .le_avdata (protocol ID = '00c24407f5702ddd739f1774a5e2bcdb', max message size = 1104 bytes) .le_gnss (protocol ID = 'faefa899507b7af1a762f95a33a1e2ff', max message size = 1104 bytes) .le_pos (protocol ID = '43630c2afa038107ba82a60b59813b6a', max message size = 1104 bytes) .le_posCtrl (protocol ID = '6cde5670dcdeaaf84719312c15d9157d', max message size = 1104 bytes) .le_data (protocol ID = 'b38b8adf952d3949dded3be5491798ea', max message size = 1104 bytes) WAITING CLIENTS ``` In above command response the binding details of data connection is .cm.cm.le\_data → .le\_data It is not shown as like other binding formats. Please help me, I want to know where I am doing mistake or any process to follow? ---
**Author:** ![spastor](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/spastor/32/80_2.png) [@spastor](https://forum.legato.io/u/spastor)\ **Post date:** [March 8, 2017, 7:54am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/2 "2017-03-08T07:54:19Z")
Hello Rups, Can you show your adef file, please ? Thanks, ---
**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forum.legato.io/u/rups)\ **Post date:** [March 8, 2017, 7:59am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/3 "2017-03-08T07:59:47Z")
adef file code: ``` version: 1.0.0 maxFileSystemBytes: 512K executables: { demoapp2 = ( DemoApp2Component ) } processes: { envVars: { LE_LOG_LEVEL = DEBUG } run: { ( demoapp2 ) } maxCoreDumpFileBytes: 512K maxFileBytes: 512K } ``` ---
**Author:** ![spastor](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/spastor/32/80_2.png) [@spastor](https://forum.legato.io/u/spastor)\ **Post date:** [March 8, 2017, 8:02am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/4 "2017-03-08T08:02:07Z")
Sorry, I forgot to ask you your Component file (cdef).😁 ---
**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forum.legato.io/u/rups)\ **Post date:** [March 8, 2017, 8:03am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/5 "2017-03-08T08:03:28Z")
cdef file code: ``` sources: { DemoApp2Component.cpp CfirstSampleclass.cpp } ``` ---
**Author:** ![spastor](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/spastor/32/80_2.png) [@spastor](https://forum.legato.io/u/spastor)\ **Post date:** [March 8, 2017, 8:08am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/6 "2017-03-08T08:08:37Z")
please add: > requires: > { > api: > { > le\_data.api > } > } If you want to connect to this api manually (because you use le\_data\_TryConnectService), add > requires: > { > api: > { > le\_data.api [manual-start] > } > } ---
**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forum.legato.io/u/rups)\ **Post date:** [March 8, 2017, 9:57am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/7 "2017-03-08T09:57:12Z")
Hi, I have updated ‘adef’ file as you suggested but it is giving error. ``` version: 1.0.0 maxFileSystemBytes: 512K executables: { demoapp2 = ( DemoApp2Component ) } requires: { api: { le_data.api [manual-start] } } processes: { envVars: { LE_LOG_LEVEL = DEBUG } run: { ( demoapp2 ) } maxCoreDumpFileBytes: 512K maxFileBytes: 512K } ``` **Error:** Unexpected character ’ ’ Expected ‘.’ DemoApp2.adef **Warning** ‘api’ subsection in ‘requires’ section is deprecated in .adef files. I have tried with : 1. le\_data.api 2. le\_data.api [manual-start] 3. api = le\_data but there is error , what is correct syntax to add it? ---
**Author:** ![daav](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/daav/32/64_2.png) [@daav](https://forum.legato.io/u/daav)\ **Post date:** [March 9, 2017, 7:53am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/8 "2017-03-09T07:53:53Z")
Hi @rups, The **require** section suggested by @spastor needs to be added to the **cdef** file. Then you’ll need to bind this interface to the service that is providing it. In the **adef** , please add the following section: ``` bindings: { demoapp2.DemoApp2Component.le_data -> dataConnectionService.le_data } ``` ---
**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forum.legato.io/u/rups)\ **Post date:** [March 9, 2017, 8:04am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/9 "2017-03-09T08:04:02Z")
I have added and tested. still error is there related to function call ’ unresolved error’ DemoApp2.adef: ``` version: 1.0.0 maxFileSystemBytes: 512K executables: { demoapp2 = ( DemoApp2Component ) } bindings: { demoapp2.DemoApp2Component.le_data -> dataConnectionService.le_data demoapp2.DemoApp2Component.le_mdc -> modemService.le_mdc } processes: { envVars: { LE_LOG_LEVEL = DEBUG } run: { ( demoapp2 ) } maxCoreDumpFileBytes: 512K maxFileBytes: 512K } ``` Component.cdef: ``` sources: { DemoApp2Component.cpp CfirstSampleclass.cpp } requires: { api: { le_data.api le_mdc.api } } ``` I have also tested by adding api with format **le\_data.api [manual-start]** any thing to be added in source file ??? because it is not supporting access to api functions. ---
**Author:** ![daav](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/daav/32/64_2.png) [@daav](https://forum.legato.io/u/daav)\ **Post date:** [March 9, 2017, 8:20am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/10 "2017-03-09T08:20:20Z")
Hi @rups Done the test, and I think this is just a refresh problem of the code editor. My guess is that the error you’re reporting is a **Semantic Error** one, correct? These errors are reported by the static code analyzer, which is triggered each time the **code** is modified, or the editor is opened. But as soon as your definition files are configured correctly (and this is the case now), if you open again the code editor, these errors should disappear, as the static code analyzer will be refreshed at this time. Another option to refresh is a right-click on the project, then **Run C/C++ code analysis** But please be careful that these errors are not yet compilation errors (reported as **C/C++ Problem** in the **Problems** view). Compilation errors will be reported when you explicitly build the project (with the hammer or run button in the toolbar). And typically, with this code, you’ll see that you have compilation errors 😉 Anyway, I’m logging the point, and we’ll check if we can avoid this refresh behavior in DS. Finally, by the way, please avoid posting topics on both forums (cf [http://forum.mangoh.io/t/error-while-accessing-le-dataconnection-api-methods/424/4](http://forum.mangoh.io/t/error-while-accessing-le-dataconnection-api-methods/424/4)) Legato forum is the good place for generic software oriented questions. MangOH forum is more dedicated to MangOH hardware/software specific questions. Thanks! ---
**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forum.legato.io/u/rups)\ **Post date:** [March 9, 2017, 9:19am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/11 "2017-03-09T09:19:51Z")
Hi, I have refresh and clean project. and then build it. same error exist. I found some different issue in console: ``` 14:47:03 ****Build of configuration Target_Legato_Debug for project DemoApp2**** make -I /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato all cd ..;mkapp -t wp85 -o Target_Legato_Debug -w Target_Legato_Debug -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/airVantage" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/wifi" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/positioning" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/logDaemon" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/secureStorage" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/supervisor" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/atServices" -i "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/modemServices" -s "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/components" -s "." -C -g -X -g -L -g DemoApp2.adef [1/13] Compiling C source [2/13] Compiling C source [3/13] Generating IPC interface code [4/13] Generating IPC interface code FAILED: mkdir -p Target_Legato_Debug/api/64979d0f501929075c20cdfc91e196e1/client && ifgen --output-dir Target_Legato_Debug/api/64979d0f501929075c20cdfc91e196e1/client --gen-client --gen-interface --gen-local --name-prefix le_mdc --file-prefix le_mdc --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/framework/c/inc --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/airVantage --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/wifi --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/positioning --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/logDaemon --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/secureStorage --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/supervisor --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/atServices --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/modemServices --import-dir /home/lateral15/Rupali/Linux/PROJECT/workspace/DemoApp2 /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/modemServices/le_mdc.api Traceback (most recent call last): File "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/bin/ifgen", line 32, in import common File "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/bin/common.py", line 8, in import jinja2 ImportError: No module named jinja2 FAILED: mkdir -p Target_Legato_Debug/api/09c50216275130832ce953f423c77f0a/client && ifgen --output-dir Target_Legato_Debug/api/09c50216275130832ce953f423c77f0a/client --gen-client --gen-interface --gen-local --name-prefix le_data --file-prefix le_data --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/framework/c/inc --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/airVantage --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/wifi --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/positioning --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/logDaemon --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/secureStorage --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/supervisor --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/atServices --import-dir /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/modemServices --import-dir /home/lateral15/Rupali/Linux/PROJECT/workspace/DemoApp2 /home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/interfaces/le_data.api Traceback (most recent call last): File "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/bin/ifgen", line 32, in import common File "/home/lateral15/legato/packages/legato.framework.16.7.0.201609081601/resources/legato/bin/common.py", line 8, in import jinja2 ImportError: No module named jinja2 ninja: build stopped: subcommand failed. make: *** [target] Error 1 Makefile:48: recipe for target 'target' failed 14:47:03 Build Finished (took 337ms) ``` ---
**Author:** ![daav](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/daav/32/64_2.png) [@daav](https://forum.legato.io/u/daav)\ **Post date:** [March 9, 2017, 9:33am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/12 "2017-03-09T09:33:22Z")
Hmm, sounds like you’re missing some basic requirements in your Linux setup. Please have a look at [http://source.sierrawireless.com/resources/airprime/software/legato\_application\_development\_kit\_linux/](http://source.sierrawireless.com/resources/airprime/software/legato_application_development_kit_linux/) in particular: ``` sudo apt-get install openjdk-8-jre libwebkitgtk-1.0-0 build-essential python-jinja2 ninja-build ``` ---
**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forum.legato.io/u/rups)\ **Post date:** [March 9, 2017, 10:07am UTC](https://forum.legato.io/t/error-while-accessing-le-data-connection-api-in-wp85xx-legato-application-project/2380/13 "2017-03-09T10:07:42Z")
Thank you @daav now all errors solved. project build successfully 😌 and sorry for post in mangOH forum. I will take care next time