| --- Log opened Sun Mar 13 00:00:32 2016 | ||
| wallento | shorne: thanks, I will have a look | 03:35 |
|---|---|---|
| bandvig_ | juliusb: Julius, IRC log doesn't work :( | 05:16 |
| wallento | shorne: fixed in https://github.com/openrisc/binutils-gdb/commit/fe709fb78f7336c1eb1f44a5a6f100e523c86b6d | 05:40 |
| wallento | I have added travis builds to binutils-gdb: https://travis-ci.org/openrisc/binutils-gdb | 06:05 |
| wallento | And made a release of gdb 7.11: https://github.com/openrisc/binutils-gdb/tree/gdb-7.11-or1k | 06:05 |
| wallento | shorne: how was it with gcc 5.2? | 06:52 |
| wallento | you missed the branch of blueCmd or was yours different/better? | 06:52 |
| shorne | wallento: I just did install, I didnt see any issues | 08:24 |
| shorne | I started it up and it works ok | 08:25 |
| shorne | I didnt see the blueCmd branch | 08:25 |
| shorne | wallento: where did you see the blueCmd branch? | 08:29 |
| wallento | shorne: https://github.com/openrisc/or1k-gcc/tree/or1k-5.2.0 | 08:35 |
| wallento | here | 08:35 |
| shorne | I was not using that | 08:37 |
| shorne | or1k-elf-gcc -v | 08:37 |
| shorne | gcc version 4.9.2 (GCC) | 08:38 |
| shorne | gcc -v | 08:38 |
| shorne | gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC) | 08:38 |
| shorne | I think when I build gdb it uses local gcc to x86. What does the gdb build need or1k-elf- for? ( I know it needs it, but not clear what its for ) | 08:41 |
| wallento | It doesn't need it | 08:46 |
| wallento | I roughly remembered you also ported gcc to 5.2, or not? | 08:46 |
| shorne | yes, so my host compiler is 5.3 (which needed the updates) | 08:47 |
| shorne | the target it the or1k-elf chain which is 4.9 | 08:47 |
| wallento | ah, okay | 08:48 |
| wallento | I got confused then | 08:48 |
| shorne | that was no problem | 08:48 |
| shorne | I guess I am a bit too, I should probably try to update my or1k-elf- chain too | 08:48 |
| wallento | I just rebuilt a newlib toolchain release | 08:49 |
| wallento | gcc 4.9.2, binutils 2.26 from upstream, newlib 2.3.0 with or1k backports and gdb 7.11 with or1k patch | 08:50 |
| wallento | If gcc 5.2 is ready we probably should merge it and I will build that too | 08:50 |
| shorne | is the or1k-gcc github based off of upstream git? | 08:51 |
| shorne | i.e. is it easy to merge? | 08:52 |
| shorne | I see the bluecmd branch | 08:52 |
| shorne | need to go for a bit.. | 08:52 |
| wallento | I think it is, but I will clarify it | 08:54 |
| olofk | wallento: Can we upstream gdb before gcc? I don't think there are any technical reasons to hold it back otherwise | 09:02 |
| olofk | Hmm...or is sim using or1ksim? I vaguely remember some circular dependency there | 09:03 |
| olofk | Does anyone know if it's possible to set top-level verilog parameters in verilator? | 09:03 |
| wallento | it is not | 09:03 |
| wallento | verilator | 09:04 |
| olofk | That sucks :/ | 09:04 |
| wallento | I put this up as an issue a while ago, but the compilation forbids that | 09:04 |
| wallento | thats why we put the core id as port for verilated models | 09:04 |
| wallento | what do you want to do? | 09:04 |
| wallento | most stuff can be done as ports fortunately | 09:04 |
| olofk | I have made some FuseSoC improvements so that you can easily set parameters for build targets and the other sims | 09:04 |
| olofk | Yeah, that's true, but some things you can't | 09:05 |
| wallento | ah, you mean at compilation time? | 09:05 |
| olofk | tep | 09:05 |
| olofk | yep | 09:05 |
| olofk | plusargs work fine in verilator | 09:05 |
| wallento | there it should be possible | 09:05 |
| olofk | I need it to pass initial rom contents and other stuff | 09:06 |
| wallento | I think you still need a wrapper for this | 09:07 |
| olofk | That's the way we do it now, but using a parameter would make it easy to handle it the same way for all targets | 09:08 |
| wallento | but you are right, technically it should not be too hard to set parameters at compile time | 09:08 |
| olofk | The other sims support it, so I find it strange that verilator doesn't | 09:08 |
| wallento | same as you set defines | 09:09 |
| wallento | and there is your Sunday project ;) | 09:09 |
| olofk | wallento: :) http://www.veripool.org/boards/2/topics/276-Verilator-Efficient-Usage-of-Verilog-Parameters | 09:10 |
| olofk | Small world :) | 09:10 |
| wallento | yeah, that was it | 09:10 |
| wallento | regarding gdb I am not sure, in contributing it does not say much | 09:11 |
| wallento | with respect to new architectures | 09:12 |
| olofk | haha http://www.veripool.org/boards/2/topics/918-Verilator-Parameter-in-package-used-for-signal-width | 09:12 |
| olofk | Are we the only users of verilator? :) | 09:12 |
| wallento | find one of Jeremy and you get a Bingo | 09:12 |
| wallento | I can have a look at the code to estimate the complexity of adding +parameter+name=value | 09:13 |
| olofk | wallento: :) | 09:13 |
| olofk | Highly appreciated if you have time to look at that | 09:14 |
| olofk | It really shouldn't be too hard I guess | 09:14 |
| wallento | I will later, but want to finish an updated tutorial now | 09:15 |
| wallento | I will create a repo openrisc/tutorials, okay? | 09:16 |
| olofk | Great | 09:16 |
| wallento | got the ORCONF2013 one running again | 09:16 |
| olofk | They need a lot of love | 09:16 |
| olofk | ah cool | 09:16 |
| olofk | People seem to use that one quite a lot | 09:16 |
| wallento | yep, I will put up a note there also | 09:16 |
| wallento | and provide prebuilt-versions | 09:16 |
| wallento | as a quick start | 09:17 |
| olofk | great. It's a lot of steps to get stuff running, so have some known good images helps | 09:18 |
| wallento | olofk: What's the plusarg in other simulators? | 11:36 |
| wallento | I think I have drafted the feature now, will push soon for testing and ask Wilson if I am going in the proper direction | 11:51 |
| mafm | blueCmd: do the Debian repos of or1k still exist somewhere? | 12:26 |
| mafm | (or anybody who knows, of course) | 14:28 |
| shorne | wallento: you mention you got orconf2013 running again, thats the tutorial I used. but had to change a few things | 17:45 |
| shorne | like use fusesoc | 17:46 |
| shorne | I also used the openrisc/orpsoc-cores since I figured julius's 2013 branch was pretty old | 17:46 |
| shorne | and so the uart pin locations was different | 17:47 |
| shorne | Is it ok to update the mediawiki to be more modern? or you want to create a new one and link to it? | 17:48 |
| --- Log closed Mon Mar 14 00:00:33 2016 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!