RELATED APPLICATION

This application claims priority to commonly owned United States Patent Application No. 63/329,117 filed April 8, 2022, the entire contents of which are hereby incorporated by reference for all purposes TECHNICAL FIELD

The present disclosure relates to systems and methods for selecting electrical components and designing functional blocks that form a total system-level solution with crossfunctional -block dependency tracking and constraint management.

BACKGROUND

Semiconductor, microchip, and microprocessor suppliers and manufacturers have software tools that enable users to select individual components having specific performance characteristics and design parameters. Component identification tools are available that provide information about components (e.g., schematics, data sheets, or software, without limitation) given specific design parameters. However, customers need further tools to identify components for complete system solutions formed with the components for particular applications. Further, a customer’ s specific design parameters rarely match 100% with template designs for complete system architectures or complete system solutions.

Many engineers lack the experience or expertise to design all of the various functions that are involved in a system solution. To aid this, many semiconductor vendors provide reference designs that can be dropped into their customer’s application or design tools that guide them on designing a specific block. Reference designs are a good starting point, but they nearly always require some amount of modification for the customer’s specific needs. Reference designs are the classic approach to providing customers with a “known good” system solution. The issue is that these are static and not easily modified without manual checking of cross-block dependencies. An example is adding additional functional blocks to an existing reference design that cause a particular supply rail to be overloaded.

Design tools are also often provided to help the customer design a specific block. However, the block is tackled by the design tools independently of the rest of the blocks in the system architecture or complete system solution. The user must know what all of the inherited constraints are in the system and track the dependencies across blocks. This can lead to bad component/circuit choices when integrated into a full system, leading to iterative cycles of physical board debugging and redesign.

There is a need for a selection and diagnostic tool to configure system-level electrical designs made up of electrical components that satisfy design parameters and have corresponding dependencies.

SUMMARY

A system-level design generator tool enables users to configure system-level designs made up of components that satisfy design parameters and have corresponding dependencies. At the top level, this may be a block diagram representing each of the functions within the system. Each block may utilize a guided parametric search or a design tool to create the solution for that individual block. The inputs into the guided parametric search and/or design tool may come from the system-level choices, constraints, and cross-block dependencies tracked by the system generator tool. This process may start from a template diagram or a blank diagram. A template diagram contains components in a particular configuration and provides a starting point from which modifications to the diagram may be made. A blank diagram contains no components and provides a clean starting point into which components may be added and modified. When a new component block is added to a system configuration, a system generator tool that tracks cross-block dependencies may recognize the additional load placed upon the specific supply rail and flag it as needing attention. The user may then visit the design tool for component block to pick a new solution for that rail that is more appropriate for the current requirements.

According to one aspect, there is provided an apparatus to configure system-level designs made up of electrical components that satisfy design parameters and have corresponding dependencies, comprising a non-transitory, machine-readable medium including instructions wherein the instructions, when loaded and executed by a processor, configure the processor to: present a system diagram of an electronic system having component blocks representing electrical components; receive constraints or parameters for each electrical component represented by the component blocks; present a list of candidate components corresponding to the constraints or parameters for each electrical component represented by the component blocks; receive an instruction to select a component from the list candidate components for each electrical component represented by the component blocks; and check system dependencies to confirm compatibility of all electrical components selected for inclusion in the system diagram.

Another aspect provides a machine-implemented method to configure system-level designs made up of electrical components that satisfy design parameters and have corresponding dependencies, comprising: presenting a system diagram having component blocks; receiving constraint or parameters for the components of the component blocks; presenting a list of components corresponding to the constraints or parameters; receiving an instruction to select a components from the list; and checking system dependencies to confirm compatibility of all components in the system diagram.

According to another aspect, there is provided a system having: a presentation circuit that presents a system diagram of an electronic system having component blocks representing electrical components; a constraint or parameter input circuit that receives constraint or parameter inputs for each electrical component represented by the component blocks; a component circuit that presents a list of candidate components corresponding to the constraints or parameters for each electrical component represented by the component blocks; a component selection circuit that receives an instruction to select a component from the list candidate components for each electrical component represented by the component blocks; and a system dependency circuit that checks system dependencies to confirm compatibility of all electrical components selected for inclusion in the system diagram.

