IRC logs for #openrisc Friday, 2016-07-15

--- Log opened Fri Jul 15 00:00:20 2016
--- Day changed Fri Jul 15 2016
ZipCPU|Laptopstekern: Thank you for the examples.  That's exactly the sort of logic I am trying to build.06:11
stekernZipCPU|Laptop: I've spent a couple of hours weeding out bugs in both of those files ;)06:12
ZipCPU|LaptopJust hours?06:12
stekernheh06:12
ZipCPU|LaptopYup.  You understand me completely.  ;)06:12
olofkwallento, ZipCPU|Laptop : Awesome! I've been meaning to do a UART thingie like that for a long time too10:33
wallentothere is rdiez' stuff too10:33
wallentohttps://github.com/rdiez/uart_dpi10:33
wallentobut I really wanted the UART experience on both sides ;)10:34
olofkkc5tja: Have you looked into etherbone, or any of the other CERN Wishbone projects? I think they have some infrastructure for external wishbone buses. Some of it is even in the upstream Linux kernel since Alessandro Rubini is quite involved with those things10:34
olofkwallento: Yeah. I haven't really looked at his stuff. Didn't feel like getting more involved with that guy10:35
olofkgtg. There's a city to explore outside!10:35
wallentoenjoy boston10:36
olofkThanks10:36
olofkAnyone need a souvernir?10:36
kc5tjaolofk: No, never heard of it.10:38
kc5tjaolofk: However, my externalized Wishbone doesn't really require software support.  It's designed to be just a dumb export of the bus.10:38
olofkI think they have something like that too10:39
kc5tjaolofk: Oh dear; wishbone-over-Ethernet?  No thanks.  That just wreaks of complexity.10:39
kc5tjaIt's just occurred to me that I have a total of three months to build a working Kestrel-3 prototype with ... *something*.10:55
kc5tjaWith the success rate I've been having building hardware, procuring hardware, or even just getting IDE tools to @#(%*ing run at all, this will not happen.  >:(10:55
kc5tjaicoBoard wants almost $150 for an FPGA board which still isn't equipped enough for my needs (and I'd need at least two), I can't get WebPACK ISE to license on my workstation, ...10:56
kc5tjaI might as well toss in the towel for this up-coming RISC-V workshop.10:57
ZipCPUkc5tja: Actually, I've been running wishbone over ethernet for some time.  It started as a wishbone over serial port project, but I then forwarded the serial port over the ethernet.12:19
ZipCPUSince then, I've made wishbone run over both the JTAG user interface as well as Digilent's 8-wire paralell DEPP interface.12:19
ZipCPUIt's the first thing I get running on any new project.12:19
kc5tjaI guess what I mean is, complexity == lots of LUTs, and I will not have that many to spare.13:33
kc5tjaOne of my long term goals is to make a Kestrel-3 with expansion slots using RapidIO.13:34
kc5tjaWhich is along the same lines as wishbone-over-X.13:34
kc5tjaFor the love of life, I just cannot find any specs on Etherbone or how it works under the hood.  :(13:37
kc5tjaAhh, found a PDF at last.13:48
kc5tjaYeah, that's several hundred KB of VHDL, and that's not an insignificant amount of logic.  Their definition of "simple" is quite different from mine.  ;-)13:54
ZipCPUkc5tja: Let's see, my wishbone over serial port consumes about 812 6-LUTs--but that includes compression, which I would probably drop if I really wanted to get the LUT count down.14:37
kc5tjaRight now, my ALU alone consumes 1800 LUTs, on a 3540 LUT device.  I still haven't sized the instruction decoder yet.15:13
kc5tjaI estimate around 300 minterms for the decoder so far.  CSR registers are not yet specified either.15:13
kc5tjaI'm sure hoping I can fit everything.  :)15:14
ZipCPUkc5tja: This is still the Kestrel-3, the 64-bit RISC-V CPU you are working on, right?15:58
kc5tjaKestrel-3 is the computer in which the CPU will be used, yes.  The CPU's name is Polaris.15:58
kc5tjaIf it turns out I need to shrink the ALU, I think the first thing to go is fast bit-shifts.  But, I sure don't want to discard those, because Kestrel-3 is a graphics-heavy machine.15:59
kc5tja(no text mode)15:59
ZipCPUkc5tja: If I remember correctly from your web pages, you have multiple "slaves" on a physical bus acting in concert, no?  If not, how on earth are you able to handle a "graphics heavy" machine if your CPU is filling up the FPGA?16:01
kc5tjaOne FPGA is the CPU.  One is the I/O chip (including video display core).  One is the RAM controller.  All three FPGAs are tied together over a common bus (an externalized, 16-bit Wishbone bus).16:02
ZipCPUThat external bus ... you're running it at 50MHz, no?16:03
kc5tjaThe CPU and I/O controller compete for the bus using a round-robin bus arbitration mechanism.16:03
kc5tjaThat was the original plan, but I may have to drop to 25MHz.16:03
ZipCPUAnd are you using the B4 spec?  Are you using the pipelining mode within it?16:03
kc5tjaAs long as I can run it at 25MHz, everything should have enough i/O throughput to keep up.16:04
kc5tjaIt's based on B4, but it's not 100% compatible (B4 doesn't specify how to export the bus externally).16:04
kc5tjaNo, no pipeline support.16:04
kc5tjaEach bus transaction takes two clock cycles (cycle 1 will drive the address bus, cycle 2 will be when we sample ACK).16:05
ZipCPUYou must at least be pipelining the 64-bit accesses across the bus ...16:05
kc5tjaSo, total throughput is 12.5 mega-transfers per second, enough to keep up with most RAM technologies.16:05
kc5tjaNope.16:05
ZipCPUSo that's 12.5MT/s at 16-bits/transfer?16:05
kc5tjaYes.16:05
ZipCPUIs there any reason you chose not to use the pipeline mode, to get closer to 25MT/s?16:06
kc5tjaWith 4 clocks per instruction, the CPU maxes out at 6.25 MIPS anyway, so no need to go faster.16:06
kc5tjaKeeping the design deliberately very, very simple.16:06
kc5tjaThat means using relatively slow, easily accessible RAMs.16:06
ZipCPU64k address space?16:07
kc5tjaI'm looking at using a 70ns RAM, which means it can keep up at most with a 14MHz bus.  So, restricting data flow to 12.5MT/s stays within the bounds.16:07
kc5tja4.2GB address space (though laid out in an unconventional manner.  256 segments of 16MB each, spread out evenly in a 64-bit address space.)16:07
kc5tjaAddress bus contains A63-A54, A31-A1.16:07
kc5tjaA53-A32 are ignored.16:08
ZipCPUYet only 16 data lines?  Are the address and data lines shared at all?16:08
kc5tjaNo.16:08
kc5tjaThough, I've considered it.16:08
kc5tjaBut I decided against it because it would have added an extra cycle of latency per transfer.16:08
ZipCPUForgive me if I ask so many questions, I find both your project and goals quite fascinating--although not my own.16:09
kc5tjaNo worries.16:09
kc5tjaI enjoy talking about it.  Frees my mind from work-day duldrums.  :)16:09
ZipCPUMy own project has been to design a "simple" computer for an FPGA.  The goal has been to reduce the LUT count as much as possible.16:09
ZipCPUThen I started realizing you can purchase speed with LUTs ... so the tradeoff isn't quite as simple as I had first imagined it to be.16:10
kc5tjaYeah.  My original goal for the project was to target the 1,000,000-gate FPGA in my Nexys-2 board.16:10
kc5tjaThere, I would have integrated everything into a single Verilog design, and clicked a button, and gotten an instant computer.16:10
ZipCPUand now you've switched to an iCE40?16:10
kc5tjaThat's how I made my Kestrel-2 (16-bit, stack-architecture predecessor to the Kestrel-3).16:10
kc5tjaYes, because I cannot get the Webpack ISE tools to license on my Ubuntu laptop.  :(16:11
ZipCPUReally?  I managed to get it done on my Ubuntu desktop somehow ...16:11
kc5tjaSo I decided to go the open-source route, but since no existing FPGA boards exist which meet my needs, I had to go and build my own.  And _that_ meant making a backplane bus to tie everything together.16:11
kc5tjaThe binary runs, but doesn't do anything.16:11
kc5tjaIt exits with result code 0.16:11
ZipCPUDid you get the license?16:12
kc5tjaNo.16:12
kc5tjaIt just dies.16:12
kc5tjaIt's like someone wrote a several megabyte main() {} program.16:12
ZipCPUOkay, there was a problem pulling firefox up to get the license.  When you click on get license, it tries to load firefox and there's an incompatibility.16:12
ZipCPUI googled it once, and so got past it ...16:12
ZipCPUJust don't ask me how any more.  I've still got Google if I need to do it again.  ;)16:13
kc5tjaAhh, if you have any information (can remember any links), that would be very helpful.16:13
kc5tjaEspecially since I only have 3 months to somehow get something I can demo at RISC-V workship #5.16:13
kc5tjaI remember googling about it, but got a lot of unhelpful references to Xilinx forum queries.16:13
kc5tjaI will try again though.16:13
kc5tjaThat said, I do still want to eventually target the iCE40s though.  I'm all about supporting open-source hardware, especially since they don't make the NExys-2 boards anymore.16:14
ZipCPUYes, they seem to be on the Nexys-4 DDR these days ...16:18
kc5tjaYeah.  And I'd be fine-ish with that were it not for the fact that I have a *perfectly* working Nexys-2 board on my desk.  ;D16:36
kc5tjaAnyone knows of a single-file equivalent to grin that does not require pip to install?17:16
kc5tjaThis would make searching through logs a bit easier on the API staging node, but I don't want to install pip just to install grin.17:18
kc5tjaerrrg!!!  Wrong channel again.17:38
kc5tjaSorry.17:38
kc5tjaThough, I did manage to solve my problem.  :)17:38
ZipCPUHere's a decent single file equivalent to grin: http://i.ebayimg.com/00/s/NTAwWDUwMA==/z/uFoAAOSwpDdVQ-Vc/$_1.JPG17:57
--- Log closed Sat Jul 16 00:00:41 2016

Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!