#timvideos

mithro: Yes, I wanted you to review my commit yesterday for another round of feedback (and totally forgot to tell you).

cr1901_modern: Please put a comment on the pull request saying as such - otherwise I'll ignore it :-P

mithro: https://github.com/timvideos/flterm/pull/3#issu... :D

Title: Add XMODEM support compatible w/ HDMI2USB by cr1901 · Pull Request #3 · timvideos/flterm · GitHub (at github.com)

cr1901_modern: Just two minor changes and we can merge...

mithro: Ok, cool

CarlFK[m]: Your new bug doesn't make any sense :-P

mithro: What's wrong with the brace wrapping on the doxygen doc blocks? They all have that ending

oh wait wait nevermind

mithro: Pushed

cr1901_modern: merged - now how about the other side :-P

mithro: Working on it :P

mithro: Do you have a pinout for the JTAG header?

cr1901_modern: On?

mithro: On Opsis... I wanted to see whether I could program the FPGA from Windows via direct connection to FPGA's JTAG pins

(this appears to be "no")

cr1901_modern: You should most definitely be able to do that

cr1901_modern: That is how _florent_ does it

cr1901_modern: The pins are standard positioned and labeled on the silkscreen

Oh... oops

mithro: I assumed I couldn't do it b/c I read the FPGA's JTAG pins go the the FX2 chip

cr1901_modern: They do

Is it a chain of multiple devices?

FX2, then LX45?

Nope, accoding to OpenOCD, only thing there is the FPGA...

cr1901_modern: Correct

hrm, Tera Term also can't display characters properly in windows using this driver ._.

And neither can PuTTY (which numato themselves use

mithro: ^^ What's the easiest way to get in contact w/ Numato?

cr1901_modern: With the Mimas?

mithro: Sadly, it extends to the Opsis too

cr1901_modern: We don't have windows drivers for the Opsis?

mithro: No, we do... just the serial port has the same problem w/ garbled characters on the Opsis as it does w/ the Mimasv2

cr1901_modern: Where are the Opsis windows drivers?

mithro: http://numato.com/product/numato-opsis-fpga-bas... Downloads tab

Title: Numato Opsis: FPGA-based open video platform | Numato Lab (at numato.com)

I started creating Windows drivers here -> https://github.com/mithro/HDMI2USB-and-Numato-O... but never finished it...

Title: GitHub - mithro/HDMI2USB-and-Numato-Opsis-Windows-Drivers: Drivers and related code/data for improving the hardware experience for the HDK on Windows (at github.com)

Wow, numato's website just changed...

I've never seen them before -- so no guarantees they work at all :-P

lol what

official windows drivers!?

"you'll need a code-signing certificate" there's a way around this so you can deploy self-signed drivers without requiring test mode

wow

but I don't remember the details

they've actually made proper inf/cat files for the usb device id's

just a cursory look over the zip contents just makes the device recognised properly under windows (capture, terminal, tofe lowspeed io), doesn't provide any software

mithro: i'm amused this happened without your knowledge lol

also this means they're selling them again?

xfxf: Well, I sent them files to sign and stuff and they sent me stuff back - I didn't realize they had published stuff

mithro: ah, the contents of their zip look the same as your repo

... bahaha, really :P. Nice!

It *definitely* wasn't finished

i rly should finish the bloody UI

in any case, something's very wrong w/ both Numato serial ports

xfxf: Yes you should

I don't have a way to debug this...

i was quite enjoying writing it, different paradigm to web programming

actually had a legitimate reason to use explicit threading

cr1901_modern: I wouldn't waste time on it

mithro: I don't intend to, but it's still a bug/problem for windows development.

cr1901_modern: Log a bug on the HDMI2USB-fx2-firmware repo about it

mithro (IRC): looks like that edid change landed ^ed6c81b (Tim Ansell 2017-08-17 13:31:39 +1000 339) {

mithro: Will do

my opsis version built: Jul 27 2017 01:11:25

mithro: Just FYI, I've never had issues w/ FTDI or Keypsan CDC drivers; Numato seems to be the only place where I have issues.

CarlFK[m]: Hrm.... Looking at https://github.com/timvideos/HDMI2USB-litex-fir... it seems like it was 8 months ago?

Title: HDMI2USB-litex-firmware/firmware/processor.c at master · timvideos/HDMI2USB-litex-firmware · GitHub (at github.com)

hmm.. um..

mithro: Btw... you said you have a blob of Numato's PIC firmware for the mimasv2 somewhere? (Just in case)

cr1901_modern: Haven't had time to look for it yet

be back later - getting lunch

mithro: That's fine... have fun

CarlFK[m]: plug in a Windows or Mac computer

mithro: um... no. ;) How about I file a bug report with whatever that GUI is? Whats the command line tool to show whatever that string is called ?

xrandr --xprops I think?

mithro : Actually I feel asleep last night so I fixed some of the errors but I try to fix all the errors by tonight.

Ishan_Bansal: no hurry, make sure you get good nights sleep :-)