DESCRIPTION OF THE DRAWINGS

The figures illustrate example methods and systems for a system-level design generator tool that enables users to configure system-level designs made up of components that satisfy design parameters and have corresponding dependencies.

FIGURE 1 illustrates an example system-level design generator tool based on tools for selecting individual components of the system.

FIGURE 2 illustrates, relative to a system generator tool for creating a new electrical control system, an example screen shot of a search screen for finding a template related to a user’s application.

FIGURE 3 illustrates a screen shot of an example template.

FIGURE 4 illustrates an example window to modify the System Interface block.

FIGURE 5 illustrates an example of the component block template of FIGURE 3, which illustrates how the system generator tool performs dependency checks between the component blocks after a component block has been modified via a configuration screen as shown in FIGURE 4.

FIGURE 6 illustrates an example screen for adding component blocks to those already in the system being generated.

FIGURE 7 illustrates an example of the system generated screen of FIGURE 5, where two additional component blocks have been added to the system.

FIGURE 8 illustrates an example of the system generated screen of FIGURE 7, where the two new component blocks have been configured by the user and cross-dependency checks have been performed.

FIGURE 9 illustrates an example screen for updating the Power Management component.

FIGURE 10 illustrates an example screen for viewing rail details, including the connections and inherited constraints.

FIGURE 11 illustrates an example screen for viewing inputs and outputs of the PSI sub-block of the Power Management component block.

FIGURE 12 illustrates an example window for updating the rail generation for component blocks or sub-blocks.

FIGURE 13 illustrates an example of how users may share and export design files from the system generator tool window.

FIGURE 14 illustrates an example flow chart of a process for generating an electronic system comprised of semiconductor and other components.

FIGURE 15 illustrates an example schematic diagram of a system generator tool.

The reference number for any illustrated element that appears in multiple different figures has the same meaning across the multiple figures, and the mention or discussion herein of any illustrated element in the context of any particular figure also applies to each other figure, if any, in which that same illustrated element is shown.

DETAILED DESCRIPTION

According to examples provided, a system generator tool may guide engineers in choosing system elements and checking cross-block dependencies and cross-function dependencies, provide a working solution for engineers, for example, add a power supply for non-power engineers, and provide an initial starting point for engineers. The system generator tool may be a software tool that helps customers select parts represented by component blocks and design functional capabilities that work together to form a system solution. The tool may check cross-block and cross-function dependencies and make component recommendations. An engineer may start from a template diagram (reference design) and customize the template diagram to add/remove component blocks, and change functional capabilities of component blocks, such as power, bandwidth, and noise. While power, bandwidth, and noise are illustrated, any parameter or functional capability of component blocks may be checked. Alternatively, an engineer may start from a blank diagram.

The system generator tool may help mass market customers select the right semiconductor parts, components, or products for their specific electronics application and design the parts, components, or products into a total system solution. A feature of the system generator tool is its ability to track system level constraints and dependencies, which provides a solution for the customer’s needs, not a static reference design or merely a bucket of parts, components, or products that may or may not work together. The system generator tool helps reduce the chance of gross errors in a new system design. It also helps speed up such designs or modifications of reference designs allowing customers to get their designs to market in fewer iterations of the hardware.

The system generator tool may provide product selection and design guidance for total system solutions to mass market customers. The system generator tool may guide engineers in choosing system elements and checking dependencies. The system generator tool may provide a working solution for engineers, for example, by recommending a power supply for non-power engineers. The system generator tool may provide an initial starting point for engineers, for example by allowing them to work from a template and then customize as needed. The system generator tool may minimize system-level inconsistencies that lead to early prototype failure. The system generator tool may track cross-block and cross-function dependencies so that dependencies are tracked and applied across all the component functional blocks of the entire system.

The system generator tool may be a web-based interface so that users may access the tool via the internet from any remote terminal. The system generator tool may be provided via a website, but it could also be built in a stand-alone, downloadable form. The system generator tool may be an application (App) installed on a computer work station or a device or a web based application accessed from the internet via a computer work station or device. A value of the online version of the system generator tool application may be that it always reflects the most recent updates in design tools, part selection, or inherited dependencies/constraints.

