<ktemkin>
(it'll take any iterable for ports; and not just lists -- that's just missing the terminal ',' that makes python interpret it as a tuple rather than just a single element)
<ktemkin>
so `ports=(top.led,)` is okay, since that generates a 1-element tuple; but `ports=(top.led)` is equivalent to `ports=top.led`, which is a signal where it expects an iterable of signals
<awygle>
ah, thanks
Vinalon has joined #nmigen
<Vinalon>
Hello! I have a quick question about using nMigen with iCE40 chips: does anyone know if it is possible to use their internal oscillators as a clock source?
<Vinalon>
All of the board definition files that I can see in the 'nmigen_boards' package seem to use an external oscillator, and define the 'default_clk' value as a pin Resource.
<Vinalon>
Thanks!
<Degi>
Hm I think you can
<whitequark>
it is possible; do you have a board that does not have any oscillator at all, or do you just want to use one of existing boards with SB_LFOSC/SB_HFOSC
<whitequark>
?
<Vinalon>
I'm thinking of Gnarly Grey's 'Upduino' - it has a 12MHz oscillator which is broken out onto one of the board's pins, but it isn't connected to the FPGA by default
<Vinalon>
It looks like their examples use the HFOSC oscillator, if I'm reading them right
<Vinalon>
(And it uses an iCE40UP5K-SG48)
<whitequark>
ok, so this will ideally require a small modification to the nMigen vendor code for iCE40