Missing le_data interface

:smiling_imp: :smiling_imp: :smiling_imp: :smiling_imp: Hi.

Still working with AR7556 on our target hardware, but have no luck with mobile data access. I implement a network controller that binds to le_data. Wondering why the component init finction is not executed. sdir list gives some hints:

[code]root@futuretelematics:~# sdir list

BINDINGS

    <root>.sdirTool -> <root>.sdirTool
    <root>.LogControl -> <root>.LogControl
    <root>.le_sup_ctrl -> <root>.le_sup_ctrl
    <root>.le_sup_state -> <root>.le_sup_state
    <root>.le_sup_wdog -> <root>.le_sup_wdog
    <root>.le_cfg -> <root>.le_cfg
    <root>.le_cfgAdmin -> <root>.le_cfgAdmin
    <root>.le_mdc -> <root>.le_mdc
    <root>.le_mrc -> <root>.le_mrc
    <root>.le_sim -> <root>.le_sim
    <root>.le_sms -> <root>.le_sms
    <root>.le_fwupdate -> <root>.le_fwupdate
    <root>.le_data -> <root>.le_data
    <root>.le_info -> <root>.le_info
    <root>.le_pos -> <root>.le_pos
    <root>.le_posCtrl -> <root>.le_posCtrl
    <root>.cellNetService.cellNetService.le_cfg -> <root>.le_cfg
    <root>.cellNetService.cellNetService.le_mrc -> <root>.le_mrc
    <root>.cellNetService.cellNetService.le_sim -> <root>.le_sim
    <root>.dcsDaemon.dataConnectionService.le_cellnet -> <root>.le_cellnet
    <root>.dcsDaemon.dataConnectionService.le_cfg -> <root>.le_cfg
    <root>.dcsDaemon.dataConnectionService.le_mdc -> <root>.le_mdc
    <root>.dcsDaemon.dataConnectionService.le_mrc -> <root>.le_mrc
    <root>.dcsDaemon.dataConnectionService.le_sim -> <root>.le_sim
    <root>.modemDaemon.modemDaemon.le_audio -> <root>.le_audio
    <root>.modemDaemon.modemDaemon.le_cfg -> <root>.le_cfg
    <root>.modemDaemon.modemDaemon.le_pm -> <root>.le_pm
    <root>.posDaemon.posDaemon.le_cfg -> <root>.le_cfg
    <root>.LogClient -> <root>.LogClient
    <root>.voiceCallService.voiceCallService.le_mcc_call -> <root>.le_mcc_call
    <root>.voiceCallService.voiceCallService.le_mcc_profile -> <root>.le_mcc_profile

SERVICES

    <root>.sdirTool  (protocol ID = 'sdirTool', max message size = 268 bytes)
    <root>.LogClient  (protocol ID = 'LogControlProtocol', max message size = 300 bytes)
    <root>.LogControl  (protocol ID = 'LogControlProtocol', max message size = 300 bytes)
    <root>.le_cfg  (protocol ID = '9dc5b2438c9592bf35478c68b2ccb9b98de2966994582a00d1fbfbf9696b607e', max message size = 1004 bytes)
    <root>.le_cfgAdmin  (protocol ID = '973013e67043ad6e6449a1c75aed2937570c0ea5ebaf7b621c61c26f2cb46613', max message size = 1004 bytes)
    <root>.le_sup_ctrl  (protocol ID = '2b977a867fd23987d4186cef497320eaf0548b548f0c54f9e06758a2713100e9', max message size = 1004 bytes)
    <root>.le_sup_wdog  (protocol ID = '2009d178ea21adf594c52414142d823048d9539a18a6ad48762302d7763f4fc9', max message size = 1004 bytes)
    <root>.le_sup_state  (protocol ID = 'eae6bae687e5624b7f7b61e6d76653d5cf7ca7dc6a161652412da5457634d9c6', max message size = 1004 bytes)
    <root>.le_wdog  (protocol ID = '4cb07efd859b58751cc5ea09134b555b0ab30957ca7aa68772eb1de1edeeae3d', max message size = 1004 bytes)
    <root>.le_avc  (protocol ID = 'e97f2cd4c04b94335be7bb58f5d46fb5ea98669becd1423f1e7475c8be884a52', max message size = 1004 bytes)
    <root>.le_antenna  (protocol ID = 'd580b40f33f314064958ec052c6a279b9d065f930c3a331c38dc35267a2f03c6', max message size = 1004 bytes)
    <root>.le_pm  (protocol ID = '721a67e77c5f65da2056fc7e91b1f1c7238245e5cc5b95c70d4455978566af16', max message size = 1004 bytes)
    <root>.le_secStore  (protocol ID = '682a132a00535deee10c25f46535c84edf8f2514c0eee3c977773bb36284c8d4', max message size = 1004 bytes)
    <root>.le_gnss  (protocol ID = '12fff060981db1dcc210b4a566be0155ded109a865fb77da85646b9171b8470b', max message size = 1004 bytes)
    <root>.le_pos  (protocol ID = '3f8357fec6d610c7bf0cd5b95083e7768bdc22ba3819bf5b80b2c492234f4591', max message size = 1004 bytes)
    <root>.le_posCtrl  (protocol ID = 'e33f0f8f7f9c0f0d74ca59ada322dbc16eb38603f7340caa23d17c8bad22f3bf', max message size = 1004 bytes)