FIGURE 1 is an example system generator tool illustrating building blocks including: system interface, Ethernet, digital control, security, power management, clock, and memory. Individual systems for identifying microchips and other components for individual component blocks may be incorporated into the system generator tool. For example, such individual systems may include: MPLAB Analog Designer, available from Microchip Technology, Inc., of Chandler Arizona, Clockworks Configurator available from Microchip Technology, Inc., of Chandler Arizona, FilterLab, and Guided Parametric Search, which are example software programs capable of identifying and configuring electronic parts, components, or products. The system generator tool may control the individual systems to build or design total systems comprising microchips and other components. The system generator tool may incorporate already available software for selecting individual components into a software tool that provides a total system solution.

FIGURE 2 illustrates an example screen shot of a system generator tool for creating a new electrical control system. A customer may use a customer account to log into the webbased interface of the system. A historical listing of systems or projects by the user may be listed under a My Systems catalog. An icon link to development tools or reference design pages may be provided. A list of templates may be provided wherein the name of each template of the list of templates is a respective hyperlink to launch a template upon which the user may click to generate a new system. Alternatively, the user may start from a blank diagram, rather than a template. Templates may include system level templates such as: smart thermostats, BLE-controlled aquarium light, robotic vacuum cleaner, air conditioner compressor motor driver, and Bluetooth LED lamp.

FIGURE 3 illustrates an example screen shot of a template, wherein in this case, it is a template for a wired point-of-sale terminal. Users can modify the name of a “local” copy of the system from the original template. This template provides for system components represented by blocks including: system interface, Ethernet, digital control, security, power management, clock, and memory. Each system component is represented by a component block and interface connections are drawn between the component blocks. A grey circle with a plus sign illustrates an icon for adding more component blocks to the system. Icons may indicate the status of each block, wherein a green circle with a check mark may indicate the status is GOOD and a yellow triangle with an exclamation point may indicate the status of the component block is NEEDS ATTENTION. If the status is NEEDS ATTENTION, the components identified or the selected parameters of an identified component may not be correct to satisfy cross-block and crossfunction dependencies. Parameters may include power, bandwidth, and noise. FIGURE 4 illustrates an example of a window to modify the System Interface block. The System Interface block itself is a hyperlink icon (see FIGURE 3) that allows a user to navigate to the System Interface configuration screen shown in FIGURE 4. The System Interface may have input supplies and digital interface characteristics. For the input supplies, a rail name of VinPoE is listed having 37 volt minimum, 57 volt maximum, and the standard is 802.3af. For the digital interfaces, an Ethernet 1 is listed, which is a type of Ethernet having parameters of 1000BASE- T. Users may modify the initial system interface template to match their application, such as changing the input supplies from VinPoE to a local 12 V supply.

FIGURE 5 illustrate and example of the component block template of FIGURE 3, which illustrates how the system generator tool performs dependency checks between the component blocks after a component block has been modified via a configuration screen as shown in FIGURE 4. Each of the blocks having a green circle with a check mark indicates the status of all dependencies between the components is GOOD. Note that in FIGURE 3, the System Interface block has a yellow triangle with an exclamation point, which indicates the status of the block is NEEDS ATTENTION. After the System Interface has been changed via the configuration screen shown in FIGURE 4, the status of the System Interface block has changed to a green circle with a check mark indicating the status of all dependencies of the System Interface are GOOD, as shown in FIGURE 5. However, because the System Interface block was reconfigured (FIGURE 4), the Power Management block status is now indicated as NEEDS ATTENTION, as shown in FIGURE 5. This may indicate the power management parameters are not correct to supply a proper level of power, i.e., the power dependency between the component blocks is not compatible or a better solution may be available as a result of the change of the system input voltage. Typically, incompatible dependencies exist between more than two component blocks. Before selecting a new component for power management, a determination may be made as to whether, or not, all component blocks have been added. If not, additional component blocks may be added before updating the power management block. A grey circle with a plus sign illustrates an icon for adding more component blocks to the system. FIGURE 6 illustrates an example screen for adding blocks, representing additional components, to those already in the system being generated. A search feature allows the user to search for component blocks. Also, search filters may be implemented to narrow the field of component blocks. A list of component blocks may be provided as searched and filtered results. Component blocks may be added to the system being generated by selecting the green plus icon adjacent to the component description. After selecting all desired component blocks, the user may navigate back to the system generator tool screen.

