|
Hello,
We are trying to adapt the AGL flounder distribution to our custom board and we decided to use 4a-framework for audio management. We built the system and there is no problem with that. Then we wrote our own specific hal configuration. But other agl services
cannot get the right device uri. When we used afb-client-demo application to see what it returns, we are seeing the device uri section is empty. You can see our log and our hal config is in the attachments.
Kind Regards
Command:
4a-api hals
Response:
Detected systemd unit file!
Port detected:
---
4a-hal-manager loaded {'verbose':false,'all':false}
---
ON-REPLY 1:4a-hal-manager/loaded: OK
{
"response":[
],
"jtype":"afb-reply",
"request":{
"status":"success",
"info":"Requested data"
}
}
Command:
4a-api roles
Response:
Detected systemd unit file!
Port detected:
---
ahl-4a get_roles
---
ON-REPLY 1:ahl-4a/get_roles: OK
{
"response":[
],
"jtype":"afb-reply",
"request":{
"status":"success"
}
}
Client:
afb-client-demo -H "localhost:1234/api?token=1234&uuid=magic"
Command:
ahl-4a multimedia { "action": "open" }
Response:
ON-REPLY 1:ahl-4a/multimedia: OK
{
"response":{
"device_uri":""
},
"jtype":"afb-reply",
"request":{
"status":"success"
}
}
Command:
4a-hal-manager loaded { "verbose": true }
Response:
ON-REPLY 1:4a-hal-manager/loaded: OK
{
"response":[
],
"jtype":"afb-reply",
"request":{
"status":"success",
"info":"Requested data"
}
}
|
Attachment:
hal-4a-4ch-daiichi-config.json
Description: hal-4a-4ch-daiichi-config.json
_______________________________________________ automotive-discussions mailing list automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
