_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
NotHet has joined #litex
<NotHet> So couple days ago I posted that Zephyr was hanging. I think I found out why. The register definitions in the Zephyr/litex_timer.c are all wrong. If I hack it to have updated addresses Zephr runs
<NotHet> It seems like the spacing between CSRs AND the location of some of the registers changed, but I am not sure
<NotHet> Might all of the litex drivers have this? I'm going to try and figure out what all could have been impacted, but I am _totally_ new to this ecosystem and its a bit of a stumble around. What all should I be looking for?
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #litex
<Wolf0> _florent_: I found this out, that's right. It's eye detection
<NotHet> Looks like the eth_liteeth.c has bad register definitions too. Bit these are a bit less straight forward to hack-to-fix
NotHet has quit [Remote host closed the connection]
<_florent_> NotHet : This is probably related to the merge https://github.com/enjoy-digital/liteeth/pull/74 (that removes an error CSR), I'll look at this tomorrow
ewen has quit [Quit: leaving]
guan has quit [Ping timeout: 252 seconds]
guan has joined #litex
key2 has quit [Read error: Connection reset by peer]
key2 has joined #litex
<Wolf0> https://www.reddit.com/r/FPGA/comments/q515qd/things_xilinx_wont_tell_you_about_their_internal/ - It took me way too long to write this, but it came out okay
key2 has quit [Ping timeout: 260 seconds]
key2 has joined #litex
NotHet has joined #litex
zjason has quit [Remote host closed the connection]
zjason has joined #litex
NotHet has quit [Remote host closed the connection]
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
NotHet_ has joined #litex
NotHet_ is now known as NotHet
NotHet has quit [Read error: Connection reset by peer]
NotHet has joined #litex
NotHet has quit [Client Quit]
NotHet has joined #litex
<NotHet> _florent_ thanks. I've also created a Zephyr PR for the timer fix https://github.com/zephyrproject-rtos/zephyr/pull/39304
NotHet has quit [Ping timeout: 252 seconds]
NotHet has joined #litex
<_florent_> NotHet: Thanks, I have a preference to revert the LiteEth change because otherwise we'll also have to update other drivers
NotHet has quit [Ping timeout: 265 seconds]
linear_cannon has quit [Ping timeout: 252 seconds]
linear_cannon has joined #litex
NotHet has joined #litex
NotHet has quit [Ping timeout: 252 seconds]
Guest48 has joined #litex
Guest48 is now known as nosky
<nosky> hi everyone, does anyone know what is the cheapest ice40 fpga that can do SATA I ?
<tnt> None of them.
<nosky> I'd have to use a SATA controller? Or maybe a fast serializer (mux) ?
<tnt> There used to be external chips but I don't think you'll find any anymore.
<tnt> But the ice40 is kind of ill suited for that anyway ... why do you want to use it to do _sata_ ?
<nosky> to get access to multi-terabyte hard drives
<tpb> Title: STARTECH.COM Ide Pata To SATA Adapter Converter For HDD/SSD/odd 40-pin - IDE2SAT2 - Redcorp.com/en (at www.redcorp.com)
<tnt> and then just access it as PATA.
<tnt> which would be way more doable on an ice40 class device. Something like an HX8k would probably do.
<nosky> do you know what kind of chip are they using on that adapter? I want the sata connector to be on the same board as the fpga
<nosky> found it, JM20330, but it's not on sale anymore
<nosky> nevermind, found it on aliexpress. Thanks for the great idea! https://www.aliexpress.com/item/1005002000538254.html
<tpb> Title: MeiMxy JM20330 JMH330 QFP NEW HDD CHIP 1PCS|Integrated Circuits| - AliExpress (at www.aliexpress.com)
NotHet has joined #litex
<NotHet> _florent_ Did the liteeth's change effect Timer's CSRs too? Looking to know if I should keep my PR or cancel it. Not sure how it all fits together, so maybe silly question.
<NotHet> Seems like the ethlite and the timer are unrelated problems? Like Timer CSRs are using the old style 8 bit CSR bus to access the 32 bit registers. But the LiteX SOC is using 32 bit wide CSR bus now. Which would mean keep the PR open?
NotHet has quit [Ping timeout: 252 seconds]
NotHet has joined #litex
<NotHet> Actually I think I see a problem in my PR now. The write into TIMER_RELOAD and TIMER_LOAD are using the 8 bit CSR bus....
NotHet has quit [Ping timeout: 252 seconds]