FIGURE 7 illustrates an example of the system generated screen of FIGURE 5, where two additional new component blocks have been added to the system: OLED Display and Temp Sense. Added component blocks OLED Display and Temp Sense need review to select interfaces and specific solutions. With the added component blocks integrated into the system being generated, the system generator tool again performs dependency checks between the component blocks. For example, blocks having a respective green circle with a check mark indicates the status of all dependencies between the components is GOOD. In this case, all component blocks are indicated as GOOD, except for the newly added component blocks (OLED Display and Temp Sense) and the Power Management block, which have a yellow triangle with an exclamation point indicating the status of the block is NEEDS ATTENTION. The user may select the OLED Display and the Temp Sense component blocks to navigate to block modification screens to identify more compatible components, i.e., components where the cross-block dependencies and cross-function dependencies may check out as GOOD. See FIGURE 4. For example, the OLED Display shown in FIGURE 7 may be replaced with an LCD as shown in FIGURE 8.

FIGURE 8 illustrates an example of the system generated screen of FIGURE 7, where the two component blocks have been replaced or reconfigured: LCD and Temp Sense. With the replaced or reconfigured component blocks integrated into the system being generated, the system generator tool again performs dependency checks between the component blocks. The blocks having a respective green circle with a check mark indicates the status of all dependencies between the components is GOOD. In this case, all component blocks are GOOD, except for the Power Management block, which has a yellow triangle with an exclamation point indicating the status of the block is NEEDS ATTENTION. Because the Power Management component provides power to all the other components, it may be more efficient to configure this component after the other components have been identified. The user may navigate to a screen for updating the Power Management block by selecting the Power Management block.

FIGURE 9 illustrates an example screen for updating the Power Management component. In this case, the power input is Vinl2V and the power outputs include: VddlO, VddCore, and VddAna. By hovering over the respective input and output blocks, the user may see summaries or select to see details. A summary of the VddCore block shows it is 1.2 V @ 50 mA. The sub-blocks PS2 and PS3, which provide power for VddCore and VddAna respectively, are indicated with a GOOD status by the green circle with a check mark. However, the sub-block for PSI indicates the status of the block is NEEDS ATTENTION. The user may select the respective sub-blocks to change the input source or override automatic parameters, such as load estimates. This may also be the interface to the MPLAB Analog Designer (MAD), which allows the user to select a specific solution for this sub-block. After updating the subblocks of the Power Management component block, the user may navigate back to the system generator tool system-level screen. The user may also view the rail details by clicking on the lines between the sub-blocks or component blocks.

FIGURE 10 illustrates an example screen for viewing rail details, including the connections to the rail and inherited constraints. In this case, the VddAna rail details are shown. Blocks connected to this rail provide respective requirements, such as load estimates and constraints. The constraints may be broad constraint classes such as restricting to low-dropout regulators, or specific performance criteria, such as tolerances and noise. The digital control of the VddAna sub-block has 1.62 Min (V), 3.63 Max (V), 4mA Load, and no constraints. The temp sense of the VddAna sub-block has 2.3 Min (V), 5.5 Max (V), 0.015 mA Load, and low noise constraints. The user may close the rail detail window to navigate back to the system generator tool system-level screen.

FIGURE 11 illustrates an example screen for viewing inputs and outputs of the PSI sub-block of the Power Management component block. See FIGURE 9. In this case, the user may select the link for the component to view/edit the selection, or select a different component. The Inputs include Vin and En block signals which are both mapped to the system net Vinl2V. The user may select these parameters to map them to other system-level signals. The Output is a Vout block signal where the system net is VddlO. The user may select the output rails to view/edit the detailed parameters, as illustrated in FIGURE 10. The user may close the input/output detail window to navigate back to the system generator tool screen. FIGURE 12 illustrates an example window for updating the rail generation for component blocks or sub-blocks. This window updates sub-block PSI of the Power Management component block shown in FIGURE 9. The rail generation window allows the user to view or alter design parameters and filters, prepopulated by the PSI sub-block constraints, for querying the MPLAB Analog Designer (MAD) to identify component blocks and sub-blocks that satisfy the needed design parameters. In particular, the MPLAB Analog Designer (MAD) may provide a list of recommendations (solution selection step) from which a user may select a specific solution to start a design generation phase, also utilizing MAD. When the user selects the specific power sub-blocks, the system generator tool may make calls to the solution database, for example implemented in MAD. The user may select appropriate components that meet the design parameters and navigate back to the system generation window. The system generator tool again performs dependency checks between the component blocks. Component blocks having a respective green circle with a check mark indicates the status of all dependencies between the components is GOOD.

