REGISTER | LOGIN
Breaking News
Design How-To

Verifying the border line between auto hardware, software

2/16/2010 03:00 PM EST
6 comments
NO RATINGS
Page 1 / 2 Next >
More Related Links
View Comments: Newest First | Oldest First | Threaded View
hiTech
User Rank
Author
re: Verifying the border line between auto hardware, software
hiTech   3/6/2010 11:10:30 PM
NO RATINGS
ARINC DO-178B (being upgraded to DO-178C) for SW and DO-254 for ASICs / FPGAs have been formally adapted by the FAA and Boeing for flight safety critical SW and SW associated FPGA/ASIC systems (Boeing 777 and 787). Some aspects of these standards may be applicable to guide development, testing, and certification of automotive safety critical subsytems

BPA
User Rank
Author
re: Verifying the border line between auto hardware, software
BPA   2/18/2010 4:02:31 PM
NO RATINGS
The author has contradicted himself. In para. 6, he says that ASIC functional verification lacks the "executable, metric-driven verification plans, functional coverage and constrained-random test generation typically being used in software development." Then at the end he says, "The central problem for the future is that software verification has no formalized methodology." So which is it? In my experience, software testing is not ad-hoc. We design our software to meet detailed requirements and specifications and develop specific tests to ensure that they are met.

winterho
User Rank
Author
re: Verifying the border line between auto hardware, software
winterho   2/17/2010 2:39:09 PM
NO RATINGS
Verification methodologies used in the hardware world like executable, metric-driven verification plans, functional coverage and constrained-random test generation are now available for software validation and test. Cadence Design Systems offer a product called ISX http://www.cadence.com/products/sd/isx/pages/default.aspx that is indeed very usefu finding bugs where hardware meets software. If anyone is interested in finding out more, visit one of the conferences embedded world http://www.embedded-world.eu/program/day-1.html?program_id=2126 in Nuremberg or CDNLive http://www.cadence.com/cdnlive/eu/2010/pages/default.aspx in Munich, Germany. Or contact me directly at markus@cadence.com

JakeClarke
User Rank
Author
re: Verifying the border line between auto hardware, software
JakeClarke   2/17/2010 12:28:57 AM
NO RATINGS
Interestingly, Audi was plagued with both throttle and brake problems about 25 years ago. It was never concluded publicly, but when the throttle is wide open, the brakes have NO vacuum assist. I'm not sure if this is true in the case of Toyota, but it may be worth looking into.

Joe Fox
User Rank
Author
re: Verifying the border line between auto hardware, software
Joe Fox   2/16/2010 6:37:15 PM
NO RATINGS
This is no different then the requirements we've had in aircraft avionics for thirty years. It's easy to build a product that has multiple standalone system (propulsion, electrical power, radios, engine control, etc). It's much more difficult when those systems are integrated with common controllers and busses. As the automotive industry pursues increased levels of integration, they are going to have to adopt the tectniques of the aerospace industry w.r.t. tiered integrtaion labs, real requirements verification, multiple system integration lines, etc. They are also going to have to be much more diligent in the development, verification, AND maintenance of appropriate interface documentation. It's not cheap, but it is required to manage the inherent complexity of deeply integrated electromechanical systems.

TiMan
User Rank
Author
re: Verifying the border line between auto hardware, software
TiMan   2/16/2010 6:27:01 PM
NO RATINGS
More than just software-- manufacturers must maintain long-term relationships with suppliers (per W.E. Deming), or bad things happen. This is why outsourcing to china and elsewhere scares me so much.

Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed