--- Log opened Thu May 22 00:00:59 2014 | ||
-!- knz_ is now known as knz | 04:12 | |
stekern | olofk: it's funny, quartus doesn't like /path/to/dir type of paths in the SEARCH_PATH global_assignment, but it's fine with them in the VERILOG_FILE assignments | 06:33 |
---|---|---|
stekern | for the SEARCH_PATH, it has to be c:\\cygwin64\\path\to\\dir | 06:34 |
stekern | this small hack fixes it: http://pastie.org/9198112 | 06:39 |
blueCmd | stekern: hah | 08:41 |
stekern | blueCmd: to what of all my hilarious statements are you laughing at? ;) | 09:05 |
* olofk turns around, looks deep into rah's eyes and says: "Honey, now is not a good time" | 09:31 | |
olofk | stekern: I found something else that was interesting regarding SEARCH_PATH | 09:32 |
olofk | In the original sockkit material there was no SEARCH_PATH specified at all, but as I did the workshop on my linux machine I had to hack the project file a bit, and my Linux copy contains SEARCH_PATH lines | 09:32 |
olofk | So it seems that Windows might implicitly pick up SEARCH_PATH from the verilog file dirs or something like that | 09:33 |
stekern | oho... but in my material there is SEARCH_PATH lines in the .qsf? | 09:33 |
olofk | Ah there is..? Weird | 09:34 |
olofk | I opened the unmodified zip file and couldn't find it in the qsf | 09:34 |
olofk | or qfp or what the fuck it's called | 09:34 |
olofk | Anyway, your cygwin patch looks good. It's one of those quirky hacks that always comes with a larger code base :) | 09:35 |
stekern | mmm, yeah.. it's .qsf, but I think those lines are actually inserted when you open the .qpf | 09:35 |
olofk | aha | 09:36 |
olofk | Which is equally fucked up | 09:36 |
stekern | I've got:set_global_assignment -name SEARCH_PATH "c:\\altera_trn\\sockit\\sockit_hw_lab_13.0\\soc_system\\synthesis\\submodules\\sequencer" | 09:36 |
stekern | in mine that I used on the win machine I used for the workshop | 09:37 |
olofk | I have set_global_assignment -name SEARCH_PATH /home/olof/altera_trn/SoCkit_HW_lab_13.0/soc_system/synthesis/submodules/sequencer | 09:37 |
olofk | Another thing... I've seen you talking about cgen patches. Is this on the binutils ml? I unsubscribed there so I'm wondering if you could CC the OpenRISC ml as well | 09:38 |
stekern | I've bet quartus has quirky hacks for this stuff too, and one of them is missing for SEARCH_PATH | 09:39 |
olofk | Or perhaps do like the linux port and have it's own ml | 09:39 |
olofk | But I guess we don't expect much traffic so a separate ml might be a bit overkill | 09:40 |
stekern | mmm, it's more of a Linux cultural norm to have sub-mailinglists too | 09:41 |
stekern | binutils isn't very high traffic, so IMO people that are interested can be signed up directly there | 09:42 |
stekern | and the cgen patches is on the cgen list, that's as low traffic as one can get ;) | 09:43 |
stekern | I've probably increased the traffic by 200% for the whole year just today and yesterday | 09:44 |
stekern | https://sourceware.org/ml/cgen/2014-q2/ | 09:44 |
rah | olofk: heh | 09:47 |
olofk | stekern: And that's high traffic compared to this sad experiment http://lists.opencores.org/pipermail/wishbone/ | 10:17 |
stekern | there was a wishbone question on the forums recently, perhaps I should have directed him there instead ;) | 10:20 |
olofk | I usually do that, but it's a little awkward because it generally means that I'm just answering him again | 10:24 |
inigom | Hey there! I'm new using OpenRisc and all the tools. I'm folowing the PinkSoc tutorial (http://wiki.pinksoc.org/doku.php/openrisc_tutorial). This tutorial now uses fusesoc. But the point | 10:31 |
inigom | is that I would like to know how te fusesoc's command line works | 10:32 |
inigom | any documentation? | 10:32 |
inigom | or suggestion? | 10:32 |
inigom | many thanks! | 10:32 |
blueCmd | stekern: all of them | 10:44 |
blueCmd | more specifically the SMP and being impatient | 10:44 |
rah | http://blog.elphel.com/2013/10/fpga-is-for-freedom/ | 10:59 |
olofk | inigom: Hi. I haven't gotten around to write any real documentation for FuseSoC yet | 14:42 |
olofk | There are a few tutorials around, and you can get some info from fusesoc --help | 14:42 |
olofk | Anything in particular you're wondering about? | 14:42 |
inigom | Hi Franck , which command should we give to run the or1200 system with fusesoc - I'm kind of lost | 15:12 |
_franck__ | if you want to run a simulation, just run fusesoc sim or1200-generic --vcd --force --elf-load=/path/to/your/elf | 15:14 |
_franck__ | --vcd is for waveform generation | 15:15 |
_franck__ | --force tells fusesoc to prepare the build directory again | 15:15 |
inigom | ERROR: 'or1200-generic' or any of its dependencies requires 'mmuart', but this core was not found | 15:17 |
_franck__ | did you download orpsoc-cores ? | 15:19 |
inigom | fusesoc sim or1200-generic --vcd --force --elf-load= ../tests/icarus-test/hello | 15:20 |
inigom | usage: fusesoc sim or1200-generic [-h] [--testcase TESTCASE] | 15:20 |
inigom | [--elf-load ELF_LOAD] [--vcd] | 15:20 |
inigom | [--timeout TIMEOUT] | 15:20 |
inigom | [--transactions TRANSACTIONS] | 15:20 |
inigom | [--jtag-vpi-enable] | 15:20 |
_franck__ | you should install fusesoc, then download orpsoc-cores. after that, create a working directory directory, put fusesoc.conf in there | 15:20 |
inigom | fusesoc sim or1200-generic: error: unrecognized arguments: --force ../tests/icarus-test/hello | 15:20 |
inigom | the above is what we are getting | 15:21 |
_franck__ | you forgot --elf-load before your elf | 15:21 |
inigom | the previous one was wrong directory | 15:21 |
inigom | we think we have the latest and greates fusesoc and oprsoc-cores | 15:21 |
_franck__ | is your fusesoc.conf correct ? | 15:22 |
_franck__ | try to use absolute path for your elf files | 15:23 |
inigom | we just did - same result . How come --force is unrecognized? | 15:25 |
inigom | .conf file seems correct | 15:25 |
inigom | and simply typing fusesoc sim wb_sdram_ctrl works fine | 15:26 |
_franck__ | does fusesoc sim wb_sdram_ctrl --force works ? | 15:28 |
_franck__ | can you paste here the _exact_ command line you are using to sim or1200-generic ? | 15:31 |
inigom | inigom@pinksoc2:~/Desktop/pinksoc/build-fusesoc$ fusesoc sim wb_sdram_ctrl --force | 15:35 |
inigom | usage: fusesoc sim wb_sdram_ctrl [-h] [--vcd] [--timeout TIMEOUT] | 15:35 |
inigom | [--transactions TRANSACTIONS] | 15:35 |
inigom | fusesoc sim wb_sdram_ctrl: error: unrecognized arguments: --force | 15:35 |
_franck__ | wait, I'll checkout the last fusesoc, to see if something is broken | 15:37 |
_franck__ | may be this: https://github.com/olofk/fusesoc/commit/e8b3d2e3b352816302ca3da1fafb6557d4af0e73 | 15:37 |
_franck__ | yeah, it's broken :( | 15:38 |
_franck__ | well, try not to use --force | 15:39 |
_franck__ | --force must be just after "sim" | 15:41 |
_franck__ | sim args must be after sim and plusargs (the one that cores provides) are after the simulated core name | 15:43 |
_franck__ | fusesoc sim --help gives you sim args | 15:44 |
_franck__ | so it's not broken :) | 15:45 |
inigom | fusesoc sim or1200-generic --vcd --force --elf-load= ../tests/icarus-test/hello | 15:45 |
_franck__ | no, fusesoc sim --force or1200-generic --vcd --elf-load=../tests/icarus-test/hello | 15:46 |
inigom | sorry my fault | 15:46 |
_franck__ | I recon, that's not easy | 15:46 |
inigom | i have paste the wrong command | 15:47 |
inigom | fusesoc sim --force wb_sdram_ctrl | 15:47 |
inigom | this works :D | 15:47 |
_franck__ | gtg, I'll be back later | 15:48 |
ysionneau | juliusb : awesome that you come to EHSM to talk about OpenRISC/mor1kx :) | 19:11 |
olofk | ysionneau juliusb : Cool. You're going to EHSM? I want to go too, but don't have time :( | 19:48 |
olofk | I saw the fusesoc cmd line confusion. It's like this: fusesoc <global args> <command> <command args> <system/core> <extra args> | 19:51 |
_franck_ | my NEEK fusesoc port is finally ready | 19:57 |
ysionneau | yep going as well, doing a talk on the NetBSD port on lm32 :) | 20:16 |
blueCmd | stekern: I'm thinking of buying an Atlys board to have it as a buildbot / shell server | 20:16 |
ysionneau | the list of talk seems really impressive | 20:16 |
ysionneau | like last year | 20:16 |
blueCmd | stekern: how many cores do you recon I could have on it? | 20:17 |
stekern | hmmm... I'll probably be more able to answer that when I have tried | 20:20 |
JakeUSC | bluecmd: How did you make the hex file for your u-boot? | 20:56 |
blueCmd | JakeUSC: I have a script .. somewhere | 20:59 |
blueCmd | bin2binsize (it's in the old OpenRISC svn repository somewhere) on the u-boot.bin file, then bin2hex.py on that | 21:00 |
blueCmd | bin2hex.py is some generic python lib | 21:00 |
JakeUSC | thanks, I was using bin2binsize and then bin2hex from the old orpsoc | 21:02 |
olofk | _franck_: Is it just the mem controller in pull request #65? | 21:14 |
_franck_ | olofk: no, that's the board port. However, github doesn't like big commit diff | 21:24 |
_franck_ | I think I'll just push it | 21:25 |
blueCmd | stekern: if you would have to guess | 22:05 |
--- Log closed Fri May 23 00:00:00 2014 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!