AR7556 device breaks legato framework


#1

Hi,

using legato 15.01 on AR7556 is not possible.

[pid 1392] <root>.le_data WAITING for <root>.le_data (protocol ID = '022cdee162039dc807bc4bc4972ac9090ea11b221e0c43005ab8faba7840d911') [pid 1486] <root>.cellNetService.cellNetService.le_mrc WAITING for <root>.le_mrc (protocol ID = 'c5da8917f55ed18a91ac4ac416c1ae65cc43e194ff182e988a338744e856bee1') [pid 1502] <root>.dcsDaemon.dataConnectionService.le_cellnet WAITING for <root>.le_cellnet (protocol ID = '94b49727ca0a34aae55bf469e20d1253297e79730f69fa20ab61e46f0dfe4152') [pid 1518] <root>.modemDaemon.modemDaemon.le_audio WAITING for <root>.le_audio (protocol ID = 'de780ed553ac1f2092ded6c34caabcc322fc7e32785cf650ccc6158be3a6035d') [pid 1608] <root>.voiceCallService.voiceCallService.le_mcc_call WAITING for <root>.le_mcc_call (protocol ID = 'c3ebec4e6dbf255d0232b7ac1b1f40b25cca87426f70491c2531e55769be0344')

Apps will not start because of missing interfaces insdie legato.

Please give hints how to use the legato with AR7556.

Thanks!

Regards,
Michael


#2

Hi Michael,

Just an insight on why Legato is not running properly on your AR7556. As you mentioned in your other thread, the AR7556 is designed for China without integrated audio codec. There is at the moment a dependency between the audioService and the modemService (for voice call). I suspect that because there are no audio codec on your module, the audioService cannot initialize properly; hence, all modem services such as sms, data etc… does not work either.

By the way, how did you get an AR7556?

Thank you,
Enoch


#3

Hi.

Thanks for your reply, in both Threads.

I get the AR7556 to be prepared for asian markets. With the proper provider I can even go online with these modules in germany. For platform, that will be spread over the world, we use the base of your modules without codec. As I work for an audiophile company, we gone use an external audio codec.

I there a way to break the dependency? E.g. by excluding the voice feature from legato build?

Thanks in advance.


#4

Hi Enoch,

on the AR7556, audioDaemon does terminate immediately with:

Jan 1 04:50:01 futuretelematics user.emerg Legato: *EMR* | audioDaemon[707]/le_pa_audio T=main | pa_audio.c SetMixerParameter() 330 | Cannot get mixer controler <DAC3 MUX>

How can that be resolved?

Thanks


#5

Hi,

Can you contact a system engineer through your vendor? They should be able to support you with this AR7556 specific issue.

Enoch


#6

Hi,

Legato 15.05 has separated the audio from modem?

I face the same issue with AR7550 devices.

[code]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_data -> <root>.le_data
    <root>.le_info -> <root>.le_info
    <root>.le_fwupdate -> <root>.le_fwupdate
    <root>.le_posCtrl -> <root>.le_posCtrl
    <root>.le_pos -> <root>.le_pos
    <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_avc  (protocol ID = 'e97f2cd4c04b94335be7bb58f5d46fb5ea98669becd1423f1e7475c8be884a52', 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_secStore  (protocol ID = '682a132a00535deee10c25f46535c84edf8f2514c0eee3c977773bb36284c8d4', 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_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   632] <root>.cellNetService.cellNetService.le_mrc WAITING for <root>.le_mrc  (protocol ID = 'c5da8917f55ed18a91ac4ac416c1ae65cc43e194ff182e988a338744e856bee1')
    [pid   633] <root>.dcsDaemon.dataConnectionService.le_cellnet WAITING for <root>.le_cellnet  (protocol ID = '94b49727ca0a34aae55bf469e20d1253297e79730f69fa20ab61e46f0dfe4152')
    [pid   639] <root>.modemDaemon.modemDaemon.le_audio WAITING for <root>.le_audio  (protocol ID = 'de780ed553ac1f2092ded6c34caabcc322fc7e32785cf650ccc6158be3a6035d')
    [pid   646] <root>.voiceCallService.voiceCallService.le_mcc_call WAITING for <root>.le_mcc_call  (protocol ID = 'c3ebec4e6dbf255d0232b7ac1b1f40b25cca87426f70491c2531e55769be0344')[/code]

Is there any special IO configuration to activate the audio codec?

On this target I also disabled the swiapp like described in this post [url]https://forum.sierrawireless.com/t/audio-feature-known-issue/11923/1]

Thanks in advance!


#7

Audio Service is not running is the very common error in Windows 7. Due to this error, Audio is not working in the windows. So, Users want to fix this error as soon as possible. Here i like to discuss two methods which help to fix it.
1- You just simple increase or decrease your computer’s volume.
2- If still you facing error then restart the Windows Audio service and all of its dependencies.
You can see the complete detail of https://appuals.com/fix-audio-service-not-running/ which will be helpful for you to resolve this error.