[Libre-soc-bugs] [Bug 519] Get output from ulx3s serial port to show up in minicom
bugzilla-daemon at libre-soc.org
bugzilla-daemon at libre-soc.org
Thu Oct 22 03:32:34 BST 2020
https://bugs.libre-soc.org/show_bug.cgi?id=519
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Cole Poirier from comment #11)
> (In reply to Luke Kenneth Casson Leighton from comment #10)
> > > Ok committed and pushed. Next question before we can close this bug. Is
> > > running
> > > `./versa_ecp5.py --load` supposed to show output in the minicom terminal?
> >
> > if everything is wired up correctly yes.
> >
> > a good test is to run picorv32 litex. ask on the #litex freenode channel
> > how to do that.
>
> Looks like it's a configuration issue in our setup because I get the
> following interactive output in minicom from running:
> `litex-boards/litex_boards/targets$ ./ulx3s.py --load --device LFE5U-85F`
>
> An ideas of what I can do to connect our 'stuff' properly?
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/litex/florent/versa_ecp5.py;hb=HEAD
32 cpu_variant = "standardjtagnoirq",
check the ulx3s class, line 72. see how duplication means the two
near-identical classes get out of sync?
>
> ```
> Welcome to minicom 2.7.1
>
> OPTIONS: I18n
> Compiled on May 6 2018, 08:02:47.
> Port /dev/ttyUSB0, 16:19:20
>
> Press CTRL-A Z for help on special keys
>
> Read speed: 10MiB/s
>
> --============== Boot ==================--
> Booting from serial...
you could have stopped around here (maybe a few more lines).
it showed success, the rest was effectively spam, because nobody is intwrested
in the *contents* of the fact that picorv32 succeeded, just that it did in fact
succeed.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the libre-soc-bugs
mailing list