Skip to content

Conversation

@angelinaaw
Copy link

No description provided.

@AL-255
Copy link
Contributor

AL-255 commented Jul 17, 2025

The second stage uses a discrete BJT? According to the specification, "The op-amp should be built using the GF180MCU technology." The second stage design is out-of-spec

@msaligane
Copy link
Member

@angelinaaw can you address these questions? also please link this issue to your team in the chipathon repo.

@angelinaaw
Copy link
Author

@angelinaaw can you address these questions? also please link this issue to your team in the chipathon repo.

Ok, thank you sir. I didn't get any notification for the previous question. I'll do it right away.

@angelinaaw
Copy link
Author

angelinaaw commented Jul 25, 2025

The second stage uses a discrete BJT? According to the specification, "The op-amp should be built using the GF180MCU technology." The second stage design is out-of-spec

Yes sir, thank you for pointing this out.
The original design in Xschem used the NPN transistor provided in the GF180 library. However, at that time, we couldn't run any simulations due to netlist and library errors, even though we had defined the models in the .sch file.
Since we were running out of time to meet the deadline, we decided to use the BJT model available in LTspice.

If it's not prohibited, we're willing to revise the design and update it accordingly so that it remains within spec.

@msaligane
Copy link
Member

@AL-255 @Subhampal9 Do you guys know if the BJT exists?

@msaligane
Copy link
Member

There are no BJT @angelinaaw and you probably want to make your own. There are hardcoded ones here: https://github.com/mabrains/globalfoundries-pdk-libs-gf180mcu_fd_pr_fossi/tree/main/cells/klayout/pymacros/cells/bjt

@angelinaaw
Copy link
Author

@msaligane Alright sir, thank you so much for the NPN and PNP cells file. However, actually our project that use BJT was only for this op-amp design challenge and might be not our main focus right now. Our main project (on main repo in sscs) doesn't use any of the BJT, but we might use it also for another project :). Our main repo is also a fork to sscs, should we make a new/separate fork to realmasic containing glayout things (list pcell, layout and phyton codes we've done, .gds file, etc)? Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants