https://www.pjrc.com/teensy/td_156/package_teensy_index.json
Version: 2.0.0-rc3-nightly.20220128
Date: 2022-01-28T03:03:44.410Z
CLI Version: 0.20.2 [13783819]
Copyright © 2022 Arduino SA
Compilation complete.
"{runtime.hardware.path}\tools\teensy_post_compile.exe" "-file=BlinkWithoutDelay.ino" "-path=R:\TEMP\arduino-sketch-57B791B5A63BFE52DB74090D946EF1E5" "-tools={runtime.hardware.path}\tools" "-board=TEENSY41" -reboot "-port=COM45" "-portlabel={serial.port.label}" "-portprotocol={serial.port.protocol}"
Upload error: Failed uploading: cannot execute upload tool: exec: "{runtime.hardware.path}\\tools\\teensy_post_compile.exe": file does not exist
Is Windows coming along in parallel or some time away yet?
Seriial Ports
/dev/ttyS10
<about 30 of these ttySnn>
Network ports
192.168.2.175 (Have no idea what that is)
Teensy Ports (Finally)
usb1/1-1/... (Teensy Micromod)
Guessing: no SEREMU support yet.
./arduino-cli monitor -v --port usb16/16-1/16-1.2
Definitely does work with arduino-cli.
Code:./arduino-cli monitor -v --port usb16/16-1/16-1.2
Tested here with a Teensy 4.1 running RawHID. Haven't checked MTP.
....
It will be interesting to see how this all works out. So far IDE wise not sure how much we gain. Will be good with the CLI stuff as maybe better for integrating into other editors...
...
Could do the same with Defragsters TSET (or a variant)?
# Finally, we compile the sketch, using the FQBN that was set
# in the build matrix.
- name: Compile Sketch
run: arduino-cli compile --fqbn ${{ matrix.fqbn }} ./blink
I got a working Windows Verify build with:
View attachment 27356Code:Version: 2.0.0-rc3-nightly.20220128 Date: 2022-01-28T03:03:44.410Z CLI Version: 0.20.2 [13783819] Copyright © 2022 Arduino SA
After Verify it opened Teensy Loader and passed the name, but Verify only.
Builds HEX and eHex for T_4.1 and Teensy Loader works
Just put TD 1.56 into "C:\Users\Tim\AppData\Local\Arduino15\packages\teensy", removed a path '..', and changed a lot of '/' to '\', and added explicit ".exe" as needed in the Boards and Platform TXT files - and restarted IDE 2.0.
IDE: Slow to load, no windows text resize, SerMon window is hard DOCKED and won't float to a stand alone window.
SerMon ID's Teensy as 3.1/3.2, and keeps needing it reselected to connect.
Arrggh: Everything in ARDUINO15 folder means harder to copy, and only single install?
Upload has a PATH making glitch - not doing 'macro' replacment for this .path?:
Code:Compilation complete. "{runtime.hardware.path}\tools\teensy_post_compile.exe" "-file=BlinkWithoutDelay.ino" "-path=R:\TEMP\arduino-sketch-57B791B5A63BFE52DB74090D946EF1E5" "-tools={runtime.hardware.path}\tools" "-board=TEENSY41" -reboot "-port=COM45" "-portlabel={serial.port.label}" "-portprotocol={serial.port.protocol}" Upload error: Failed uploading: cannot execute upload tool: exec: "{runtime.hardware.path}\\tools\\teensy_post_compile.exe": file does not exist
Note: I installed nightly on windows (earlier on Ubuntu, then edited the extra boards, reloaded and tried to install:
...
Directory of C:\Users\Tim\AppData\Local\Arduino15\packages\teensy
01/28/2022 01:29 AM <DIR> .
01/28/2022 01:25 AM <DIR> ..
01/28/2022 01:22 AM <DIR> avr
01/28/2022 01:29 AM <DIR> tools
Cool. Does it build?
Though looking at the IDE ... I'm not sure how it is any improvement worth fighting for, hopefully a TSET like kick off for the IDE 2.0 CLI still works like for the current version.
I've modified TSET to work with another STM board in %appdata%\...\Arduino15\... and that worked where it was a Manager installed board.
Yep I probably could manually copy the stuff like you mentioned... But I think I will wait until Paul has initial setup...
Yes not much new useful things for me. Unless I am missing some obvious things like:
ability to edit core files
ability to edit library files
...
Building Sketch: ".\MakeFiles.ino"
Using board 'teensy41' from platform in folder: C:\Users\Tim\AppData\Local\Arduino15\packages\teensy\avr
Using core 'teensy4' from platform in folder: C:\Users\Tim\AppData\Local\Arduino15\packages\teensy\avr
Detecting libraries used...
... /// build here
"C:\\Users\\Tim\\AppData\\Local\\Arduino15\\packages\\teensy\\tools\\teensy_size" "R:\\temp\\arduino_build_MakeFiles.ino\\MakeFiles.ino.elf"
teensy_size: Memory Usage on Teensy 4.1:
teensy_size: FLASH: code:103968, data:16476, headers:8576 free for files:7997444
teensy_size: RAM1: variables:18752, code:101288, padding:29784 free for local variables:374464
teensy_size: RAM2: variables:28800 free for malloc/new:495488
Multiple libraries were found for "SD.h"
Used: C:\Users\Tim\AppData\Local\Arduino15\packages\teensy\avr\libraries\SD
Not used: C:\T_Drive\Arduino-1.8.19\libraries\SD
Using library SD at version 2.0.0 in folder: C:\Users\Tim\AppData\Local\Arduino15\packages\teensy\avr\libraries\SD
Using library SdFat at version 2.1.0 in folder: C:\Users\Tim\AppData\Local\Arduino15\packages\teensy\avr\libraries\SdFat
Using library SPI at version 1.0 in folder: C:\Users\Tim\AppData\Local\Arduino15\packages\teensy\avr\libraries\SPI
Using library MTP_Teensy at version 1.0.0 in folder: C:\T_Drive\tCode\libraries\MTP_Teensy
upload@9706370-Teensy Uploading to board '9706370-Teensy' (Teensy 4.1)
upload@9706370-Teensy Triggering board reboot
upload@9706370-Teensy Waiting for Teensy Loader
[Finished in 17.0s]
Yep I probably could manually copy the stuff like you mentioned... But I think I will wait until Paul has initial setup...
Yes, indeed, best to wait.
Just to confirm, 2 of the tools are completely different implementations for Arduino 1.8 vs Arduino 2.0 & arduino-cli. When Arduino merges #1640, I will be adding code to specifically check for which version of Arduino we're using and whether it is running with a GUI or headless.
So there's not much value to testing by kludging the tools designed for Arduino 1.8 into use on Arduino 2.0. By doing so, you may discover problems which will be present with the properly updated tools, but you'll probably encounter all sorts of issues due to using the not-meant-for-2.0 tools.
I got the Wincows multithreaded discovery tool to compile this morning. Will begin testing here this afternoon (at the moment, Robin & I are working on PJRC business stuff.... can't spend all hours programming). Hopefully by tonight I should have a feeling for whether the Windows stuff is going to be "soon" or "troublesome".