Can someone help with any open source autosar stack if any. I need classic as well as adaptive versions.
brief of what am doing: I need to implement this autosar stack on an Aurix Tricore lite kit.
EB provide evaluation edition for free which includes TC38XQ port.
https://www.elektrobit.com/products/ecu/eb-tresos/evaluation-package/
Related
Could anyone please tell me if the linuxptp is planning to release IEEE802.1AS-2020 support for linuxptp stack
Is there any plan/timeline for this release?
If already released can anyone please provide me the information about the same
or is there any opensource ptp stack which support IEEE802.1AS-2020 support?
Regards,
Sunil Kumar
There is no plan for supporting IEEE802.1AS-2020 by LinuxPTP maintainers and There is an Alternative for linuxptp which has IEEE802.1AS-2020 support it is provided by Company called Excelfore.
Currently, NXP's GenAVB_TSN support IEEE802.1AS-2020
https://github.com/NXP/GenAVB_TSN
Here's a link to "TSN Documentation Project for Linux*"
Describing:
Linux PTP also supports the Automotive Profile. To run ptp4l in that mode, the command-line is the same as presented in Synchronizing the PHC but with a different configuration file.
In last couple months while learning to develop Java Card applets I managed to develop ISO 7816 compatible file system applet. I successfully implemented most of the standardized APDU commands from 7816-4, -8, -9 standards (I used other available functional descriptions and standards like OpenPGP applet, IAS ECC, MUSCLE, CoolKey etc. to help me understand former standards).
Now I am trying to develop PKCS#11 implementation for this my own applet. I am familiar with using OpenSC tools for already supported cards (opensc-tool, opensc-explorer, pkcs15-init, pkcs15-tool etc.). But I would like to develop driver for this applet for OpenSC.
I browsed information available on their project site on github and found some documentation on implementing custom driver for OpenSC (entersafe card example, and general suggestions for card driver implementation). Also I found that on gooze.eu there were available some tutorials on OpenSC, but this site is no longer available.
So my questions are:
Where can I find some more information on OpenSC API in order to understand available driver code and to manage to develop my own?
Any general overview of API, about OpenSC architecture, description of available functions (description on intended usage of structures and functions such as sc_format_apdu, sc_transpit_apdu, sc_card_operatins as an example etc.) to give me a jumpstart for understanding OpenSC source code and implementing a card driver.
Are there any man pages for OpenSC API (googling I was able to find some, but very incomplete and sporadic).
Any information would be very helpful.
Why don't you either use IsoApplet (that has both JavaCard applet and OpenSC driver) or if you want to develop your own, learn from its source code.
Also, if you have studied the standards and existing applets (and drivers) you should have enough domain knowledge to get an idea of what some of the API functions do. If not, keep your code somewhere in public and you can (hopefully) get support from the OpenSC developers via mailing list.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm totally new to AUTOSAR and Arctic Studio. I have read the documentation available on www.autosar.org and now I would like to start playing around, understanding and writing some code.
I also found that only open source free development environment available for AUTOSAR platform is Arctic Studio (please correct me if I'm wrong). So I downloaded and installed it. I followed all the steps at http://212.181.18.149/wiki/Quick-start_Tutorial but unfortunately my build was not error-free.
I read example codes given in the 'examples' folder but didn't exactly get what happening or how to get started with writing even a simple code.
I was wondering if anyone could point me a direction to create a "Hello World" equivalent for AUTOSAR.
Writing a hello world equivalent in Autosar won't help you to familar with the concept.
you require the following things to get a know how about Autosar.
1)you need the MCAL(microcontroller layer),BSW and a simple application in the system.Non autosar component which can be included as Complex device driver is optional.
2)Create a sample application which sends a data 1 or 0 from a swc to any IO driver(preferable DIO)
depending on this you turn an LED on or off based on the corresponding registers
Also check for the supported boards on the Arcore site.
Commasso also provides an open source tool for Autosar but only to its members
AUTOSAR is a platform configurable based in layers.
You need the MCAL layer from the semiconductor company. The BSW+RTE layer created by your company/university or maybe some free plus the RTOS, then you integrate all for your uC, and create your "Hello World" in the APP layer, in some SWC to "print/send/show" the "Hello world" message.
If you don't have RTE or APP layer, you can create a CDD to execute your "Hello World".
The easiest way should be only using the MCAL: put the "hello world" in the main function, just integrate/configure the MCAL, (and the Startup). Check it with the debugger.
Arctic Core supports about a dosen different development boards which are listed in boards/ folder. If you have one of these, you can actually build and run a small project which prints "Hello world" over the UART or blinks a LED.
Walk through this tutorial and introduction to AUTOSAR by one of the biggest 3rd party provides, Vector Informatik GmbH.
The typical "Hello world" in the Embedded and Electronics world would be a blinking LED. Such examples exist for AUTOSAR too, however as has been pointed out you need several tools, libraries, packages, hardware to make this happen. Another way of "Hello world" in AUTOSAR could be a CAN message which you send on the bus, which is a key feature of every vehicle ECU being able to communicate.
There is another version of open source AUTOSAR platform available, How ever it is not completely free, Check this out
https://www.comasso.org/
Sorry this question really indicate that you are not much aware of AUTOSAR, as per AUTOSAR there is no UART module either.. of course blinking a LED is possible using DIO module along with PORT module.
I will try to explain as much as I can, please correct me if I am wrong and I am working in AUTOSAR development from last 5 years..
AUTOSAR is a collection of different requirement for developing ECU's in automotive industry.
Its some what open to all also, you can get all latest requirement on it from http://www.autosar.org/
Its total number of components or modules depends on your application and ECU.
Its architecture is in such a way that you can develope any one or few module or component and can use it with any other AUTOSAT compatible module / components. ( if both designed for same AUTOSAR major versions).
BR
Jerry James
If a developer wishes to learn how to hook windows APIs and gain modifications control over the system as a whole, including
say, hooking into kernel functions, NTDLL
Windows Internals 5th Edition (PRO-Developer) (Hardcover)
Is this the ultimate authority on this subject?
if not, what is?
The book you mention is very good.
For user space hooks, consider the following Programming Applications for Microsoft Windows by Jeffery Richter.
I am planning to use SCTP for a embedded Linux project. Anybody has some comments on SCTP usage, mostly in one-to-many mode? Did it beat using a home-made UDP-based equivalent solution?
I control the network environement and all devices involved, so compatibility is not an issue.
I have made extensive use of lksctp and have found it to be robust and interoperable with many other implementations of sctp. The standard for the sockets API for SCTP is still evolving but is quite mature and I would expect any further changes to be backwards compatible.
I would use it with confidence.
The ACE library has a performance test for SCTP, so I would assume that it works.
Currently these programs provide the only example code on
how to use ACE's wrapper-facades for SCTP. In the future additional
code will be placed in the ACE_wrappers/examples/IPC_SAP/SOCK_SAP
directory.
Using a framework like ACE is a good idea anyway, as it alloes you to program on a higher level and shields you from the error prone low level details of socket programming. As an additional bonus your code will be portable to all platforms that ACE supports.
Best answer is the comment:
Also, SCTP support in Glibc is less than ideal (in other words, non-present) -- you must use the libraries from lksctp, and it's not entirely well-integrated into the normal sockets API. Just one more reason to use a nice library that encapsulates the low-level functionality :) – ephemient