_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://freenode.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
rohitksingh has quit [Ping timeout: 256 seconds]
rohitksingh has joined #litex
Degi_ has joined #litex
Degi has quit [Ping timeout: 264 seconds]
Degi_ is now known as Degi
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
futarisIRCcloud has joined #litex
HoloIRCUser has joined #litex
HoloIRCUser1 has quit [Read error: Connection reset by peer]
CarlFK has quit [Remote host closed the connection]
CarlFK has joined #litex
gregdavill has joined #litex
_whitelogger has joined #litex
gregdavill has quit [Ping timeout: 246 seconds]
rohitksingh has quit [Ping timeout: 260 seconds]
ambro718 has joined #litex
HoloIRCUser1 has joined #litex
HoloIRCUser has quit [Ping timeout: 264 seconds]
<sajattack[m]> am I the only one getting a kernel panic running spisdcardboot?
<somlo> works great for me booting (bbl(linux-riscv64(busybox))) on litex+rocket
<sajattack[m]> post #435 and #436?
<somlo> at litex commit c547b2cc (as of a few hours ago
<sajattack[m]> hrm
<sajattack[m]> maybe my buildroot got messed
<somlo> actually, much faster than before (with the reclocking thing)
<sajattack[m]> let me try the official images
<somlo> not sure about buildroot -- I have busybox built into the kernel, wrapped inside BBL, as a single boot.bin file
<somlo> now I need to figure out how to make the SPI-mode SDCard visible to the Linux kernel, so I can mount it once I'm done booting
<somlo> I know there's "mmc_spi" to start, but no idea if it'll work out of the box or if it might need a bit of "surgery" first :)
<sajattack[m]> I keep getting this https://ghostbin.co/paste/rp7p4
<tpb> Title: rp7p4 - Ghostbin (at ghostbin.co)
<sajattack[m]> or some variation thereof
<sajattack[m]> sometimes it says the initramfs contains junk or something
<sajattack[m]> other times it kernel panics even earlier
<somlo> sajattack[m]: fwiw, we're exercising different #ifdef branches of spisdcardboot(), but we both have at least one spi_sdcard_readFile() and one boot() call in there
<sajattack[m]> ok
<somlo> so I think those work fine for both of us. It's what happens once you jump to the data you transferred over into memory that things go south for you
<sajattack[m]> yeah
<sajattack[m]> memtest is ok
<sajattack[m]> but maybe the sdcard is dirty somehow
<somlo> could be the stuff you transfer over is already corrupted somehow, or maybe some overrun of some kind ?
<somlo> I haven't played with vexriscv linux, so I don't know much about all the ways it can go wrong
<sajattack[m]> it worked before reclocking
<somlo> easy (if maybe a bit time consuming) would be to check out a pre-reclocking commit and build that, see if reclocking consistently breaks it for you
<sajattack[m]> yeah
<somlo> i.e, "git bisect" :)
<somlo> then you'd have a specific commit to blame for your troubles, and a slightly smaller problem space to deal with
<sajattack[m]> idk git bisect but I can git log and git checkout
<somlo> sajatacc[m]: web‪chick.net/node/99 (there's many more guides if you google)
<somlo> you'll love it :)
<somlo> pick a commit that works, pick one that breaks, let git tell you which ones to try until you find the one that broke your stuff
<sajattack[m]> cool
<sajattack[m]> `2bf31a31da336b628825aced248396b8ba3e3105 is the first bad commit`
<sajattack[m]> as I suspected
HoloIRCUser has joined #litex
HoloIRCUser1 has quit [Ping timeout: 250 seconds]
tucanae47 has joined #litex
rohitksingh has joined #litex
HoloIRCUser2 has joined #litex
HoloIRCUser has quit [Read error: Connection reset by peer]
Degi has quit [Read error: Connection reset by peer]
peepsalot has quit [Ping timeout: 250 seconds]
gregdavill has joined #litex
peepsalot has joined #litex
HoloIRCUser2 has quit [Ping timeout: 250 seconds]
HoloIRCUser has joined #litex