lekernel changed the topic of #milkymist to: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs
xiangfu has joined #milkymist
gbraad has joined #milkymist
gbraad has quit [Changing host]
gbraad has joined #milkymist
jimmythehorn has quit [Quit: jimmythehorn]
fsk has quit [Quit: fsk]
antgreen has joined #milkymist
digshadow has joined #milkymist
digshadow has quit [Client Quit]
digshadow has joined #milkymist
hypermodern has joined #milkymist
hypermodern has left #milkymist [#milkymist]
Martoni has joined #milkymist
lekernel has quit [*.net *.split]
kristianpaul has quit [*.net *.split]
roh has quit [*.net *.split]
mumptai has joined #milkymist
kristianpaul has joined #milkymist
kristianpaul has joined #milkymist
lekernel has joined #milkymist
roh has joined #milkymist
kristianpaul has quit [Ping timeout: 255 seconds]
kristianpaul has joined #milkymist
kristianpaul has quit [Changing host]
kristianpaul has joined #milkymist
fsk has joined #milkymist
Gurty has quit [Ping timeout: 245 seconds]
mumptai has quit [Ping timeout: 240 seconds]
xiangfu has quit [Read error: Connection reset by peer]
xiangfu has joined #milkymist
azonenberg has quit [Read error: Operation timed out]
<larsc>
more Xilinx madness, I think I'll join the haters club. I tried to use their Linux driver for SPI on zynq today. Which of course didn't work at all, but after some fixing I got it to a point where it would only fail sometimes.
<larsc>
like 1 in 5 SPI transfers wouldn't start
<larsc>
you start a SPI transfer by writing a 1 to a register, repeating that line 5 times makes the issue go away
<larsc>
So I read through the datasheet and found this: 'The SPI reference clock (spi_ref_clk) must be set to a higher frequency than the CPU_1x clock
<larsc>
frequency.
<larsc>
'
<larsc>
spi_ref_clk was 100MHz and CPU_1x was 133MHz, so this explains why the edge is lost sometimes
<larsc>
But turns out the Xilinx tools don't allow you to set a higher frequency for SPI core than 100MHz...
<larsc>
Manually overwriting the clock register, so the core is clocked at 200MHz also fixes the issue
sb0 has joined #milkymist
aeris has quit [Ping timeout: 252 seconds]
sb0 has quit [Ping timeout: 276 seconds]
aeris has joined #milkymist
sb0 has joined #milkymist
sb0 has quit [Ping timeout: 272 seconds]
gbraad has quit [Ping timeout: 248 seconds]
gbraad has joined #milkymist
gbraad has quit [Changing host]
gbraad has joined #milkymist
<lekernel>
larsc, use lm32 :)
<lekernel>
you can run it at 200MHz on kintex 7
<larsc>
can't really compete with a dual core ARM with 1300 MIPS each, so that's not really an option
<larsc>
just got a call from one of their support guys, 'yeay, known issue, but we didn't bother to make the AR public'...
<Fallenou>
=)
<larsc>
but at least it will be fixed in 14.5
<larsc>
lekernel: It would be interesting to see though how well the lm32 would compare to the microblaze in our designs for non-zynq platforms
<lekernel>
already ran mibench on milkymist/lm32 vs. edk/microblaze, similar clock frequency and caches. milkymist is some 20% faster.
<larsc>
not bad
<larsc>
for some reason we seem to the microblaze on 100MHz even on K7
xiangfu has quit [Remote host closed the connection]
gbraad has quit [Ping timeout: 264 seconds]
aeris has quit [Ping timeout: 255 seconds]
aeris has joined #milkymist
kyak has joined #milkymist
digshadow has quit [Quit: Leaving.]
kilae has joined #milkymist
digshadow has joined #milkymist
digshadow has quit [Client Quit]
azonenberg has joined #milkymist
sb0 has joined #milkymist
<larsc>
das hackerhaus ist das schon viel besser
jimmythehorn has joined #milkymist
mumptai has joined #milkymist
<larsc>
ups
<larsc>
wrong channel
Martoni has quit [Quit: ChatZilla 0.9.90 [Firefox 19.0/20130218165301]]
lekernel has quit [Read error: Operation timed out]
sb0 has quit [Ping timeout: 272 seconds]
sb0 has joined #milkymist
lekernel has joined #milkymist
<mwalle>
Fallenou: could you send a patch for the CFG2 CSR to the binutils ml ?
<antgreen>
\
<sb0>
and I think for the other MMU CSRs too, if they are definitive?