Need some advice about amb.
Description
Environment
Activity
Zheng Wenlong February 2, 2017 at 4:19 AM
Hi Mr.Stephane
Thanks for reply. Now I know what shold I do.
This issus will be closed.
Stephane Desneux January 31, 2017 at 10:36 AM
The first step is to develop the low level CAN binding: you can follow this step on https://lf-automotivelinux.atlassian.net/browse/SPEC-428#icft=SPEC-428.
Then depending on what the plugin was doing, it will possible to implement the same functionnality using the new CAN framework.
For writing and controlling a device, you can also take a look at the HVAC demo (application contains a Qt UI and a binding to relay operations to HVAC hardware) : check here: https://gerrit.automotivelinux.org/gerrit/gitweb?p=apps%2Fhvac.git;a=summary
Zheng Wenlong January 30, 2017 at 6:19 AM
Hi Mr Stephane
Thanks for reply.
Please let me explain what we did right now.
1 We add a source plugin to amb named "canrawplugin". (can300 support)
This plugin open can port "slcan0" or "vcan0" to read can data. Then push the data to amb core.
2 Modify dbus sink plugin, amb-qt and ces2017-demo, let "qml demo" read can data through dbus sink plugin.
3 Do some performances test for amb and ces2017-demo, and fix bugs.
We have done 1&2 and doing 3 right now. For further target, we sure want use afm to get can data.
May I ask, Is there any chance to port "canrawplugin", "dbus-amb-qt" and "qml demo" to afm? Does it difficult?
Stephane Desneux January 27, 2017 at 9:47 AM
@Zheng Wenlong let me clarify things:
meta-amb has been removed from AGL-repo on the master branch. That means that meta-amb (and thus ambd) wont be in the next DD release
but meta-amb has been kept in the chinook branch, on purpose.
So it's still possible to use the legacy code, but only on Chinook release.
I believe that pushing amb in further releases of AGL is not a good idea, even in development repository. At least, you can use the feature "agl-localdev" which adds a "meta-localdev" layer to the build (see meta-agl-extra/templates/features/agl-localdev), where you would import the amb recipe (you can directly fork the upstream meta-amb and rename it meta-localdev).
Best regards.
Stéphane
Zheng Wenlong January 27, 2017 at 12:44 AM(edited)
To Mr Jan-Simon:
I'm sorry to reopen this. We have some platform that still needs it, Can we add amb to meta-agl-devel as a oem needs library?
Otherwise we will consider another ways.
Hi Mr Jan-Simon Moeller
I noticed these is a merge for chinook to deleted amb(automotive message broker). Actually We is doing some work with amb now in Toyota.
I also noticed these is a new layer meta-amb which include amb recepie, but without any patches and without amb-qt library. What we done is need some patches and amb-qt library.
Can we use the meta-amb layer and do some modify?