Using tycommander, not returning from upload

[Knas]

Hello, due to the trouble with the Arduino IDE and uploading to several teensys connected i'm trying to switch to tycommander, the trouble i'm having right now is that the Arduino IDE won't stop saying "uploading" unless i close the tycommander window which then means i loose track of what code goes to which teensy. I've edited my platform.local.txt as follows (i'm on ubuntu)

tools.teensyloader.cmd.path=/usr/bin/tycommander
tools.teensyloader.upload.pattern="{cmd.path}" upload --autostart --wait --delegate "{build.path}/{build.project_name}.hex"

Also, is there a better IDE for using Teensy (not PlatformIO)? I'm working on a project with two teensys sharing almost all the code and the Arduino IDE is quite limited when it comes to making larger projects.

Thanks

Karl

 

[luni]

A few notes:

• What happens without the --delegate?
• Do you actually need the IDE to upload? Once TyCommander has the hex file accociated, you can upload from there. It remembers the accociation even if you restart it. So compile with the IDE and press the upload button in TyCommander
• Just because I'm curious, whats wrong with PIO?

 

[Knas]

A few notes:

• What happens without the --delegate?

I haven't tried it, i guess i should once i get back home

• Do you actually need the IDE to upload? Once TyCommander has the hex file accociated, you can upload from there. It remembers the accociation even if you restart it. So compile with the IDE and press the upload button in TyCommander

Actually, you're right this should work. I was under the impression that the temp build location changes with every build but it seems it's not. I was looking to see if i could specify the build location myself but i couldn't find anything.

• Just because I'm curious, whats wrong with PIO?

Unless i'm mistaken PlatformIO only works for Visual Studio which is Microsoft which is a company i have no interest in supporting. Reading up on the issue with uploading to multiple Teensys from the Arduino IDE, itseems to me that PlatformIO is also even worse in recognizing which Teensy is which as it enumerates the devices by name rather than location - names tend to change when a teensy is reset.

thanks!

 

[luni]

I was under the impression that the temp build location changes with every build but it seems it's not.

IIRC (I don't use the Arduino IDE a lot) it used to change the build location only at startup but this might have changed.

Unless i'm mistaken PlatformIO only works for Visual Studio which is Microsoft which is a company i have no interest in supporting. Reading up on the issue with uploading to multiple Teensys from the Arduino IDE, itseems to me that PlatformIO is also even worse in recognizing which Teensy is which as it enumerates the devices by name rather than location - names tend to change when a teensy is reset.

Of course your dislike of Microsoft is none of my business. I just want to mention that vsCode is open source (https://github.com/microsoft/vscode) and is totaly free. Also, PIO supports other editors (Atom + ???) as well. But, you are right, vsCode is probably the most widely used editor for PIO. When I use PIO I always use it together with TyCommander. The main reason is the built in serial monitor which is so much better than the PIO (or Arduino) one. Of course TyCommander also takes care of multiple Teensies, PIO has nothing to do with this. When I do Client/Server development with multiple Teensies I like the possibiltiy to adapt the color scheme per project folder, e.g. give the title bar for the server FW editor another color as for the client FW editor, which IMHO is super useful.

 

[defragster]

That last used here file : boards.local.txt
Looks like this {handy to drop in after Updates without needing to change the actual boards.txt each time}:

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"

As @luni notes TyCommander adds great features so I use it often with multiple Teensys online.

In use here are often PJRC LOCKABLE / LOCKED T_4.x's and TyCommander can't program them so the --delegate is needed and it works well.

Not sure if the cmd.path EXE indicated makes the difference where the "...C.exe" is specified?: TyCommanderC.exe

 

[Knas]

It seems that if i start pycommander manually before trying to upload it all works swimmingly, the locations of the hex files are indeed being kept the same and yes, the serial monitor is so much better...

Thanks!