--- Log opened Sun Jan 15 00:00:15 2017 | ||
-!- shorne_ is now known as shorne | 02:55 | |
shorne | ZipCPU: I think its adv_debug_sys, but you can see in the fusesoc-cores repo how each soc is configured | 02:56 |
---|---|---|
shorne | basically for most "bootstrapping" its OpenOCD --> jtag --> target | 02:57 |
shorne | Also you can store a bootloader into flash which the cpu can boot from, I havent tried that yet, but olofk was talking about that recently. | 02:59 |
shorne | sdfs | 03:38 |
shorne | Hello, wallento, stekern: I did a pr for musl cross version bump here | 03:39 |
shorne | https://github.com/openrisc/musl-cross/pull/1 | 03:39 |
shorne | If no issue I would like to merge | 03:39 |
wallento | Yes, please merge | 03:41 |
promach | hi, I am trying to have a build of mor1kx on my FPGA board. I just have a UART softcore running. How would I proceed ? | 03:41 |
shorne | wallento: thanks, will do after travis passes | 03:42 |
shorne | I should make a news announcement and post to the website like you did before too | 03:42 |
shorne | I am not so good at that though | 03:42 |
shorne | :) | 03:42 |
wallento | you are right, that is a great idea | 03:50 |
wallento | please do, I am sure it will be good :) | 03:51 |
bandvig | ZipCPU: I use U-Boot on my Atlys board. I upload prepared U-Boot image by Ethernet with TFTP. | 05:28 |
promach | I am having problem | 06:30 |
promach | pkg_resources.DistributionNotFound: The 'fusesoc==1.5' distribution was not found and is required by the application | 06:30 |
promach | with | 06:30 |
promach | https://github.com/openrisc/mor1kx/wiki/Setting-up-a-mor1kx-development-and-verification-environment | 06:30 |
promach | I have fusesoc installed in a virtualenv | 06:31 |
promach | with this command env/bin/pip install fusesoc | 06:31 |
promach | and | 06:32 |
promach | python -m venv env | 06:32 |
ZipCPU|Laptop | promach: Olof usually answers any fusesoc issues, but I don't see him on the users list for this channel. | 07:41 |
ZipCPU|Laptop | bandvig, shorne: Thanks for your answers! | 07:42 |
ZipCPU|Laptop | I certainly found adv_debug_sys connected to all the systems I examined within the orpsoc-cores set. | 07:43 |
ZipCPU|Laptop | bandvig: uboot ... sure, but ... how do you get uboot on your board? That's really my question--how you get the first, virgin load, onto your FPGA board. | 07:44 |
bandvig | ZipCPU|Laptop: it was really quite long story. Some times ago I told it here. Shortly speaking I followed http://www.rte.se/blog/blogg-modesty-corex/openrisc-1200-soft-processor/2.1 in my OpenRISC journey | 08:09 |
ZipCPU|Laptop | "The official implementation [of OpenRISC] is maintained by developers at OpenCores.org" ... still? ;P | 08:14 |
ZipCPU|Laptop | That was a lot of reading just to learn that you used the IMPACT tools to load your first program into flash and then ran from there. | 08:29 |
promach | olofk: I have a problem with fusesoc | 10:28 |
promach | <promach> pkg_resources.DistributionNotFound: The 'fusesoc==1.5' distribution was not found and is required by the application | 10:29 |
promach | <promach> with | 10:29 |
promach | <promach> https://github.com/openrisc/mor1kx/wiki/Setting-up-a-mor1kx-development-and-verification-environment | 10:29 |
promach | <promach> I have fusesoc installed in a virtualenv | 10:29 |
promach | <promach> with this command env/bin/pip install fusesoc | 10:29 |
promach | <promach> and | 10:29 |
promach | <promach> python -m venv env | 10:29 |
mafm | is there any openrisc presence at fosdem? | 16:39 |
olofk | mafm: Not sure actually. | 16:47 |
olofk | wallento: You're going to FOSDEM? | 16:47 |
olofk | Seems like I missed quite some discussion while I was busy rebuilding the network at home | 16:48 |
olofk | Network over the power lines is great btw! As long as you find some good outlets to plug in the stuff | 16:48 |
olofk | Anyway | 16:48 |
olofk | ZipCPU: By default, an OpenRISC CPU is set up to run from address 0x100 | 16:49 |
olofk | What we normally do however, is to make it start executing from address 0xf0000000 (just a convention), where we have placed a boot ROM | 16:49 |
olofk | With FuseSoC it's of course easy to select which ROM contents you want to use | 16:50 |
olofk | The two most widely bootloaders (to be placed in that ROM) is | 16:50 |
olofk | 1. Clear r3 and jump to address 0x100. This is good when you are using a JTAG debugger and adv_debug_sys to program an application to RAM | 16:51 |
olofk | 2. Load an image from SPI Flash and jump to address 0x100 | 16:51 |
olofk | I've been considering several other bootloaders as well | 16:51 |
mafm | olofk: I didn't find any talk scheduled by the name of "openrisc" or "or1k", but there might be many topics related to openrisc/librecores, so just asking | 16:52 |
olofk | Such as listen to a UART, where it could accept a file in Intel/Motorola hex format that could be programmed to RAM | 16:52 |
olofk | Or a zmodem receiver | 16:52 |
olofk | mafm: Yes, there will be presence from FOSSi Foundation. I'd love to go myself, but I can't this year | 16:53 |
olofk | The hardest part of writing these boot loaders has been that I can't use any RAM, since I don't know if the application will overwrite it, so I'm writing them in 100% asm to make sure that they only use registers for storage | 16:54 |
mafm | olofk: btw, there are good chances that I will attend orconf 2017 if it's in the UK :D | 16:59 |
mafm | too bad that riscv conf is in china, no way to go there :( | 16:59 |
olofk | mafm: Great. Looking forward to see you again at orconf | 17:01 |
mafm | olofk: is there any proposal about where in the UK it would be? | 17:10 |
olofk | mafm: Yes. We will announce it later this month | 17:11 |
mafm | hope that it's close to Stansted :D | 17:15 |
mafm | (Cambridge or London, that is :P) | 17:16 |
shorne | mafm: riscv in china? Im in Japan, maybe I can swing by :) | 17:20 |
andrzejr | shorne, where in Japan are you? | 17:33 |
mafm | shorne: I think that in shanghai, but not officially announced yet | 17:36 |
shorne | andrzejr: tokyo | 17:39 |
andrzejr | shorne, I've been living there myself for some years. Tokyo, Yokohama. | 17:43 |
olofk | stekern: I'm considering to remove the qsys stuff you added for the quartus backend in FuseSoC. The code is becoming a bit hard to maintain, and I think it could be done by a tcl script that is launched by FuseSoC instead. Any thoughts? | 18:06 |
promach | olofk: did you see my question ? | 18:54 |
stekern | olofk: sure, that's probably doable | 23:35 |
--- Log closed Mon Jan 16 00:00:16 2017 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!