Is a new gds for the new module created in such a case and the project is accepted or does it yield the same gds that was already available?

@Vrushabh Damle Very good point. Not as simple an answer as you might hope. First,

user_project_wrapper.gds

is what gets integrated into caravel. I don’t think any other files are relevant (besides

verilog/rtl/user_defines.v

). Second, if you change

user_proj_example.v

but keep the same pins, you can use

user_project_wrapper.v

without changes. Third, even if you don’t change

user_project_wrapper.v

, you must remake the final

gds/user_project_wrapper.gds

to include the new

user_proj_example.gds

Thanks @Mitch Bailey for helping me out but I still don't understand it because the project had the original

user_proj_example

module and under it, they defined the new module but they had not instantiated the new module in the

user_proj_example

. So would the new gds file be according to the new module or the same as the old one given that both the modules are present in

user_proj_example.v

and neither of them are called in the other one

Which one does

user_project_wrapper.v

call?

The user_project_wrapper.v called for the module user_proj_example.

Unfortunately, the gds would pass the precheck and tapeout, but wouldn’t match the intended design. There have been talks about adding LVS to the precheck also, but there are many issues that need to be resolved (including runtime for designs with multiple sram blocks).

Thanks a lot for helping me out