emilgoh /  ThreePhase_PWM_Generator

Created
Maintained by emilgoh
With the increasing demand for renewable energy and automation with drones and robots, the three-phase PWM technique is an essential component in a chip to drive motors and manage power in power electronic systems, facilitating a smooth conversion of electrical energy.The design also included dead time, which is essential in preventing short circuits, thus enhancing the safety of systems.  |   https://github.com/emilgoh/pwm-caravel
Members 1
Emil Goh committed 11 months ago

Three-Phase Pulse Width Modulator (PWM) with Dead Time

Author: Emil Goh

Background

Three-phase PWM is a crucial technique to enable efficient and precise control of electrical energy in various applications. It is fundamental in driving motors and managing power systems to facilitate a smooth conversion of electrical energy. A three-phase PWM is especially important to control brushless DC motors.

As the world's demand for automation through robots and drones and renewable energy systems such as solar inverters and wind turbines, increases rapidly, the integration of this technique in chips even more important.

The design has also incorporated dead time which is essential in preventing short circuits, enhancing safety and reliability of the power electronic system.

Objective

To develop a three-phase PWM with dead time that can be integrated as a peripheral in the Caravel harness to control electrical energy for various power electronic systems, using ChatGPT-4 to generate the RTL of the design.

Circuit Design

The three-phase PWM circuit is designed to generate 3 PWM waveforms with its complementary signal (6 PWM waveforms altogether), each 120 degrees out of phase with the others. The duty cycle of the waveforms can also be adjusted by modifying the duty cycle input signal. Dead time is also introduced such that each of the PWM waveforms will not be toggled HIGH and LOW simultaneously, which could cause a short circuit. This ensures safe operation in applications when driving power electronics.

PWM Block Diagram

The overall circuit of the three-phase PWM can be seen above.

The three-phase PWM design can be broken down into the following components:

  1. Controls

    1. Signals
      1. Clock: Main clock signal to drive circuit
      2. Reset: To reset the circuit to the default state
      3. Enable: To activate and deactivate the circuit
    2. Duty Cycle Control
      1. Duty Cycle Input: Represents the desired PWM duty cycle
      2. Subtractor: Subtracts the input duty cycle with the counter resolution, inverting the input to the PWM comparators
  2. 3 PWMs, each consisting of the following:

    1. Up Counter: 8-bit counter (256 resolution), automatically resets to 0 after hitting 255
    2. Comparator: Compares the counter value with the subtracted duty cycle value to produce the PWM waveform
    3. D Flip Flop (DFF): To filter out unwanted transitions
  3. Phase Control (2 sets), each set consists of the following:

    1. “One-third” Comparator: Compares the previous PWM’s counter output with 33.3% of the counter resolution. As such, the comparator will only produce a HIGH signal when the previous counter reaches 85/256.
    2. S-R Latch: Used to sustain the HIGH signal produced by the “one-third” comparator

    The signal from the S-R latch is connected to the ENABLE input of the PWM. This results in the counter of the following PWM being activated, only when the previous counter reaches 33.3% of its resolution and produces a second PWM waveform with a 120-degree phase difference. This logic is applied to the third PWM.

  4. 3 Dead Time Generators, each consisting of the following:

    1. Shift Register (4 DFF cascaded together): delays each PWM output by 4 clock cycles
    2. AND gate: Produces the main PWM output
    3. NOR gate: Produces the complementary PWM output

    The dead time generator output is produced by inputting the PWM waveform from each PWM module and the delayed PWM waveform. It introduces a short delay between the turn-on and off times of the PWM signals to prevent overlaps.

    More information on how the implemented Dead Time Generator works: Dead Time Generator Operation

Pin-out

PWM Caravel GPIO Type
clk wb_clk_i input
rst wb_rst_i input
en io_in 23 input
duty_cycle io_in 24 - 31 input
pwm1_out io_out 32 output
pwm1_comp_out io_out 33 output
pwm2_out io_out 34 output
pwm2_comp_out io_out 35 output
pwm3_out io_out 36 output
pwm3_comp_out io_out 37 output

LLM Conversational Flowchart

The conversational flow used is inspired by ChipChat and AI by AI. LLM Conversation

The flowchart is designed such that the user will always be in the conversation loop until the design is satisfied. Apart from the error loop, there is also an improvement loop and thus, the user will only have to use one single GPT chat session to design their desired circuit.

However, it is recommended that each circuit is broken down into smaller components and developed in separate chats. From experience, it seems that ChatGPT does not remember every single bit of the conversation, and codes that are recalled might contain errors. By breaking the circuit into smaller parts, the conversation could be more manageable and less confusing for users.

In this case, two ChatGPT-4 chats were used. The first chat was used to design a single-phase PWM and the second was to improve and build on the existing single-phase PWM. Eventually, generating and developing a three-phase PWM with dead time. The links to the conversations can be found at the bottom of this section.

ChatGPT-4 with web browsing feature was used to design the three-phase PWM. This LLM was selected as it is known to be the best code generation model before fine-tuning. The web browsing feature was activated such that ChatGPT can search the web if it encounters unfamiliar prompts.

Custom Instruction and Initial Prompt

Following ChipChat’s method of prompting ChatGPT, it is essential to tune ChatGPT such that it will respond to prompts as expected.

Here is an example from the Three-Phase PWM conversation, instructing ChatGPT to respond like an IC designer in Verilog:

I want you to act as an IC designer, and implement the following in Verilog.

