I just updated to the RC2 version and copied over my open Dhrystone sketch from the T_3.6 OC to 256 MHz thread and it worked!
That uses an alternate CORE from Frank_B with timing adjustments to support OC of the 180 MCU beyond 240 MHz to 256 MHz. It is a single file program with no libraries - but the create uses an updated boards.txt to define the new speed.
It built the makefile correctly and created a usable HEX with no problem. The first time in creation I did not specify desired 256 MHz speed and optimization, I restarted VisualTeensy made the changes and they were properly applied! I have an update pending for 'Visual Studio Code' and that applied correctly and the build worked.
Two things I note:
> Building with IDE to Tycommander allows selecting one or more - in my case 5 T_3.6's to send the same HEX to. For some reason what works in the IDE does not under VisualTeensy as only a single device can be selected from the list for upload?
> When built in the IDE the code compiled "Fastest, pure-code with LTO" had a count selected that resulted in exactly 100,000 microseconds used in Dhrystone loop execution on all 5 T_3.6's - on multiple compile/upload cycles. Occasionally 1 or 2 T_3.6's would use 100,001 us.
--- when built with VisualTeensy the T_3.6's somehow come out to these 'slightly higher' values suggesting something is not building the same:: Micros Run Time: 100008, 100009, 100009, 100008, 100014. On two GUI resets of each they all stabilized to 100009
Question: Could VisualTeensy be added as a Build Task in tasks.json? This would allow project adjustments within without leaving VScode to find a way to run VisualTeensy.exe
Good work! That piece of code is much more colorful and readable than in the Arduino IDE.
Here is the project folder in case it helps - of course it won't build without the 256 MHz CORE:
View attachment Dhrystone.zip
<Update > Of course it can be built at 240 MHz - just longer runtime - and still a small 4/106671 part difference::
> IDE on all 5 T_3.6's gives: Micros Run Time: 106671
> Visual Teensy gives: Micros Run Time: 106675 or 106676 on Reset, but the first exec on upload had a 106681 and 106686 as well.