#timvideos

mithro: I am adding notes to the readme, like PATH=$PWD/conda/bin:$PWD/bin:$PATH

CarlFK: I'm pretty sure the code should find the unbind-helper without you adding it to the bin

mithro: oh, I thought you ran it

CarlFK: no

Title: HDMI2USB-mode-switch/lsusb.py at master · timvideos/HDMI2USB-mode-switch · GitHub (at github.com)

mithro: Write to /sys/bus/usb/drivers/uvcvideo/unbind failed http://paste.ubuntu.com/17841615/

Title: Ubuntu Pastebin (at paste.ubuntu.com)

CarlFK: does "/sys/bus/usb/devices/1-1.5:1.0/driver/unbind" exist?

CarlFK: and can you do a "ls -l bin/unbind-helper" ?

--w------- 1 root root 4096 Jun 25 00:37 /sys/bus/usb/devices/1-1.5:1.0/driver/unbind

-rwxr-xr-x 1 juser juser 9056 Jun 25 00:46 bin/unbind-helper

CarlFK: did you cancel the "make unbind-helper" command?

mithro: maybe. I hit enter until the sudo failed, then $ chmod 755 bin/unbind-helper

then re-ran make

CarlFK: so you do see that there are two very important commands after that one in the makefile?

mithro: makefiles that call sudo is... not going to go over well with the debian folk

CarlFK: They wouldn't be using the Makefile

CarlFK: they would be doing the equivalent in the debian/rules file and the binary would be installed as being owned by root when the package is installed

well.. I suspect the way you have this setup is going to make it hard for them. but I am not sure what would be better ... so ... never mind.

-rwsr-xr-x 1 root root 9056 Jun 25 00:46 bin/unbind-helper

CarlFK: The makefile sets up a developer environment - they are going to be doing a "python setup.py install" like any other python module

mithro: Running 'fxload -t fx2lp -D /dev/bus/usb/001/011 -I /home/juser/HDMI2USB-mode-switch/hdmi2usb/firmware/fx2/atlys/ixo-usb-jtag.hex -v'

b'Permission denied : /dev/bus/usb/001/011\n' http://paste.ubuntu.com/17841879/

Title: Ubuntu Pastebin (at paste.ubuntu.com)

CarlFK: they'll probably want to rewrite/rework the unbind helper anyway

CarlFK: oh... That would be fixed by the udev rules

Hrm, I wonder if the udev rules could also fix the unbind permissions....

CarlFK: okay, maybe you should be running this as root if you haven't installed the udev rules

LOL sudo: hdmi2usb-mode-switch: command not found

it does't get the users path

CarlFK: yeah

mithro: this installs, right? sudo setup.py install

CarlFK: Yes, but I've never tested that :P

lol

CarlFK: I only have so much time

from setuptools import setup

ImportError: No module named 'setuptools'

ok, um.. let me sudo -s and set the path

sudo apt-get python3-setuptools I think

too late.

DNA = 110000001100000011000000110000001100000011000000110000001 (0x181818181818181)

I just re-run until it works, right ?

