@defragster trying to get this to work on an RPI4. A little fuzzy on what actually goes in the { }. You have a {cmd.path}, {build.path} and a {build.project_name}.
In the IDE1, one needed to open tycommander and click Tools > Integrate to Arduino. Do I need to do that for IDE2? If so, where is the Arduino path? /temp/Arduino ? When I select anything in /temp it says it is not a valid Arduino directory.
I created a file local.platform.txt in /home/bruce/.arduino15/packages/teensy/hardware/avr/0.58.3 (Soon to be updated, but one step at a time...) Contents of file right now are:
Is it that I need to update tycommander? A bit lost here...Code:tools.teensyloader.cmd.path=/home/bruce/Apps/tytools-0.9.7/build/linux/tycommander tools.teensyloader.upload.pattern="{cmd.path}" upload --autostart --wait --delegate "{build.path}/{build.project_name}.hex"
Here is what I usually use in PIO.
Code:[TeensyBase] platform = teensy upload_command = C:\toolchain\TyTools\tyCommanderC upload $SOURCE --autostart --wait --multi [env:T4.0] extends =TeensyBase board = Teensy40 [env:T3.2] extends = TeensyBase board = Teensy31
Thanks. Haven't tried platform.io yet. Wasn't quite sure how to install it. Went to the GitHub site and they assumed you knew everything. But I didn't. Is it a decent development environment? How hard is it to set up Teensy or other microcontrollers?
Are you using Apple silicon? I have an M3 Max and have run into issues with older stuff.I just downloaded those 2023 binaries for Mac and Windows and both worked will for my purposes.
The source would need to be compiled with a paid version of QT, would it not?
Have an M3 Max MacBookPro (Nov 2023). Have permissions issues with TyCommander, how do I undo whatever I may have denied? Sorry for the question here, but I'm close, so close to getting this working. I compiled with two serials, and TyCommander saw the second port, but I have yet to get any output on the second port.My Mac is now an M4, and the windows box is 2 years old.
Building from source, including an installer that does not scare users on Mac or Windows, and a simple UI of each… would be a plus.
It’s not a big enough pain point for me to enter the rabbit hole.
Try making a "platform.local.txt" file beside the platform.txt in use {with correct path to the .EXE} [then fresh start of the IDE]Arduino IDE2 is hanging up when Teensy loader runs and TyCommander is running.
tools.teensyloader.cmd.path=T:\T_Drive\TyComm\TyCommanderC.exe
tools.teensyloader.upload.pattern="{cmd.path}" upload --autostart --wait --delegate "{build.path}/{build.project_name}.hex"
Well, it may be the solution for Windows, but I'm using a Mac, and I have no idea where the actual app executables are located on a Mac. Google tells me they can be found in the Applications area.Guessing this is the issue and resolution?
Try making a "platform.local.txt" file beside the platform.txt in use {with correct path to the .EXE} [then fresh start of the IDE]
Code:tools.teensyloader.cmd.path=T:\T_Drive\TyComm\TyCommanderC.exe tools.teensyloader.upload.pattern="{cmd.path}" upload --autostart --wait --delegate "{build.path}/{build.project_name}.hex"
The "--delegate" option was added to tell TyCommander to drop the USB connections, expecting the Teensy Loader to be active
Then when the 'go to Bootloader' command is issued to Teensy, the loader will proceed to perform the upload.
TyCommander will then resume as SerMon when the upload is complete.
This was added to TyCommander when LOCKING Teensy was created and only the Loader knew the upload process of eHex, but use of Tycommander was still preferred as it handles multiple Teensy units better, or any combination of Dual or Triple USB Serial.