General > General Technical Chat
Drawbacks when working on automotive firmware development?
ace1903:
I apologize if subject is unclear. English is not my native language and know that better words are needed for my question.
Lately I am getting job offerings to work on development on automotive firmware as contractor. Although my many years experience on firmware development, this area is new for me.
I wanted to ask if someone has experience working on automotive to share it here.
I prepared like summary of pros and cons when working on automotive. Maybe there are some my misconceptions and I would like someone with experience to prove it wrong.
Pros:
1) Requirements are well defined and known upfront. No stupid request like IOT battery powered artificial network device that needs to work on single AAA battery 10 years.
2) Defined workflow. Requirement specification, software architecture design, codding, code reviews and good QA testing with no skipping steps.
3) Hardware is designed by professionals and well tested. No endless debugging to find out that power supply causes glitches in software
4) Automatics tests and code coverage tests prevents single change to break whole firmware.
Cons:
1) Job looks boring. Looking at single software module for years each day.
2) Automatic counting of LOC produced each day adds stress
3) Everyone wants internet gateway nowadays with API that is limited and not to break existing software.
4) Knowledge is kept at company core and it is difficult to learn something that will be valuable outside that sector.
5) Part that is given to contractors most often is headers exported from Autosar and single doc file. One can work for years not knowing how whole software works.
Everyone is welcomed to comment and share experience.
Mecanix:
The position may be interesting if you are given the role where innovation is key to performance and corporate competition (aka incentives).
Neural networks powered automotive and systems comes to mind.. for instance.
Conventional transistor firmware'ing is getting pretty redundant in this sector, to my limited knowledge?
ace1903:
I am little bit disappointed because I expected experts from Continental, Bosch, Aptiv, ZF, ThyssenKropp to say anonymously a word or two
abut what they like or dislike in their everyday jobs.
Conventional transistor firmware I think it is on top notch now since this semiconductor shortage. Seems quick replacement firmware is needed for the chips that are available instead of that were used.
Neural networks are fine but wondering how much of that code can be made MISRA compatible and under ISO26262.
Mecanix:
Highest concentration of automotive sector's M.E & E.E. are on the Siemens forums. Transport, aviation, aerospace too...
May or may not be in line with the topic directly (product specific forums) however these folks could give you hints RE trending innovations in the making. Reasoning; see if that matches your job offer's objectives long term-wise and decide then.
e.g.
https://blogs.sw.siemens.com/thought-leadership/2021/10/19/automotive-industry-and-the-impact-of-covid-the-future-car-on-e-e-systems-ep-2-transcript/
ps note the conclusion where it reads "...Automotive E/E Systems Revolution".
amyk:
--- Quote from: ace1903 on November 15, 2021, 01:43:07 pm ---2) Automatic counting of LOC produced each day adds stress
--- End quote ---
They still do that? I've heard horror stories about how companies did that a long time ago, and it resulted in awful bloated code.
Navigation
[0] Message Index
[#] Next page
Go to full version