okay, so that could/should? also be -2 on this specific board, yes?
you can set it to -2 yes, using -2/-3 just allow more flexibility in the generated frequencies
is adding self.add_platform_command("set_property CONFIG_VOLTAGE 3.3 [current_design]") to Platform's _init_(): the correct way to fix the warnings about the config voltage (and similar for CFGBVS)?
is there some documentation regarding the LiteSATA IP I could read up on?
peeps[zen] has joined #litex
peepsalot has quit [Ping timeout: 240 seconds]
peepsalot has joined #litex
peeps[zen] has quit [Ping timeout: 260 seconds]
cjearls has joined #litex
I have a question about using a custom build of VexRiscv for Linux-on-Litex-Vexriscv:
Once I've correctly generated a new VexRiscv core with the hardware that I wanted to add, how do I add it to the linux-on-litex-vexriscv directory such that it is built instead of the default vexriscv core?
lf has quit [Ping timeout: 260 seconds]
lf has joined #litex
Also, is there a way to tell what the settings are for the default vexriscv core that's used for Linux-on-LiteX? I want to be sure I'm not removing anything important, just that I'm added the hardware I'm interested in
So if I want to add code to VexRiscv to define a new plugin, then to enable that plugin, where would that happen?
Is there somewhere I should be checking for this information or a description of the build process? I don't want to be wasting anyone's time with really basic questions if I can be finding the answer myself
I figure that since litex only deals with prebuilt .v files, you can build your own .v in whatever manner you like and then either overwrite one of the existing .v files or add a new variant