cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #openFPGALoader
<cr1901>
can openfpgaloader be used to write the User Flash Memory of MachXO2 parts?
<cr1901>
And if not, where would be a good place to add this functionality (new flag? existing flag?)
<trabucayre>
currently no
<trabucayre>
only for machXO3D
<trabucayre>
using flash-sector
<cr1901>
Okay, I don't mind adding the functionality for openfpgaloader if it's accepted.
<cr1901>
if it'll be accepted*
<cr1901>
for machxo2* I mean
<trabucayre>
If you have an example I can check too
<cr1901>
Unfortunately, not right now. Lattice advertises "hey, we have user flash" for their parts, but doesn't actually make the process of _using_ them all that simple :'D
<cr1901>
I just got a MachXO2EVN board today. Looking for sample code to test the UFM
<trabucayre>
I also have this board but never tried to play with UFM
<trabucayre>
heuu... In fact not sure. Maybe I have tried to dump content
<cr1901>
I'm looking thru my PDFs now on how to get started
<trabucayre>
ok
<cr1901>
The "EFB usage" guide, which contains info on UFM, gives some links to reference designs. Unfortunately, they all assume you want to program the UFM via Wishbone interface proxy (analogous to JTAG proxy to SPI flash)
<trabucayre>
yep, I don't remember exactly but some informations may be found in machXO3 docs
<trabucayre>
I have to check, but not now, it's a bit late here :)
<cr1901>
understood... I'll make a toy design to play with
<trabucayre>
I bought mine during covid to help someone with EBR :)
<trabucayre>
(lockdown)
<cr1901>
That's when I did the bulk of MachXO2 REing. But recent events have convinced me to do some more
<trabucayre>
"recent events" ?
<cr1901>
It's a secret for now ;)
<trabucayre>
I have tried to adapt facade to my model -> fail :(
<trabucayre>
ok
<cr1901>
It needs work
<trabucayre>
when you know how to REing FPGA :)
<cr1901>
The most complex design I got working w/ facade was a UART
<trabucayre>
ok
* cr1901
is cheating a bit to generate a bitstream
<cr1901>
I took the output of the EFB-generator wizard, and asked Diamond to route that verilog file as-is with no user-constraints
<cr1901>
that way I can study how the EFB influences the bitstream w/o needing to bother actually making a working design
<cr1901>
trabucayre: Does openFPGAloader have a "dry-run" setting (parse input file but don't run commands)?"
<trabucayre>
no...
<cr1901>
No worries
<trabucayre>
I have piece of code using openFPGALoader to do that
<trabucayre>
or a simple return/comment section
<trabucayre>
TN1204 provides sequence
<trabucayre>
and machXO3D may help too
<trabucayre>
sequences are more or less same for all lattice devices
<cr1901>
Understood... it looks like Lattice will only generate EFM contents in JED files, not .bit files
<cr1901>
UFM*
<trabucayre>
for machXO .bit file is officially used to load
<trabucayre>
not to write?
<cr1901>
I've never played w/ machXO1 FPGAs, so I can't comment :(
<trabucayre>
Sorry but sleep time :(
<cr1901>
No worries, I'm rambling lol
<trabucayre>
:)
<cr1901>
I'll try not to flood the channel w/ my minddumps while you're asleep LOL
<trabucayre>
wait until I've finished my slice of salted butter bread and my first coffee. :)