"Error: board TinyFPGA-BX not connected" [SOLVED]


#41

Which option allows you to see the new VID:PID?

I should have specified I was testing that in IceStorm… I’m not reproducing that error in Atom now, which suggests progress.


#42

Ok, I did the following to manually update IceStorm’s package for this in Windows:

C:\Users\MYUSERNAME\.icestudio\venv\Scripts\activate
pip install --upgrade tinyprog

Now IceStorm works correctly as well. Sorry for the confusion, but it seems to be working now!


#43

Whew! I was just about to suggest that for IceStudio. :smile:


#44

i got this…

c:\blink_project>tinyprog --update-bootloader

TinyProg CLI
------------
Using device id 1d50:6130
Only one board with active bootloader, using it.

The following update:

    New Version: 1.0.1
    Notes: Updates USB VID:PID to fix issues with APIO not recognizing the board.

is available for this board:

    COM3: TinyFPGA BX 1.0.0
        UUID: f55e9edd-ba84-4bc7-89cf-3a1b4187d0a2
        FPGA: ice40lp8k-cm81

Would you like to perform the update? [y/N] y
Fetching stage one...
Programming stage one...
Erasing: 100%|███████████████████████████████████████████████████████████████████| 135k/135k [00:00<00:00, 137kB/s]
Writing: 100%|███████████████████████████████████████████████████████████████████| 135k/135k [00:00<00:00, 173kB/s]
Reading: 100%|███████████████████████████████████████████████████████████████████| 135k/135k [00:00<00:00, 216kB/s]
...Success!
Waiting for stage one to reconnect....connected!
Fetching stage two...
Programming stage two...
Erasing: 100%|███████████████████████████████████████████████████████████████████| 299k/299k [00:01<00:00, 152kB/s]
Writing: 100%|███████████████████████████████████████████████████████████████████| 299k/299k [00:01<00:00, 186kB/s]
Reading: 100%|███████████████████████████████████████████████████████████████████| 299k/299k [00:01<00:00, 208kB/s]
...Success!

and also…

c:\blink_project>apio upload
[Sun Jul 15 19:30:31 2018] Processing TinyFPGA-BX

tinyprog -c COM4 --program hardware.bin

TinyProg CLI

Using device id 1d50:6130
Programming COM4 with hardware.bin
Programming at addr 028000
Waking up SPI flash
135100 bytes to program

Erasing: 0%| | 0.00/135k [00:00<?, ?B/s]
Erasing: 24%|##4 | 32.8k/135k [00:00<00:00, 150kB/s]
Erasing: 73%|#######2 | 98.3k/135k [00:00<00:00, 153kB/s]
Erasing: 97%|#########7| 131k/135k [00:00<00:00, 149kB/s]
Erasing: 100%|##########| 135k/135k [00:00<00:00, 152kB/s]

Writing: 0%| | 0.00/135k [00:00<?, ?B/s]
Writing: 12%|#2 | 16.6k/135k [00:00<00:00, 152kB/s]
Writing: 27%|##7 | 36.9k/135k [00:00<00:00, 161kB/s]
Writing: 42%|####2 | 57.1k/135k [00:00<00:00, 167kB/s]
Writing: 57%|#####7 | 77.3k/135k [00:00<00:00, 172kB/s]
Writing: 73%|#######2 | 98.6k/135k [00:00<00:00, 178kB/s]
Writing: 87%|########6 | 117k/135k [00:00<00:00, 175kB/s]
Writing: 100%|##########| 135k/135k [00:00<00:00, 180kB/s]

Reading: 0%| | 0.00/135k [00:00<?, ?B/s]
Reading: 18%|#7 | 24.0k/135k [00:00<00:00, 219kB/s]
Reading: 35%|###5 | 47.4k/135k [00:00<00:00, 218kB/s]
Reading: 52%|#####2 | 70.9k/135k [00:00<00:00, 217kB/s]
Reading: 69%|######9 | 93.8k/135k [00:00<00:00, 215kB/s]
Success!
Reading: 87%|########7 | 118k/135k [00:00<00:00, 217kB/s]
Reading: 100%|##########| 135k/135k [00:00<00:00, 216kB/s]
============================================= [SUCCESS] Took 4.53 seconds =============================================

then it has usb device not recognized… but that is expected.

c:\blink_project>apio system --lsserial
Number of Serial devices found: 0

sos blinking OK.

upon pressing the button…

c:\blink_project>apio system --lsserial
Number of Serial devices found: 1

COM4
Description: USB Serial Device (COM4)
Hardware info: USB VID:PID=1D50:6130 SER=6 LOCATION=1-7.4

so it swaps from COM3 to COM4.


#45

also atom programs the board as well no problems. I think you have fixed all issues :smiley:


#46

before pressing button, with blinking sos.

c:\blink_project>tinyprog -l

TinyProg CLI
------------
Using device id 1d50:6130
No port was specified and no active bootloaders found.
Activate bootloader by pressing the reset button.

c:\blink_project>tinyprog -m
[]

