-
Notifications
You must be signed in to change notification settings - Fork 152
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
Not seeing all the possible teensy boards after compile #72
Comments
oh if this helps my gcc version: gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0 |
Am having the same issue, cannot flash to my 4.0 |
Linux command line shells usually require ./ to be added if you wish the run the copy you've just compiled. Otherwise, the shell will run the (too old with Teensy 4.0 support) copy located somewhere else on your computer. So after you have successfully compiled a new copy of teensy_loader_cli, and it's in the current working directory, to run it would would type "./teensy_loader_cli". This isn't anything specific to teensy_loader_cli. It's simply how the command line interface works on nearly all Linux distros. |
OS: Ubuntu 21.04, 21.10
I have installed the library in the read me.
MCUs listed from --list-mcus
Supported MCUs are:
Ironically have a teensy 3.2 and a 4.0, which aren't on the list.
I have tried changing the teensy_loader_cli.c file to
https://github.com/PaulStoffregen/teensy_loader_cli/blob/master/teensy_loader_cli.c#L1051-L1078
surprisingly, didn't change which I thought I would see something.
after a compile I get:
cc -O2 -Wall -s -DUSE_LIBUSB -o teensy_loader_cli teensy_loader_cli.c -lusb
Let me know if there is any other data that would help debug this issue. I am not seeing anyone else having this issue so I am probably doing something wrong.
just typing make in the directory to compile, OS is selected as Linux.
The text was updated successfully, but these errors were encountered: