Thursday, 2020-12-10

*** tpb has joined #litex00:00
*** lf has quit IRC00:06
*** lf has joined #litex00:06
*** CarlFK has quit IRC00:44
*** kgugala has quit IRC00:50
*** kgugala has joined #litex00:50
*** Bertl_oO is now known as Bertl_zZ00:51
*** lf has quit IRC01:03
*** lf has joined #litex01:03
*** Degi has quit IRC01:25
*** Degi has joined #litex01:26
*** lkcl has quit IRC02:10
*** lkcl has joined #litex02:23
*** Dolu_ has quit IRC02:38
*** CarlFK has joined #litex02:59
*** rachsug_ has joined #litex05:06
*** cjearls has joined #litex05:50
*** kgugala_ has joined #litex05:57
*** kgugala has quit IRC05:59
*** cjearls has quit IRC06:12
*** cjearls has joined #litex06:14
*** kgugala has joined #litex06:15
*** kgugala_ has quit IRC06:18
*** cjearls has quit IRC06:24
*** m4ssi has joined #litex06:31
*** futarisIRCcloud has joined #litex06:42
*** kgugala has quit IRC07:20
*** kgugala has joined #litex07:20
*** kgugala has quit IRC07:41
*** kgugala has joined #litex07:41
*** cjearls has joined #litex08:03
cjearlsHi, I am attempting to use Linux-on-LiteX-VexRiscv, but I'd like to add my custom core to the board instead of the standard VexRiscv core. I have found that the VexRiscv_Linux.v in pythondata_cpu_vexriscv is the CPU that is being packaged up into the bitstream. Is there a way to rerun synthesis of this core with updated VexRiscv code so I can implement the changes I need?08:14
cjearlsI'm using the orangecrab board, in case that is necessary information08:14
cjearlsI'm having trouble understanding how the flow from source code to a working design is happening for a few of the pieces of the bitstream and software. I'm working on decoding it by reading the Python scripts, but they bounce around a fair bit between scripts, so I was hoping someone might know what direction I'm looking to go in and have advice on how to more effectively get there08:15
*** Bertl_zZ is now known as Bertl08:23
*** CarlFK has quit IRC08:50
*** futarisIRCcloud has quit IRC08:52
*** lkcl has quit IRC08:53
*** lkcl has joined #litex09:05
*** CarlFK has joined #litex09:58
*** Dolu_ has joined #litex11:26
*** Bertl is now known as Bertl_oO12:13
*** lambda has quit IRC15:05
*** lambda has joined #litex15:07
scanakciHi cjearls, I did not play with vexriscv. Based on my previous experience with another cpu, you should be starting with cpu.py for you your core. https://github.com/enjoy-digital/litex/blob/master/litex/soc/cores/cpu/vexriscv/core.py#L26018:29
scanakciFor instance, vexriscv fetches the necessary code here from pythondata_cpu_vexriscv folder. I am not sure how Linux-on-Litex-VexRiscv designed, though.18:30
*** peeps[zen] has joined #litex19:16
cjearlsscanakci: Do you mean core.py? It looks like you're right, I'll take a closer look and see if I can find what I'm looking for. Thanks.19:16
*** peepsalot has quit IRC19:16
*** peeps[zen] is now known as peepsalot19:16
*** cjearls has quit IRC20:29
scanakci@cjearls: yeah core.py. welcome20:40
*** CarlFK has quit IRC21:44
*** CarlFK has joined #litex21:50
*** CarlFK has quit IRC22:04
*** m4ssi has quit IRC22:23
*** acathla has quit IRC23:06
*** acathla has joined #litex23:08
*** Dolu_ has quit IRC23:22
*** kgugala has quit IRC23:59

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!