- 23 Feb, 2021 3 commits
-
-
Jonathan Currier authored
-
Jonathan Currier authored
also delay boot at kermit transfer by ~1s to allow the program to resume listening to the console
-
Jonathan Currier authored
Note that the intigration might want to be improved a bit.
-
- 22 Feb, 2021 3 commits
-
-
Jonathan Currier authored
-
Jonathan Currier authored
however none of the bits are hooked up.
-
Jonathan Currier authored
-
- 21 Feb, 2021 3 commits
-
-
Jonathan Currier authored
-
Jonathan Currier authored
-
Jonathan Currier authored
-
- 19 Feb, 2021 10 commits
-
-
Jonathan Currier authored
-
Jonathan Currier authored
note so really weird stuff is going on, simply commenting out/uncommenting an _early_dbg_abi call can change the behavior of print code invoked *before* it. (and interrupts are disabled, so it should all be polling)
-
Jonathan Currier authored
it seems injecting the waits has cause it to work... which means there is still a bug
-
Jonathan Currier authored
-
Jonathan Currier authored
-
Jonathan Currier authored
-
Jonathan Currier authored
-
Jonathan Currier authored
-
Jonathan Currier authored
-
Jonathan Currier authored
-
- 15 Jan, 2021 1 commit
-
-
Raptor Engineering Development Team authored
-
- 16 Oct, 2020 2 commits
-
-
Raptor Engineering Development Team authored
There is a conflict between the LiteX way of doing things and the POWER way of handling interrupt tables. LiteX expects to be able to put a ROM at address 0 and load an application into RAM at a higher address; POWER is architected to jump to exception handlers at 0x100...0x1000. As a result of this, we have taken the approach of placing generic exception handler entry / exit routines into ROM, and reserving a single pointer in SRAM to determine the C ISR handler location. If no application is loaded, this pointer is set to the BIOS ROM ISR. When an application loads, before reenabling interrupts, it needs to set __rom_isr_address to the address of the application's ISR, otherwise the BIOS ROM ISR will continue to be used. Tested to operate with the built-in UART in IRQ mode, both in BIOS and in loaded RAM application.
-
Raptor Engineering Development Team authored
-
- 01 Aug, 2020 3 commits
-
-
Raptor Engineering Development Team authored
This reverts commit f3dda2b1.
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
- 21 Jul, 2020 3 commits
-
-
Florent Kermarrec authored
-
Florent Kermarrec authored
-
Florent Kermarrec authored
-
- 20 Jul, 2020 7 commits
-
-
enjoy-digital authored
Fix Vivado crash when using 1:1 wishbone.Converter
-
enjoy-digital authored
wire up missing register bits.
-
enjoy-digital authored
interconnect/csr_bus: fix paged access warning
-
Ilia Sergachev authored
-
Jędrzej Boczar authored
Fixes an issue with Vivado which crashes with SIGSEGV when building litex-buildenv at: https://github.com/antmicro/litex-buildenv/commit/cc003bef3ac1407f9788ec8b7cc52d5981f8364a and litex bumped to 4a18b828, with options: CPU=mor1kx; CPU_VARIANT=linux; PLATFORM=arty; FIRMWARE=linux; TARGET=net The only difference in Verilog is that we avoid creating new Interface and doing `new_interface.connect(interface)`, so this shouldn't make any difference, but this somehow generates the error in Vivado (tested on v2018.3 and v2019.2).
-
Florent Kermarrec authored
software/liblitesdcard/spisdcard: remove optimization on receive_block (not working on all configs) and increase max clk_freq to 20MHz.
-
Florent Kermarrec authored
- Make sure MOSI is latched on start, MISO is stable during Xfer (last value). - Allow clk_divider down to 2. - improve test errors reporting with hex() on AssertEqual.
-
- 18 Jul, 2020 1 commit
-
-
bunnie authored
Not sure how they went missing...but just noticed them.
-
- 17 Jul, 2020 4 commits
-
-
Florent Kermarrec authored
-
Florent Kermarrec authored
-
Florent Kermarrec authored
-
Florent Kermarrec authored
-