| Deutsch English Français Italiano |
|
<u9dkjj51rak4jjpdp4g7m22k0fc231bof1@4ax.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: JM <sunaecoNoChoppedPork@gmail.com> Newsgroups: sci.electronics.design Subject: Re: Grounded grid VHF front-end Date: Sun, 17 Nov 2024 18:28:45 +0000 Organization: A noiseless patient Spider Lines: 36 Message-ID: <u9dkjj51rak4jjpdp4g7m22k0fc231bof1@4ax.com> References: <1r2rj8l.msi28f14weovyN%liz@poppyrecords.invalid.invalid> <vgpiks$e1ei$1@solani.org> <vgq12n$ao84$2@dont-email.me> <vgq4rj$eagg$1@solani.org> <eld1jjl15hq8ohgm3kifpodkktupt1lr3g@4ax.com> <vgqg85$6t1$1@solani.org> <vhbh7j$26abk$1@paganini.bofh.team> <vhc2ts$9v2r$1@solani.org> <vhcvsg$28q26$1@paganini.bofh.team> <p49kjjpfq4t25in8slsak4moi59rj1pusp@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Date: Sun, 17 Nov 2024 19:29:10 +0100 (CET) Injection-Info: dont-email.me; posting-host="b9d54e26a9cde1c378b98c955a9813d2"; logging-data="818583"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+fRsj9RgTli8SG7FLpoeOd" User-Agent: ForteAgent/8.00.32.1272 Cancel-Lock: sha1:+Q/al/P3qLkN8PJQOI6OZq1ANRk= Bytes: 2619 On Sun, 17 Nov 2024 09:33:54 -0800, john larkin <JL@gct.com> wrote: >On Sun, 17 Nov 2024 14:50:58 -0000 (UTC), antispam@fricas.org (Waldek >Hebisch) wrote: > >>USB can do milliseconds, ethernet hundreds of microseconds, small >>micros can do much better. Theoretically with a micro connected via USB >>one can synchronize clocks of the micro and PC with microsecond >>accuracy, I plan to try this but do not know how this will work. > >We're designing some products around the RP2040, the Pi Pico >processor. > >Turns out that in some cases, it's easier to bit-bang an SPI interface >than program an SPI engine. To fine-tune timings in 7 ns increments, >we can use no-op instructions. > >I wonder what's a safe c-language NOP single-clock operation that no >compiler is smart enough to optimize out and doesn't add a bunch of >loads and stores. > >We're experimenting with that sort of timing on an oscilloscope. The >GCC or whatever code timing tools don't work in this case. > >Something like > > gpio_put(FIRST_GPIO, 1); > gpio_put(FIRST_GPIO, 0); > gpio_put(FIRST_GPIO, 1); > gpio_put(FIRST_GPIO, 0); > >Makes the port pin change every 7 ns. That's astounding. So maybe a >dummy port bang is my no-op. Just repeat what we just set it to. > Code in assembly. It's trivial to use assembly code with c in gcc.