News for hackers. Stuff that matters.
Re:Clear – Open-Source FPGA ASIC by aappleby on Wednesday February 23, 2022 @12:32AM (#30438007)
8x8, so 64 4-luts and 64 flipflops? I'm not sure what I could build with that. Maybe a frequency counter with a SPI output, not much more.
Re:Clear – Open-Source FPGA ASIC by krasin on Wednesday February 23, 2022 @12:56AM (#30438126)
Yes, it's very limited. Personally, I backed for two reasons:

1. It will add a nice open-source reference design for a (small) FPGA that is compatible with the open-source SkyWater PDK. I am sure someone will take it and improve upon.

2. I am curious to try building a small batch of my own chips on this process (for a hobby project), but while I am somewhat comfortable with designing digital logic, I am less confident in my ability to take a chip and be able to communicate with it. By paying ~$80, I will be getting half of the experience (which would cost ~$10k otherwise)

Re:Clear – Open-Source FPGA ASIC by throwaway81523 on Wednesday February 23, 2022 @01:58AM (#30438461)
It's pretty bogus for them to even call such a thing an fpga. Why did they design it that way?
Re:Clear – Open-Source FPGA ASIC by krasin on Wednesday February 23, 2022 @03:11AM (#30438832)
For the first point, I think they are fine: FPGA stands for field-programmable gate array. This is exactly what they make, even though the array is very small.

As for the question, I don't know. But they have a comment section, maybe it's worth asking them directly?

Re:Clear – Open-Source FPGA ASIC by marcan_42 on Wednesday February 23, 2022 @02:44AM (#30438698)
Yeah, that's a bit ridiculous. The smallest commercial FPGA you can buy, as far as I know, is the smallest MachXO2 with 256 LUTs, and that's already in the "a little bit of glue logic" territory. How do they do anything useful with 64 LUTs? With 38 I/Os, you're going to spend all your LUTs just interfacing with them... Am I missing something here?

Edit: if this is the right project, then I see most of the I/Os aren't actually user I/Os in this design. https://github.com/Manarabdelaty/Caravel-OpenFPGA-EF

Re:Clear – Open-Source FPGA ASIC by eternityforest on Wednesday February 23, 2022 @03:01AM (#30438774)
I don't think I could build much of anything interesting at all.

Maybe a modulator for some obscure LED protocol that would probably be just fine in software on a 50 cent MCU anyway.

But it is something that's never been done before, or at least has rarely been done this cheap.

Re:Clear – Open-Source FPGA ASIC by cpldcpu on Wednesday February 23, 2022 @02:46AM (#30438705)
This CPU should fit :)

https://github.com/cpldcpu/MCPU

Re:Clear – Open-Source FPGA ASIC by aappleby on Wednesday February 23, 2022 @03:05AM (#30438796)
CPLDs handle programmable logic much differently than FPGAs - it might not actually fit.
Re:Clear – Open-Source FPGA ASIC by cpldcpu on Wednesday February 23, 2022 @09:33AM (#30441355)
nah, it will easily fit. not sure about routing ressources though.

=== CPU8BIT2 ===

   Number of wires:                319
   Number of wire bits:           3029
   Number of public wires:          38
   Number of public wire bits:     209
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:                 79
     $_DFF_PP0_                     24
     $lut                           55
Re:Clear – Open-Source FPGA ASIC by ur-whale on Wednesday February 23, 2022 @06:21AM (#30439958)
> I'm not sure what I could build with that

A hardware true random number generator using ring oscillators

Re:Clear – Open-Source FPGA ASIC by denton-scratch on Wednesday February 23, 2022 @06:46AM (#30440072)
For which you'd want at least two rings, with mutually-prime numbers of inverters - e.g. 53 and 11. But you'll also need a serial-in parallel-out shift register, which I guess you can probably do with a dozen gates. So maybe you could have rings of 41 and 11.

Would it work? How could you avoid entrainment between the two rings?

I tried this using a handful of TTL chips and a breadboard, but I'm not good at this kind of thing, and it didn't work (or rather, I couldn't prove it was working).

Re:Clear – Open-Source FPGA ASIC by ur-whale on Wednesday February 23, 2022 @07:45AM (#30440378)
>For which you'd want at least two rings, with mutually-prime numbers of inverters

Why?

I was under the impression that all that mattered was the phase noise in the ring oscillators (and therefore the phase drift)?

Also, not sure why would you need a shift register?

Just something that samples the output of the TRNG on a pin at a reasonably low freq and bitbangs what it gets on an output pin hooked up to the RX pin a serial-USB thingie should do the trick.

Re:Clear – Open-Source FPGA ASIC by denton-scratch on Wednesday February 23, 2022 @09:29AM (#30441304)
Well, I understand the principle to be that you use one ring oscillator to sample the state of the other; then you sample the output of the first oscillator on a clock. Phase noise just makes both oscillators more-or-less chaotic. How are you supposed to measure the phase noise?

Yes, you could use a serial-USB chip, and collect one bit at a time. So you're right, there's no need for a shift register.

Mutually prime: isn't it desirable that the sampling oscillator runs substantially slower than the sampled oscillator? You don't want successive samples to be from the same cycle of the sampled oscillator. I'm handwaving about mutual primality; but I'm thinking that you want to maximise the length of cycle over which the two oscillators would be expected to coincide, absent phase noise. I suppose having more inverters in each ring would increase the influence of phase noise, and increase the combined cycle length.

And I still don't know how you avoid the two oscillators becoming entrained - they can influence one-another through the supply line.

Re:Clear – Open-Source FPGA ASIC by ur-whale on Wednesday February 23, 2022 @02:49PM (#30445473)
I believe you only need one ring oscillator: thermal effects pretty much guarantee that phase noise will be present, especially if the ring is short: the shorter the oscillator (very few not gates) the faster it will oscillate, especially with modern silicon.

You then sample it using the crystal clock but at a slow pace (say 1kHz).

You are correct that you may see some sort of self-synchronization effect between the sampler loop and the ring osc., especially given that it's pretty much impossible to know what the FPGA routing and placement tools will do.

The trick here is that yes: the random numbers you're going to get out of these types of potentially intertwined systems is of very low quality from a uniformity perspective: you absolutely can't use the output directly because statistically speaking, it has very low entropy.

But from a true random number generation perspective, these time series of bit do contain some entropy of the completely unpredictable kind (generated by a truly random physical process).

And therefore, if you use this low-entropy stream of bit, some of which are pretty much guaranteed to be impossible to predict and feed them to - say - a stream cipher, you're going to get something that is both truly (as opposed to pseudo) random and uniform.

Clearly, you don't do that last part on the FPGA/CPLD but in software, on the other side of the USB bridge.

Re:Clear – Open-Source FPGA ASIC by denton-scratch on Wednesday February 23, 2022 @04:06PM (#30446443)
> I believe you only need one ring oscillator: thermal effects pretty much guarantee that phase noise will be present

OK, that seems to be a different model, that I wasn't aware of. The model that I described can be thought of as a jittery oscillator sampling another jittery oscillator.

> the shorter the oscillator (very few not gates) the faster it will oscillate, especially with modern silicon.

Yabbut surely the more inverters in the loop, the more jitter per cycle? I thought that the jitter in ring oscillators was ultimately down to the unpredictability of switching speed in gates. So the more gates in the loop, the more jitter. Is this wrong?

> these time series of bit do contain some entropy

Yes. The output is biased. So you have to debias it (or "distill" it); for a hardware circuit, I'd have thought a hardware debiaser would be more sensible than running it through a software-driven stream cipher. Instead use the Von Neumann debiaser, which as I recall can be implemented with a couple of gates.

Ah - now I remember why you need a shift register! The Von Neuman circuit doesn't output bits regularly; it compares successive pair of bits, and outputs a bit only when the inputs differ. With a heavily biased input stream, its output will be quite slow.

[Edit] For added jitteriness, you can build up a chain of oscillators, each sampling the next. If you have plenty of gates, I suspect you can make a raw source with a lot of entropy to distill.

[Edit Edit] The stream cipher serves as a whitener; the Von Neumann circuit doesn't do that. You still have to encrypt or hash the output to obliterate any patterns the Von Neumann circuit doesn't address - which is lots.