RGD2

Probably shouldn't be pulled unless we can confirm with perhaps icetime + OpenTimer that it is reasonable.

If you disable the random number generator in icestorm/j1a.v, then icetime makes better sense of it. The loop in that part causes icetime to give silly results. On Thursday, 29...

Yes, that's it. Look up icetime [on Clifford's site](http://www.clifford.at/icestorm/). Scroll down to the "Where is the Documentation?" heading, there's a link there to the [Lattice iCE Technology library](http://www.latticesemi.com/~/media/LatticeSemi/Documents/TechnicalBriefs/SBTICETechnologyLibrary201504.pdf), which documents...

I have something similar for the j1a, but I handle getting the flash by using the `#flash build/nuc.hex` command built into the python serial client, no extra IO device needed....

Oh, thank god! Not your fault at all, how you could you have suspected that some crazy loon would later come and make your j1 multicore? I saw >r and...

I think I may just add an additional private context register to the j4a to resolve this (via the io space), I can then just rewrite the `do loop i...

I stumbled across the [hive processor](http://opencores.org/project,hive) on opencores.org the other day (whilst looking for a 16x16 signed multipliers to poach... found one!) and it's got me thinking. I wouldn't be...

FWIW, here's a workaround: ``` : 750ns dup if begin 1- dup 0= until then drop ; : ms dup if begin 1- dup 0= 1332 750ns until then drop...

I'm on Ubuntu 14.04.3 LTS, with much the same problem... connecting after a clean build results in no action. ``` dye025@dadc-nc:~/build/swapforth/j1a$ sha1sum icestorm/j1a.bin 4fad6215eda768073e397c8dd46772423586bb36 icestorm/j1a.bin ``` short HEAD's are: -...

Oh, just a note: the first build works fine, it's the second one (after #flash build/nuc.hex, and rerunning make -C icestorm and reprogramming icestorm/j1a.bin ) that doesn't, for me at...