Fault detection in parallel hardware
Through the software-based test library, the parallel hardware components are comprehensively diagnosed and tested, and faults are identified and responded to faults, which solves the shortcomings of parallel processor fault detection in the existing technology, and achieves efficient and low-cost fault detection and response capabilities, satisfying the Detection frequency requirements for safety-critical applications.
Patent Information
- Application Number
- CN202410671519.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-30
- Filing Date
- 2024-05-28
- Publication Date
- 2024-12-03
AI Technical Summary
The prior art is difficult to effectively detect and respond to failures in parallel hardware, especially in safety-critical applications. Conventional methods such as bit parity and error correction codes are not suitable for fault detection of parallel processors, and the redundant system is costly. And it is difficult to meet the detection frequency requirements such as in the ISO 26262 standard.
Using a software-based test library, the test mode is generated to cover all operations and data paths of hardware components by performing diagnostic tests of various hardware components multiple times, including integer and floating point operations, matrix multiplication, bit operations, etc., and through the results Comparison and hash functions identify potential faults, perform correction or failover operations in response to detected faults.
It realizes efficient fault detection and response to parallel hardware components, meets the detection frequency requirements of safety-critical applications, reduces the cost of redundant systems, and improves the accuracy and reliability of hardware fault detection.
Smart Images

