@User has left the channel

@User has left the channel

@User has left the channel

Hello, does anyone have experience with SKY130 and BAG2 (in the same project). Thx

@yasuyuki saito has left the channel

Laygo2+Sky130+magic - collaboration between NiftyLab Hanyang University Korea and AC3E, Chile with Docker help from JKU, Austria. Hopefully bootcamp participants will be able to test and polish it until end of August. https://github.com/akiles-esta-usado/laygo2_iic.git

On Monday we start with Laygo2 onboarding, if interested to attend and try it out pls send me an email so that I can invite you to the channel. Thx.

NiftyLab members prepared Laygo2 onboarding material for us.

In case there's anyone else out there trying to understand / work with the BAG3 code base, I've spent several weeks now attempting to understand how it works and how to set it up. I'd love to talk shop with anybody who is similarly stuck and looking for a comrade.

@Kennedy Caisley I am involved in some with some others to liberate BAG3 from OpenAccess and support the open source tools. We have some basic proof of concept work but that is ongoing

Have you got anything up and running yet or still evaluating it?

@yrrapt I've made some progress on setting up a basic example repository, but I've been unable to get the tool working thus far. In particular, I'm stuck on how to properly build and import the pybag submodule. Have you had success with the development branch of BAG3? My day job requires Cadence tools (TSMC 28 nm), but on the side I'm very interested in helping with the development efforts to port the tool to open source alternatives. Is there a place where these porting discussions are taking place?

@Kennedy Caisley in theory you can just install it with pip. You can have a look at the very basic instructions I've put here: https://github.com/yrrapt/bag/tree/develop

But I assume you don't have access to the OpenAccess files in which it's not much use until we can finish the job of separation BAG and OpenAccess.

You can use BAG2 without OpenAccess source files coz it uses the skill interface to virtuoso

Great, thank you for the pointers @yrrapt. I've recloned the

bag3

develop branch on two separate machines, one with

CentOS 7.9

and the other with

Ubuntu 20.04.

On each, I built a fresh python venv, and tried compiling the

bag

and

pybag

modules. In each case, the

bag

modules built properly, but the sub-module

pybag

is problematic. I've tried to read the

CMakeLists.txt

and follow the error

build.log

, to find clues about what packages might be missing or variables not configured, but no luck so far. My machines have the following: CentOS 7.9 • Python 3.9.14 (built from source) • CMake 3.17.5 • fmt 8.22 • Boost 1.53.0 • gcc 7.3.1 Ubuntu 20.04 • Python 3.8.10 • CMake 3.16.3 • fmt 8.30 • Boost 1.71.0 • gcc 9.4.0 Running

python -m pip install .

, I'm seeing build logs that contain the error below.

in ./build.log
....
    CMake Error at cbag/CMakeLists.txt:94 (find_package):
      Could not find a package configuration file provided by "fmt" with any of
      the following names:
    
        fmtConfig.cmake
        fmt-config.cmake
    
      Add the installation prefix of "fmt" to CMAKE_PREFIX_PATH or set "fmt_DIR"
      to a directory containing one of the above files.  If "fmt" provides a
      separate development package or SDK, be sure it has been installed.
....

I think I need to point

CMake

toward my

fmt

and

spdlog

installs.

@Kennedy Caisley I also encountered cmake issues with fmt libraries and a few other items. I was building on Ubuntu. My modifications to the cmake configuration in the forked repo above should resolve those library issues. But regardless of that, the bluecheetah team and by extension Berkeley wireless group use the source or at least headers of the OpenAccess library. Note that this is not just the OpenAccess distributed binaries already shipped with virtuoso, it's more. It is prohibively difficult for most people to get access to this source code (despite the name "open"access), and I don't just mean individuals but most universities and companies also give up before getting this code. That's why I'm currently working on decoupling OpenAccess from BAG3 - it won't be as fully featured as the OpenAccess variant but it would be accesible

You can try cloning my forked repo and compile with OpenAccess enabled, it should resolve the cmake issues you see but will get stuck trying to find the OpenAccess source