WAITING CLIENTS

    [pid  8036] <root>.le_data WAITING for <root>.le_data  (protocol ID = '022cdee162039dc807bc4bc4972ac9090ea11b221e0c43005ab8faba7840d911')
    [pid  8058] <root>.cellNetService.cellNetService.le_mrc WAITING for <root>.le_mrc  (protocol ID = 'c5da8917f55ed18a91ac4ac416c1ae65cc43e194ff182e988a338744e856bee1')
    [pid  8060] <root>.dcsDaemon.dataConnectionService.le_cellnet WAITING for <root>.le_cellnet  (protocol ID = '94b49727ca0a34aae55bf469e20d1253297e79730f69fa20ab61e46f0dfe4152')
    [pid  8077] <root>.modemDaemon.modemDaemon.le_audio WAITING for <root>.le_audio  (protocol ID = 'de780ed553ac1f2092ded6c34caabcc322fc7e32785cf650ccc6158be3a6035d')
    [pid  8100] <root>.voiceCallService.voiceCallService.le_mcc_call WAITING for <root>.le_mcc_call  (protocol ID = 'c3ebec4e6dbf255d0232b7ac1b1f40b25cca87426f70491c2531e55769be0344')

[/code]
As you can see there is a dependency chain down to le_mrc!

Why does the component serving the le_mrc is not coming up? Is this related to useage of the AR7556 in european area? AR7556 is designed for China without integrated audio codec.

Iā€™m running

root@futuretelematics:~# legato version
15.01.0.Beta-1-g157af17
root@futuretelematics:~# legato status
Legato framework is running.
root@futuretelematics:~# 

Maybe a hint, fwupdate and cm programs also do not run. They just do nothing, no error message. Apps are running:

root@futuretelematics:~# app status
[running] airvantage
[stopped] audioService
[running] avcService
[running] cellNetService
[running] dataConnectionService
[running] modemService
[running] monService
[running] positioningService
[running] powerMgr
[running] secStore
[running] voiceCallService

I have this problem with SIM inserted and with no SIM.

Please help finding the root cause.

Some more infos on used hardware:

[code]AT+CGMR
SWI9X15A_06.03.39.00 r26591 CNSHZ-AR-BUILD 2015/01/29 00:28:10

AT+CGMM
AR7556

AT+GCAP
+GCAP: +CGSM,+FCLASS,+DS

AT+CFUN?
+CFUN: 1

AT+CPAS
+CPAS: 0[/code]

My second development device is an AR7550. This does not show these problems, although the firmware is older!

root@futuretelematics:~# legato version 15.01.0.Beta-1-g157af17 root@futuretelematics:~# fwupdate query Firmware Version: SWI9X15A_06.03.32.00 r25917 CNSHZ-AR-BUILD 2014/12/13 09:06:29 Bootloader Version: SWI9X15A_06.03.32.00 r25917 CNSHZ-AR-BUILD 2014/12/13 09:06:29 Linux Version: 3.4.91-yocto-standard #10 PREEMPT Mon May 11 11:02:44 CEST 2015

My AR7556 is broken by failed update process?

Tried to restore the firmware by executing SWI9X15W_06.03.39.00-wp_yocto-cwe.exe under windows fails with error code 77.

Not healed by restoring base software with SWI9X15W_06.03.39.00-ar_yocto-cwe.exe and reinstalling legato framework. All my tries failed, there must be something special about the AR7556 device!

PLEASE help!

Please refer to your other thread for my response regarding this subject: https://forum.sierrawireless.com/t/ar7556-device-breaks-legato-framework/12041/2

As for failing the update process, you are currently trying to apply a WP7 firmware package SWI9X15W_06.03.39.00-wp_yocto-cwe.exe on an AR7. That is why it is failing. To get access to the AR7 firmware package, you will need to contact your FAE.

Thanks,
Enoch