Skip to content

Common Errors

Jump to bottom Edit New page
Tim Ansell edited this page Sep 1, 2018 · 1 revision

Common Errors

unable to open ftdi device

device not found

This error means that a HDMI2USB board in JTAG mode was not detected. Power cycle the board and make sure you have followed the 3) Configure your board section.

Warn : Adapter driver 'usb_blaster' did not declare which transports it allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
Warn : incomplete ublast_vid_pid configuration
jtagspi_program
Info : usb blaster interface using libftdi
Error: unable to open ftdi device: device not found
inappropriate permissions on device

This error means that your user doesn't have permission to talk to the HDMI2USB board. This is normally caused by not installing the udev rules which come with HDMI2USB-mode-switch.

Warn : Adapter driver 'usb_blaster' did not declare which transports it allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
Warn : incomplete ublast_vid_pid configuration
jtagspi_program
Info : usb blaster interface using libftdi
Error: unable to open ftdi device: inappropriate permissions on device!

Warn: Bypassing JTAG setup events due to errors

If you get an error like this;

Info : This adapter doesn't support configurable speed
Info : JTAG tap: xc6s.tap tap/device found: 0x03030303 (mfg: 0x181 (Solectron), part: 0x3030, ver: 0x0)
Warn : JTAG tap: xc6s.tap       UNEXPECTED: 0x03030303 (mfg: 0x181 (Solectron), part: 0x3030, ver: 0x0)
Error: JTAG tap: xc6s.tap expected 1 of 13: 0x04000093 (mfg: 0x049 (Xilinx), part: 0x4000, ver: 0x0)
Error: JTAG tap: xc6s.tap expected 2 of 13: 0x04001093 (mfg: 0x049 (Xilinx), part: 0x4001, ver: 0x0)
Error: JTAG tap: xc6s.tap expected 3 of 13: 0x04002093 (mfg: 0x049 (Xilinx), part: 0x4002, ver: 0x0)
Error: JTAG tap: xc6s.tap expected 4 of 13: 0x04004093 (mfg: 0x049 (Xilinx), part: 0x4004, ver: 0x0)
Error: JTAG tap: xc6s.tap expected 5 of 13: 0x04024093 (mfg: 0x049 (Xilinx), part: 0x4024, ver: 0x0)

It means the JTAG firmware on the FX2 has gotten confused. Use mode-switch tool to switch to serial mode and then back to the jtag mode like this;

hdmi2usb-mode-switch --mode=serial
hdmi2usb-mode-switch --mode=jtag

Load the firmware

make firmware-load

If you see no output, press ‘Enter’ a few times. You can then kick off the firmware loading process again:

BIOS> serialboot
Booting from serial...
Press Q or ESC to abort boot completely.
sL5DdSMmkekro
[FLTERM] Received firmware download request from the device.
[FLTERM] Uploading kernel (86484 bytes)...
[FLTERM] Upload complete (10.6KB/s).
[FLTERM] Booting the device.
[FLTERM] Done.
Executing booted program at 0x40000000
HDMI2USB firmware booting...

opsis_eeprom: Init...finished.

hardware version info
===============================================
           DNA: 0137be87d98719f0
           MAC: d8:80:39:57:04:94

gateware version info
===============================================
      platform: opsis
        target: video
      revision: 5f07955beabcf9cebe0e896c4e51242075566cb6

firmware version info
===============================================
      platform: opsis
        target: video
    git commit: 5f07955beabcf9cebe0e896c4e51242075566cb6
    git branch: master
  git describe: v0.0.4-203-g5f07955
    git status:
    --
    ?? ../../../../HDMI2USB-mode-switch/
    --

         built: May 31 2018 10:43:25
        uptime: 00:00:00
-----------------------------------------------
MDIO mode: 1000Mbps / link: down
Add a custom footer
Clone this wiki locally