after pressing the button, is this.

c:\blink_project>tinyprog -l

TinyProg CLI
------------
Using device id 1d50:6130
Only one board with active bootloader, using it.
Boards with active bootloaders:

    COM4: TinyFPGA BX 1.0.0
        UUID: f55e9edd-ba84-4bc7-89cf-3a1b4187d0a2
        FPGA: ice40lp8k-cm81

c:\blink_project>tinyprog -m
[
{
“boardmeta”: {
“name”: “TinyFPGA BX”,
“fpga”: “ice40lp8k-cm81”,
“hver”: “1.0.0”,
“uuid”: “f55e9edd-ba84-4bc7-89cf-3a1b4187d0a2”
},
“bootmeta”: {
“bootloader”: “TinyFPGA USB Bootloader”,
“bver”: “1.0.1”,
“update”: “https://tinyfpga.com/update/tinyfpga-bx”,
“addrmap”: {
“bootloader”: “0x000a0-0x28000”,
“userimage”: “0x28000-0x50000”,
“userdata”: “0x50000-0x100000”
}
},
“port”: “COM4”
}
]


#47

thanks for the assistance. :slight_smile:


#48

Thanks, Luke. Version 1.0.11 solved my issues. Appreciate your support.


#49

I’m seeing a possibly related but also slightly different problem. Tinyprog 1.0.18 works fine for me, and I can even do tinyprog -p hardware.bin to upload an image to the FPGA. However apio upload consistently reports the error:

$ apio upload
Error: board TinyFPGA-BX not available

Note that this text is “available” not “connected” so it’s slightly different to the other posts in this thread.

I’ve just installed all the tools today on Mac OSX 10.12.6 so everything is the latest version as far as I can tell. I’m using apio 0.4.0b3 as per the TinyFPGA BX user guide.

$ tinyprog -m
[
  {
    "boardmeta": {
      "name": "TinyFPGA BX",
      "fpga": "ice40lp8k-cm81",
      "hver": "1.0.0",
      "uuid": "03cfce7b-b1d9-467a-a05e-1a08839f1786"
    },
    "bootmeta": {
      "bootloader": "TinyFPGA USB Bootloader",
      "bver": "1.0.1",
      "update": "https://tinyfpga.com/update/tinyfpga-bx",
      "addrmap": {
        "bootloader": "0x000a0-0x28000",
        "userimage": "0x28000-0x50000",
        "userdata": "0x50000-0x100000"
      }
    },
    "port": "USB 20.1"
  }
]
$ pip freeze | grep -E 'apio|tinyprog'
apio==0.4.0b3
tinyprog==1.0.18

#50

APIO looks for the TinyFPGA BX board by checking connected serial ports and looking for their USB VID:PID if they have one. Because later versions of MacOS don’t attach a serial driver to the BX, APIO doesn’t see the board appear and thinks its not connected.

I think @JesusArroyo will need to update APIO to use tinyprog -m to look for connected TinyFPGA BX boards instead.

In the meantime, you’ll have to use tinyprog -p hardware.bin to bypass APIO and program the bitstream directly.


#51

Ok, thanks for the fast reply. I can live with tinyprog -p for now. I noticed there didn’t seem to be a serial port TTY “appearing” when connected, so that explains that I think.


#52

Hi, i also have a problem problem.

When i run tinyprog -p hardware.bin

I get this:

    TinyProg CLI
------------
Using device id 1d50:6130
Only one board with active bootloader, using it.

Traceback (most recent call last):
File “/home/aleksandar/.local/bin/tinyprog”, line 11, in
sys.exit(main())
File “/home/aleksandar/.local/lib/python2.7/site-packages/tinyprog/main.py”, line 290, in main
with active_port:
File “/home/aleksandar/.local/lib/python2.7/site-packages/tinyprog/init.py”, line 60, in enter
self.ser = serial.Serial(self.port_name, timeout=1.0, writeTimeout=1.0).enter()
File “/home/aleksandar/.local/lib/python2.7/site-packages/serial/serialutil.py”, line 240, in init
self.open()
File “/home/aleksandar/.local/lib/python2.7/site-packages/serial/serialposix.py”, line 268, in open
raise SerialException(msg.errno, “could not open port {}: {}”.format(self._port, msg))
serial.serialutil.SerialException: [Errno 13] could not open port /dev/ttyACM0: [Errno 13] Permission denied: ‘/dev/ttyACM0’

And when try to run as sudo, it says there is no command called tinyprog…

When i run apio upload it says that the board is not connected.


#53

Adding your user to the tty and dialout groups should give you access to /dev/ttyACM0 without sudo:

usermod -a -G tty yourUserName
usermod -a -G dialout yourUserName


#54

still the same error


#55

More information at https://askubuntu.com/questions/58119/changing-permissions-on-serial-port.

dialout seems to be the relevant group.

You probably need to logout and log back in again. A good idea to unplug the TinyFPGA and plug it back in again.


#56

works now, i didnt log out and back in. thanks!