mithro: juser@cnt1:~$ hwinfo --monitor --short

monitor: HDMI2USB-1 HDMI2USB-2 Acer AL1511

CarlFK: hrm?

hwinfo --monitor shows Model: "HDMI2USB-2" Vendor: OHW

CarlFK: That is what I expect?

mithro: yes - mostly just showing you what the command is in case you need it

issue closed. Now I can make coffee

CarlFK: Happy to solve your bug before you created it :-P

mithro: do more of that! :p

mithro: I just realized something (I think)... the opsis bitstream (i.e. the .bit/.bin file generated by ISE) embeds an extra copy of the LiteX BIOS in addition to the copy that's stored in flash. Is this correct?

cc: _florent_ ^^

cr1901_modern: yes

cr1901_modern: we want the same flash layout for consistence

But having an embedded gateware means we don't have to flash the bios seperately

mithro: So why doesn't mimasv2 have the same issue?

The mimasv2 doesn't have the space being an lx9

cr1901_modern: at some point the lx45 in the Atlys / Opsis might get to full and we have to kick the bios out

We should probably do that for the hdmi2usb target at some point

I see... I tried reprogramming the opsis earlier... just as a test I loaded a bitstream by itself (no flash), and was surprised to see the LiteX BIOS w/ a "Sept 6, 2017" date

(instead of a MiSoC BIOS w/ Jan 2016 date :P)

So it threw me off a bit

Sorry

No worries

right now I have a bigger issue. I flashed new firmware successfully, but I lost ttyACM0 :/

dmesg says: Product: Opsis (JTAG Mode)

It does make it quick to load the gateware and then tftp the firmware during development

mithro: True :P

cr1901_modern: the FPGA will reset the FX2 after booting

So this indicates the FPGA failed to boot properly (because it didn't exist JTAG mode)?

Not necessarily

cr1901_modern: I sent you a lsio board right?

mithro: Yes, you did. It's attached to my Opsis right now

cr1901_modern: you can use the USB UART on that too see everything even when the FX2 is being reset

You have to set an environment variable to get that to happen

To build a gateware with lsio board support

Otherwise, just remove the jumper that will prevent the FPGA from resetting the FX2

mithro: Worth a shot. B/c right now my current status is... I can program the Opsis flash via my JTAG adapter (TLDR; it is most convenient for me right now compared to the "mode switch" way). But ttyACM1 decided to disappear when I power cycled the board

(power cycle == "unplug it/plug it back in")

What target are you flashing with at the moment?

The flash.bin generated from opsis_lm32_base + bios + hdmi2usb firmware

I flashed it at address 0

The fx2 should come up in JTAG mode in that config in theory

Btw at some point I want to get mode switch working on windows

mithro: Unplugging opsis USB cable now and plugging back in.

Now we have fx2 loader in python that should be more doable

mithro: "Btw at some point I want to get mode switch working on windows" Understood. Just doing what I thought would be the quickest way :P.