Issue with implementation

[ashrithaMula]

I am trying to run implementation in vivado but getting a place error and also insufficient I/O ports. I am also getting IO clock placer failed.

[tmahlburg]

Do you have this file in your project?
https://github.com/Digilent/Basys3/blob/master/Resources/XDC/Basys3_Master.xdc
You need to uncomment the pins and the clock used here in that file.

[ashrithaMula]

Hello! Yes, I did. But, still getting the same placing error that the resources are not sufficient.(IO ports).

…

On Wed, Jan 17, 2024, 16:15 Till Mahlburg ***@***.***> wrote: Do you have this file in your project? https://github.com/Digilent/Basys3/blob/master/Resources/XDC/Basys3_Master.xdc You need to uncomment the pins and the clock used here in that file. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEVMLH7UMO67G6ZW4ZRHTBDYO6TSZAVCNFSM6AAAAABBOFPMVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJVGU2DSOBYHA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[tmahlburg]

Did you follow this tutorial by digilent to set up vivado?
https://digilent.com/reference/programmable-logic/guides/getting-started-with-vivado
Especially the "Adding the constraints file"?
And is basys3.v set as the top file of the implementation?

[tmahlburg]

Uncommented should be lines 7-9, 47-78, 267-270 and 285-294, btw.

[ashrithaMula]

Yes I did. Can you share me the picosoc code. Did you change anything in that?

…

On Fri, Jan 19, 2024, 22:40 Till Mahlburg ***@***.***> wrote: Uncommented shuold be the lines 7-9, 267-270 and 285-294, btw. — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEVMLH5FUPSPN2LK6KTLMFDYPKSJBAVCNFSM6AAAAABBOFPMVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBQG44DGNZVHE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[tmahlburg]

No, I didn't change anything in there. Even if I did, it would not explain the placement error. Can you share your .xdc file and the exact error message?

[ashrithaMula]

Hello. I sent you my constraint file. Can you please check it once.

…

On Sat, Jan 20, 2024, 21:38 Ashritha Mula ***@***.***> wrote: On Sat, Jan 20, 2024 at 4:45 PM Till Mahlburg ***@***.***> wrote: > No, I didn't change anything in there. Even if I did, it would not > explain the placement error. Can you share your .xdc file? > > — > Reply to this email directly, view it on GitHub > <#4 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BEVMLH4V423SIMG2MZJW7PDYPORO5AVCNFSM6AAAAABBOFPMVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGA3DQMZXGI> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> >

[ashrithaMula]

Hii. That over utilization issue is resolved. I just had one doubt. Where did you store the instructions? How can we use flash chip to store the instructions?

…

On Tue, Jan 23, 2024, 11:23 Ashritha Mula ***@***.***> wrote: Hello. I sent you my constraint file. Can you please check it once. On Sat, Jan 20, 2024, 21:38 Ashritha Mula ***@***.***> wrote: > > > On Sat, Jan 20, 2024 at 4:45 PM Till Mahlburg ***@***.***> > wrote: > >> No, I didn't change anything in there. Even if I did, it would not >> explain the placement error. Can you share your .xdc file? >> >> — >> Reply to this email directly, view it on GitHub >> <#4 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/BEVMLH4V423SIMG2MZJW7PDYPORO5AVCNFSM6AAAAABBOFPMVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGA3DQMZXGI> >> . >> You are receiving this because you modified the open/close state.Message >> ID: ***@***.***> >> >

[tmahlburg]

Glad to hear that.
You can just load your compiled .bin file, this forum post describes how it should work:
https://forum.digilent.com/topic/227-how-to-program-the-quad-spi-flash-on-the-basys3/

[tmahlburg]

You can also look at my other project picoramsoc, if you want to load the instructions directly into the RAM.