I am attempting to design a three-phase pulse width modulator (PWM).

Apart from that, the specifications of the design prompted to ChatGPT should be as detailed as possible.

Here is an example from the Single PWM conversation, prompting ChatGPT to generate the RTL of a single PWM module:

I am trying to create a Verilog model for a pulse width modulator (PWM). The pulse width modulator should contain the following components and the respective specifications:

  1. Up Counter:
  • Input: Clock, Reset
  • 8 bits
  • Counter should automatically reset after reaching 255
  1. Comparator:
  • Input: Duty Cycle of PWM, i.e. 128/256 for 50% duty cycle
  • Input: Output of Up Counter
  1. D Flip Flop:
  • Input: Clock, Reset
  • Input: Output of Comparator
  • Output: PWM signal

The components should be separated into different modules and later combined into a single PWM module.

ChatGPT was able to generate an RTL with some errors. This brings us to the error feedback loop so that ChatGPT could fix the error encountered.

Error Feedback Loop

A few feedbacks when faced with an error have been implemented. Firstly, the error message produced by the simulator is prompted to the GPT.

An example of the “error message” feedback from the Single PWM conversation would be as such:

There is an error on line 14 in the implementation.

It could also be pasted directly into the prompt. Here is an example of another error message:

this is the error message:
.v:50: error: reg count; cannot be driven by primitives or continuous assignment.
pwm.v:50: error: Output port expression must support continuous assignment.
pwm.v:50: : Port 3 (count) of UpCounter is connected to count
2 error(s) during elaboration.

When the same error persists even after prompting the error message, the user could carry on with human feedback. An example from the Single PWM conversation will be:

There is an extra semicolon at the end of the module.

The user could also prompt ChatGPT with a sample code. This is an example from the Three-Phase PWM conversation:If errors persist, the user can prompt the GPT with a sample code. This is an example from the Three-Phase PWM conversation:

This is an example code of an SR latch. Can you code according to this structure and logic?

module SR_latch(  
    input en, rst, S, R,  
    output reg Q  
);  
   
   always@(*) begin    
        if(rst) Q<= 1'b0;  
        else if(en) begin  
            case({S,R})  
                2'b00 : Q<= Q;  
                2'b01 : Q<= 1'b0;  
                2'b10 : Q<= 1'b1;  
                default : Q<=2'bxx;  
            endcase  
        end
    end  
endmodule  

By examining the logic and structure of the example code, ChatGPT would generate a code similar to the sample code, fitting it into the design.

Here is a sample of the generated code by ChatGPT to be fitted into the Three-Phase PWM design:

module SRLatch(
    input wire en,
    input wire rst,
    input wire set,
    input wire reset,
    output reg q
);

    always @(*) begin
        if (rst)
            q <= 1'b0;
        else if (en) begin
            case ({set, reset})
                2'b00 : q <= q;  // Retain previous state
                2'b01 : q <= 1'b0;  // Reset
                2'b10 : q <= 1'b1;  // Set
                default: q <= 1'bx;  // Undefined state
            endcase
        end
    end

endmodule

Improvement Loop

There has to be some form of improvement which ChatGPT could do after generating an RTL which has no errors and works as expected. It could also be a feature which was missed out in the previous prompt. Thus, having this improvement loop allows the user to repeat the generation of the RTL with desired improvements implemented without human intervention.

An improvement was made in the Single PWM conversation as the ENABLE signal was overlooked in the previous prompts.

Can you add an 'enable' signal in the PWM module?

ChatGPT was able to add the ENABLE signal to the existing code. The only downside to this is that the user has to simulate the generated code again to check for validity.

Links

Below are the links to the conversations with ChatGPT-4:

Single-Phase PWM: https://chat.openai.com/share/ff55a56d-56fa-400e-878d-bc47a241caec

Three-Phase PWM: https://chat.openai.com/share/6900a303-3c33-4b63-9cd5-74ca69348593

Simulation and Results

Simulation is done using iVerilog and viewed on GTKWave.

Below is the overview of the waveform as the duty cycle increases from 0% to 25%, 50%, and 75%. Wave Overview

As observed in the waveform below, when the duty cycle is set to 25%, there is a dead time of 4 clock cycles in between each transition. 25% Duty Cycle

The waveform changes when the duty cycle is adjusted. 75% Duty Cycle

The three-phase PWM with dead time is working as expected.

The VCD file can also be found here: Output Waveform .

Conclusion

The design generates 3 PWM with 3 complement signals, with a dead time of 4 clock cycles. It also passes the MPW precheck and tape-out processes on the Efabless platform with no error.

Reflection and Acknowledgement

Despite coming from an electrical engineering background, this is the first time I went through the entire IC design RTL to GDS (and maybe to chip) flow. It has been a refreshing and exciting experience to be a small part of this movement to democratise IC design by submitting a simple design for the AI-generated Open-Source Silicon Design Challenge.

I would like to use this opportunity to thank my mentor, Dr Teo Tee Hui, and Mr Xiang Mao Yang from the Singapore University of Technology and Design (SUTD) for their unwavering support and guidance. Also, a big thank you to the Efabless team who has made all these possible.

License UPRJ_CI Caravel Build

:exclamation: Important Note

Please fill in your project documentation in this README.md file

Refer to README for a quickstart of how to use caravel_user_project

Refer to README for this sample project documentation.

Refer to the following readthedocs for how to add cocotb tests to your project.

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.