<promach>
corecode : is your usb verilog code posted in github repo ?
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh_work has joined #yosys
pie___ has joined #yosys
pie__ has quit [Ping timeout: 244 seconds]
lutsabound has quit [Quit: Connection closed for inactivity]
emeb has quit [Quit: Leaving.]
rohitksingh has joined #yosys
<jayaura>
Hi, icebox_stat can list how many resources were used, but can some tool list whats the maximum available resources for the fpga the design was compiled for ?
ZipCPU has joined #yosys
leviathanch has quit [Remote host closed the connection]
m4ssi has joined #yosys
rohitksingh has quit [Remote host closed the connection]
rohitksingh has joined #yosys
leviathanch has joined #yosys
<corecode>
promach: i don't have usb verilog code
<corecode>
jayaura: you mean what the model has resources?
citypw has quit [Ping timeout: 244 seconds]
<jayaura>
corecode: yes, like giving the resource summary as "GBUF: 8 of 8" instead of "GBUF: 8" as I see now
<corecode>
i guess you could modify the code
<jayaura>
I mentioned gbuf figuratively.
<corecode>
yes
<jayaura>
i mean, the toolchain already know what resouces the fpga part contains. why not just say it :P
<corecode>
because you didn't change the code yet
<jayaura>
is that necessary? when I do a clean build, shouldnt it report the used and available resources?
<corecode>
what do you mean by clean build
<daveshah>
Both arachne-pnr and nextpnr will print both resource usage and total available during pnr
<jayaura>
Ah sorry my mistake. I needed to look inbetween. I was looking at the end. arachne-pnr was only reporting span4 and span12 at the end, and not the LCs statistics, which was summarized right after placement
<promach>
corecode : wait, I thought you said coded something on usb ?
<corecode>
yes, for microcontrollers
<promach>
so, the code is not in verilog ?
<promach>
corecode
<corecode>
no, it's code, not design
<promach>
corecode : I do not get you
<promach>
I remembered you said you coded something on usb ?
<promach>
"it's code, not design" ??
proteusguy has joined #yosys
massi_ has joined #yosys
<corecode>
yes, code
<corecode>
for a microcontroller
<corecode>
no hdl
<promach>
c ?
<corecode>
yes
<promach>
I really do not want to deal with the usb linux driver c code
<promach>
that is so ugly to debug if you really need to (which I think is bug-free)
<promach>
corecode
<corecode>
what is bug free?
<promach>
free of bugs
<corecode>
what is bug free
<promach>
like receiving the wrong data from the usb protocol
<MoeIcenowy>
but I think I will choose to use the oscillator on board with my own board ;-)
<MoeIcenowy>
just borrow a bitstream from UPduino now to test
<MoeIcenowy>
my iCE40UP5K-SG48I's arrived LCSC at Shenzhen today
<MoeIcenowy>
and will ship to me tomorrow
<tnt>
oh they have ice40s now ?
kraiskil has quit [Ping timeout: 240 seconds]
<corecode>
MoeIcenowy: where are you at?
<MoeIcenowy>
tnt: no, it's digikey via LCSC ;-)
<MoeIcenowy>
corecode: Guangzhou
<corecode>
ah, close to sz
<corecode>
or?
<MoeIcenowy>
yes, close to sz
<MoeIcenowy>
1 hrs of high-speed train
<MoeIcenowy>
s/hrs/hr/
<corecode>
did you move there or were you born there?
<tnt>
MoeIcenowy: oh they do that ? didn't know
<MoeIcenowy>
corecode: moved here 9 yrs ago
<MoeIcenowy>
tnt: only available at China
<corecode>
do you like it?
<MoeIcenowy>
strangely the components at Digikey via LCSC is (very) slightly cheaper than Digikey itself
<corecode>
maybe special contract
<MoeIcenowy>
for example, the price of iCE40UP5K-SG48I on Digikey itself is CNY 49
<MoeIcenowy>
but on Digikey via LCSC it's 47
<MoeIcenowy>
and Digikey itself requires one order must be at least CNY300
<MoeIcenowy>
but Digikey via LCSC has no restriction
<MoeIcenowy>
(yes, my order is only 5 iCE40UP5K-SG48I's, so it's less than 300
<corecode>
i guess they pool orders
rohitksingh has quit [Ping timeout: 255 seconds]
rohitksingh has joined #yosys
ec0 has quit [Ping timeout: 250 seconds]
ec0 has joined #yosys
maikmerten has joined #yosys
kraiskil has joined #yosys
leviathanch has quit [Remote host closed the connection]
citypw has quit [Ping timeout: 240 seconds]
X-Scale has quit [Ping timeout: 244 seconds]
X-Scale` has joined #yosys
massi_ has quit [Remote host closed the connection]
<emeb>
corecode: yay - got my old u4k breakout board blinking w/ your icestorm work. Thanks for getting that going.
lutsabound has joined #yosys
<corecode>
cool
<emeb>
corecode: do you have any idea how much effort it would be to add support for the LED driver core in u4k? Without that those three pins appear to be unusable.
<corecode>
you can put ios on there
<corecode>
but they are OD
<emeb>
corecode: Ah ok - I'll give that a shot.
<emeb>
OD is fine for driving LEDs - just don't get the current control I guess.
<corecode>
yes
<emeb>
seems to work fine. thx.
<corecode>
cool
rohitksingh has quit [Remote host closed the connection]
<emeb>
so I guess it's just that the proper hooks for those IP cores isn't in nextpnr at the moment?
<corecode>
no
<corecode>
the cores for the u4k are a bit different
<emeb>
ah, so it would be necessary to RE them and add support to yosys too.
<corecode>
yes, most of the work will be in icestorm
<emeb>
ok, probably not really worth it just to save a few resistors. :)
<emeb>
corecode: is there anyplace I can look to see exactly what features of u4k are unsupported, or is it just a "try and find out" problem?
<corecode>
yes, look in icebox.py at the list of peripherals
<ylamarre>
Documentation is in the code! :D
<ylamarre>
Ah! :P
<corecode>
the u4k ones are really short compared to the 5k
<corecode>
so those can be reversed and/or confirmed
<emeb>
corecode: thanks - I'll take a look.
<emeb>
(don't know the ice* codebase well enough to know where everything is)
<daveshah>
emeb: The resource utilisation print of nextpnr is also a good list of what primitives are available
<daveshah>
although, of course, it doesn't tell you which will actually work
* ylamarre
was actually joking.
<ylamarre>
But turns out, code IS the doc in this case...
<emeb>
daveshah: cool
<emeb>
ylamarre: I figured you were actually right.
<ylamarre>
emeb: From what I remember icebox.py is quite nice to go through. Not too difficult to read last time I checked.
<emeb>
so looks like all the stuff I care about is there.
<ylamarre>
But that was like 3 years ago when there was only support for ice40LP/HX
<emeb>
looking at it now - it's a big file but not hard to navigate.
<emeb>
heh - u4k extra bits db "made up" - I guess that means they don't actually work.
<corecode>
yea i didn't bother with trying them for a different footprint
<emeb>
heh, yeah. the other footprints are not super easy to design with.
<emeb>
I've got one of the "official" Lattice breakouts for the u4k and it's got the little WLCSP-36 part. Hard to imagine the kind of PCB rules you'd need to use that.
<corecode>
yey so you can port for that footprint
<emeb>
lol yes - if I knew WTF I was doing. :)
<corecode>
yea that's how i started
<emeb>
I know that clifford wrote up some #exactsteps for the the process of adding stuff a few years back. I wonder if those still apply.
ZipCPU has quit [Ping timeout: 257 seconds]
ZipCPU has joined #yosys
kraiskil has quit [Ping timeout: 250 seconds]
<corecode>
so if you just want to map out connections, just instantiate the IP core and look at the explain output
m4ssi has joined #yosys
lutsabound has quit [Quit: Connection closed for inactivity]
lutsabound has joined #yosys
maikmerten has quit [Remote host closed the connection]
jwhitmore has joined #yosys
gsi__ is now known as gsi_
<emeb>
corecode: for the n00b, which tool generates explain?
<emeb>
derp - icebox_explain. :P
jwhitmore has quit [Ping timeout: 245 seconds]
<corecode>
:D
<emeb>
is it my imagination or are the cell coords given by explain off-by-one from those displayed in the icecube floorplanner?
<emeb>
nah - they're fine.
m4ssi has quit [Quit: Leaving]
lutsabound has quit [Quit: Connection closed for inactivity]