Visual Micro wrote on Jun 17
th, 2019 at 6:48pm:
Not sure I fully understand. If the current board has the vid/pid passed on usb connect then we use the current board otherwise we look for a board with the vid/pid. That's only if you have enabled the "auto select board"
Hmm. Hard for me to explain more simply but I'll try. And I thought my pseudocode was so simple.
At the moment if "auto select" is on, then every time you see a Teensy3x board ID, you
force the Target = Teensy3.2
Regardless of the fact that 2ms ago the whole project was setup and successfully compiled for Teensy3.5/6/999.
To be clear - it does this every single time the board loads a sketch, so there is now way for a 3.5/6 board user to leave autoselect on as part of their other work routine, even if they have a pile of other units to manage.
My suggestion is:
Implement the above logic only
if "auto select board" is on,
and the ID # turns out to be a Teensy3.x.
It will just mean that those of us w/ Teensy3.x won't be forced to choose either not use auto select (again I have a stack of different devboards here so it IS nice...) or, constantly have to correct the forced ID.
Home
Pages: 1
Start Debugging session changes target 3.6->3.2 ?!? (Read 1340 times)