Hi all I was trying to run the caravel_user_project_analog provided by efabless, the link to the github is https://github.com/efabless/caravel_user_project_analog/tree/main The documentation to this sample project is given in the link https://github.com/efabless/caravel_user_project_analog/blob/main/docs/source/index.rst Under the run full chip simulation section when I try to run the make verify-testbench-name command I get a permission denied error and when I run sudo make verify-testbench-name command I get the "no rule to make target" error. In the documentation they say that the verilog test-benches are under this directory verilog/dv, a screenshot of the same is attached below for your reference. The screenshot of the mprj_por folder is also provided. Can someone tell me why am I getting this error message and please do give provide me your valuable suggestions so that I am able to correct this error and move forward.

hi @Milan P Manoj, just last night I managed to successfully embed my design in the caravan project (caravel analog) - the thread with all the details is just above the one you started. I had no need to run the

make verify

etc. command, I just did DRC/LVS checks in local and then pushed the design over to efabless platform and there I started the tapeout job. So, maybe try that as well, while trying to solve the issue you mention here. Regarding the issue itself, here are couple of things from my experience: 1. be careful about running docker containers - by default, they require

sudo

, but there's a way (it's not secure, but on your personal machine its fine, just don't delete important stuff) to do it without sudo, it's quite easily found with google. 2. permission denied messages are related to the status of your files/folders that you can see if you do

ls -l

. So you might wanna try that first, to make sure all of those files/folders you are trying to use without

sudo

are actually permitted to be used by user

milan

3. not finding

target

when doing

make

is usually related to two things: (i) you are trying to run

make

on the wrong path; or (ii) the Makefile might be referring to things using relative paths that include

~

which means home directory - and home directory is

/home/milan

when you execute without

sudo

but home directory is

/root

when you try to execute with

sudo

So, please do check the paths that your Makefile is trying to include and execute.