https://open-source-silicon.dev logo
Join Slack
Powered by
********************************* Hello <!channel>...
# announcements
j
********************************* Hello <!channel> Just a reminder for the deadline for project submissions for GFMPW-0 is December 5, 2022 @ 11:59pm PST. There are some important updates for submitting projects to the shuttle: 1. A new tag 
gfmpw-0d
has been posted for caravel_user_project and mpw_precheck. 2. caravel_user_project wrapper macro has been modified to correct the power ring for integrating with Caravel. 3. You need to UPDATE YOUR PROJECT and RERUN OPENLANE in order for your project to successfully integrate with Caravel. 4. These instructions provide the steps needed to update an existing project from the previous tag ‘gfmpw-0b’. 5. mpw_precheck has been update to include an updated DRC check as well as density, GPIO defines and XOR checks. 6. You must update verilog/rtl/user_defines.v for each IO and specify a valid power-on default configuration. Precheck will fail without this. Please post to #gf180mcu with any questions. *********************************
m
@jeffdi was this supposed to include a link
4.These instructions provide the steps needed to update an existing project from the previous tag ‘gfmpw-0b’.
j
thx!
v
@Mitch Bailey my repo already got submitted. Can you guide me with git commands to merge 
gfmpw-0d
branch with my repo? Thanks
m
4 These instructions provide the steps needed to update an existing project from the previous tag ‘gfmpw-0b’.
👍 1
v
Tape out submission still not enabled right?
p
is that intentional?
I'll be applying the patches with:
Copy code
git remote add efabless 
git fetch efabless
git diff gfmpw-0b...gfmpw-0d openlane/ verilog/ Makefile  | git apply -3 -
to make sure I don't miss anything 🙂
j
@proppy where is this from? https://github.com/efabless/caravel_user_project/commit/17bbec35943e3072832f66aaa683693d95c21227 user_defines.v in the project is initialized with invalid values that need to be replaced by the user.
the git sequence above is good, but the curl statements in the instructions maybe easier for people. if someone has a project starting from 
gfmpw-0a
, they need more updates than just the 3 files in the instructions.
e
If you just use curl you are going to create a diverging history with the upstream repo
That means future commands will have to be rebased and face a much more difficult merge. Because there will be conflicting changes in the users branch and Efabless'
p
@jeffdi this commit (17bbec35) is on the gf180mcu branch, it's the commit on the gfmpw-0c tag
people will also need that file to be updated to correct the constant defined on top with the gf180mcu values (and if I'm not mistaken the instructions don't include instructions to get the new version)
@jeffdi you probably also need to update https://github.com/efabless/caravel_user_project/blob/gf180mcu/docs/source/index.rst to point to the new tag
and disable the template feature of the repo (because it will create a new repo with a single commit w/ no related history)
@Ethan Mahintorabi the instructions for gfmpw-0a (https://github.com/efabless/caravel_user_project/blob/gfmpw-0a/docs/source/index.rst) were using the GitHub template feature, so people wouldn't be able to do a regular "pull" from a repo with an unrelated history.
e
Ah, well that's unfortunate
p
(not saying I'm in favor of curling either, I'd prefer to provide people with the patch they can cleanly apply on their repo)
so that they can be sure they don't miss any changes that were made between the two reference tags, and get proper git conflict markers if they happen to have modified the affected files (
git apply -3
does that well apparently)
j
here is a patch for 
gfmpw-0b
to 
gfmpw-0d
caravel_user_project_gfmpw-0b_to_gfmpw-0d.patch
download and run 
git apply <patch_file>
@proppy what is the best way to distribute this?
i can also create one from 
gfmpw-0a
create a 
_patch
directory in the repo?
e
Add it to a github release
j
e
Yeah! Perfect
l
Saw the step "make user_proj_exampe" in the instructions. Is it must? We won't use that macro in our designs. So, why do we need to harden user_proj_exampe?
p
@Lab Lecture I think it basically was a way to say "re-harden your macro"
l
No, There is a catch.
Open in Slack
PreviousNext
Powered by