You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when loading the FX2 firmware on Opsis we are still getting the "fallback" serial number reported in the USB information.
[1905564.963987] usb 3-4.3: New USB device found, idVendor=2a19, idProduct=5442
[1905564.963992] usb 3-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1905564.963995] usb 3-4.3: Product: HDMI2USB.tv - Numato Opsis Board
[1905564.963998] usb 3-4.3: Manufacturer: TimVideos.us
[1905564.964000] usb 3-4.3: SerialNumber: 0123456789abcdef
It is working on the shipping firmware;
[1905693.473306] usb 3-4.3: New USB device found, idVendor=2a19, idProduct=5442
[1905693.473310] usb 3-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1905693.473313] usb 3-4.3: Product: HDMI2USB.tv - Numato Opsis Board
[1905693.473315] usb 3-4.3: Manufacturer: TimVideos.us
[1905693.473317] usb 3-4.3: SerialNumber: ffffd8803956c79a
[1905693.492402] uvcvideo: Found UVC 1.00 device HDMI2USB.tv - Numato Opsis Board (2a19:5442)
[1905693.493315] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
[1905693.494804] cdc_acm 3-4.3:1.2: ttyACM0: USB ACM device
JTAG mode is also working;
[1905520.002403] usb 3-4.3: New USB device found, idVendor=16c0, idProduct=06ad
[1905520.002408] usb 3-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1905520.002412] usb 3-4.3: Product: Opsis (JTAG Mode)
[1905520.002428] usb 3-4.3: Manufacturer: Numato
[1905520.002430] usb 3-4.3: SerialNumber: ffffd8803956c79a
From @mithro on June 8, 2016 7:49
Currently when loading the FX2 firmware on Opsis we are still getting the "fallback" serial number reported in the USB information.
It is working on the shipping firmware;
JTAG mode is also working;
Copied from original issue: timvideos/HDMI2USB-litex-firmware#264
The text was updated successfully, but these errors were encountered: