-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build does not meet timing #8
Comments
My suggestion is that when a host device, computer, connected to the fomu hardware, that computer initialises its com. port toggling the tx line causing the fomu hardware to go into an unknown state. Re-powering the device causes it to return to a state to a dfu accessible device. |
Have redesigned j1eforth for the FOMU and have it working back on the HACKER board. I have built for PVT, but am unable to test. |
Maybe you can try my USB-CDC implementation, in which you can use a lower clock for j1eforth design. |
Thanks, I'll give that a try. Looks nice!
…On Tue, 23 Nov 2021 at 16:22, ulixxe ***@***.***> wrote:
Maybe you can try my USB-CDC implementation, in which you can use a lower
clock for j1eforth design.
Look at https://github.com/ulixxe/usb_cdc
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN4SYT245XQTCFJ2FEV7PZ3UNO5SZANCNFSM4SNX7VNQ>
.
|
Hi there,
Tried wiring it in as
https://github.com/rob-ng15/Silice-Playground/tree/master/j1eforth/FOMU-TEST
the connection to the USB_CDC is in frameworks/fomu_USB_SPRAM.v
Whilst it builds, it does not create a working ttyACM0, probably a
mis-understanding on my part as to how to wire it in. Rob.
…On Thu, 25 Nov 2021 at 13:03, Rob Shelton ***@***.***> wrote:
Thanks, I'll give that a try. Looks nice!
On Tue, 23 Nov 2021 at 16:22, ulixxe ***@***.***> wrote:
> Maybe you can try my USB-CDC implementation, in which you can use a lower
> clock for j1eforth design.
> Look at https://github.com/ulixxe/usb_cdc
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#8 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AN4SYT245XQTCFJ2FEV7PZ3UNO5SZANCNFSM4SNX7VNQ>
> .
>
|
Hi Rob,
I hope this helps. |
The design runs in a single clock domain, driven by
clki
. This pin is a 48 MHz signal, and as a result the entire design actually runs at 48 MHz.As a result, the system is overclocked and can fail on some devices:
The text was updated successfully, but these errors were encountered: