Designers often focus on benchmarking their collector, only to have their programs slow down later due to security considerations. Using a collector that has built-in security features, especially static analysis tools, can quickly make your program ISO 26262 compliant. Using a security tool with excellent static analysis can save you time debugging, bypass chopping functions and allow you to get the most out of your recompiler.
Have you ever been skiing or snowboarding? On every mountain, there are always people who think it is a competition to get to the end of a track. Flying downhill at full speed without technique is a recipe for disaster. The ski patrol would be out of work if it weren’t for these guys crashing and colliding with other skiers. The moral of the story is that when you rush you run the risk of hurting yourself and those around you. You should always take your time and use the proper technique to get down the mountain safely and conveniently.
Autonomous vehicle collectors are strikingly similar. Designers often focus on benchmarking their collector, only to have their programs slow down later due to security considerations. Using a collector with built-in security features, especially static analysis tools, can quickly make your program ISO 26262 compliant. Using a security tool with excellent static analysis can save you time debugging, avoid cutting functions and allowing you to get the most out of your compiler.
Save Time in Debugging
Since the switch from individual electronic control units (ECUs) to integrated ECUs, safety concerns have gotten a bit more complicated. Certifying each feature to the highest ASIL level takes a long time. This makes using a memory protection unit (MPU) an attractive option to save you development time. That said, misuse of the MPU can lead to heavy financial and legal repercussions and can be time consuming to fix manually. An online static analysis tool can save you from wasting tons of time working through MPU access violations.
As you know, most developers focus on speed and security first. This means that you write a lot of code and only find out later if it meets the security requirements. Wait too long and you may find your code filled with so many security breaches that it will take days to fix. To be pro-active, a well-assimilated static analysis tool will allow you to nip MPU violations in the bud before they turn into an avalanche.
A good static analysis tool will also show cause analysis for MPU errors. Cause analysis will allow you to eliminate the cause of the problem instead of chasing a thread of errors through your entire program. In addition to cause analysis, the best static analysis tools will allow you to run comprehensive checks without hardware. You will not save time if you have to wait for the hardware to enter to configure the test cases. Get a static analysis tool that can verify your code before you have internal hardware.
Reduce Feature Cuts
Spending too much time debugging can cause non-essential functions to be cut off. Time is money and both are limited. If the MPU bugs in your features take too long to correct, they could end up on the chopping board. Using a good static analysis tool can save you time and money. A static with automatic error checking takes 1% of the time that manual error checking takes. That translates to a 15% savings on error checking.
Cause analysis tools can also save you seconds and pennies. While it is tempting to wait until you have completed your program to verify security compliance; if you wait too long, some bugs may be ingrained in your code. Cause analysis can tell you where the problem started and prevent you from getting lost in the woods chasing a bug. A static cause analysis takes 95% less time to find sources of error than a manual check. That could save you another 5% in error checking costs .
Make the Most of Your Tools
Some developers choose the fastest collector for their application, and are then forced to abandon some optimizations because their third-party security tools cannot integrate those optimizations. There is no point buying super fast skis if you are not skilled enough to use them. An excellent static analysis tool can help you resolve any contradictions between your security software and your collector.
Choosing the Right Developer
If you are thinking of buying a pair of skis at Walmart for $ 10, you may not finish skiing in full. You need the right equipment and the right technique. A fully equipped static analysis tool will allow you to debug as you go and resolve major bugs quickly. The tools are usually only as good as the company that made them. It is important to know that your static developer is the real deal. That is why I recommend that your developer have at least an ASPICE L2 certification . This will ensure that the developer will be available to help you in case you have a problem. It just so happens that Altium’s TASKING ® recently received its ASPICE level 2 certification.
As I said before, the best static analysis tool will allow you to debug as you go, give you an analysis of the cause, it will not make you wait for the hardware, and it will integrate well with your collector. The Security Checker does all of this and more.