CarlFK: Yeah - for the moment :(

CarlFK: actually you might need to force it into serial mode

mithro: how do I do that ?

CarlFK: hdmi2usb-mode-switch --mode=serial

Oh, wait you are on an Atlys....

AssertionError: serial mode only valid on the opsis.

lol

CarlFK: Just try again maybe?

CarlFK: basically, the different FX2 firmware we are using fight with each other about how the FX2 should be configured

mithro: iv tried over 5 times. normally it gets it by the third when I was doing whatever commands I was doing for lca

CarlFK: What were you doing for LCA?

CarlFK: At some point we need to fix the FX2 firmware to actually properly set up the FX2 so we don't get those failures.

mithro: er, not lca. what someone at DC figured out and I dropped it in the lca repo:

https://github.com/xfxf/video-scripts/blob/mast... # repeat these 3 lines until it works

Title: video-scripts/opsis_setup.sh at master · xfxf/video-scripts · GitHub (at github.com)

CarlFK: sure

CarlFK: those are opsis commands....

ah right. I haven't done this to an atlys

CarlFK: okay

CarlFK: can you try power cycling the Atlys and running the command a few times?

power cycled, re-ran, worked the first time ... well, new error

DNA = 100110010110101100010110111000010010100001101000001001011 (0x132d62dc250d04b)

loaded file /home/juser/HDMI2USB-mode-switch/hdmi2usb/firmware/spartan6/atlys/bscan_spi_xc6slx45.bit to pld device 0 in 4s 414024us

Info : JTAG tap: xc6s.tap tap/device found: 0x34008093 (mfg: 0x049 (Xilinx), part: 0x4008, ver: 0x3)

Error: Unknown flash device (ID 0x00ffffff)

CarlFK: there is one peculiarity with the Atlys if it is still running the stock firmware from Digilent

Title: Ubuntu Pastebin (at paste.ubuntu.com)

CarlFK: This board still has the stock Digilent firmware on it, right?

mithro: correct

CarlFK: let me dig up the special thing you need to do the first time

Dammit, where did I put it....

Neuron1k: we are running a little bit, will ping when we are ready

mithro: ok

CarlFK: http://paginas.fe.up.pt/~ee06211/doku.php?id=di...

Title: digilent_atlys [Generation of Reconfigurable Circuits from Machine Code] (at paginas.fe.up.pt)

CarlFK: I'm sure I wrote better instructions down somewhere....

Neuron1k: In your blog you mentioned hacking on a model

Neuron1k: can you publish that code somewhere

mithro: It is added on my github

Neuron1k: can you link it here

Title: litejpeg/test/model at master · Neuron1k/litejpeg · GitHub (at github.com)

mithro: this? " The workaround is to set the J11 jumper on the board to avoid power on flash boot, thus leaving the flash in legacy SPI mode."

CarlFK: Yes

CarlFK: I think you need to remove the jumper after the board has booted while the power is still connected

CarlFK: Please write this down somewhere in the Wiki

mithro: k

mithro: is j11 next to the usb-A jack, says "HOST" and in the picture here it doesn't look like there are header pins to jump?

CarlFK: it should definitely be around that big USB HOST connector

CarlFK: JP9 seems to be on one side and JP11 on the other

mithro: so .. jumper off, power, jumper on, hdmi2usb-mode-switch --flash-gateware... ?

CarlFK: no

CarlFK: jumper on, power on, jumper off, hdmi2usb-mode-switch --flash-gateware

mithro: welll ... it didn't error

mithro: I was expecting the hdmi2usb colorbars ,

CarlFK: Does jp11 on your board have a header? Or are you just shorting it with a screwdriver?

mithro: header

Neuron1k: heyo

Neuron1k: sorry about running late, we are now getting setup

mithro: ok, I will join the call

CarlFK: I might be back in a bit, otherwise I'll respond on my phone in 30 minutes

mithro: k

Neuron1k: are you on?

shenki: yes

Neuron1k: ok. you keep dropping and coming back

shenki: I can't see you

Neuron1k: okay. we can't see you either

Neuron1k: you've joined, but no video nor voice

Neuron1k: do you want to try inviting us to a new hangout?

shenki: ok, I will drop and could you invite me instead?

ok

Neuron1k: have you tried restarting your browser?

CarlFK: did ti work?

CarlFK: Have to run, will be back tomorrow

CarlFK: I'll push some updates to the udev rules which fix the permissions on unbind tomorrow

k

mithro: isn't there another step?

mobydikc: you still around? I'm heading to bed.

CarlFK: what do you mean?

mithro: don't i need to send hdmi2usb.hex ?

As I said, I've never been game enough to flash the ERPROM on an Atlys

Which is where the .hex file goes

mithro: what does this do: fxload -B libusb -D vid=0x16c0,pid=0x06ad -t fx2lp -I hdmi2usb.hex

Loads it into ram

That doesn't persist after power cycle

Btw where does your fxload come from?

k - so I either need to do that, or hdmi2usb-mode-switch --load-fx2-firmware

Yes

root@cnt1:~/HDMI2USB-mode-switch# apt-cache policy fxload

500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

Title: Index of /ubuntu (at archive.ubuntu.com)

hmm, not sure it works

CarlFK: the mode switch tool will aways get the right vid:pid matter what mode the Atlys is in

hdmi2usb-mode-switch --load-fx2-firmware /home/juser/HDMI2USB-firmware-prebuilt/archive/master/v0.0.0-639-g956a8b3/atlys/hdmi2usb/hdmi2usb.hex

no error, but still not colorbars

CarlFK: I haven't tested --load-fx-firmware recently but as the system has to load fx2 firmware to do the other operations, it would be weird if broken.

CarlFK: you should get color bars after the gateware