[genivi-dlt] changes in DLT; AUTOSAR harmonization

Lipka, Christoph (ADITG/ESA) clipka at jp.adit-jv.com
Wed Apr 5 02:42:22 EDT 2017


Hello Jeremiah,

Sorry for not answering, I was on holiday for a longer time.
I like to discuss also on these topics:
- DLT in shared Libraries
- DLT security aspects (Injection messages, etc.)

These topics might be also interested for others.

BTW: Is someone from AUTOSAR attending to explain/discuss the changes in detail?

Regards,
Christoph 

-----Ursprüngliche Nachricht-----
Von: genivi-diagnostic-log-and-trace [mailto:genivi-diagnostic-log-and-trace-bounces at lists.genivi.org] Im Auftrag von Jeremiah Foster
Gesendet: Dienstag, 28. März 2017 00:09
An: Alexander.AW.Wenzel at bmw.de
Cc: genivi-diagnostic-log-and-trace at lists.genivi.org; eg-si at mail.genivi.org; Lipka, Christoph (ADITG/ESA)
Betreff: Re: [genivi-dlt] changes in DLT; AUTOSAR harmonization

Hello Everyone,

I'm bringing up this topic again since we need to create an agenda for discussion at GENIVI's AMM. The All Members Meeting offers an opportunity for various stakeholders to go through the specifications and do any needed harmonization work. I've already received some input from AUTOSAR folks and its important that we bring up the topics that affect GENIVI members usage of DLT so that they are not surprised or confused when the changes come into the component and that may have an impact on production software.

It looks like a discussion on the removal of deprecated control messages and the addition of new control messages might be one topic. UDP in DLT daemon might be another. Do we have more topics? Do we need more input?

Please reply to this thread and I'll help in creating a session at the AMM and any needed GENIVI infrastructure for completing the work.

Regards,

Jeremiah


On Mon, Mar 13, 2017 at 9:31 AM, <Alexander.AW.Wenzel at bmw.de> wrote:

