I've set up a dev system on Ubuntu (18.04) on a virtual machine hosted by Virtualbox 5.2.8 on a Windows 10 laptop.
I downloaded the Teensy loader app from https://www.pjrc.com/teensy/loader_linux.html and followed the instructions to install it on the virtual machine... the program launches OK but I can't persuade it to recognise a Teensy3.2 which is connected via USB. Works OK under windows with the same hardware (i.e. the [windows] loader recognises when the program button is pressed on the 3.2) , so I've at least ruled out the USB lead and port hardware.
I set a USB filter for "Van Ooijen Technische Informatica Teensy Halfkay Bootloader [0103]" and checked the vendor id = 16c0 and product id = 0478, which matches the data in the 'rules' file (49-teensy.rules) which I created in /etc/udev/rules.d (by following the instructions mentioned earlier) and there's also a filter set on Teensyduino Raw HID [0100] with the same vendor and product ids.
The (virtual) USB controller is enabled for v3.0.
I tried with it connected before starting up the VM, and also plugging it in after the VM has started up. When unplugging, inserting,or pressing the program button on the 3.2 I get audible alerts from Windows, implying that W10 has 'captured' the device rather than the interface being routed through to the VM. Nothing else is running on the host apart from a file explorer window.
Can anyone suggest the way ahead for diagnosis please?
I downloaded the Teensy loader app from https://www.pjrc.com/teensy/loader_linux.html and followed the instructions to install it on the virtual machine... the program launches OK but I can't persuade it to recognise a Teensy3.2 which is connected via USB. Works OK under windows with the same hardware (i.e. the [windows] loader recognises when the program button is pressed on the 3.2) , so I've at least ruled out the USB lead and port hardware.
I set a USB filter for "Van Ooijen Technische Informatica Teensy Halfkay Bootloader [0103]" and checked the vendor id = 16c0 and product id = 0478, which matches the data in the 'rules' file (49-teensy.rules) which I created in /etc/udev/rules.d (by following the instructions mentioned earlier) and there's also a filter set on Teensyduino Raw HID [0100] with the same vendor and product ids.
The (virtual) USB controller is enabled for v3.0.
I tried with it connected before starting up the VM, and also plugging it in after the VM has started up. When unplugging, inserting,or pressing the program button on the 3.2 I get audible alerts from Windows, implying that W10 has 'captured' the device rather than the interface being routed through to the VM. Nothing else is running on the host apart from a file explorer window.
Can anyone suggest the way ahead for diagnosis please?