Figure CN119065876A_ABST
Abstract
Description
Background Art
[0001] Computing hardware is susceptible to faults or component failures that may affect the hardware's ability to accurately process data. In some cases, hardware faults may be permanent, such as a logic element that is permanently fixed at a particular value (e.g., 0 or 1). Hardware faults, when persistently undetected, may result in corrupted or otherwise incorrect data for operations, applications, or other software running using the hardware element, which in safety-critical contexts (such as autonomous machines, robots, and / or data centers) may result in high-risk situations and / or conditions.
[0002] Typically in safety-critical applications, fault detection strategies are implemented to detect hardware faults when they occur. In some cases, fault detection testing must be performed periodically to comply with one or more standards and / or regulations. For example, the International Organization for Standardization ("ISO") Standard No. 26262, entitled "Road Vehicles—Functional Safety" ("ISO 26262"), specifies that 90% of faults in automotive components are to be detected to meet Automotive Safety Integrity Level B (ASIL-B). Such testing can be scheduled and then performed at a frequency that meets a Fault Tolerant Time Interval ("FTTI") or other intervals that allow corrective, preventive, and / or other safety actions to be performed in the event of a critical hardware fault being detected.
[0003] There are many challenges in hardware fault detection. Some conventional methods use technologies such as bit parity or error correction code ("ECC"). These methods can detect faults in memory cells, but may not be suitable for identifying faults in other hardware components. Generally, conventional strategies rely on mechanisms that are integrated with the hardware being tested. For example, built-in self-test ("BIST") is used to detect manufacturing defects, but has been reapplied to detect faults in the system. However, these tests may not be suitable for detecting errors during runtime within the detection interval (such as FTTI) required by safety regulations and / or to respond to faults. Some other technologies that can be used to identify hardware faults rely on the redundant execution of operations by hardware components. However, truly redundant systems have significant additional costs because at least twice the hardware components are required to provide redundancy. Further, many of these conventional technologies focus on fault detection in processors (such as CPUs) that are executed serially, but these technologies are not suitable for parallel processors with many dedicated hardware components (such as GPUs and other acceleration hardware). BRIEF DESCRIPTION OF THE DRAWINGS
[0004] The present system and method for fault detection in parallel hardware are described in detail below with reference to the accompanying drawings, in which:
[0005] Figure 1is a block diagram illustrating an example hardware fault detection system according to some embodiments of the present disclosure;
[0006] Figure 2 is a block diagram illustrating a method of hardware fault detection according to some embodiments of the present disclosure;
[0007] Figure 3 is an example processor according to some embodiments of the present disclosure;
[0008] Figure 4 is a schematic diagram illustrating example test mode allocation according to some embodiments of the present disclosure;
[0009] Figure 5 is a schematic diagram illustrating example operational test mode allocations according to some embodiments of the present disclosure;
[0010] Figure 6 is a flow chart illustrating a method for performing hardware fault detection according to some embodiments of the present disclosure;
[0011] Fig. 7A is an illustration of an example autonomous vehicle according to some embodiments of the present disclosure;
[0012] Figure 7B According to some embodiments of the present disclosure, Fig. 7A Examples of autonomous vehicle camera positions and fields of view;
[0013] Figure 7C According to some embodiments of the present disclosure, Fig. 7A a block diagram of an example system architecture for an example autonomous vehicle;
[0014] Fig.7D According to some embodiments of the present disclosure Fig. 7A A system diagram of communications between a cloud-based server and an example autonomous vehicle; and
[0015] Figure 8 is a block diagram of an example computing device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION
[0016] In the following description, numerous specific details are set forth in order to provide a more thorough understanding of at least one embodiment. However, it will be apparent to one skilled in the art that the inventive concept may be practiced without one or more of these specific details.
[0017] Disclosed are systems and methods related to fault detection in parallel hardware. For example, such systems and / or methods may use fault detection diagnostic techniques that use a library of software-based tests to thoroughly and / or efficiently test hardware components (such as components used by a GPU) to detect and / or identify one or more permanent hardware faults within one or more hardware components. The disclosed diagnostic techniques may perform one or more diagnostic tests that test various hardware components (such as memory, computing units, tensor cores, processors, and / or logic units). Each hardware component and the connection and / or data path associated therewith may be tested according to a test frequency. The test frequency may be selected and / or configured so that each hardware component is tested at least once per cycle according to a test frequency (such as FTTI). Diagnostic tests may be scheduled and other operations. For example, diagnostic tests may be scheduled so that they are performed together with other operations, such as operations associated with autonomous or semi-autonomous machines and / or other actively running systems. In one example, an autonomous or semi-autonomous machine may devote 10% of its operating time and / or resources to performing one or more diagnostic tests on a hardware component, while the remaining 90% may be reserved for performing ongoing processes unrelated to the diagnostic tests.
[0018] Diagnostic testing includes multiple tests performed on various components. For example, diagnostic testing may include, but is not limited to, one or more of the following:
[0019] 1. Testing of integer point and / or floating point addition, multiplication, dot product and accumulation, min / max, compare and set, predicates, logical operations, shift operations, integer to floating point conversions, and packed vector operations for various integer and floating point representations including, but not limited to: UINT32, INT32, INT8, UINT8, INT4, FP64, FP16, FP8, BF16, and / or TF32;
[0020] 2. Tests for matrix multiplication operations used to diagnose the Tensor Core data path;
[0021] 3. Test of bit operations;
[0022] 4. Testing of atomic operations on shared memory and global memory for integer and / or floating point operations;
[0023] 5. Testing of unified datapath integer and / or floating-point arithmetic and logic operations;
[0024] 6. Tests on L1 and L2 data / instruction caches;
[0025] 7. Testing of the memory management unit, including the translation lookaside buffer ("TLB"), for various addressing modes;
[0026] 8. Testing of various intermediate first-in-first-out ("FIFO") memories, data structures and / or buffers;
[0027] 9. Testing for loading and / or storing from global memory with different operand sizes;
[0028] 10. Tests for loading and / or storing from local storage;
[0029] 11. Test for asynchronous global to shared memory load;
[0030] 12. Tests for constant cache diagnostics via strided accesses to read operations;
[0031] 13. Testing for misaligned L1 / L2 cache accesses and / or buffer misses;
[0032] 14. Testing of operation after cache compression; and / or
[0033] 15. Test of data transmission between hardware and host device.
[0034] In some embodiments, hardware diagnostic tests may be performed using an application programming interface ("API") and / or instructions for scheduling individual tests between hardware components. When the API is called, a test pattern specific to a particular hardware may be accessed from one or more libraries and / or other storage devices. In some examples, the test pattern may be algorithmically defined so that the test pattern may be generated to cover each possible operation, subcomponent, and / or data value for a particular hardware component. The test pattern may be algorithmically generated to provide a general coverage and / or pseudo-random input pattern to the hardware component so that these test patterns provide complete coverage of hardware components and functions. For example, a test pattern designed for one or more processors may include one or more computational functions (e.g., for performing matrix operations) initiated on the processor, wherein the computational function targets each computational thread of the processor in addition to each associated data path, register, shared memory address, and local memory address. In such an example, a function may be called to cause a block of threads to be executed concurrently on each processor by occupying each execution path within the processor. In some examples, the test pattern is based on the characteristics of a particular component (e.g., tensor core, cache, adder, etc.) being tested. For example, a test pattern may be generated to test each memory cell in a memory component of a processor, such as an L1 cache and / or an L2 cache.
[0035] Performing diagnostic tests using a test pattern may include providing one or more input values to one or more hardware components, obtaining one or more output values, and comparing the one or more output values with one or more expected values associated with the test pattern. For example, a test of a read / write operation to a memory may attempt to write an input value to a specific memory address, then read the value stored at the address as an output value, and compare the output value with an expected value (e.g., input value) associated with a test pattern (e.g., a read / write operation) to obtain a comparison result value. As another example, a matrix multiplication operation may be tested by providing one or more input matrices to one or more tensor cores that can output one or more result matrices, and comparing the one or more output matrices with one or more expected matrices associated with a test pattern (e.g., a matrix multiplication operation) to obtain a comparison result value. In some examples, before performing the comparison, a hash function may be applied to the result value generated by the output or in response to the test pattern to generate a result hash value. The result hash value may be compared with the expected hash value associated with the test pattern to determine whether the tested component exhibits correct operation. For example, if the resulting hash value is equal to the expected hash value, then the corresponding component can be identified as operating correctly. On the other hand, if the resulting hash value does not match the expected hash value, then the corresponding component can be identified as operating incorrectly and / or exhibiting a potential failure. In some examples, if a failure is detected (e.g., by failure of one or more diagnostic tests), an indication indicating the potential failure and / or other information associated with the corresponding hardware component can be provided.
[0036] In some embodiments, in response to identifying one or more hardware failures, one or more actions may be performed. For example, in response to detecting and / or identifying one or more hardware failures, the autonomous machine may use one or more control components to perform mitigation operations, such as fail-safe and / or other safety operations. As another example, in response to identifying one or more hardware components exhibiting a potential failure, the data center may perform one or more failover operations.
[0037] refer to Figure 1 , Figure 11 is a block diagram illustrating an example hardware fault detection system 100 ("system 100") according to some embodiments of the present disclosure. It should be understood that this and other arrangements described herein are set forth as examples only. In addition to or in place of the arrangements and elements shown, other arrangements and elements (e.g., machines, interfaces, functions, orders, functional groupings, etc.) may be used, and some elements may be omitted entirely. Further, many of the elements described herein are functional entities that may be implemented as discrete or distributed components or in combination with other components, and in any suitable combination and position. The various functions described herein as being performed by an entity may be performed by hardware, firmware, and / or software. For example, the various functions may be implemented by a processor that executes instructions stored in a memory.
[0038] System 100 may include client device 102, one or more networks 108, and / or one or more processors 104. One or more processors 104 may include and / or be connected to one or more hardware components 106. Client device 102 may include fault detection application 110, fault manager 132, storage device 140, one or more processors 150, and / or one or more control components 160.
[0039] The components of system 100 may be configured to communicate over one or more networks, such as network 108, and / or other network types described herein. One or more networks 108 may include one or more networks of any number of network types. In some examples, one or more networks 108 include one or more data bus protocols and / or topologies (e.g., controller area network (“CAN”), FlexRay, Ethernet, etc.). One or more components of system 100 may be configured to use one or more network interfaces to connect one or more components of system 100 through one or more networks 108. Client device 102 may include one or more components for performing one or more operations associated with an autonomous or semi-autonomous machine (e.g., fault detection, safety confirmation, etc.). For example, client device 102 may include one or more components for performing one or more diagnostic tests of hardware component 106, one or more components for performing calculations (e.g., using one or more processors 104), and / or one or more components for making predictions corresponding to an autonomous machine. As an example, the client device 102 may generate and execute one or more diagnostic tests, such as tests to be used to verify or otherwise acquire the performance and / or functionality of one or more hardware components of an autonomous machine, semi-autonomous machine, and / or other hardware device.
[0040] Processor 104 may include one or more components for processing data associated with one or more autonomous or semi-autonomous machine operations. In some embodiments, one or more processors 104 may provide additional and / or alternative processing to processing performed by client device 102. In some examples, processor 104 may perform processing associated with system 100. For example, one or more processors 104 may be configured to process measurement data from one or more inertial measurement unit sensors and / or other sensors (such as LiDAR and cameras associated with client device 102). In some embodiments, one or more processors 104 may be evaluated by fault detection application 110 to detect one or more hardware faults associated with one or more hardware components 106 of one or more processors 104. Hardware components may include one or more instruction caches, one or more texture units, cache / shared memory, one or more thread schedulers, one or more thread dispatchers, one or more registers, and / or one or more computing functional units, such as the following about Figure 3 Those described.
[0041] The fault detection application 110 may include one or more components configured to detect one or more hardware faults associated with the one or more processors 104. For example, the fault detection application 110 may be used to detect one or more faults within one or more hardware components 106 (e.g., tensor cores, caches, adders, ALUs, etc.) of or connected to the one or more processors 104. The fault detection application 110 may include a test pattern generator 120 and / or a result evaluator 130.
[0042] The test pattern generator 120 may include one or more components configured to generate and / or access one or more diagnostic test patterns, such as those described above, for detecting one or more hardware faults associated with the one or more processors 104. Test patterns may be generated by the test pattern generator 120 to evaluate a portion of the hardware component 106 for potential faults. For example, the test pattern generator 120 may generate one or more test patterns that evaluate one or more operations of the hardware component 106. In at least one embodiment, the test patterns generated by the test pattern generator 120 may be stored (e.g., in the storage device 140) so that the test patterns may be reused for subsequent fault detection operations.
[0043] In some examples, one or more test patterns generated by the test pattern generator 120 and / or obtained from a storage device (e.g., storage device 140) may be provided to one or more processors 104 to be executed. For example, one or more processors 104 may perform one or more operations according to one or more test patterns. In such an example, one or more processors 104 may perform operations using instructions and / or values indicated by one or more test patterns. One or more processors 104 may perform one or more diagnostic tests using hardware components 106. In at least one embodiment, one or more processors 104 may be caused to execute one or more instructions corresponding to one or more test patterns in parallel. In some examples, one or more processors 104 may generate one or more output values and / or indications in response to executing one or more test patterns (such as test patterns generated by the test pattern generator 120).
[0044] In at least one embodiment, the result evaluator 130 includes one or more components configured to evaluate one or more result values. For example, the result evaluator 130 can receive one or more output values calculated by one or more processors 104 and can use the one or more output values to determine one or more result values, which can be used to determine whether a potential fault can be identified. In some examples, the result evaluator 130 can compare one or more result values with one or more expected result values. In such an example, the result value generated by one or more processors 104 in response to a test mode can be compared with the expected result value associated with the test mode by the result evaluator 130. In at least one embodiment, the result evaluator 130 can obtain one or more expected result values from a storage device 140 and / or can use one or more processors (such as one or more processors 150) to calculate the expected result value.
[0045] In some embodiments, the result evaluator 130 may generate (e.g., as one or more result values) a fault state based on comparing one or more output values generated by the one or more processors 104 with one or more expected values. For example, the result evaluator 130 may generate a fault state indicating that one or more faults are detected (or no faults are detected) in the one or more processors 104. In some examples, the result evaluator 130 may apply a hash function to the output values or result values generated by the one or more processors 104 in response to the test pattern to generate a result hash value. In such an example, the result hash value may be compared by the result evaluator 130 with the expected hash value associated with the test pattern to determine whether one or more of the hardware components 106 are exhibiting correct operation (e.g., non-faulty operation). In some examples, if a fault is detected (e.g., a fault tested by one or more diagnostics), an indication may be provided to the fault manager 132 as a fault state, which indicates and / or identifies one or more potential faults and / or provides other information associated with one or more hardware components 106 corresponding to the one or more potential faults. In some examples, result evaluator 130 may provide the fault status to fault manager 132 .
[0046] The fault manager 132 includes one or more components configured to perform one or more actions based on the fault status generated by the result evaluator 130. For example, based on the fault status, the fault manager 132 may (e.g., using the control component 160) indicate one or more actions to be performed (e.g., one or more corrective operations). The fault manager 132 may make one or more decisions based on the fault status. For example, the fault manager 132 may determine one or more operations to be performed based on a fault status indicating that a threshold number of faults with respect to one or more processors 104 are detected. In some examples, the fault manager 132 may cause one or more operations to be performed by the control component 160. For example, in response to the fault status identifying one or more hardware faults received by the fault manager 132, the fault manager 132 may cause the control component 160 to perform one or more mitigation operations, such as one or more fail-safe operations and / or one or more other safety operations. The mitigation operation may be performed on one or more of the hardware components 106 associated with (e.g., identified by) the fault status.
[0047] The client device 102 may include a memory (not shown) that may be implemented as one or more non-transitory processor-readable media storing processor-executable instructions that, when executed by one or more processors 150, implement the fault detection application 110, the fault manager 132, the control component 160, etc. The memory (not shown) may be implemented as or use a storage device 140. The one or more processors 150 may include one or more circuits that execute at least a portion of the instructions. The one or more processors 150 may be implemented, for example, using a main central processing unit ("CPU") complex, one or more microprocessors, one or more microcontrollers, one or more graphics processing units ("GPU"), one or more data processing units ("DPU"), etc. As additional non-limiting examples, the memory (e.g., one or more non-transitory processor-readable media) may be implemented, for example, using volatile memory (e.g., dynamic random access memory ("DRAM")) and / or non-volatile memory (e.g., hard drive, solid state device ("SSD"), etc.). The client device 102 may include a user interface (not shown) that a user may use to enter user input into the client device 102. The user interface (not shown) may include a display device (not shown) that a user may use to view information generated and / or displayed by the client device 102. The one or more processors 150, the user interface, and / or the memory may communicate with each other via one or more connections, such as a bus, a peripheral component interconnect express (“PCIe”) connection (or bus), etc.
[0048] Figure 2 1 is a block diagram illustrating a method 200 for hardware fault detection according to some embodiments of the present invention. As a non-limiting example, the method 200 may be performed by one or more processors 150 (see Figure 1 ) to execute. Figure 2 , processes (e.g., Figure 1 The fault detection application 110 shown in FIG. 1 sends instructions 202 to a test pattern generator 204. The test pattern generator 204 may be implemented as or using the test pattern generator 120 (see FIG. Figure 1 In some embodiments, the test pattern generator 204 receives instructions 202 that instruct the test pattern generator 204 to generate and / or access a test pattern 206. For example, the instructions 202 may cause the test pattern generator 204 to store data from one or more storage devices (such as Figure 1206). In other examples, the test pattern generator 204 may generate the test pattern based at least in part on the instructions 202. The test pattern generator 204 may determine the test pattern 206 based on one or more characteristics and / or components of the processor 208 to be tested. The test pattern 206 may be provided to the processor 208 or otherwise accessed by the processor 208. The processor 208 may be implemented as or use one or more of the one or more processors 104 (see Figure 1 ).
[0049] In at least one embodiment, the processor 208 may execute the test pattern 206. For example, the processor 208 may perform one or more operations and / or calculations according to the test pattern 206. The processor 208 may generate and / or calculate one or more results 210 as a result of executing the test pattern 206. In some examples, the results 210 may include one or more values used by the result evaluator 212 to detect one or more faults in the processor 208. As an example, the test pattern 206 that tests the arithmetic logic unit (“ALU”) of the processor 208 may cause the processor 208 to perform one or more integer addition and / or subtraction operations to generate one or more output values as the results 210. Once the results 210 have been generated by the processor 208, the results 210 may be provided to and / or accessed by the result evaluator 212. The result evaluator 212 may be implemented as or using the result evaluator 130 (see Figure 1 ).
[0050] The result evaluator 212 may receive the result 210 that may have been generated by the processor 208, and may determine whether the result 210 indicates one or more hardware faults associated with the processor 208. In some examples, the result evaluator 212 may compare the result 210 with one or more expected result values associated with the test pattern 206. In such an example, if the result 210 matches the expected value, the result evaluator 212 may determine that executing the test pattern 206 did not cause any faults in the processor 208. In other examples, if the result 210 does not match the expected value, the result evaluator 212 may determine that executing the test pattern 206 did cause one or more faults in the processor 208. In some embodiments, the result evaluator 212 may generate a fault status 214 based on finding one or more faults associated with the processor 208 and / or the absence of any faults. In at least one embodiment, the fault status 214 may include one or more indications of one or more faults associated with the processor 208 and / or the test pattern 206. In some embodiments, the fault status 214 may be provided to the fault manager 216. Fault manager 216 may be implemented as or use fault manager 132 (see Figure 1 ).
[0051] The fault manager 216 may obtain the fault status 214 and make one or more decisions based on the fault status 214. For example, the fault manager 216 may determine one or more operations to be performed based on the fault status 214 indicating at least that a threshold number of faults with respect to the processor 208 have been detected. In some examples, based on the fault status 214, the fault manager 216 may cause the control component 218 to perform one or more operations. For example, the control component 218 may perform mitigation operations, such as fail-safe and / or other safety operations, in response to the fault manager 216 detecting and / or identifying one or more hardware faults. The control component 218 may be implemented as or using the control component 160 (see Figure 1 ).
[0052] Figure 3 An example processor 300 is shown in accordance with at least one embodiment. In at least one embodiment, the processor 300 may include Figure 1300 may be within one or more processors 104. In at least one embodiment, processor 300 may be a graphics processing unit ("GPU"). In at least one embodiment, processor 300 includes one or more hardware components that can be configured to perform one or more types of operations. In at least one embodiment, processor 300 includes one or more hardware components that can be evaluated using one or more diagnostic test modes (such as those described above). The hardware components of processor 300 may include a shared instruction cache 302, a texture unit 318, and a cache / shared memory 320 that are common to execution resources within processor 300. In at least one embodiment, processor 300 includes one or more cores and may include multiple slices 301A-301N or partitions for each core. A graphics processor (e.g., Figure 1One or more processors 104 shown in ) may include multiple instances of processor 300. Slices 301A-301N may include support logic, which includes local instruction caches 304A-304N, thread schedulers 306A-306N, thread dispatchers 308A-308N, and register groups 310A-310N, respectively. Groups 310A-310N may each include any number of registers, including a single register, and groups 310A-310N may include the same number of registers, or at least two of groups 310A-310N may include different numbers of registers. In at least one embodiment, the slices 301A-301N may include an additional function unit ("AFU") group 312A-312N, a floating point unit ("FPU") group 314A-314N, an integer arithmetic logic unit ("ALU") group 316A-316N, an address calculation unit ("ACU") group 313A-313N, a double precision floating point unit ("DPFPU") group 315A-315N, and a matrix processing unit ("MPU") group 317A-317N, respectively. The groups 312A-312N may each include any number of AFUs, including a single AFU, and the groups 312A-312N may include the same number of AFUs, or at least two of the groups 312A-312N may include different numbers of AFUs. The groups 313A-313N may each include any number of ACUs, including a single ACU, and the groups 313A-313N may include the same number of ACUs, or at least two of the groups 313A-313N may include different numbers of ACUs. The groups 314A-314N may each include any number of FPUs, including a single FPU, and the groups 314A-314N may include the same number of FPUs, or at least two of the groups 314A-314N may include different numbers of FPUs. The groups 315A-315N may each include any number of DPFPUs, including a single DPFPU, and the groups 315A-315N may include the same number of DPFPUs, or at least two of the groups 315A-315N may include different numbers of DPFPUs. The groups 316A-316N may each include any number of ALUs, including a single ALU, and the groups 316A-316N may include the same number of ALUs, or at least two of the groups 316A-316N may include different numbers of ALUs. The groups 317A-317N may each include any number of MPUs, including a single MPU, and the groups 317A-317N may include the same number of MPUs, or at least two of the groups 317A-317N may include different numbers of MPUs. In at least one embodiment, the processor 300 is referred to as a computational unit or an arithmetic unit.
[0053] In at least one embodiment, the FPU group 314A-314N can perform single-precision (e.g., 32-bit) and half-precision (e.g., 16-bit) floating point operations, while the DPFPU group 315A-315N performs double-precision (e.g., 64-bit) floating point operations. In at least one embodiment, the ALU group 316A-316N can perform variable-precision integer operations with 8-bit, 16-bit, and / or 32-bit precision, and can be configured for mixed-precision operations. In at least one embodiment, the MPU group 317A-317N can also be configured for mixed-precision matrix operations, including half-precision floating point and / or 8-bit integer operations. In at least one embodiment, the MPU group 317A-317N can perform various matrix operations to accelerate Compute Unified Device Architecture ("CUDA") programs, including enabling support for accelerated general matrix-to-matrix multiplication ("GEMM"). In at least one embodiment, the AFU groups 312A-312N may perform additional logical operations not supported by the floating point or integer units, including trigonometric operations (eg, sine, cosine, etc.).
[0054] Figure 4 4 is an example test pattern allocation 400 according to some embodiments of the present disclosure. The test pattern allocation 400 may be at least partially composed of a test pattern generator 402 and one or more hardware components (e.g., Figure 1 406) (e.g., L1 cache 404 and / or L2 cache 406). For example, the test pattern generator 402 can obtain the test pattern to be executed by the processor (e.g., Figure 1 One or more processors 104 shown in Figure 2 The test pattern generator 402 may be implemented as or use the test pattern generator 120 (see, for example, the processor 208 shown in FIG. 1 ). Figure 1 ) and / or test pattern generator 204 (see Figure 2 ).
[0055] Test mode assignment 400 may include one or more test modes, such as test mode 410A, test mode 410B, test mode 410C, and / or test mode 410D (referred to herein individually or collectively as test mode 410). In some examples, L1 cache 404 may include one or more portions of memory, such as memory 420A and / or memory 420B, each of which may include one or more hardware components corresponding to one or more memory addresses. Similarly, in some examples, L2 cache 406 may include one or more portions of memory, such as memory 420C and / or memory 420D, each of which may include one or more hardware components corresponding to one or more memory addresses.
[0056] In at least one embodiment, each of the test patterns 410 may be generated by the test pattern generator 402 to test one or more specific hardware components for potential failures. For example, the test pattern 410A may be configured to test the memory 420A of the L1 cache 404, while the test pattern 410B may be configured to test the memory 420B of the L1 cache 404. As another example, the test pattern 410C may be configured to test the memory 420C of the L2 cache 406, while the test pattern 410D may be configured to test the memory 420D of the L2 cache 406. In some examples, multiple test patterns (such as the test pattern 410) may be used to test a single component, while in at least one other example, a single test pattern may be used to test multiple components.
[0057] Figure 5 5 is an example operational test pattern assignment 500 according to some embodiments of the present disclosure. The operational test pattern assignment 500 may be at least partially implemented by one or more hardware components (e.g., Figure 1 For example, the test pattern generator 502 may obtain one or more test patterns to be executed by the processor 504 to detect whether the test patterns cause any failures to occur in one or more hardware components. The test pattern generator 502 may be implemented as or using the test pattern generator 120 (see Figure 1 ) and / or test pattern generator 204 (see Figure 2 ). Processor 504 may be implemented as or use processor 104 (see Figure 1 ) and / or processor 208 (see Figure 2 ).
[0058] Operational test mode assignment 500 may include one or more test modes, such as test mode 510A, test mode 510B, test mode 510C, test mode 510D, test mode 510E, test mode 510F, test mode 510G, and / or test mode 510H (referred to herein individually or collectively as test mode 510). Operational test mode assignment 500 may include one or more hardware components, such as ALU 520A, FPU 520B, MPU 520C, and / or memory 520D. In some examples, ALU 520A, FPU 520B, MPU 520C, and / or memory 520D may be included in processor 504 and / or one or more other processors (such as those described above). As a non-limiting example, ALU 520A may be ALU group 316A (see Figure 3 ), FPU 520B may be a member of FPU group 314A (see Figure 3 ), and / or MPU 520C may be a member of MPU group 317A (see Figure 3 ) is a member of the
[0059] In at least one embodiment, each of the test patterns 510 may be generated by the test pattern generator 502 and used to detect potential faults by testing one or more specific operations associated with one or more hardware components. For example, the test pattern 510A may be configured to test integer addition operations performed by the ALU 520A, while the test pattern 510B may be configured to test integer subtraction operations performed by the ALU 520A. As another example, the test pattern 510C may be configured to test floating-point addition operations performed by the FPU 520B, while the test pattern 510D may be configured to test floating-point subtraction operations performed by the FPU 520B. As another example, the test pattern 510E may be configured to test matrix multiplication operations performed by the MPU 520C, while the test pattern 510F may be configured to test matrix transformation operations performed by the MPU 520C. As another example, test mode 510G may be configured to test a memory read operation performed by memory 520D, while test mode 510H may be configured to test a memory write operation performed by memory 520D. In some examples, multiple test modes (such as test mode 510) may be configured to test a single operation, while in at least one other example, a single test mode may be configured to test multiple different operations of one or more components.
[0060] Now refer to Figure 6, each block of the method 600 described herein includes a computing process that can be performed using any combination of hardware, firmware, and / or software. For example, various functions can be implemented by a processor executing instructions stored in a memory. The method 600 can also be embodied as computer usable instructions stored on a computer storage medium. The method 600 can be provided by a stand-alone application, a service or a hosted service (standalone or in combination with another hosted service), or a plug-in to another product, to name a few. In addition, by way of example, with respect to Figure 1 The methods 600 are described with reference to the system 100 of FIG. However, these methods may additionally or alternatively be performed by any one system or any combination of systems, including but not limited to those described herein.
[0061] Figure 6 is a flow chart illustrating a method 600 for performing hardware fault detection according to some embodiments of the present disclosure. At block 602, the fault detection application 110 (see Figure 1 )(For example, by Figure 1 One or more processors 150 shown in the figure) obtain one or more diagnostic test patterns. For example, the test pattern generator 120 (see Figure 1 ) generated by the fault detection application 110 may be retrieved and / or provided to one or more processors, such as one or more processors 104 (see Figure 1 In at least one embodiment, the fault detection application 110 provides one or more input values associated with one or more diagnostic test modes to the one or more processors 104 .
[0062] At block 604, one or more processors 104 (see Figure 1 ) execute and / or cause one or more hardware components 106 (see Figure 1 ) executes the diagnostic test pattern to generate one or more result values. For example, at block 602, one or more result values may be generated by one or more processors 104 based on one or more diagnostic test patterns obtained by the fault detection application 110 and provided to the one or more processors 104 by the fault detection application 110. In such an example, the one or more processors 104 may execute and / or cause one or more hardware components 106 (see Figure 1 ) performs one or more operations associated with a diagnostic test mode.
[0063] At block 606, the fault detection application 110 (see Figure 1 ) executes and / or causes the result evaluator 130 (see Figure 1) detects one or more hardware faults. For example, based on the result values generated by one or more processors 104 and / or hardware components 106 in response to executing the diagnostic test mode at block 604, the result evaluator 130 may determine that one or more hardware faults associated with the one or more processors 104 are detected. After block 606, the method 600 may terminate.
[0064] The systems and methods described herein may be used by, but are not limited to, non-autonomous vehicles, semi-autonomous vehicles (e.g., in one or more adaptive driver assistance systems (ADAS)), robots or robotic platforms with and without drivers, warehouse vehicles, off-road vehicles, vehicles coupled to one or more trailers, airships, boats, shuttles, emergency response vehicles, motorcycles, electric or motorized bicycles, aircraft, engineering vehicles, submarines, drones, and / or other vehicle types. The systems and methods described herein may be used in augmented reality, virtual reality, mixed reality, robotics, security and surveillance, autonomous or semi-autonomous machine applications, and / or any other technology space in which two or more clocks are synchronized.
[0065] The systems and methods described herein may be used by, but are not limited to, non-autonomous vehicles, semi-autonomous vehicles (e.g., in one or more adaptive driver assistance systems (ADAS)), robots or robotic platforms with and without drivers, warehouse vehicles, off-road vehicles, vehicles coupled to one or more trailers, airships, boats, shuttles, emergency response vehicles, motorcycles, electric or motorized bicycles, aircraft, engineering vehicles, submarines, drones, and / or other vehicle types. In addition, the systems and methods described herein may be used for a variety of purposes, including, by way of example and not limitation, for machine control, machine motion, machine actuation, synthetic data generation, model training, perception, augmented reality, virtual reality, mixed reality, robotics, safety and surveillance, simulation and digital twins, autonomous or semi-autonomous machine applications, deep learning, environmental simulation, object or actor simulation and / or digital twins, data center processing, conversational AI, light transport simulation (e.g., ray tracing, path tracing, etc.), collaborative content creation for 3D assets, cloud computing, web-hosted services or web-hosted platforms, and / or any other suitable application.
[0066] The disclosed embodiments may be included in a variety of different systems, such as automotive systems (e.g., control systems for autonomous or semi-autonomous machines, perception systems for autonomous or semi-autonomous machines), systems implemented using robots, aerial systems, medical systems, boating systems, smart area monitoring systems, systems for performing deep learning operations, systems for performing simulation operations, systems for performing digital twin operations, systems implemented using edge devices, systems including one or more virtual machines (VMs), systems for performing synthetic data generation operations, systems implemented at least in part in a data center, systems for performing conversational AI operations, systems implementing one or more language models - such as large language models (LLMs) that process text, images, sensors, audio, and / or other data types, systems for performing light transport simulations, systems for performing collaborative content creation of 3D assets, systems implemented at least in part using cloud computing resources, systems for implementing web-hosted services (e.g., for performing program optimization at runtime) or web-hosted platforms (e.g., an integrated development environment including program optimization as a service), as an application programming interface ("API") between two or more separate applications or systems, and / or other types of systems.
[0067] Example Autonomous Vehicle
[0068] Fig. 7A 700 is an illustration of an example autonomous vehicle 700 according to some embodiments of the present disclosure. Autonomous vehicle 700 (alternatively referred to herein as "vehicle 700") may include, but is not limited to, a passenger vehicle, such as a car, a truck, a bus, a first response vehicle, a shuttle, an electric or motorized bicycle, a motorcycle, a fire truck, a police vehicle, an ambulance, a boat, an engineering vehicle, a submarine, a drone, and / or another type of vehicle (e.g., a vehicle that is unmanned and / or accommodates one or more passengers). Autonomous vehicles are generally described according to the automation levels defined by the National Highway Traffic Safety Administration (NHTSA), a division of the U.S. Department of Transportation, and the Society of Automotive Engineers (SAE) "Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles" (Standard No. J3016-201806 issued on June 15, 2018, Standard No. J3016-201609 issued on September 30, 2016, and previous and future versions of the standard). The vehicle 700 may be capable of implementing functions consistent with one or more of Levels 3-5 of autonomous driving levels. For example, depending on the embodiment, the vehicle 700 may be capable of conditional automation (Level 3), high automation (Level 4), and / or full automation (Level 5).
[0069] The vehicle 700 may include components such as a chassis, a body, wheels (e.g., 2, 4, 6, 8, 18, etc.), tires, axles, and other components of the vehicle. The vehicle 700 may include a propulsion system 750, such as an internal combustion engine, a hybrid power plant, an all-electric engine, and / or another type of propulsion system. The propulsion system 750 may be connected to a drive train of the vehicle 700, which may include a transmission, to achieve propulsion of the vehicle 700. The propulsion system 750 may be controlled in response to receiving a signal from a throttle / accelerator 752.
[0070] A steering system 754, which may include a steering wheel, may be used to steer the vehicle 700 (e.g., along a desired path or route) when the propulsion system 750 is operating (e.g., when the vehicle is in motion). The steering system 754 may receive signals from a steering actuator 756. For fully automated (Level 5) functionality, a steering wheel may be optional.
[0071] Brake sensor system 746 may be used to operate vehicle brakes in response to receiving signals from brake actuator 748 and / or brake sensors.
[0072] May include one or more CPUs, system on chip (SoC) 704 ( Figure 7C ) and / or one or more controllers 736 of one or more GPUs may provide signals (e.g., representing commands) to one or more components and / or systems of the vehicle 700. For example, the one or more controllers may send signals to operate vehicle brakes via one or more brake actuators 748, to operate the steering system 754 via one or more steering actuators 756, to operate the propulsion system 750 via one or more throttles / accelerators 752, and / or to operate the propulsion system 750. The one or more controllers 736 may include one or more onboard (e.g., integrated) computing devices (e.g., supercomputers) that process sensor signals and output operating commands (e.g., signals representing commands) to enable autonomous driving and / or assist a human driver in driving the vehicle 700. The one or more controllers 736 may include a first controller 736 for autonomous driving functions, a second controller 736 for functional safety functions, a third controller 736 for artificial intelligence functions (e.g., computer vision), a fourth controller 736 for infotainment functions, a fifth controller 736 for redundancy in emergency situations, and / or other controllers. In some examples, a single controller 736 may handle two or more of the above functions, two or more controllers 736 may handle a single function, and / or any combination thereof.
[0073] The one or more controllers 736 may provide signals for controlling one or more components and / or systems of the vehicle 700 in response to sensor data (e.g., sensor input) received from one or more sensors. The sensor data may be received from, for example and without limitation, a global navigation satellite system sensor 758 (e.g., a global positioning system sensor), a RADAR sensor 760, an ultrasonic sensor 762, a LIDAR sensor 764, an inertial measurement unit (IMU) sensor 766 (e.g., an accelerometer, a gyroscope, a magnetic compass, a magnetometer, etc.), a microphone 796, a stereo camera 768, a wide angle camera 770 (e.g., a fisheye camera), an infrared camera 772, a surround camera 774 (e.g., a 360 degree camera), a long-range and / or mid-range camera 798, a speed sensor 744 (e.g., for measuring the velocity of the vehicle 700), a vibration sensor 742, a steering sensor 740, a brake sensor 746 (e.g., as part of a brake sensor system 746), and / or other sensor types.
[0074] One or more of the controllers 736 may receive inputs (e.g., represented by input data) from the instrument cluster 732 of the vehicle 700 and provide outputs (e.g., represented by output data, display data, etc.) via a human machine interface (HMI) display 734, an audible annunciator, a speaker, and / or via other components of the vehicle 700. These outputs may include information such as vehicle speed, velocity, time, map data (e.g., Figure 7C The HMI display 734 may include information such as the HD map 722 of the vehicle 700, location data (e.g., the location of the vehicle 700 on the map), directions, locations of other vehicles (e.g., occupancy grid), information about objects and object states as sensed by the controller 736, etc. For example, the HMI display 734 may display information about the presence of one or more objects (e.g., street signs, warning signs, traffic light changes, etc.) and / or information about driving maneuvers that the vehicle has made, is making, or will make (e.g., changing lanes now, leaving 34B in two miles, etc.).
[0075] The vehicle 700 also includes a network interface 724 that can communicate via one or more networks using one or more wireless antennas 726 and / or a modem. For example, the network interface 724 may be capable of communicating via LTE, WCDMA, UMTS, GSM, CDMA2000, etc. The one or more wireless antennas 726 may also enable communication between objects in the environment (e.g., vehicles, mobile devices, etc.) using one or more local area networks such as Bluetooth, Bluetooth LE, Z-wave, ZigBee, etc. and / or one or more low power wide area networks (LPWANs) such as LoRaWAN, SigFox, etc.
[0076] Figure 7BFor use according to some embodiments of the present disclosure Fig. 7A 700. The cameras and respective fields of view are an example embodiment and are not intended to be limiting. For example, additional and / or replaceable cameras may be included, and / or the cameras may be located at different locations on the vehicle 700.
[0077] The camera type for the camera may include, but is not limited to, a digital camera that may be suitable for use with components and / or systems of the vehicle 700. The camera may operate at an automotive safety integrity level (ASIL) B and / or at another ASIL. The camera type may have any image capture rate, such as 60 frames per second (fps), 120fps, 240fps, etc., depending on the embodiment. The camera may be capable of using a rolling shutter, a global shutter, another type of shutter, or a combination thereof. In some examples, the color filter array may include a red-white-white-white (RCCC) color filter array, a red-white-white-blue (RCCB) color filter array, a red-blue-green-white (RBGC) color filter array, a Foveon X3 color filter array, a Bayer sensor (RGGB) color filter array, a monochrome sensor color filter array, and / or another type of color filter array. In some embodiments, a clear pixel camera such as a camera with an RCCC, RCCB, and / or RBGC color filter array may be used in an effort to improve light sensitivity.
[0078] In some examples, one or more of the cameras can be used to perform advanced driver assistance system (ADAS) functions (e.g., as part of a redundant or fail-safe design). For example, a multi-function monocular camera can be installed to provide functions including lane departure warning, traffic sign assistance, and intelligent headlight control. One or more of the cameras (e.g., all of the cameras) can simultaneously record and provide image data (e.g., video).
[0079] One or more of the cameras may be mounted in a mounting assembly such as a custom designed (3-D printed) assembly to cut off stray light and reflections from within the car (e.g., reflections from the dashboard reflected in the windshield mirror) that may interfere with the camera's image data capture capabilities. With respect to the wing mirror mounting assembly, the wing mirror assembly may be custom 3-D printed so that the camera mounting plate matches the shape of the wing mirror. In some examples, one or more cameras may be integrated into the wing mirror. For side view cameras, one or more cameras may also be integrated into the four pillars at each corner of the cab.
[0080] A camera (e.g., a front-facing camera) having a field of view that includes a portion of the environment in front of the vehicle 700 can be used for surround view to help identify the forward path and obstacles, as well as assist in providing information critical to generating an occupancy grid and / or determining a preferred vehicle path with the help of one or more controllers 736 and / or control SoCs. The front-facing camera can be used to perform many of the same ADAS functions as LIDAR, including emergency braking, pedestrian detection, and collision avoidance. The front-facing camera can also be used for ADAS functions and systems, including lane departure warning ("LDW"), autonomous cruise control ("ACC"), and / or other functions such as traffic sign recognition.
[0081] A variety of cameras may be used in the front-facing configuration, including, for example, a monocular camera platform including a CMOS (complementary metal oxide semiconductor) color imager. Another example may be a wide-angle camera 770, which may be used to sense objects (e.g., pedestrians, intersection traffic, or bicycles) entering the field of view from the periphery. Figure 7B Only one wide-angle camera is shown in the figure, but there may be any number of wide-angle cameras 770 on the vehicle 700. In addition, one or more remote cameras 798 (e.g., a long-view stereo camera pair) may be used for depth-based object detection, especially for objects for which a neural network has not yet been trained. One or more remote cameras 798 may also be used for object detection and classification and basic object tracking.
[0082] One or more stereo cameras 768 may also be included in the front configuration. The stereo camera 768 may include an integrated control unit including an expandable processing unit that may provide a multi-core microprocessor and programmable logic (e.g., FPGA) with an integrated CAN or Ethernet interface on a single chip. Such a unit may be used to generate a 3-D map of the vehicle environment, including distance estimates for all points in the image. An alternative stereo camera 768 may include a compact stereo vision sensor that may include two camera lenses (one on each side) and an image processing chip that may measure the distance from the vehicle to the target object and use the generated information (e.g., metadata) to activate autonomous emergency braking and lane departure warning functions. Other types of stereo cameras 768 may be used in addition to or alternatively to those described herein.
[0083] A camera having a field of view of a portion of the environment including the sides of the vehicle 700 (e.g., a side view camera) can be used for surround viewing, providing information used to create and update the occupancy grid and generate side impact collision warnings. Figure 7BThe four surround cameras 774 shown in FIG. 7 can be located around the vehicle 700. The surround cameras 774 can include wide-angle cameras 770, fisheye cameras, 360-degree cameras, and / or the like. For example, four fisheye cameras can be placed in front, behind, and on the sides of the vehicle. In an alternative arrangement, the vehicle can use three surround cameras 774 (e.g., left, right, and rear), and can utilize one or more other cameras (e.g., a forward-facing camera) as a fourth surround camera.
[0084] A camera having a field of view that includes a portion of the environment behind the vehicle 700 (e.g., a rear view camera) can be used to assist with parking, surround view, rear collision warning, and creating and updating occupancy grids. A variety of cameras can be used, including but not limited to cameras that are also suitable as front cameras as described herein (e.g., long-range and / or mid-range cameras 798, stereo cameras 768, infrared cameras 772, etc.).
[0085] Figure 7C For use according to some embodiments of the present disclosure Fig. 7A Block diagram of an example system architecture of an example autonomous vehicle 700. It should be understood that this arrangement and other arrangements described herein are set forth merely as examples. Other arrangements and elements (e.g., machines, interfaces, functions, sequences, functional groupings, etc.) may be used in addition to or in place of those shown, and some elements may be omitted entirely. Further, many of the elements described herein are functional entities that may be implemented as discrete or distributed components or in combination with other components, and in any appropriate combination and location. The various functions described herein as being performed by an entity may be implemented by hardware, firmware, and / or software. For example, the various functions may be implemented by a processor executing instructions stored in a memory.
[0086] Figure 7C Each of the components, features, and systems of the vehicle 700 is illustrated as being connected via a bus 702. The bus 702 may include a controller area network (CAN) data interface (alternatively, referred to herein as a "CAN bus"). The CAN may be a network inside the vehicle 700 that assists in controlling various features and functions of the vehicle 700, such as the actuation of brakes, acceleration, braking, steering, windshield wipers, and the like. The CAN bus may be configured to have tens or even hundreds of nodes, each with its own unique identifier (e.g., a CAN ID). The CAN bus may be read to find steering wheel angle, ground speed, engine speed per minute (RPM), button position, and / or other vehicle status indicators. The CAN bus may be ASIL B compatible.
[0087] Although bus 702 is described as a CAN bus here, this is not intended to be limiting. For example, in addition to or alternatively to the CAN bus, FlexRay and / or Ethernet can be used. In addition, although bus 702 is represented by a single line, this is not intended to be limiting. For example, there can be any number of buses 702, which may include one or more CAN buses, one or more FlexRay buses, one or more Ethernet buses, and / or one or more other types of buses using different protocols. In some examples, two or more buses 702 can be used to perform different functions, and / or can be used for redundancy. For example, a first bus 702 can be used for a collision avoidance function, and a second bus 702 can be used for drive control. In any example, each bus 702 can communicate with any component of the vehicle 700, and two or more buses 702 can communicate with the same component. In some examples, each SoC 704, each controller 736, and / or each computer in the vehicle can have access to the same input data (e.g., input from a sensor of the vehicle 700), and can be connected to a common bus such as a CAN bus.
[0088] The vehicle 700 may include one or more controllers 736, such as those described herein. Fig. 7A Those controllers described. Controller 736 can be used for a variety of functions. Controller 736 can be coupled to any other different components and systems of vehicle 700, and can be used for control of vehicle 700, artificial intelligence of vehicle 700, infotainment for vehicle 700, and / or the like.
[0089] The vehicle 700 may include one or more system on chip (SoC) 704. The SoC 704 may include a CPU 706, a GPU 708, a processor 710, a cache 712, an accelerator 714, a data store 716, and / or other components and features not shown. The SoC 704 may be used to control the vehicle 700 in a variety of platforms and systems. For example, one or more SoCs 704 may be combined with an HD map 722 in a system (e.g., a system of the vehicle 700), and the HD map may be downloaded from one or more servers (e.g., a server) via a network interface 724. Fig.7D one or more servers 778) to obtain map refreshes and / or updates.
[0090] The CPU 706 may include a CPU cluster or a CPU complex (alternatively, referred to herein as a "CCPLEX"). The CPU 706 may include multiple cores and / or L2 caches. For example, in some embodiments, the CPU 706 may include eight cores in a coherent multiprocessor configuration. In some embodiments, the CPU 706 may include four dual-core clusters, each of which has a dedicated L2 cache (e.g., a 2MB L2 cache). The CPU 706 (e.g., CCPLEX) may be configured to support simultaneous cluster operations, such that any combination of clusters of the CPU 706 can be active at any given time.
[0091] CPU 706 may implement power management capabilities including one or more of the following features: each hardware block may be automatically clock gated when idle to save dynamic power; each core clock may be gated when the core is not actively executing instructions due to the execution of WFI / WFE instructions; each core may be independently power gated; each core cluster may be independently clock gated when all cores are clock gated or power gated; and / or each core cluster may be independently power gated when all cores are power gated. CPU 706 may further implement an enhanced algorithm for managing power states, in which allowed power states and expected wake-up times are specified, and hardware / microcode determines the optimal power state to enter for the core, cluster, and CCPLEX. The processing core may support a simplified power state entry sequence in software, with the work being offloaded to the microcode.
[0092] The GPU 708 may include an integrated GPU (alternatively, referred to herein as an "iGPU"). The GPU 708 may be programmable and efficient for parallel workloads. In some examples, the GPU 708 may use an enhanced tensor instruction set. The GPU 708 may include one or more streaming microprocessors, each of which may include an L1 cache (e.g., an L1 cache with at least 96KB storage capacity), and two or more of these streaming microprocessors may share an L2 cache (e.g., an L2 cache with 512KB storage capacity). In some embodiments, the GPU 708 may include at least eight streaming microprocessors. The GPU 708 may use a computer-based application programming interface (API). In addition, the GPU 708 may use one or more parallel computing platforms and / or programming models (e.g., NVIDIA's CUDA).
[0093] In the case of automotive and embedded use, GPU 708 can be power optimized to achieve optimal performance. For example, GPU 708 can be manufactured on fin field effect transistors (FinFETs). However, this is not intended to be limiting, and GPU 708 can be manufactured using other semiconductor manufacturing processes. Each streaming microprocessor can merge several mixed precision processing cores divided into multiple blocks. For example and without limitation, 64 PF32 cores and 32 PF64 cores can be divided into four processing blocks. In such an example, each processing block can be allocated 16 FP32 cores, 8 FP64 cores, 16 INT32 cores, two mixed precision NVIDIA tensor cores for deep learning matrix arithmetic, L0 instruction cache, thread beam (warp) scheduler, dispatch unit and / or 64KB register file. In addition, the streaming microprocessor can include independent parallel integer and floating point data paths to provide efficient execution of workloads using a mix of calculations and addressing calculations. The streaming microprocessor may include independent thread scheduling capabilities to allow for finer-grained synchronization and collaboration between parallel threads. A streaming microprocessor may include a combined L1 data cache and shared memory unit to increase performance while simplifying programming.
[0094] GPU 708 can include high bandwidth memory (HBM) and / or a 16GB HBM2 memory subsystem that provides a peak memory bandwidth of approximately 900 GB / s in some examples. In some examples, synchronous graphics random access memory (SGRAM), such as fifth generation graphics double data rate synchronous random access memory (GDDR5), can be used in addition to or in lieu of HBM memory.
[0095] The GPU 708 may include unified memory technology that includes access counters to allow memory pages to be more accurately migrated to the processor that accesses them most frequently, thereby improving the efficiency of memory ranges shared between processors. In some examples, address translation service (ATS) support can be used to allow the GPU 708 to directly access the CPU 706 page table. In such an example, when the GPU 708 memory management unit (MMU) experiences a miss, an address translation request can be transmitted to the CPU 706. In response, the CPU 706 can look up the virtual-physical mapping for the address in its page table and transmit the translation back to the GPU 708. In this way, unified memory technology can allow a single unified virtual address space to be used for the memory of both the CPU 706 and the GPU 708, thereby simplifying GPU 708 programming and porting applications to the GPU 708.
[0096] In addition, GPU 708 may include access counters that can track how often GPU 708 accesses the memory of other processors. Access counters can help ensure that memory pages are moved to the physical memory of the processor that accesses them most frequently.
[0097] SoC 704 may include any number of caches 712, including those described herein. For example, cache 712 may include an L3 cache available to both CPU 706 and GPU 708 (e.g., connected to both CPU 706 and GPU 708). Cache 712 may include a write-back cache that may track the state of a line, for example, by using a cache coherence protocol (e.g., MEI, MESI, MSI, etc.). Depending on the embodiment, the L3 cache may include 4MB or more, although smaller cache sizes may also be used.
[0098] One or more SoCs 704 may include one or more arithmetic logic units (ALUs) that may be utilized in performing processing of any of a variety of tasks or operations with respect to the vehicle 700, such as processing a DNN. Additionally, one or more SoCs 704 may include a floating point unit (FPU) or other math coprocessor or digital coprocessor type for performing mathematical operations within the system. For example, one or more SoCs 704 may include one or more FPUs that are integrated as an execution unit within one or more CPUs 706 and / or one or more GPUs 708.
[0099] SoC 704 may include one or more accelerators 714 (e.g., hardware accelerators, software accelerators, or combinations thereof). For example, SoC 704 may include a hardware acceleration cluster, which may include optimized hardware accelerators and / or large on-chip memory. The large on-chip memory (e.g., 4MB SRAM) may enable the hardware acceleration cluster to accelerate neural networks and other calculations. The hardware acceleration cluster may be used to supplement GPU 708 and offload some tasks of GPU 708 (e.g., free up more cycles of GPU 708 for performing other tasks). As an example, accelerator 714 may be used for targeted workloads (e.g., perception, convolutional neural networks (CNNs), etc.) that are sufficiently stable to be easily controlled for acceleration. When used herein, the term "CNN" may include all types of CNNs, including region-based or regional convolutional neural networks (RCNNs) and fast RCNNs (e.g., for object detection).
[0100] The accelerator 714 (e.g., a hardware acceleration cluster) may include a deep learning accelerator (DLA). The DLA may include one or more tensor processing units (TPUs) that may be configured to provide an additional 10 trillion operations per second for deep learning applications and reasoning. The TPU may be an accelerator configured to perform image processing functions (e.g., for CNN, RCNN, etc.) and optimized for performing image processing functions. The DLA may be further optimized for a specific set of neural network types and floating point operations and reasoning. The design of the DLA may provide higher performance per millimeter than a general-purpose GPU, and far exceeds the performance of the CPU. The TPU may perform several functions, including a single instance convolution function, support, for example, INT8, INT16, and FP16 data types for both features and weights, and post-processor functions.
[0101] The DLA can quickly and efficiently execute neural networks, particularly CNNs, on processed or unprocessed data for any of a wide variety of functions, such as, but not limited to: a CNN for object recognition and detection using data from a camera sensor; a CNN for distance estimation using data from a camera sensor; a CNN for emergency vehicle detection and identification and detection using data from a microphone; a CNN for facial recognition and vehicle owner identification using data from a camera sensor; and / or a CNN for safety and / or security-related events.
[0102] The DLA can perform any function of the GPU 708, and by using an inference accelerator, for example, the designer can target any function to either the DLA or the GPU 708. For example, the designer can focus the processing of CNNs and floating point operations on the DLA, and leave other functions to the GPU 708 and / or other accelerators 714.
[0103] The accelerator 714 (e.g., a hardware acceleration cluster) may include a programmable vision accelerator (PVA), which may be alternatively referred to herein as a computer vision accelerator. The PVA may be designed and configured to accelerate computer vision algorithms for advanced driver assistance systems (ADAS), autonomous driving, and / or augmented reality (AR) and / or virtual reality (VR) applications. The PVA may provide a balance between performance and flexibility. For example, each PVA may include, for example and without limitation, any number of reduced instruction set computer (RISC) cores, direct memory access (DMA), and / or any number of vector processors.
[0104] The RISC core can interact with an image sensor (e.g., an image sensor of any camera described herein), an image signal processor, and / or the like. Each of these RISC cores can include any amount of memory. Depending on the embodiment, the RISC core can use any of a number of protocols. In some examples, the RISC core can execute a real-time operating system (RTOS). The RISC core can be implemented using one or more integrated circuit devices, application specific integrated circuits (ASICs), and / or storage devices. For example, the RISC core can include an instruction cache and / or a tightly coupled RAM.
[0105] The DMA may enable components of the PVA to access system memory independently of the CPU 706. The DMA may support any number of features used to provide optimizations for the PVA, including, but not limited to, support for multi-dimensional addressing and / or circular addressing. In some examples, the DMA may support addressing in up to six or more dimensions, which may include block width, block height, block depth, horizontal block stepping, vertical block stepping, and / or depth stepping.
[0106] The vector processor can be a programmable processor that can be designed to efficiently and flexibly perform programming for computer vision algorithms and provide signal processing capabilities. In some examples, the PVA can include a PVA core and two vector processing subsystem partitions. The PVA core can include a processor subsystem, one or more DMA engines (e.g., two DMA engines), and / or other peripherals. The vector processing subsystem can operate as the main processing engine of the PVA, and can include a vector processing unit (VPU), an instruction cache, and / or a vector memory (e.g., VMEM). The VPU core can include a digital signal processor, such as, for example, a single instruction multiple data (SIMD), a very long instruction word (VLIW) digital signal processor. The combination of SIMD and VLIW can enhance throughput and rate.
[0107] Each of the vector processors may include an instruction cache and may be coupled to a dedicated memory. As a result, in some examples, each of the vector processors may be configured to execute independently of the other vector processors. In other examples, the vector processors included in a particular PVA may be configured to employ data parallelism. For example, in some embodiments, multiple vector processors included in a single PVA may execute the same computer vision algorithm, but on different regions of an image. In other examples, the vector processors included in a particular PVA may execute different computer vision algorithms simultaneously on the same image, or even execute different algorithms on sequence images or portions of an image. Among other things, any number of PVAs may be included in a hardware acceleration cluster, and any number of vector processors may be included in each of these PVAs. In addition, the PVA may include additional error correction code (ECC) memory to enhance overall system security.
[0108] The accelerator 714 (e.g., a hardware acceleration cluster) may include an on-chip computer vision network and SRAM to provide high bandwidth, low latency SRAM for the accelerator 714. In some examples, the on-chip memory may include at least 4MB of SRAM consisting of, for example and not limited to, eight field-configurable memory blocks, which may be accessed by both the PVA and the DLA. Each pair of memory blocks may include an advanced peripheral bus (APB) interface, a configuration circuit system, a controller, and a multiplexer. Any type of memory may be used. The PVA and DLA may access the memory via a backbone that provides high-speed memory access to the PVA and DLA. The backbone may include an on-chip computer vision network that interconnects the PVA and DLA to the memory (e.g., using APB).
[0109] The on-chip computer vision network may include an interface that determines that both the PVA and DLA provide ready and valid signals before transmitting any control signals / addresses / data. Such an interface may provide separate phases and separate channels for transmitting control signals / addresses / data, as well as burst communication for continuous data transmission. This type of interface may comply with ISO 26262 or IEC 61508 standards, but other standards and protocols may also be used.
[0110] In some examples, SoC 704 may include a real-time ray tracing hardware accelerator such as described in U.S. Patent Application No. 16 / 101,232 filed on August 10, 2018. The real-time ray tracing hardware accelerator may be used to quickly and efficiently determine the position and range of objects (e.g., within a world model) in order to generate real-time visualization simulations for RADAR signal interpretation, for sound propagation synthesis and / or analysis, for SONAR system simulations, for general wave propagation simulations, for comparison with LIDAR data for the purpose of positioning and / or other functions, and / or for other purposes. In some embodiments, one or more tree traversal units (TTUs) may be used to perform one or more ray tracing related operations.
[0111] The accelerator 714 (e.g., a hardware accelerator cluster) has a wide range of uses in autonomous driving. The PVA can be a programmable visual accelerator that can be used in key processing stages in ADAS and autonomous vehicles. The capabilities of the PVA are a good match for algorithmic domains that require predictable processing, low power, and low latency. In other words, the PVA performs well on semi-dense or dense rule computations, and even on small data sets that require predictable runtimes with low latency and low power. Therefore, in the context of a platform for autonomous vehicles, the PVA is designed to run classic computer vision algorithms because they are effective at object detection and integer math.
[0112] For example, according to one embodiment of the technology, PVA is used to perform computer stereo vision. In some examples, algorithms based on semi-global matching can be used, but this is not intended to be limiting. Many applications for level 3-5 autonomous driving require instant motion estimation / stereo matching (e.g., structure from motion, pedestrian recognition, lane detection, etc.). PVA can perform computer stereo vision functions on input from two monocular cameras.
[0113] In some examples, PVA can be used to perform dense optical flow. For example, PVA can be used to process raw RADAR data (e.g., using a 4D fast Fourier transform) to provide a processed RADAR signal before transmitting the next RADAR pulse. In other examples, PVA is used for time-of-flight depth processing, for example, by processing raw time-of-flight data to provide processed time-of-flight data.
[0114] DLA can be used to run any type of network to enhance control and driving safety, including, for example, a neural network that outputs a confidence measure for each object detection. Such a confidence value can be interpreted as a probability, or as providing a relative "weight" of each detection compared to other detections. This confidence value enables the system to make further decisions about which detections should be considered true positive detections rather than false positive detections. For example, the system can set a threshold for confidence and only consider detections that exceed the threshold as true positive detections. In an automatic emergency braking (AEB) system, a false positive detection will cause the vehicle to automatically perform emergency braking, which is obviously undesirable. Therefore, only the most confident detection should be considered a trigger for AEB. DLA can run a neural network for regressing confidence values. The neural network can take at least some subset of parameters as its input, such as bounding box dimensions, ground plane estimates obtained (e.g., from another subsystem), inertial measurement unit (IMU) sensor 766 output related to vehicle 700 orientation and distance, 3D position estimates of objects obtained from neural networks and / or other sensors (e.g., LIDAR sensor 764 or RADAR sensor 760), etc.
[0115] SoC 704 may include one or more data stores 716 (e.g., memory). Data store 716 may be on-chip memory of SoC 704 that may store neural networks to be executed on the GPU and / or DLA. In some examples, one or more data stores 716 may be large enough to store multiple instances of a neural network for redundancy and safety. Data store 716 may include an L2 or L3 cache 712. References to data stores 716 may include references to memory associated with a PVA, DLA, and / or other accelerator 714 as described herein.
[0116] One or more SoCs 704 may include one or more processors 710 (e.g., embedded processors). Processors 710 may include a boot and power management processor, which may be a dedicated processor and subsystem for handling boot power and management functions and related safety implementations. The boot and power management processor may be part of the SoC 704 boot sequence and may provide runtime power management services. The boot power and management processor may provide clock and voltage programming, auxiliary system low power state transitions, SoC 704 thermal and temperature sensor management, and / or SoC 704 power state management. Each temperature sensor may be implemented as a ring oscillator whose output frequency is proportional to the temperature, and the SoC 704 may use the ring oscillator to detect the temperature of the CPU 706, GPU 708, and / or accelerator 714. If it is determined that the temperature exceeds a threshold, the boot and power management processor may enter a temperature fault routine and place the SoC 704 in a lower power state and / or place the vehicle 700 in a driver safety parking mode (e.g., parking the vehicle 700 safely).
[0117] Processor 710 may also include a set of embedded processors that can be used as an audio processing engine. The audio processing engine can be an audio subsystem that allows full hardware support for multi-channel audio through multiple interfaces and a wide range of flexible audio I / O interfaces. In some examples, the audio processing engine is a dedicated processor core with a digital signal processor with dedicated RAM.
[0118] The processor 710 may also include an always-on-processor engine that can provide the necessary hardware features to support low-power sensor management and wake-up use cases. The always-on-processor engine may include a processor core, tightly coupled RAM, supporting peripherals (such as timers and interrupt controllers), various I / O controller peripherals, and routing logic.
[0119] The processor 710 may also include a safety cluster engine that includes a dedicated processor subsystem that handles safety management of automotive applications. The safety cluster engine may include two or more processor cores, tightly coupled RAM, supporting peripherals (e.g., timers, interrupt controllers, etc.), and / or routing logic. In safety mode, the two or more cores may operate in lockstep mode and act as a single core with comparison logic to detect any differences between their operations.
[0120] Processor 710 may also include a real-time camera engine, which may include a dedicated processor subsystem for handling real-time camera management.
[0121] Processor 710 may also include a high dynamic range signal processor, which may include an image signal processor, which is a hardware engine that is part of the camera processing pipeline.
[0122] The processor 710 may include a video image compositer, which may be a processing block (e.g., implemented on a microprocessor) that implements video post-processing functions required for a video playback application to produce a final image for a player window. The video image compositer may perform lens distortion correction for the wide-angle camera 770, the surround camera 774, and / or for an in-cab surveillance camera sensor. The in-cab surveillance camera sensor is preferably monitored by a neural network running on another instance of the advanced SoC, configured to recognize in-cab events and respond accordingly. The in-cab system may perform lip reading to activate mobile phone service and place calls, dictate emails, change vehicle destinations, activate or change the vehicle's infotainment system and settings, or provide voice-activated web surfing. Certain functions are only available to the driver when the vehicle is operating in autonomous mode and are disabled in other circumstances.
[0123] The video image compositer may include enhanced temporal noise reduction for both spatial and temporal noise reduction. For example, in the case of motion in the video, the noise reduction appropriately weights the spatial information and reduces the weight of information provided by adjacent frames. In the case where an image or portion of an image does not include motion, the temporal noise reduction performed by the video image compositer may use information from previous images to reduce noise in the current image.
[0124] The video image compositor may also be configured to perform stereoscopic rectification on the input stereoscopic footage frames. The video image compositor may further be used for user interface composition when the operating system desktop is in use and the GPU 708 does not need to continuously render new surfaces. Even when the GPU 708 is powered on and actively performing 3D rendering, the video image compositor may be used to offload the GPU 708 to improve performance and responsiveness.
[0125] The SoC 704 may also include a mobile industry processor interface (MIPI) camera serial interface for receiving video and input from a camera, a high-speed interface, and / or a video input block that may be used for camera and related pixel input functions. The SoC 704 may also include an input / output controller that may be controlled by software and may be used to receive I / O signals that are not committed to a specific role.
[0126] SoC 704 may also include a wide range of peripheral interfaces to enable communication with peripherals, audio codecs, power management and / or other devices. SoC 704 may be used to process data from cameras (connected via Gigabit multimedia serial links and Ethernet), sensors (e.g., LIDAR sensor 764, RADAR sensor 760, etc., which may be connected via Ethernet), data from bus 702 (e.g., speed of vehicle 700, steering wheel position, etc.), data from GNSS sensor 758 (connected via Ethernet or CAN bus). SoC 704 may also include dedicated high-performance mass storage controllers, which may include their own DMA engines, and which may be used to free up CPU 706 from routine data management tasks.
[0127] SoC 704 can be an end-to-end platform with a flexible architecture that spans automation levels 3-5, providing a comprehensive functional safety architecture that leverages and efficiently uses computer vision and ADAS technologies to achieve diversity and redundancy, together with deep learning tools to provide a platform for a flexible and reliable driving software stack. SoC 704 can be faster, more reliable, and even more energy efficient and space efficient than conventional systems. For example, when combined with CPU 706, GPU 708, and data storage 716, accelerator 714 can provide a fast and efficient platform for level 3-5 autonomous vehicles.
[0128] The technology thus provides capabilities and functionality that cannot be achieved by conventional systems. For example, computer vision algorithms can be executed on CPUs, which can be configured using high-level programming languages such as the C programming language to execute a wide variety of processing algorithms across a wide variety of visual data. However, CPUs often fail to meet the performance requirements of many computer vision applications, such as those related to, for example, execution time and power consumption. In particular, many CPUs are unable to execute complex object detection algorithms in real time, which is a requirement for in-vehicle ADAS applications and a requirement for practical Level 3-5 autonomous vehicles.
[0129] In contrast to conventional systems, by providing a CPU complex, a GPU complex, and a hardware acceleration cluster, the techniques described herein allow multiple neural networks to be executed simultaneously and / or sequentially, and the results to be combined together to achieve Level 3-5 autonomous driving functions. For example, a CNN executed on a DLA or dGPU (e.g., GPU 720) may include text and word recognition, allowing the supercomputer to read and understand traffic signs, including signs for which a neural network has not been specifically trained. The DLA may also include a neural network that can recognize, interpret, and provide semantic understanding of the signs, and pass that semantic understanding to a path planning module running on the CPU complex.
[0130] As another example, as required for Level 3, 4, or 5 driving, multiple neural networks may be running simultaneously. For example, a warning sign consisting of "Caution: Flashing Lights Indicate Icing Conditions" along with electric lights may be interpreted by several neural networks independently or collectively. The sign itself may be recognized as a traffic sign by a deployed first neural network (e.g., a trained neural network), and the text "Flashing Lights Indicate Icing Conditions" may be interpreted by a deployed second neural network that informs the vehicle's path planning software (preferably executing on a CPU complex) that icing conditions exist when the flashing lights are detected. The flashing lights may be identified by operating a deployed third neural network over multiple frames that informs the vehicle's path planning software of the presence (or absence) of the flashing lights. All three neural networks may be running simultaneously, for example, within the DLA and / or on the GPU 708.
[0131] In some examples, a CNN for facial recognition and owner recognition can use data from the camera sensor to identify the presence of an authorized driver and / or owner of the vehicle 700. The always-on sensor processing engine can be used to unlock the vehicle and turn on the lights when the owner approaches the driver's door, and in security mode, disable the vehicle when the owner leaves the vehicle. In this way, the SoC 704 provides security against theft and / or carjacking.
[0132] In another example, a CNN for emergency vehicle detection and identification can use data from microphone 796 to detect and identify emergency vehicle sirens. In contrast to conventional systems that use general classifiers to detect sirens and manually extract features, SoC 704 uses CNN to classify environmental and urban sounds and to classify visual data. In a preferred embodiment, the CNN running on the DLA is trained to identify the relative closing rate of emergency vehicles (e.g., by using the Doppler effect). The CNN can also be trained to identify emergency vehicles specific to the local area in which the vehicle is operating, as identified by the GNSS sensor 758. Thus, for example, when operating in Europe, the CNN will seek to detect European sirens, and when in the United States, the CNN will seek to identify only North American sirens. Once an emergency vehicle is detected, with the assistance of the ultrasonic sensor 762, the control program can be used to execute emergency vehicle safety routines to slow the vehicle, drive to the side of the road, stop the vehicle, and / or idle the vehicle until the emergency vehicle passes.
[0133] The vehicle may include a CPU 718 (e.g., a discrete CPU or dCPU) that may be coupled to the SoC 704 via a high-speed interconnect (e.g., PCIe). The CPU 718 may include, for example, an X86 processor. The CPU 718 may be used to perform any of a variety of functions, including, for example, arbitrating potentially inconsistent results between ADAS sensors and the SoC 704, and / or monitoring the status and health of the controller 736 and / or the infotainment SoC 730.
[0134] The vehicle 700 may include a GPU 720 (e.g., a discrete GPU or dGPU) that may be coupled to the SoC 704 via a high-speed interconnect (e.g., NVIDIA's NVLINK). The GPU 720 may provide additional artificial intelligence functionality, for example, by executing redundant and / or different neural networks, and may be used to train and / or update the neural network based at least in part on input from sensors of the vehicle 700 (e.g., sensor data).
[0135] The vehicle 700 may also include a network interface 724, which may include one or more wireless antennas 726 (e.g., one or more wireless antennas for different communication protocols, such as cellular antennas, Bluetooth antennas, etc.). The network interface 724 can be used to enable wireless connections with the cloud (e.g., with a server 778 and / or other network devices), with other vehicles, and / or with computing devices (e.g., a passenger's client device) via the Internet. In order to communicate with other vehicles, a direct link can be established between the two vehicles, and / or an indirect link can be established (e.g., across a network and through the Internet). The direct link can be provided using a vehicle-to-vehicle communication link. The vehicle-to-vehicle communication link can provide the vehicle 700 with information about vehicles approaching the vehicle 700 (e.g., vehicles in front of, to the side of, and / or behind the vehicle 700). This functionality can be part of the collaborative adaptive cruise control functionality of the vehicle 700.
[0136] The network interface 724 may include a SoC that provides modulation and demodulation functions and enables the controller 736 to communicate over a wireless network. The network interface 724 may include a radio frequency front end for up-conversion from baseband to radio frequency and down-conversion from radio frequency to baseband. The frequency conversion may be performed by a known process and / or may be performed using a super-heterodyne process. In some examples, the radio frequency front end function may be provided by a separate chip. The network interface may include a wireless function for communicating via LTE, WCDMA, UMTS, GSM, CDMA2000, Bluetooth, Bluetooth LE, Wi-Fi, Z-wave, ZigBee, LoRaWAN, and / or other wireless protocols.
[0137] The vehicle 700 may also include data storage 728, which may include an off-chip (e.g., external to the SoC 704) storage device. The data storage 728 may include one or more storage elements, including RAM, SRAM, DRAM, VRAM, flash memory, a hard disk, and / or other components and / or devices that can store at least one bit of data.
[0138] The vehicle 700 may also include a GNSS sensor 758 (e.g., GPS and / or assisted GPS sensor) for assisting with mapping, perception, occupancy grid generation, and / or path planning functions. Any number of GNSS sensors 758 may be used, including, for example and without limitation, GPS using a USB connector with an Ethernet to serial (RS-232) bridge.
[0139] The vehicle 700 may also include a RADAR sensor 760. The RADAR sensor 760 may be used by the vehicle 700 for remote vehicle detection even in darkness and / or inclement weather conditions. The RADAR functional safety level may be ASIL B. The RADAR sensor 760 may use CAN and / or bus 702 (e.g., to transmit data generated by the RADAR sensor 760) for control and access to object tracking data, accessing Ethernet in some examples to access raw data. A variety of RADAR sensor types may be used. For example and without limitation, the RADAR sensor 760 may be suitable for front, rear, and side RADAR use. In some examples, a pulse Doppler RADAR sensor is used.
[0140] The RADAR sensor 760 may include different configurations, such as long-range with a narrow field of view, short-range with a wide field of view, short-range side coverage, and the like. In some examples, the long-range RADAR may be used for adaptive cruise control functions. The long-range RADAR system may provide a wide field of view (e.g., within a range of 250m) achieved by two or more independent scans. The RADAR sensor 760 may help distinguish between static and moving objects and may be used by the ADAS system for emergency brake assistance and forward collision warnings. The long-range RADAR sensor may include a single-station multimode RADAR with multiple (e.g., six or more) fixed RADAR antennas and high-speed CAN and FlexRay interfaces. In an example with six antennas, the central four antennas may create a focused beam pattern designed to record the surroundings of the vehicle 700 at a higher rate with minimal traffic interference from adjacent lanes. The other two antennas may expand the field of view, making it possible to quickly detect vehicles entering or leaving the lane of the vehicle 700.
[0141] As an example, a medium-range RADAR system may include a range of up to 760m (front) or 80m (rear) and a field of view of up to 42 degrees (front) or 750 degrees (rear). A short-range RADAR system may include, but is not limited to, a RADAR sensor designed to be mounted on both ends of a rear bumper. When mounted on both ends of a rear bumper, such a RADAR sensor system may create two beams that continuously monitor the blind spots behind and beside the vehicle.
[0142] Short-range RADAR systems can be used in ADAS systems for blind spot detection and / or lane change assistance.
[0143] The vehicle 700 may also include an ultrasonic sensor 762. The ultrasonic sensor 762, which may be placed on the front, rear, and / or sides of the vehicle 700, may be used for parking assistance and / or creating and updating an occupancy grid. A variety of ultrasonic sensors 762 may be used, and different ultrasonic sensors 762 may be used for different detection ranges (e.g., 2.5 m, 4 m). The ultrasonic sensor 762 may operate at a functional safety level of ASILB.
[0144] The vehicle 700 may include a LIDAR sensor 764. The LIDAR sensor 764 may be used for object and pedestrian detection, emergency braking, collision avoidance, and / or other functions. The LIDAR sensor 764 may be ASIL B for functional safety level. In some examples, the vehicle 700 may include multiple LIDAR sensors 764 (e.g., two, four, six, etc.) that may use Ethernet (e.g., to provide data to a Gigabit Ethernet switch).
[0145] In some examples, the LIDAR sensor 764 may be able to provide a list of objects and their distances for a 360-degree field of view. Commercially available LIDAR sensors 764 may have, for example, an advertised range of approximately 100m, an accuracy of 2cm-3cm, and support for 100Mbps Ethernet connections. In some examples, one or more non-protruding LIDAR sensors 764 may be used. In such examples, the LIDAR sensor 764 may be implemented as a small device that can be embedded in the front, back, side, and / or corner of the vehicle 700. In such examples, the LIDAR sensor 764 may provide a field of view of up to 120 degrees horizontally and 35 degrees vertically, with a range of 200m, even for low reflectivity objects. The front-mounted LIDAR sensor 764 may be configured for a horizontal field of view between 45 and 135 degrees.
[0146] In some examples, LIDAR technologies such as 3D flash LIDAR may also be used. 3D flash LIDAR uses flashes of laser as an emission source to illuminate the vehicle's surroundings up to about 200m. The flash LIDAR unit includes a receiver that records the laser pulse transmission time and reflected light on each pixel, which in turn corresponds to the range from the vehicle to the object. Flash LIDAR can allow highly accurate and distortion-free images of the surrounding environment to be generated with each laser flash. In some examples, four flash LIDAR sensors can be deployed, one on each side of the vehicle 700. Available 3D flash LIDAR systems include solid-state 3D staring array LIDAR cameras (e.g., non-scanning LIDAR devices) with no moving parts other than fans. The flash LIDAR device can use 5 nanosecond Class I (eye-safe) laser pulses per frame, and can capture the reflected laser light in the form of a 3D range point cloud and co-registered intensity data. By using flash LIDAR, and because flash LIDAR is a solid-state device with no moving components, the LIDAR sensor 764 may be less susceptible to motion blur, vibration, and / or shock.
[0147] The vehicle may also include an IMU sensor 766. In some examples, the IMU sensor 766 may be located at the center of the rear axle of the vehicle 700. The IMU sensor 766 may include, for example and without limitation, an accelerometer, a magnetometer, a gyroscope, a magnetic compass, and / or other sensor types. In some examples, for example, in a six-axis application, the IMU sensor 766 may include an accelerometer and a gyroscope, while in a nine-axis application, the IMU sensor 766 may include an accelerometer, a gyroscope, and a magnetometer.
[0148] In some embodiments, the IMU sensor 766 can be implemented as a miniature high-performance GPS-assisted inertial navigation system (GPS / INS) that combines a micro-electromechanical system (MEMS) inertial sensor, a high-sensitivity GPS receiver, and an advanced Kalman filter algorithm to provide estimates of position, velocity, and attitude. Thus, in some examples, the IMU sensor 766 can enable the vehicle 700 to estimate heading by directly observing and correlating velocity changes from the GPS to the IMU sensor 766 without the need for input from a magnetic sensor. In some examples, the IMU sensor 766 and the GNSS sensor 758 can be combined into a single integrated unit.
[0149] The vehicle may include a microphone 796 positioned in and / or around the vehicle 700. The microphone 796 may be used for, among other things, emergency vehicle detection and identification.
[0150] The vehicle may also include any number of camera types, including a stereo camera 768, a wide-angle camera 770, an infrared camera 772, a surround camera 774, a long-range and / or mid-range camera 798, and / or other camera types. These cameras can be used to capture image data around the entire periphery of the vehicle 700. The type of camera used depends on the embodiment and the requirements of the vehicle 700, and any combination of camera types can be used to provide the necessary coverage around the vehicle 700. In addition, the number of cameras can vary depending on the embodiment. For example, the vehicle may include six cameras, seven cameras, ten cameras, twelve cameras, and / or another number of cameras. As an example and not limitation, the cameras can support Gigabit Multimedia Serial Link (GMSL) and / or Gigabit Ethernet. Each of the cameras described herein may include a 10GbE compliant wireless communications interface (NFC) interface. Fig. 7A and Figure 7B Described in more detail.
[0151] The vehicle 700 may also include a vibration sensor 742. The vibration sensor 742 may measure vibrations of components of the vehicle, such as axles. For example, changes in vibration may indicate changes in the road surface. In another example, when two or more vibration sensors 742 are used, the difference between the vibrations may be used to determine friction or slip of the road surface (e.g., when there is a vibration difference between a powered drive shaft and a free-spinning shaft).
[0152] The vehicle 700 may include an ADAS system 738. In some examples, the ADAS system 738 may include a SoC. The ADAS system 738 may include autonomous / adaptive / automatic cruise control (ACC), cooperative adaptive cruise control (CACC), forward collision warning (FCW), automatic emergency braking (AEB), lane departure warning (LDW), lane keeping assist (LKA), blind spot warning (BSW), rear cross traffic warning (RCTW), collision warning system (CWS), lane centering (LC), and / or other features and functions.
[0153] The ACC system may use a RADAR sensor 760, a LIDAR sensor 764, and / or a camera. The ACC system may include a longitudinal ACC and / or a lateral ACC. The longitudinal ACC monitors and controls the distance to the vehicle immediately in front of the vehicle 700, and automatically adjusts the vehicle speed to maintain a safe distance from the vehicle in front. The lateral ACC performs distance keeping and suggests that the vehicle 700 change lanes when necessary. The lateral ACC is related to other ADAS applications such as LC and CWS.
[0154] CACC uses information from other vehicles, which can be received from other vehicles indirectly via a wireless link or through a network connection (e.g., through the Internet) via a network interface 724 and / or a wireless antenna 726. A direct link can be provided by a vehicle-to-vehicle (V2V) communication link, while an indirect link can be an infrastructure-to-vehicle (I2V) communication link. Typically, the V2V communication concept provides information about the vehicle immediately ahead (e.g., the vehicle immediately ahead of the vehicle 700 and in the same lane as it), while the I2V communication concept provides information about traffic farther ahead. The CACC system may include either or both of the I2V and V2V information sources. Given information about the vehicle ahead of the vehicle 700, CACC can be more reliable, and it is possible to improve the smoothness of traffic flow and reduce road congestion.
[0155] The FCW system is designed to alert the driver to hazards so that the driver can take corrective action. The FCW system uses a front camera and / or RADAR sensor 760 coupled to a dedicated processor, DSP, FPGA and / or ASIC, which is electrically coupled to driver feedback such as a display, speaker and / or vibration component. The FCW system can provide warnings in the form of, for example, sound, visual warnings, vibrations and / or rapid brake pulses.
[0156] The AEB system detects an impending front collision with another vehicle or other object and can automatically apply the brakes if the driver does not take corrective action within specified time or distance parameters. The AEB system can use a front camera and / or RADAR sensor 760 coupled to a dedicated processor, DSP, FPGA and / or ASIC. When the AEB system detects a hazard, it typically first alerts the driver to take corrective action to avoid the collision, and if the driver does not take corrective action, the AEB system can automatically apply the brakes in an effort to prevent or at least mitigate the effects of the predicted collision. The AEB system may include technologies such as dynamic brake support and / or collision approach braking.
[0157] The LDW system provides visual, audible, and / or tactile warnings, such as steering wheel or seat vibrations, to alert the driver when the vehicle 700 crosses a lane marking. When the driver indicates an intention to leave the lane, by activating a turn signal, the LDW system is not activated. The LDW system may use a front-facing camera coupled to a dedicated processor, DSP, FPGA, and / or ASIC that is electrically coupled to driver feedback such as a display, speaker, and / or vibration assembly.
[0158] The LKA system is a variation of the LDW system. If the vehicle 700 begins to leave the lane, the LKA system provides steering input or braking to correct the vehicle 700.
[0159] The BSW system detects and warns the driver of vehicles in the car's blind spot. The BSW system can provide visual, auditory and / or tactile alerts to indicate that it is unsafe to merge or change lanes. The system can provide additional warnings when the driver uses a turn signal. The BSW system can use a rear-facing camera and / or RADAR sensor 760 coupled to a dedicated processor, DSP, FPGA and / or ASIC, which is electrically coupled to driver feedback such as a display, speaker and / or vibration component.
[0160] The RCTW system can provide visual, audible, and / or tactile notifications when an object is detected outside the range of the rear camera while the vehicle 700 is in reverse. Some RCTW systems include AEB to ensure that the vehicle brakes are applied to avoid a crash. The RCTW system can use one or more rear RADAR sensors 760 coupled to a dedicated processor, DSP, FPGA, and / or ASIC that is electrically coupled to driver feedback such as a display, speaker, and / or vibration assembly.
[0161] Conventional ADAS systems may be prone to false positive results, which may annoy and distract the driver, but are typically not catastrophic because the ADAS system alerts the driver and allows the driver to decide whether the safety condition really exists and take action accordingly. However, in the autonomous vehicle 700, in the case of conflicting results, the vehicle 700 itself must decide whether to pay attention to the results from the main computer or the auxiliary computer (e.g., the first controller 736 or the second controller 736). For example, in some embodiments, the ADAS system 738 can be a backup and / or auxiliary computer for providing perception information to the backup computer rationality module. The backup computer rationality monitor can run redundant and diverse software on hardware components to detect faults in perception and dynamic driving tasks. The output from the ADAS system 738 can be provided to the supervisory MCU. If the outputs from the main computer and the auxiliary computer conflict, the supervisory MCU must determine how to coordinate the conflict to ensure safe operation.
[0162] In some examples, the master computer can be configured to provide a confidence score to the supervisory MCU, indicating the master computer's confidence in the selected result. If the confidence score exceeds a threshold, the supervisory MCU can follow the direction of the master computer, regardless of whether the auxiliary computer provides conflicting or inconsistent results. In the case where the confidence score does not meet the threshold and the master computer and the auxiliary computer indicate different results (e.g., conflicts), the supervisory MCU can arbitrate between these computers to determine the appropriate result.
[0163] The supervisory MCU may be configured to run a neural network that is trained and configured to determine conditions under which the auxiliary computer provides a false alarm based, at least in part, on outputs from the primary computer and the auxiliary computer. Thus, the neural network in the supervisory MCU may learn when the output of the auxiliary computer may be trusted and when it may not. For example, when the auxiliary computer is a RADAR-based FCW system, the neural network in the supervisory MCU may learn when the FCW system is identifying a metal object that is not actually dangerous, such as a drainage grate or manhole cover that triggers an alarm. Similarly, when the auxiliary computer is a camera-based LDW system, the neural network in the supervisory MCU may learn to ignore the LDW when a cyclist or pedestrian is present and lane departure is actually the safest strategy. In an embodiment that includes a neural network running on the supervisory MCU, the supervisory MCU may include at least one of a DLA or a GPU suitable for running the neural network with associated memory. In a preferred embodiment, the supervisory MCU may include a component of the SoC 704 and / or be included as a component of the SoC 704.
[0164] In other examples, the ADAS system 738 may include an auxiliary computer that uses traditional computer vision rules to perform ADAS functions. In this way, the auxiliary computer can use classic computer vision rules (if-then), and the presence of a neural network in the supervisory MCU can improve reliability, safety, and performance. For example, diverse implementations and intentional non-identity make the entire system more fault-tolerant, especially for failures caused by software (or software-hardware interface) functions. For example, if there is a software vulnerability or error in the software running on the main computer and the non-identical software code running on the auxiliary computer provides the same overall result, the supervisory MCU can be more confident that the overall result is correct and that the vulnerability in the software or hardware used by the main computer does not cause a substantial error.
[0165] In some examples, the output of the ADAS system 738 can be fed to the perception block of the main computer and / or the dynamic driving task block of the main computer. For example, if the ADAS system 738 indicates a forward collision warning due to an object immediately ahead, the perception block can use this information in identifying the object. In other examples, the auxiliary computer can have its own neural network that is trained and thus reduces the risk of false positives as described herein.
[0166] The vehicle 700 may also include an infotainment SoC 730 (e.g., an in-vehicle infotainment system (IVI)). Although illustrated and described as an SoC, the infotainment system may not be an SoC and may include two or more discrete components. The infotainment SoC 730 may include a combination of hardware and software that can be used to provide audio (e.g., music, personal digital assistant, navigation instructions, news, radio, etc.), video (e.g., TV, movies, streaming, etc.), phone (e.g., hands-free calling), network connectivity (e.g., LTE, WiFi, etc.), and / or information services (e.g., navigation system, rear parking assistance, radio data system, vehicle-related information such as fuel level, total distance covered, brake fuel level, oil level, door open / closed, air filter information, etc.) to the vehicle 700. For example, the infotainment SoC 730 may include a radio, a disc player, a navigation system, a video player, USB and Bluetooth connections, an onboard computer, onboard entertainment, WiFi, steering wheel audio controls, hands-free voice controls, a head-up display (HUD), an HMI display 734, a telematics device, a control panel (e.g., for controlling and / or interacting with various components, features and / or systems), and / or other components. The infotainment SoC 730 may further be used to provide information (e.g., visual and / or auditory) to a user of the vehicle, such as information from an ADAS system 738, autonomous driving information such as planned vehicle maneuvers, trajectories, surrounding environment information (e.g., intersection information, vehicle information, road information, etc.), and / or other information.
[0167] The infotainment SoC 730 may include GPU functionality. The infotainment SoC 730 may communicate with other devices, systems, and / or components of the vehicle 700 via a bus 702 (e.g., a CAN bus, Ethernet, etc.). In some examples, the infotainment SoC 730 may be coupled to a supervisory MCU so that in the event of a failure of a master controller 736 (e.g., a main and / or backup computer of the vehicle 700), the GPU of the infotainment system may perform some self-driving functions. In such an example, the infotainment SoC 730 may place the vehicle 700 in a driver-safe parking mode as described herein.
[0168] The vehicle 700 may also include an instrument cluster 732 (e.g., a digital instrument panel, an electronic instrument cluster, a digital instrument panel, etc.). The instrument cluster 732 may include a controller and / or a supercomputer (e.g., a separate controller or a supercomputer). The instrument cluster 732 may include a set of instruments, such as a speedometer, a fuel level, an oil pressure, a tachometer, an odometer, a turn indicator, a shift position indicator, a seat belt warning light, a parking brake warning light, an engine fault light, an airbag (SRS) system information, a lighting control, a safety system control, navigation information, and the like. In some examples, information may be displayed and / or shared between the infotainment SoC 730 and the instrument cluster 732. In other words, the instrument cluster 732 may be included as part of the infotainment SoC 730, or vice versa.
[0169] Fig.7D For a cloud-based server and Fig. 7A Schematic diagram of a system for communicating between an example autonomous vehicle 700. System 776 may include a server 778, a network 790, and a vehicle including vehicle 700. Server 778 may include multiple GPUs 784 (A) -1284 (H) (collectively referred to as GPUs 784 here), PCIe switches 782 (A) -782 (H) (collectively referred to as PCIe switches 782 here), and / or CPUs 780 (A) -780 (B) (collectively referred to as CPUs 780 here). GPUs 784, CPUs 780, and PCIe switches may be interconnected with high-speed interconnects and / or PCIe connections 786 such as, for example and without limitation, NVLink interfaces 788 developed by NVIDIA. In some examples, GPUs 784 are connected via NVLink and / or NVSwitch SoCs, and GPUs 784 and PCIe switches 782 are connected via PCIe interconnects. Although eight GPUs 784, two CPUs 780, and two PCIe switches are illustrated, this is not intended to be limiting. Depending on the embodiment, each of the servers 778 may include any number of GPUs 784, CPUs 780, and / or PCIe switches. For example, each of the servers 778 may include eight, sixteen, thirty-two, and / or more GPUs 784.
[0170] Server 778 may receive image data over network 790 and from a vehicle, the image data representing images showing unexpected or changed road conditions, such as recently begun road work. Server 778 may transmit neural network 792, updated neural network 792, and / or map information 794, including information about traffic and road conditions, over network 790 and to the vehicle. Updates to map information 794 may include updates to HD map 722, such as information about construction sites, potholes, curves, flooding, or other obstacles. In some examples, neural network 792, updated neural network 792, and / or map information 794 may have been generated from new training and / or data received from any number of vehicles in the environment and / or based on experience from training performed at a data center (e.g., using server 778 and / or other servers).
[0171] Server 778 can be used to train a machine learning model (e.g., a neural network) based on training data. The training data can be generated by the vehicle, and / or can be generated in a simulation (e.g., using a game engine). In some examples, the training data is labeled (e.g., when the neural network benefits from supervised learning) and / or undergoes other preprocessing, while in other examples, the training data is not labeled and / or preprocessed (e.g., when the neural network does not require supervised learning). Training can be performed according to any one or more categories of machine learning techniques, including but not limited to, such as: supervised training, semi-supervised training, unsupervised training, self-learning, reinforcement learning, joint learning, transfer learning, feature learning (including principal component and cluster analysis), multilinear subspace learning, manifold learning, representation learning (including alternate dictionary learning), rule-based machine learning, anomaly detection, and any variant or combination thereof. Once the machine learning model is trained, the machine learning model can be used by the vehicle (e.g., transmitted to the vehicle via network 790), and / or the machine learning model can be used by server 778 to remotely monitor the vehicle.
[0172] In some examples, server 778 can receive data from the vehicle and apply the data to the latest real-time neural network for real-time intelligent reasoning. Server 778 may include a deep learning supercomputer and / or a dedicated AI computer powered by GPU 784, such as DGX and DGX Station machines developed by NVIDIA. However, in some examples, server 778 may include a deep learning infrastructure of a data center powered only by CPUs.
[0173] The deep learning infrastructure of server 778 may be capable of fast real-time inference, and may use this capability to assess and verify the health of the processors, software, and / or associated hardware in vehicle 700. For example, the deep learning infrastructure may receive periodic updates from vehicle 700, such as a sequence of images and / or objects located in the sequence of images that vehicle 700 has located (e.g., via computer vision and / or other machine learning object classification techniques). The deep learning infrastructure may run its own neural network to identify objects and compare them to the objects identified by vehicle 700, and if the results do not match and the infrastructure concludes that the AI in vehicle 700 has failed, then server 778 may transmit a signal to vehicle 700 instructing the fail-safe computer of vehicle 700 to take control, notify passengers, and complete a safe parking maneuver.
[0174] For reasoning, the server 778 may include a GPU 784 and one or more programmable reasoning accelerators (e.g., NVIDIA's TensorRT 3). The combination of GPU-powered servers and reasoning acceleration can make real-time responses possible. In other examples, such as when performance is not so important, CPU, FPGA, and other processor-powered servers can be used for reasoning.
[0175] Example computing device
[0176] Figure 8 8 is a block diagram of an example one or more computing devices 800 suitable for implementing some embodiments of the present disclosure. The computing device 800 may include an interconnect system 802 that directly or indirectly couples the following devices: memory 804, one or more central processing units (CPUs) 806, one or more graphics processing units (GPUs) 808, communication interfaces 810, I / O ports 812, input / output components 814, power supplies 816, and one or more presentation components 818 (e.g., displays), and one or more logic units 820.
[0177] although Figure 8 The various blocks of are shown as being connected via an interconnect system 802 having wires, but this is not intended to be limiting and is merely for clarity. For example, in some embodiments, a presentation component 818 such as a display device may be considered an I / O component 814 (e.g., if the display is a touch screen). As another example, the CPU 806 and / or the GPU 808 may include memory (e.g., the memory 804 may represent a storage device in addition to the memory of the GPU 808, the CPU 806, and / or other components). In other words, Figure 8The computing devices in the description are merely illustrative. No distinction is made between categories such as "workstations," "servers," "laptops," "desktops," "tablets," "client devices," "mobile devices," "handheld devices," "game consoles," "electronic control units (ECUs)," "virtual reality systems," "augmented reality systems," and / or other device or system types, as all of these are considered Figure 8 within the range of computing devices.
[0178] The interconnection system 802 may represent one or more links or buses, such as an address bus, a data bus, a control bus, or a combination thereof. The interconnection system 802 may include one or more bus or link types, such as an industry standard architecture (ISA) bus, an extended industry standard architecture (EISA) bus, a video electronics standard association (VESA) bus, a peripheral component interconnect (PCI) bus, a peripheral component interconnect express (PCIe) bus, and / or another type of bus or link. In some embodiments, there is a direct connection between components. As an example, the CPU 806 may be directly connected to the memory 804. Further, the CPU 806 may be directly connected to the GPU 808. In the case where there is a direct connection or a point-to-point connection between components, the interconnection system 802 may include a PCIe link for performing the connection. In these examples, the PCI bus does not need to be included in the computing device 800.
[0179] The memory 804 may include any of a variety of computer-readable media. Computer-readable media may be any available media that can be accessed by the computing device 800. Computer-readable media may include volatile and nonvolatile media and removable and non-removable media. By way of example and not limitation, computer-readable media may include computer storage media and communication media.
[0180] Computer storage media may include volatile and nonvolatile media and / or removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, and / or other data types. For example, memory 804 may store computer-readable instructions (e.g., representing programs and / or program elements, such as an operating system). Computer storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other storage technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage devices, cassettes, magnetic tape, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by computing device 800. As used herein, computer storage media does not include the signals themselves.
[0181] Computer storage media may contain computer readable instructions, data structures, program modules, and / or other data types in a modulated data signal such as a carrier wave or other transmission mechanism, and include any information delivery media. The term "modulated data signal" may refer to a signal that has one or more of its characteristics set or changed in such a way that information is encoded into the signal. By way of example and not limitation, computer storage media may include wired media such as a wired network or a direct wired connection, and wireless media such as sound, RF, infrared, and other wireless media. Any combination of the above should also be included within the scope of computer readable media.
[0182] The CPU 806 may be configured to execute at least some computer-readable instructions to control one or more components of the computing device 800 to perform one or more of the methods and / or processes described herein. Each of the CPUs 806 may include one or more cores (e.g., one, two, four, eight, twenty-eight, seventy-two, etc.) capable of simultaneously processing a large number of software threads. The CPU 806 may include any type of processor, and may include different types of processors, depending on the type of computing device 800 implemented (e.g., a processor with fewer cores for mobile devices and a processor with more cores for servers). For example, depending on the type of computing device 800, the processor may be an Advanced RISC Machine (ARM) processor implemented using Reduced Instruction Set Computing (RISC) or an x86 processor implemented using Complex Instruction Set Computing (CISC). The computing device 800 may also include one or more CPUs 806 in addition to one or more microprocessors or supplementary coprocessors such as math coprocessors.
[0183] In addition to or as an alternative to the CPU 806, the GPU 808 may be configured to execute at least some of the computer-readable instructions to control one or more components of the computing device 800 to perform one or more of the methods and / or processes described herein. One or more of the GPUs 808 may be an integrated GPU (e.g., where one or more of the CPUs 806 and / or one or more of the GPUs 808 may be a discrete GPU). In an embodiment, one or more of the one or more GPUs 808 may be a coprocessor of one or more of the one or more CPUs 806. The GPU 808 may be used by the computing device 800 to render graphics (e.g., 3D graphics) or perform general-purpose computing. For example, one or more GPUs 808 may be used for general-purpose computing (GPGPU) on a GPU. The GPU 808 may include hundreds or thousands of cores capable of processing hundreds or thousands of software threads simultaneously. The GPU 808 may generate pixel data for outputting an image in response to a rendering command (e.g., a rendering command from the CPU 806 received via a host interface). GPU 808 may include graphics memory such as display memory for storing pixel data or any other suitable data (such as GPGPU data). Display memory may be included as part of memory 804. GPU 808 may include two or more GPUs operating in parallel (e.g., via a link). The link may directly connect the GPU (e.g., using NVLINK) or may connect the GPU through a switch (e.g., using NVSwitch). When combined together, each GPU 808 may generate pixel data or GPGPU data for different parts of output or for different outputs (e.g., a first GPU for a first image and a second GPU for a second image). Each GPU may include its own memory, or may share memory with other GPUs.
[0184] In addition to or as an alternative to the CPU 806 and / or the GPU 808, the logic unit 820 may be configured to execute at least some of the computer-readable instructions to control one or more components of the computing device 800 to perform one or more of the methods and / or processes described herein. In an embodiment, the one or more CPUs 806, the one or more GPUs 808, and / or the one or more logic units 820 may perform any combination of methods, processes, and / or portions thereof, separately or jointly. One or more of the logic units 820 may be a part of and / or integrated into one or more of the CPUs 806 and / or the GPUs 808, and / or one or more of the logic units 820 may be a discrete component or otherwise external to the CPUs 806 and / or the GPUs 808. In an embodiment, one or more of the logic units 820 may be a coprocessor of one or more of the CPUs 806 and / or the GPUs 808.
[0185] Examples of logic unit 820 include one or more processing cores and / or components thereof, such as a tensor core (TC), a tensor processing unit (TPU), a pixel vision core (PVC), a vision processing unit (VPU), a graphics processing cluster (GPC), a texture processing cluster (TPC), a streaming multiprocessor (SM), a tree traversal unit (TTU), an artificial intelligence accelerator (AIA), a deep learning accelerator (DLA), an arithmetic logic unit (ALU), an application specific integrated circuit (ASIC), a floating point unit (FPU), an I / O element, a peripheral component interconnect (PCI) or a peripheral component interconnect express (PCIe) element, etc.
[0186] The communication interface 810 may include one or more receivers, transmitters, and / or transceivers that enable the computing device 800 to communicate with other computing devices via an electronic communication network, including wired and / or wireless communications. The communication interface 810 may include components and functionality that enable communication over any of a number of different networks, such as a wireless network (e.g., Wi-Fi, Z-wave, Bluetooth, Bluetooth LE, ZigBee, etc.), a wired network (e.g., via Ethernet or Infiniband communications), a low power wide area network (e.g., LoRaWAN, SigFox, etc.), and / or the Internet.
[0187] The I / O ports 812 can enable the computing device 800 to be logically coupled to other devices including I / O components 814, presentation components 818, and / or other components, some of which can be built into (e.g., integrated into) the computing device 800. Illustrative I / O components 814 include microphones, mice, keyboards, joysticks, game pads, game controllers, satellite dishes, scanners, printers, wireless devices, and the like. The I / O components 814 can provide a natural user interface (NUI) that processes air gestures, voice, or other physiological inputs generated by a user. In some examples, the input can be transmitted to an appropriate network element for further processing. The NUI can implement any combination of voice recognition, stylus recognition, facial recognition, biometric recognition, gesture recognition on and adjacent to the screen, air gestures, head and eye tracking, and touch recognition associated with the display of the computing device 800 (as described in more detail below). The computing device 800 may include a depth camera such as a stereo camera system, an infrared camera system, an RGB camera system, touch screen technology, and combinations of these for gesture detection and recognition. Additionally, computing device 800 may include an accelerometer or gyroscope to enable motion detection (e.g., as part of an inertial measurement unit (IMU)). In some examples, the output of the accelerometer or gyroscope may be used by computing device 800 to render immersive augmented reality or virtual reality.
[0188] The power supply 816 may include a hardwired power supply, a battery power supply, or a combination thereof. The power supply 816 may provide power to the computing device 800 to enable the components of the computing device 800 to operate.
[0189] The presentation component 818 may include a display (e.g., a monitor, a touch screen, a television screen, a head-up display (HUD), other display types, or a combination thereof), a speaker, and / or other presentation components. The presentation component 818 may receive data from other components (e.g., GPU 808, CPU 806, etc.) and output the data (e.g., as an image, video, sound, etc.).
[0190] The present disclosure may be described in the general context of machine-usable instructions or computer codes executed by a computer or other machine such as a personal digital assistant or other handheld device, including computer-executable instructions such as program modules. Typically, program modules including routines, programs, objects, components, data structures, etc. refer to codes that perform specific tasks or implement specific abstract data types. The present disclosure may be practiced in a variety of system configurations, including handheld devices, consumer electronics, general-purpose computers, more specialized computing devices, etc. The present disclosure may also be practiced in a distributed computing environment in which tasks are performed by remote processing devices linked through a communication network.
[0191] At least one embodiment of the present disclosure may be described in terms of the following:
[0192] 1. A method comprising: causing one or more hardware components to generate at least one result value based at least on performing one or more diagnostic tests according to at least one diagnostic test mode; and using the at least one result value to detect one or more hardware faults associated with the one or more hardware components.
[0193] 2. The method of clause 1, further comprising: causing one or more corrective actions to be performed in response to detecting the one or more hardware failures.
[0194] 3. The method of clause 1 or 2, further comprising causing the one or more hardware components to generate the at least one result value based at least on providing one or more input values associated with the at least one diagnostic test mode to the one or more hardware components.
[0195] 4. A method as described in any of clauses 1-3, wherein the one or more hardware components include at least one tensor processor.
[0196] 5. The method of any of clauses 1-4, wherein the one or more hardware components are caused to generate the at least one result value according to a diagnostic frequency.
[0197] 6. The method as described in any of clauses 1-5 further includes: algorithmically generating a portion of the at least one diagnostic test mode based at least in part on a portion of the one or more hardware components, the portion of the at least one diagnostic test mode causing the portion of the one or more hardware components to execute one or more instructions in parallel.
[0198] 7. The method of any of clauses 1-6, further comprising: providing an indication of the one or more hardware failures.
[0199] 8. A method as described in any of clauses 1-7, wherein at least one diagnostic test mode is used to test one or more of the following: floating-point vector operations; integer-point vector operations; matrix multiplication operations; bit operations; memory operations; data path operations; asynchronous data operations; cache stride access operations; misaligned cache accesses; cache misses; operations after cache compression; or transmissions between the one or more hardware components and a host device.
[0200] 9. The method of any of clauses 1-8, further comprising: selecting the at least one diagnostic test pattern from a plurality of pre-existing diagnostic test patterns.
[0201] 10. A system for use with one or more hardware components and at least one network, the system comprising: one or more processing units; and a network interface, the network interface being used to connect the one or more processing units to the one or more hardware components via the at least one network, the one or more processing units being used to: transmit diagnostic information to the one or more hardware components via the network interface so that the one or more hardware components generate at least one result value based at least on performing one or more diagnostic tests according to at least one diagnostic test mode, receive result information from the one or more hardware components via the network interface at least partially based on the at least one result value; and use the result information to detect one or more hardware faults associated with the one or more hardware components.
[0202] 11. The system of clause 10, wherein the one or more processing units are to cause one or more corrective operations to be performed in response to detecting the one or more hardware failures.
[0203] 12. The system of clause 10 or 11, further comprising: one or more control components, the one or more control components being used to perform at least a portion of the one or more corrective operations.
[0204] 13. The system of any of clauses 10-12, wherein the diagnostic information comprises one or more input values associated with the at least one diagnostic test mode.
[0205] 14. The system as described in any of clauses 10-13 further comprises: at least one processor, the at least one processor including the one or more hardware components or connected to the one or more hardware components, the network interface being used to connect the one or more processing units to the one or more hardware components by connecting the one or more processing units to the at least one processor via the at least one network, the one or more hardware components including at least one tensor processor.
[0206] 15. The system of any of clauses 10-14, wherein the one or more processing units are configured to cause the one or more hardware components to generate the at least one result value according to a diagnosis frequency.
[0207] 16. A system as described in any of clauses 10-15, wherein the one or more processing units are used to: generate one or more of the at least one diagnostic test mode based at least in part on the one or more hardware components, at least a portion of the one or more generated patterns being used to cause at least a portion of the one or more hardware components to execute one or more instructions in parallel.
[0208] 17. The system of any of clauses 10-16, wherein the one or more processing units are configured to provide an indication of the one or more hardware failures.
[0209] 18. The system of any of clauses 10-17, wherein using the result information to detect the one or more hardware failures comprises comparing the at least one result value to at least one expected value associated with the at least one diagnostic test mode.
[0210] 19. A processor comprising: one or more processing units, wherein the one or more processing units are used to perform operations, the operations comprising: causing one or more hardware components to generate at least one result value by performing one or more diagnostic tests according to at least one diagnostic test mode; and using the at least one result value to detect one or more hardware faults associated with the one or more hardware components.
[0211] 20. A processor as described in clause 19, wherein the processor is included in at least one of the following: a control system for an autonomous or semi-autonomous machine; a perception system for an autonomous or semi-autonomous machine; a first system for performing simulation operations; a second system for performing deep learning operations; a third system implemented using an edge device; a fourth system implemented using a robot; a fifth system comprising one or more virtual machines (VMs); a sixth system implemented at least in part in a data center; a seventh system for performing digital twin operations; an eighth system for performing light transport simulations; a ninth system for performing collaborative content creation of 3D assets; a tenth system for performing conversational artificial intelligence operations; an eleventh system for generating synthetic data; a twelfth system for implementing a web-hosted service for detecting program workload inefficiencies; an application as an application programming interface (API); a thirteenth system implemented at least in part using cloud computing resources; or a fourteenth system for presenting one or more of virtual reality content, augmented reality content, or mixed reality content.
[0212] As used herein, the description of "and / or" about two or more elements should be interpreted as referring to only one element or a combination of elements. For example, "element A, element B and / or element C" may include only element A, only element B, only element C, element A and element B, element A and element C, element B and element C, or elements A, B and C. In addition, "at least one of element A or element B" may include at least one of element A, at least one of element B, or at least one of element A and at least one of element B. Further, "at least one of element A and element B" may include at least one of element A, at least one of element B, or at least one of element A and at least one of element B.
[0213] The subject matter of the present disclosure is described in detail herein to meet statutory requirements. However, the description itself is not intended to limit the scope of the present disclosure. On the contrary, the inventors have contemplated that the claimed subject matter may also be embodied in other ways to include steps different from the steps described herein in conjunction with other current or future technologies or combinations of similar steps. Moreover, although the terms "step" and / or "block" may be used herein to imply different elements of the method employed, these terms should not be interpreted as implying any particular order among or between the various steps disclosed herein, unless the order of the steps is explicitly described.
Claims
1. A method comprising: causing one or more hardware components to generate at least one result value based at least on performing one or more diagnostic tests according to at least one diagnostic test mode; as well as The at least one result value is used to detect one or more hardware faults associated with the one or more hardware components.
2. The method of claim 1, further comprising: One or more corrective operations are caused to be performed in response to detecting the one or more hardware failures.
3. The method of claim 1, further comprising: The one or more hardware components are caused to generate the at least one result value based at least on providing one or more input values associated with the at least one diagnostic test mode to the one or more hardware components.
4. The method of claim 1, wherein the one or more hardware components include at least one tensor processor. The method of claim 1 , wherein the one or more hardware components are caused to generate the at least one result value according to a diagnostic frequency.
6. The method of claim 1, further comprising: A portion of the at least one diagnostic test pattern is algorithmically generated based at least in part on a portion of the one or more hardware components, the portion of the at least one diagnostic test pattern causing the portion of the one or more hardware components to execute one or more instructions in parallel.
7. The method of claim 1, further comprising: An indication of the one or more hardware failures is provided.
8. The method of claim 1 , wherein the at least one diagnostic test mode is used to test one or more of the following: Floating point vector operations; Integer point vector operations; Matrix multiplication operations; Bit operations; Memory operations; Data path operations; Asynchronous data operations; Cache stride access operations; Misaligned cache accesses; cache access misses; Operations after cache compression; or Transmissions between the one or more hardware components and a host device.
9. The method of claim 1, further comprising: The at least one diagnostic test mode is selected from a plurality of pre-existing diagnostic test modes.
10. A system using one or more hardware components and at least one network, the system comprising: one or more processing units; as well as a network interface for connecting the one or more processing units to the one or more hardware components via the at least one network, the one or more processing units being configured to: transmitting diagnostic information to the one or more hardware components via the network interface to cause the one or more hardware components to generate at least one result value based at least on performing one or more diagnostic tests according to at least one diagnostic test mode, receiving, via the network interface, result information from the one or more hardware components based at least in part on the at least one result value; as well as The result information is used to detect one or more hardware failures associated with the one or more hardware components.
11. The system of claim 10, wherein the one or more processing units are configured to: One or more corrective operations are caused to be performed in response to detecting the one or more hardware failures.
12. The system of claim 11, further comprising: One or more control components for performing at least a portion of the one or more corrective operations.
13. The system of claim 10, wherein the diagnostic information comprises one or more input values associated with the at least one diagnostic test mode.
14. The system of claim 10, further comprising: at least one processor, the at least one processor comprising or connected to the one or more hardware components, the network interface being used to connect the one or more processing units to the one or more hardware components by connecting the one or more processing units to the at least one processor via the at least one network, the one or more hardware components comprising at least one tensor processor.
15. The system of claim 10, wherein the one or more processing units are configured to: The one or more hardware components are caused to generate the at least one result value according to a diagnosis frequency.
16. The system of claim 10, wherein the one or more processing units are configured to: One or more generated patterns of the at least one diagnostic test pattern are generated based at least in part on the one or more hardware components, at least a portion of the one or more generated patterns being used to cause at least a portion of the one or more hardware components to execute one or more instructions in parallel.
17. The system of claim 10, wherein the one or more processing units are configured to: An indication of the one or more hardware failures is provided.
18. The system of claim 10, wherein using the result information to detect the one or more hardware failures comprises: The at least one result value is compared to at least one expected value associated with the at least one diagnostic test mode.
19. A processor comprising: One or more processing units, the one or more processing units configured to perform operations, the operations comprising: causing one or more hardware components to generate at least one result value by performing one or more diagnostic tests according to at least one diagnostic test mode; and The at least one result value is used to detect one or more hardware faults associated with the one or more hardware components.
20. The processor of claim 19, wherein the processor is included in at least one of: control systems for autonomous or semi-autonomous machines; Perception systems for autonomous or semi-autonomous machines; a first system for performing simulation operations; a second system for performing deep learning operations; A third system implemented using edge devices; The fourth system is implemented using robots; a fifth system comprising one or more virtual machines VM; A sixth system implemented at least in part in a data center; a seventh system for performing digital twin operations; an eighth system for performing light transport simulations; A ninth system for performing collaborative content creation of 3D assets; a tenth system for performing conversational artificial intelligence operations; an eleventh system for generating synthetic data; a twelfth system for implementing a web-hosted service for detecting program workload inefficiencies; Applications as application programming interfaces (APIs); A thirteenth system implemented at least in part using cloud computing resources; or A fourteenth system for presenting one or more of virtual reality content, augmented reality content, or mixed reality content.
