Analysis of Aurix Microcontroller Configuration and Resource-Sharing

Abstract

The temptation to work more swiftly develops because every breakthrough in this cutting-edge era occurs too quickly. Verification and validation engineers encounter a number of problems with erroneous configuration and recurrent global resource sharing in the development of microcontrollers and expend a lot of time and effort troubleshooting them. This superfluous debugging and effort can be avoided by a sound feedback mechanism that offers a full overview of the microcontroller configuration and decides whether configuration and resource sharing are shared by many peripherals. Utilizing the same port pin for many IPs, giving different interrupts the same priority, incorrectly configuring an IP to receive a different clock frequency, or using the same memory address for multiple data buffers are a few problems. Due to the setup issues, the application will have faults that are difficult to fix and take a lot of effort to troubleshoot. If the application is big and uses numerous IP addresses, it would be difficult to identify such configuration problems by going through it. It is exceedingly difficult if the application code is not provided. To avoid such situations, there should be a smarter way to deal with them. Engineers are forced to concentrate on the application’s actual results by avoiding needless debugging caused by configuration errors. In order to detect configuration errors even when the source code is unavailable, such a method should also be capable of doing so while the application is executing on the hardware.