@yrrapt Wow, okay. I didn't realize that BAG3 required this OpenAccess library. If I understand correctly, do you mean that even if one has Cadence Virtuoso licenses, they still don't necessarily have everything needed to make BAG3 function? I've read a couple papers using BAG (like this one, for example) from research groups outside UC Berkeley/BlueCheetah, but it appears they used BAG2, which I suppose didn't have this dependency on OA? This is frustrating, and also good motivation to invest time separating the BAG3 code base. Otherwise BAG will likely see very limited usage. Regarding my compilation misadventures: Building your forked BAG repository, the CMake

find_packge()

errors were resolved for

fmt

,

spdlog

, and

yaml-cpp

dependencies once I had installed the 'devel' variants of each from Ubuntu's repositories. However, I'm still seeing two errors: 1. On Line #46 of this file, there is a strange bit of code:

<<<<<<< HEAD

, which is throwing a parsing error. I'm not at all familiar with CMake syntax, but it looks like a typo? It doesn't appear in the equivalent file in the

ucb-art

repository. 2. CMake also complains of a missing a module called

FindPythonLibsNew

. It's doesn't sound like a standard package, and I'm not sure where I can acquire it from:

CMake Error at pybind11_generics/pybind11/tools/pybind11Tools.cmake:17 (find_package):
    By not providing "FindPythonLibsNew.cmake" in CMAKE_MODULE_PATH this
    project has asked CMake to find a package configuration file provided by
    "PythonLibsNew", but CMake did not find one.
  
    Could not find a package configuration file provided by "PythonLibsNew"
    with any of the following names:
  
      PythonLibsNewConfig.cmake
      pythonlibsnew-config.cmake
  
    Add the installation prefix of "PythonLibsNew" to CMAKE_PREFIX_PATH or set
    "PythonLibsNew_DIR" to a directory containing one of the above files.  If
    "PythonLibsNew" provides a separate development package or SDK, be sure it
    has been installed.
  Call Stack (most recent call first):
    pybind11_generics/pybind11/tools/pybind11Common.cmake:201 (include)
    pybind11_generics/pybind11/CMakeLists.txt:169 (include)

@Kennedy Caisley Yep, exactly, additional OpenAccess files are required on top of the standard Virtuoso installation. Yes, most people are using BAG2 right now. In fact that paper comes from @Mirjana Videnovic Misic who has initiated and supported a lot of the work trying to extend BAG both BAG2 and 3. That issue 1 is a git merge issues, the HEAD text is from a clash so I've not merged something correctly there, I will fix it. I'm not sure about the second one of the top of me head but I will look into it. Thanks for find these issues.

Hello I have recently started looking into BAG. I have a couple of questions: 1. Is BAG3 the stable version or should I start from BAG2 [ The repo of BAG3 looks as if it is left in the middle of work] 2. Is BAG mature enough to be integrated with other PDKs as well, I saw a repo of Sky130 with BAG. What was the result? Can I run sky130 on BAG? A good starting point would be great, if anyone has gone through the flow please let me know

Does anyone here have documentation on porting BAG to new process technologies?

Hello, last information is that BWRC (Berkeley Wireless Research lab) has published initial work-in-progress BAG3++ documentation. It mentions the instructions for installing the dependencies, the openly available workspaces, and some basic examples. BWRC students will keep adding more detailed explanations and more complicated examples, but the current version should be sufficient to get started. As the current main developer Ayan Biswas is soon graduating I will try to get contact point for reporting any bugs or missing information that you may encounter in the doc.

Ayan will add to the documentation page names of the main developers @Bob Zhou and @Felicia Guo - such they can be reached after he graduates. (I hope I have tagged the right names)

As for documentation about creating workspace for technologies other than given cds_ff_mpt and SKY130, Ayan mentioned that this might be the next document added to the page.

Developer's Guide: Setting up BAG 3++ in a new PDK https://bag3-readthedocs.readthedocs.io/en/latest/new_pdk_setup.html#

I believe there is already on GitHub technology related files for SKY130

however, for BAG3++ to work proprietary PDK is needed as virtuoso is still main engine.