billchenchina has quit [Ping timeout: 256 seconds]
vagrantc has joined #riscv
pecastro has joined #riscv
FL4SHK has quit [Ping timeout: 264 seconds]
FL4SHK has joined #riscv
prabhakarlad8 has quit [Ping timeout: 260 seconds]
jobol has joined #riscv
Xyz has joined #riscv
vagrantc has quit [Quit: leaving]
prabhakarlad has joined #riscv
junaid_ has joined #riscv
junaid_ has quit [Ping timeout: 260 seconds]
davidlt has quit [Ping timeout: 264 seconds]
davidlt has joined #riscv
rurtty has joined #riscv
Trifton has quit [Quit: Error: no route to host]
pedja has joined #riscv
BootLayer has quit [Quit: Leaving]
EchelonX has joined #riscv
rurtty has quit [Ping timeout: 265 seconds]
jacklsw has joined #riscv
zjason`` has joined #riscv
zjason` has quit [Ping timeout: 260 seconds]
aerkiaga has joined #riscv
vagrantc has joined #riscv
billchenchina has joined #riscv
<geertu>
conchuod: Looks like I missed the {microchip-=>}mpfs-icicle-kit.dtb rename...
<geertu>
Hence I've been using an old DTB sinc quite a while. However, when switching to the new DTB, it hangs on starting the kernel. I verified that behavior with v6.1-rc7 and riscv defconfig.
BootLayer has joined #riscv
<conchuod>
Unless you're going to update your fpga image, perhaps you should stay there geertu..
<conchuod>
I've been trying to keep the DT up to date with whatever the most recent fpga image is
<geertu>
IC
<geertu>
Basically I wanted to try the LEDs, now they have been enabled ;-)
<conchuod>
The memory got moved around, because of course that's configurable...
<geertu>
I weas indeed puzzled by the change of addres for some nodes...
<conchuod>
I've been kinda unsure as to how I should handle that with a new dts every time something gets moved around - because it's not just DDR thats been moved
junaid_ has joined #riscv
<conchuod>
s/with/without
<conchuod>
I've resorted to changing the compatible, but I'm open to any better suggestions!
<geertu>
Changing the compatible string sounds fine to me.
<geertu>
However, do we want to keep separate DTS files with the older versions around?
<conchuod>
Yeah, that's what I mean. It sounds like something that could bloat like crazy (although hopefully not..).
<geertu>
How do I find out the rtl version I have?
<conchuod>
Good one.
<conchuod>
The HSS spits out it's version number, something like 0.99.29
<geertu>
0.99.16
<geertu>
BTW, as there is no reset switch on Icicle, I guess pulling J19 low is the way to go?
<conchuod>
The button SW18 should do it
rurtty has joined #riscv
<conchuod>
But I that may be more recent that your rtl.. .16 predates us printing the HSS version in our release notes ha
<conchuod>
2021.04 is what you have AFAICT geert
<geertu>
conchuod: Right, SW4 resets the board. Who guess the RTL uses a debug switch for reset? ;-)
<conchuod>
I think that's reconfigurable ha
<conchuod>
They implemented HSM in the most recent HSS versions so if you do decide to update you'll at least get that.
<geertu>
HSM?
<conchuod>
Sorry, SRST
<conchuod>
Muddling my acronyms today.
<geertu>
SRST?
<conchuod>
The opensbi reset extension
<geertu>
OK, but that doesn't help for remote control in a farm.
<geertu>
So J19?
<geertu>
or soldering on SW4
<conchuod>
J19 low should do it
<geertu>
Yep
<conchuod>
Either way Geert, I am not sure what to do about the "old" reference design DTs. I think the plan is to drop anything fabric related entirely and get it from overlays in the future. But for the previous iterations idk
<geertu>
conchuod: So I should use the old DTS from just before microchip,mpfs-icicle-reference-rtlv2203 was added, and re-add the new devices like GPIO and LED?
<conchuod>
Yeah, should be okay.
___nick___ has joined #riscv
<geertu>
somlo: conchuod: The DTS from 7eac0081a8e9 (rtlv2203) also seems to boot
motherfsck has quit [Ping timeout: 265 seconds]
<conchuod>
Yeah that one should too, the memory map is the same. There's some additional peripheral in the fabric I think compared to what you have - the PWM and I2C I think.
<conchuod>
s/the same/mostly the same/
davidlt has quit [Ping timeout: 248 seconds]
kehvo has quit [Ping timeout: 248 seconds]
kehvo has joined #riscv
junaid_ has quit [Ping timeout: 260 seconds]
billchenchina has quit [Remote host closed the connection]
kehvo has quit [Changing host]
kehvo has joined #riscv
motherfsck has joined #riscv
pecastro has quit [Ping timeout: 260 seconds]
<somlo>
geertu: ?
<somlo>
geertu: is this in any way related to litex? :)
<geertu>
somlo: Sorry, silly mistake
<geertu>
somlo: I might have found the reason of the CRC errors. Looks like I had plugged the OrangeCrab in a different USB port.
<geertu>
My machine has USB 2.0, 3.1 Gen 1, and 3.1 Gen 2.
<somlo>
geertu: no worries :) oh, and while we're talking DTBs, my hope is that for FPGA based SoCs meant to run Linux there's enough spare capacity to build the DTB into the "bios" that's included in the bitstream (particularly a TODO item of mine in connection to litex)
<somlo>
all this side-loading of DTBs (or building them into the opensbi image) is wearing thin for me :)
<geertu>
The latter might have issues. With the USB 2.0 port, it worked on first try, but is slower than before. So perhaps the 3.1 Gen1 port is the best one ;-)