Skip to content

Bad format file filter if started without programmer plugged in #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MartinCowen opened this issue Apr 27, 2021 · 0 comments
Open

Comments

@MartinCowen
Copy link

I started TinyFPGA Programmer v1.1.5 applicaion without it being connected by USB to the programmer, by mistake since it was my first time using it. The Select File button brings up the Select File dialog but I was unable to see my JED file because the file filter has the incorrect syntax, so I thought I had not managed to generate one correctly from my first usage of Lattice Diamond. However, the file could be seen in Windows Explorer. Workaround - use the all files option and type *.jed in the File name.
tinyfpga programmer not plugged in wrong filter

The problem does not occur if the USB connection is present when the application is started, irrespective of power to the target board.

jiapei100 pushed a commit to LongerVisionRobot/TinyFPGA-Programmer-Application that referenced this issue Dec 3, 2023
Fix for Issue tinyfpga#11, provide consistent usage of "--mode" parameter.

    --mode is not mandatory for all use-cases of the programmer

    while flashing m4app or appfpga images, --mode [m4/fpga/fpga-m4] should be specified - this is enforced, and error message displayed if not specified

    standalone use of --mode continues to be available :
    qfprog --mode to read the currently active mode on the board
    qfprog --mode [m4/fpga/fpga-m4] to set the mode, without needing to flash images.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant