Creating high-speed FPGA design using Qorc-SDK

Post Reply
Vesuvius
Posts: 1
Joined: Tue Sep 05, 2023 1:02 pm

Hi,
We are trying to create LPC controller design to work as LPC slave (on EOS-S3 FPGA) and we are having serious problems with meeting timing requirements. One of the problems is that we cannot use any CLOCK pads as these don't work - there is no input, just as if pad was not connected. Input works only BIDIR pads which don't have CLOCK functionality. For development I'm using latest Qorc SDK release, however I tried also using F4PGA, with the same effect.

Artur
Robert
Posts: 29
Joined: Fri May 15, 2020 8:27 am

What frequency external clock are you trying to use?

I would suggest bring the clock in on a FBIO pin and then instantiating a global clock buffer. I will look at creating an example if this is still an issue.
Annata23
Posts: 1
Joined: Tue Mar 05, 2024 9:08 am

Robert wrote: Fri Jan 19, 2024 3:19 pm What frequency external clock are you trying to use?

I would suggest bring the clock in on a FBIO pin and then instantiating a global clock buffer. I will look at creating an example if this is still an issue.
Can you create an example for it? I still don't quite word hurdle understand this issue
meltobserve
Posts: 1
Joined: Wed Sep 11, 2024 6:49 am

Vesuvius wrote: Tue Sep 05, 2023 1:45 pm Hi,
We are trying to create LPC controller design to work as LPC slave (on EOS-S3 FPGA) and we are having serious problems with meeting timing requirements. One of the problems is that we cannot use any CLOCK pads as these don't work - there is no input, just as if pad was not connected. Input works only BIDIR pads which don't have CLOCK functionality. For development I'm using latest Qorc SDK release, however I tried also using F4PGA, with the same effect.

Artur
Based on your description, it seems like only BIDIR pads are functioning for input, while CLOCK pads remain unresponsive, which could be causing your timing problems. You’ve tried both the latest Qorc SDK and F4PGA but are encountering the same issue.
benchcivil
Posts: 1
Joined: Mon Sep 23, 2024 4:58 am

Robert wrote: Fri Jan 19, 2024 3:19 pm What frequency external clock are you trying to use?

I would suggest bring the clock in on a FBIO pin and then instantiating a global clock buffer. I will look at creating an example if this is still an issue.
Please give me ancoreball example, thanks!
firsthandrain
Posts: 1
Joined: Wed Oct 02, 2024 8:04 am

Robert wrote: Fri Jan 19, 2024 3:19 pm What frequency external clock are you trying to use?

I would suggest bring the clock in on a FBIO pin and then instantiating a global clock buffer. I will look at creating an example if this is still an issue.connections game
I'm not understanding how using an external clock frequency affects and relates to this?
visoroptimistic
Posts: 1
Joined: Thu Oct 03, 2024 9:41 am

Do you have any more answers to this question? Please share more.geometry dash lite
FreddyBlackwell
Posts: 2
Joined: Wed Nov 20, 2024 9:24 am

Vesuvius wrote: Tue Sep 05, 2023 1:45 pm Hi,
We are trying to create LPC controller design to work as LPC slave (on EOS-S3 FPGA) and we are having serious problems with meeting timing requirements. One of the problems is that we cannot use any CLOCK pads as these don't work - there is no input, just as if pad was not connected.ragdoll hit Input works only BIDIR pads which don't have CLOCK functionality. For development I'm using latest Qorc SDK release, however I tried also using F4PGA, with the same effect.

Artur
The problem you're describing with the CLOCK pads not functioning suggests that there might be either an issue with the FPGA configuration or an incompatibility with the specific pads being used.
ColeHarry
Posts: 1
Joined: Thu Jan 16, 2025 2:51 am

It sounds like a challenging issue you're facing with the LPC controller design. If the CLOCK pads aren't functioning as expected and only BIDIR pads are working, it could be worth double-checking the pin configurations and constraints in your design files. Sometimes, incorrect pin assignments or missing configurations in the Qorc SDK or F4PGA can lead to such behavior.
Post Reply