FIGURE 13 illustrates an example of how users may share and export design files from the system generator tool. Once the system generator tool has generated the system design, the system design can be shared with colleagues and/or downloaded. Downloads may include a block diagram, schematics, simulation files, a bill of materials, or software/firmware libraries, a printed circuit board layout, and software, without limitation.

FIGURE 14 illustrates an example flow chart of a process for generating a system comprised of semiconductors and other components. The algorithm starts and prompts the user to select 10 a new system. The new system may be selected from a template diagram or a blank diagram. If a blank diagram is selected, the user builds 20 the system by adding component blocks. The user is then prompted to select 40 individual components for each of the component blocks in the system. The system receives 42 component constraints and parameters to configure an individual component block. The system generator tool then presents 44 a list of component candidates from the database of components. The system receives user selections 46 of a component from the list or the system generator tool selects the component from the list. The subroutine 40, 42, 44, 46 for selecting individual components is repeated for each component block in the system diagram. After all the individual components in the system diagram have been selected, the system generator tool checks 50 for system constraints and dependencies and indicates to the user whether each block is GOOD or NEEDS ATTENTION. The user may then modify 60 a block by returning to the subroutine 40, 42, 44, 46 for selecting individual components. The user may also add or remove 70 component blocks from the system diagram by returning to the subroutine 40, 42, 44, 46 for selecting individual components. If no blocks are to be modified and no blocks are to be added or removed, the system generator tool allows the user to output 80 system diagrams, schematics, and bills of materials.

FIGURE 15 illustrates an example schematic diagram of a system generator tool 150 having a processor 151 and a non-transitory machine readable medium 152. The system generator tool 150 also has a system diagram presentation circuit 153 presenting a system diagram of an electronic system having component blocks representing electrical components , a constraints or parameters input circuit 154 receiving constraints or parameters for each electrical component represented by the component blocks, a candidate component presentation circuit 155 presenting a list of candidate components corresponding to the constraints or parameters for each electrical component represented by the component blocks, a component selection circuit 156 receiving an instruction to select a component from the list candidate components for each electrical component represented by the component blocks, and a check system dependencies circuit 157 checking system dependencies all electrical components selected for inclusion in the system diagram. System generator tool 150, system diagram presentation circuit 153, constraints or parameters input circuit 154, candidate component presentation circuit 155, component selection circuit 156, and check system dependencies circuit 157 may be implemented by instructions for execution by processor 151, analog circuitry, digital circuitry, control logic, digital logic circuits programmed through hardware description language, application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), programmable logic devices (PLD), or any suitable combination thereof, whether in a unitary device or spread over several devices. System generator tool 150, system diagram presentation circuit 153, constraints or parameters input circuit 154, candidate component presentation circuit 155, component selection circuit 156, and check system dependencies circuit 157 may be implemented by instructions for execution by processor 151 through, for example, a function, application programming interface (API) call, script, program, compiled code, interpreted code, binary, executable, executable file, firmware, object file, container, assembly code, or object. For example, system generator tool 150, system diagram presentation circuit 153, constraints or parameters input circuit 154, candidate component presentation circuit 155, component selection circuit 156, and check system dependencies circuit 157 may be implemented by instructions stored in the non- transitory medium 152 such as a memory that, when loaded and executed by the processor 151 such as CPU (or any other suitable processor), cause the functionality of system generator tool 150, system diagram presentation circuit 153, constraints or parameters input circuit 154, candidate component presentation circuit 155, component selection circuit 156, and check system dependencies circuit 157 described herein.

In particular examples, the system tool may call other tools via APIs, wherein the system may be a network of processors that perform the tasks.

Although examples have been described above, other variations and examples may be made from this disclosure without departing from the spirit and scope of these disclosed examples.