Identified ports of protocols other than serial or network not shown in Board Selector #1365
Comments
|
@per1234 - The Teensy example above is probably a valid choice. That is for example, when you build for a Teensy 4.1 you have several options for what USB type you are building for. Only those types in the list that have the word Serial in their name, like Serial, or Serial + MTP Disk (Experimental) .. Actually, would create a Standard Windows CDC ACM Serial port. Most of the other instead create what the Teensy refers to as a Serial Emulator (SEREMU), which is sort of another special RAW HID, which the pluggable Serial Monitor code can talk to. like wise the upload code can talk to. Question: over the last few nightly builds it feels like the Arduino code is losing track of which Com port to use, much more often. I mentioned this on the forum thread: Where ptillisch (@kittaakos ?) mentioned that it is probably related to the recent PR: Wondering if I should create new issue, or it is maybe also related to this. |
Arduino Forum user "ptillisch" is me (the "p" is for "Per", my first name).
I didn't, and wouldn't say "probably" at this stage in the investigation. The next step will be to do a bisection, which will indicate whether there was a regression, and if so, at which commit/PR that happened. I haven't done the bisection yet because the intermittent (hopefully pseudo-intermittent) nature of the bug makes doing that more difficult. I was hoping I could find the conditions required to consistently reproduce the bug before starting on the bisection.
I will take care of that (UPDATE: #1366). I already started on preparing one, but then ran into the intermittency and decided I needed to attempt to progress with the investigation a bit farther first in order to ensure the formal report is actionable by the developers.
I don't think it is related from a technical standpoint. However, not seeing the port listed in the "Board Selector" may give the user the impression that the IDE has "lost track" of the port, even though that can occur completely independently from the bug that causes the loss of the port selection. |
Closes #1 95A0 365 - Ref: 79ea0fa - Ref: 74bfdc4 Signed-off-by: Akos Kitta <a.kitta@arduino.cc>
Describe the problem
The Arduino pluggable discovery system allows the use of any communication channel between an Arduino board and the Arduino development software. This means that, in addition to the traditional "serial" and "network" protocols supported by Arduino IDE 1.x, Arduino IDE 2.x supports any arbitrary protocol which may be implemented by a package developer.
These are presented to the user via the same interfaces as serial and network ports:
🐛 Ports of protocols other than "serial" and "network" are not shown in the latter two.
To reproduce
Equipment
ⓘ The issue is not specific to Teensy hardware. However, I am not aware of any other boards that currently use alternative port protocols.
Steps
ⓘ These first two steps are required to ensure there isn't a preexisting user-created board association for the port.
🙂 The
teensyprotocol port is shown on the menu, and identified as the appropriate board:🐛 The identified
teensyprotocol port is not shown on the menu:🐛 The identified
teensyprotocol port is not shown on the "PORTS" menu:Expected behavior
Protocol is not a factor in whether a port is shown in the "Board Selector" menu and "Select Other Board and Port" dialog. The same criteria should be applied to all ports.
Arduino IDE version
2.0.0-rc9.2.snapshot-34a7fdb
Operating system
Windows, Linux
Operating system version
Windows 10, Ubuntu 20.04
Additional context
I bisected the introduction of the bug to #1332 (it does not occur when using the build from d674ab9)
Even though the stated purpose of that PR was only to cause unidentified network ports to be shown in the "Board Selector" menu, the PR also changed the code so that even identified ports of any other protocol are no longer shown.
All is as expected in the Arduino CLI output (note that the Teensy board's port has a
matching_boardsobject):This is an example of the problems that can be caused by the current practice of treating ports of specific protocols differently than others in the Arduino IDE codebase: #1334
Issue checklist
The text was updated successfully, but these errors were encountered: