_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://libera.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
Degi_ has joined #litex
Degi has quit [Ping timeout: 252 seconds]
Degi_ is now known as Degi
<sajattack[m]> seems #siglenthax died with freenode
<sajattack[m]> unless there's a libera with another name
FabM has joined #litex
FabM has joined #litex
cr1901 has quit [Ping timeout: 260 seconds]
cr1901 has joined #litex
<_florent_> sajattack[m]: Hi, for things related to https://github.com/360nosc0pe/scope you can discuss it here
<sajattack[m]> Alright thanks
<_florent_> for now the project is pause, but I'm playing to play with it again with micropython
<sajattack[m]> I ordered an SDS1104X-E yesterday and was trying to decipher the eevblog instructions but I think I've figured it out now
<sajattack[m]> I was curious if your yocto would work with default gateware or only the custom bitstream?
<_florent_> with micropython configuring/handling the peripherals, providing a standalone scope and processing still done on the Host with GlScopeClient
<sajattack[m]> redbeard in the unnamed re discord has made some progress towards a buildroot/yocto for the default gateware as I understand it
<_florent_> sajattack[m]: I sorry I haven't used the yocto part, on my side I reused the existing reverse engineering of the Scope and have been porting LiteX to it
<_florent_> so only focused on the PL side
<sajattack[m]> Oh I didn't realize it was someone else
<_florent_> @
<_florent_> G33KatWork here has been involved in the yocto part IIRC
<_florent_> If you want to play with the default gateware/software over SCPI, there are also some efforts to support it with GLScopeClient (#scopehal)
peepsalot has quit [*.net *.split]
linear_cannon has quit [*.net *.split]
_franck_ has quit [*.net *.split]
awordnot has quit [*.net *.split]
shorne has quit [*.net *.split]
RaYmAn_ has quit [*.net *.split]
RaYmAn_ has joined #litex
shorne has joined #litex
linear_cannon has joined #litex
awordnot has joined #litex
_franck_ has joined #litex
peepsalot has joined #litex
<tnt> Any special trick to get litex to generate a .bin instead of .bit ?
<tnt> Heh, build <> target env.
<sajattack[m]> I think the relevant bit is line 130
Guest53 has quit [Quit: Ping timeout (120 seconds)]
<sajattack[m]> Or maybe I misunderstood your comment
<tnt> Oh no, it's me ... I confused channels.
<tnt> I also asked somewhere else where to program the fpga with OSS tools and I thought this was an answer to that.
<tnt> I ended up instaling Vivado Lab edition to the remote machine so I could program the fpga.
<tnt> Unfortunately ... bitstream doesn't seem to do anything :/
<tnt> If I just have the SoCCore and pretty much nothing else, I should still see something on the serial right ?
<sajattack[m]> I think so
<tnt> Damn, being remote suck ... can't check wiring, can't see if leds are blinking, ...
<_florent_> tnt: OpenOCD will work allow to load the .bit, but not sure anyone did the BSCAN<>SPI proxy bitstreams for Ultrascale
<_florent_> tnt: you can try a very minimal bistream:
<_florent_> with LiteX, set with_uart to False
<_florent_> and
<_florent_> serial_pads = platform.request("serial")
<_florent_> self.comb += serial_pads.tx.eq(serial_pads.rx)
<_florent_> Then just see if you get an echo :)
<tnt> _florent_: Ah thanks, I was just looking how to do that :p ( do an echo without conflicting ).
<tnt> Well, echo seems to work.
<_florent_> ok, so UART is ok, maybe an issue with the clock?
<_florent_> you can test something like this:
<tpb> Title: hastebin (at hastebin.com)
<_florent_> ah, you can directly pass serial_pads to IOStreamer
<_florent_> otherwise can you share the target file you were testing?
<tnt> Sure I can upload them, gimme a sec.
<tpb> Title: Index of /~tnt/stuff/adi/ (at people.osmocom.org)
<_florent_> it looks fine, are you sure the 122.88MHz clock is enabled at startup?
<tnt> I am not ... I just hope so because it's the only clock source to the PL I could find on this board ...
<_florent_> If the PCIe is plugged, you can probably get the 100MHz PCIe clock with something like this:
<tpb> Title: Snippet | IRCCloud (at www.irccloud.com)
<tnt> _florent_: I'll give that a shot.
<tnt> ERROR: [DRC REQP-1929] IBUFDS_GTE4_O_may_only_drive_GTxE4: The IBUFDS_GTE4 IBUFDS_GTE4 O pin may only be connected to the GTREFCLK pin of a GTHE4_COMMON, GTHE4_CHANNEL, GTYE4_COMMON, or GTYE4_CHANNEL component. The IBUFDS_GTE4 O pin cannot drive MMCME2_ADV.
<tnt> ERROR: [DRC RTSTAT-1] Unrouted nets: 1 net(s) are unrouted. The problem bus(es) and/or net(s) are main_crg_clkin.
<_florent_> ok, you can try with the ODIV2 output
<_florent_> and set p_REFCLK_HROW_CK_SEL=0 to have ODIV2 = O
lexano has joined #litex
<tnt> Can litex configure the PS part to get its clock from there ?
<tnt> (on a 10k$ dev board with thousands of IO, you would think they'd put a oscillator somewhere that's always running ....)
<_florent_> tnt: Have you been able to do a test with the PCIe clock?
<tnt> _florent_: yeah, no luck either. I had to add a BUFG_GT after the IBUFDS_GTE4 for it to route, but still nothng.
<tnt> I made a 'cloked' echo ( self.sync += serial_pads.tx.eq(serial_pads.rx) ) to be as simple as I could, and no joy.
<tnt> I asked for configrmation that the board was indeed plugged into a PC, didn't get an answer yet.
<_florent_> for the Zynq, you can look at:
<_florent_> and
<_florent_> tnt: otherwise, here is something I was doing on a 7-series board to use the clock from the configuration internal oscillator:
<tpb> Title: Snippet | IRCCloud (at www.irccloud.com)
<_florent_> you can probably do something similar on Ultrascale
<tnt> _florent_: tx, I'll give that a shot.
<tnt> I got confirmation the board is in a pcie slot at least.
<tnt> _florent_: \o/ Got to the bios prompt :)
<tnt> I guess now the best would be to use that clock to configure the 120.88 MHz clock and actually use that as the system clock.
peeps[zen] has joined #litex
peepsalot has quit [Ping timeout: 252 seconds]
<_florent_> tnt: great, so you used the STARTUPE3's CFGMCLK?
<tnt> ATM I just let Xilinx remap the STARTUPE2 but I'll clean it up to E3 version.
<tnt> Only difference is clock is 50MHz and not 65MHz
<_florent_> tnt: ok, as you were saying it's really a shame you don't have a valid input clock available from the PL for a board of this price :)
peeps[zen] has quit [Ping timeout: 245 seconds]
peepsalot has joined #litex
FabM has quit [Quit: Leaving]
peeps[zen] has joined #litex
peepsalot has quit [Ping timeout: 252 seconds]
peepsalot has joined #litex
peeps[zen] has quit [Ping timeout: 245 seconds]
<G33KatWork> sajattack[m]: I did some yocto stuff for the Siglent scope, but it was all custom. We ditched everything Siglent did including the gateware, so at this stage it's pretty useless. We started building our own, but florent got way farther with LiteX than we did
<G33KatWork> I also reverse engineered a good part of the hardware
<sajattack[m]> ok good to know, thanks
Guest53 has joined #litex
<Wolf0> G33KatWork: I'm working on doing that with Xilinx's HBM2 memory controller. It's a REALLY cool design
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
C-Man has joined #litex
nickoe has joined #litex
Guest53 has quit [Ping timeout: 256 seconds]