> Hello Christoph,
>
> I was involved in the review of the new AUTOSAR DLT Standard. The 
> Standard was split into two documents, one describing the DLT Protocol 
> only and the other handling the DLT SW component in AUTOSAR.
>
> You can find the new version here:
>
> 1) Diagnostic, Log and Trace Protocol Specification
> http://www.autosar.org/fileadmin/files/standards/classic/4-2/software-
> architecture/system-services/standard/AUTOSAR_SWS_
> DiagnosticLogAndTrace.pdf
>
> 2) Specification of Diagnostic Log and Trace
> http://www.autosar.org/fileadmin/files/standards/classic/4-2/software-
> architecture/system-services/standard/AUTOSAR_SWS_
> DiagnosticLogAndTrace.pdf
>
> The first document is the more important document for GENIVI DLT 
> implementation. It is important that GENIVI DLT implementation will be 
> compatible with AUTOSAR standard also in future. During review of the 
> changes I took care, that the protocol was not changed completely. 
> There were only some unnecessary control messages removed, which are 
> also not important for GENIVI implementation and some new control 
> messages were added. Nevertheless we need a walkthrough of the changes 
> to identify, which things must be changed.
>
> An important topic for us in the future will be the support of UDP in 
> the DLT daemon. The DLT Viewer already supports UDP. Perhaps someone 
> in the DLT community has already a UDP implementation or is interested 
> in the development of this feature.
>
> The document 2) should also be analysed, if any incompatibility to the 
> AUTOSAR standard exists, but it is not a must have to implement all 
> the AUTOSAR specific feature in GENIVI.
>
> Best regards
>
>     Alex
>
> --
> BMW Group
> Alexander Wenzel
> Architect. Connected Drive, I and C Syst.
> EE-60
>
> Postanschrift:
> 80788 München
>
> Tel: +49-89-382-54199
> Mobil: +49-151-601-54199
> Mail: alexander.aw.wenzel at bmw.de
> Web: http://www.bmwgroup.com/
> --------------------------------------------------------------------
> Bayerische Motoren Werke Aktiengesellschaft
> Vorstand: Harald Krüger (Vorsitzender), Milagros Caiña 
> Carreiro-Andree, Markus Duesmann, Klaus Fröhlich, Nicolas Peter, Ian 
> Robertson, Peter Schwarzenbauer, Oliver Zipse.
> Vorsitzender des Aufsichtsrats: Norbert Reithofer Sitz und 
> Registergericht: München HRB 42243
> --------------------------------------------------------------------
>
> -----Ursprüngliche Nachricht-----
> Von: genivi-diagnostic-log-and-trace [mailto:genivi-diagnostic-log- 
> and-trace-bounces at lists.genivi.org] Im Auftrag von Lipka, Christoph
> (ADITJ/SWG)
> Gesendet: Dienstag, 28. Februar 2017 10:00
> An: genivi-diagnostic-log-and-trace at lists.genivi.org;
> eg-si at mail.genivi.org
> Betreff: Re: [genivi-dlt] changes in DLT; AUTOSAR harmonization
>
> Hello Rinat,
>
> Thanks for your effort in helping to stay aligned between GENIVI and 
> AUTOSAR.
> Could you please explain a bit the motivation of the AUTOSAR standard 
> update and the proposed changes?
>
> Regarding [1]. I want to distinguish here between AUTOSAR defined DLT 
> Services and User defined DLT services as implemented in GENIVI. I 
> appreciate the alignment of AUTOSAR defined services:
> •         Set verbose mode
> •         Set timing packets
> •         Use ECU id
> •         Use session id
> •         Use timestamp
> •         Use extended header
> •         Get software version
> •         Set communication interface maximum bandwidth
> •         Message buffer overflow (will be replaced by a new DLT message
> “BufferOverflowNotification”)
>
> User defined Services have been added to support features that make 
> sense on Linux, but not necessarily supported by an AUTOSAR ECU (e.g. 
> Logstorage, MultiNode). I actually like them to be untouched while 
> aligning to new AUTOSAR specification update. These are in your list:
> •         Message connection info
> •         Message unregister context
> •         Timezone
> •         Marker
> •         Offline log storage
> •         (Dis)Connect passive Node
> •         Passive Node status information
> Some of them might be unnecessary or incomplete. E.g. why is there a 
> unregister context message, but no message for registering a context, 
> application or unregister an application?
>
> Could you please share more information regarding all *LogChannel* 
> related proposed Control Messages?
>
> Regarding [2]: Connectionless implementation: You wrote DLT messages 
> shall be sent nevertheless a client is connected or not. How does this 
> fit to the implementation of startup buffering in GENIVI? In the 
> current implementation, the DLT user library contains a startup buffer 
> to be filled when DLT Daemon is not yet started. After connection to 
> DLT Daemon is established, this buffer is flushed to DLT Daemon. The 
> DLT Daemon itself also contains a ringbuffer which gets filled as long 
> as no client is connected. This “double buffer” concept is critical to 
> minimize the logging impact especially during system startup, where 
> many applications get started and depending on the configured log 
> level sending a hugh amount of log messages.
> Both points need to be clarified.
>
> We may have to step back and define and compare use cases of DLT from 
> a AUTOSAR and Linux user perspective.
>
> Besides that I have some more questions/remarks:
> - This change is quite big, I propose to do a version update to DLT 
> Daemon
> 3.0 for this implementation
> - Are you already plan when this gets implemented?
> - What changes to you expect for the DLT Viewer to support such changes?
> Do you plan to update DLT Viewer side?
> - When thinking about such changes and when the implementation need to 
> be updated, we may have to consider other Linux related topics like a
>   * thread safe user library
>   * DLT logging from within shared libraries
>   * DLT and container
>   * security aspects
>   * etc.
>   This is not necessarily related, but might be discussed as well.
>
> There is already a session scheduled for the AMM:
> https://collab.genivi.org/wiki/display/genivi/
> AllMemberMeetingSpring2017SessionContent#AllMemberMeetingSpring2017Ses
> s
> ionContent-DLTworkshopandreadout
> Are you going to add description for it?
> I just got the allowance to join the AMM and I am looking forward to 
> discuss this topic with you and hopefully many other interested members.
>
> Best regards
>
> Christoph Lipka
> Software Group (ADITJ/SWG)
>
> Tel. +81-(0)566 61-5124
>
> From: Rinat.Asmus at bmw.de [mailto:Rinat.Asmus at bmw.de]
> Sent: Thursday, February 23, 2017 12:00 AM
> To: genivi-diagnostic-log-and-trace at lists.genivi.org;
> eg-si at mail.genivi.org
> Cc: Lipka, Christoph (ADITJ/SWG); Niemeyer, Ralph (ADITG/SW1)
> Subject: changes in DLT; AUTOSAR harmonization
>
> Dear GENIVI user list,
> BMW is using DLT in several series projects. Some of the ECUs are 
> using AUTOSAR, some are using other platforms. Unfortunately, current 
> DLT implementations and specifications vary.
> Our goal is  to reduce complexity and harmonize the GENIVI and future 
> AUTOSAR implementations in respect to
> •         [1] The DLT Protocol including the defined DLT Control Messages
> •         [2] A connectionless Implementation (DLT Messages shall be sent
> independently whether or not a Logging Device is connected to the ECU) 
> Regarding the topic [1] DLT Protocol: The available Control Messages 
> shall be harmonized in the following way:
> ⇨  Set these DLT Control Messages to deprecated:
> •         Message connection info
> •         Message unregister context
> •         Timezone
> •         Marker
> •         Offline log storage
> •         (Dis)Connect passive Node
> •         Passive Node status information
> •         Set verbose mode
> •         Set timing packets
> •         Use ECU id
> •         Use session id
> •         Use timestamp
> •         Use extended header
> •         Get software version
> •         Set communication interface maximum bandwidth
> •         Message buffer overflow (will be replaced by a new DLT message
> “BufferOverflowNotification”)
>
> ⇨  Introduce these new DLT Control Messages:
> •         GetDefaultTraceStatus
> •         GetLogChannelNames
> •         GetTraceStatus
> •         SetLogChannelAssignment
> •         GetLogChannelThreshold
> •         SetLogChannelThreshold
> •         BufferOverflowNotification (replaces the current  DLT message
> “Message buffer overflow”)
> Regarding the topic [2] Connectionless implementation:
> The DLT implementation shall allow a connectionless mode which means 
> that it should work without any mandatory interaction of a DLT Logging Device.
> For these two reasons, we would like to get in touch with you and 
> would like to discuss further details in the upcoming GENIVI face 2 
> face meeting in May.
> --
> BMW Group
> Rinat Asmus
> AUTOSAR project lead
> Hufelandstr. 1
>
> Postal address:
> 80937 München
>
> Tel: +49-89-382-65843
> Mail: rinat.asmus at bmw.de
> Web: http://www.bmwgroup.com/
> --------------------------------------------------------------------
> Bayerische Motoren Werke Aktiengesellschaft
> Vorstand: Harald Krüger (Vorsitzender), Milagros Caiña 
> Carreiro-Andree, Markus Duesmann, Klaus Fröhlich, Nicolas Peter, Ian 
> Robertson, Peter Schwarzenbauer, Oliver Zipse.
> Vorsitzender des Aufsichtsrats: Norbert Reithofer Sitz und 
> Registergericht: München HRB 42243
> --------------------------------------------------------------------
>
> _______________________________________________
> genivi-diagnostic-log-and-trace mailing list 
> genivi-diagnostic-log-and-trace at lists.genivi.org
> http://lists.genivi.org/mailman/listinfo/genivi-diagnostic-log-and-tra
> ce _______________________________________________
> genivi-diagnostic-log-and-trace mailing list 
> genivi-diagnostic-log-and-trace at lists.genivi.org
> http://lists.genivi.org/mailman/listinfo/genivi-diagnostic-log-and-tra
> ce
>



-- 

Jeremiah C. Foster
GENIVI COMMUNITY MANAGER

Pelagicore AB
Ekelundsgatan 4, 6tr SE-411 18
Gothenburg, Sweden
M: +1.860.772.9242
jeremiah.foster at pelagicore.com
www.pelagicore.com <http://www.luxoft.com/pelagicore>


Registered Office Gothenburg, Sweden
Registration No. 556780-4199
_______________________________________________
genivi-diagnostic-log-and-trace mailing list genivi-diagnostic-log-and-trace at lists.genivi.org
http://lists.genivi.org/mailman/listinfo/genivi-diagnostic-log-and-trace


More information about the genivi-diagnostic-log-and-trace mailing list