VirtualBox

Opened 14 years ago

Closed 8 years ago

#6536 closed defect (obsolete)

MSP-FET430UIF USB JTAG Debugger / IAR Embedded Workbench Problems

Reported by: David Stude Owned by:
Component: USB Version: VirtualBox 3.1.6
Keywords: Cc:
Guest type: Windows Host type: Windows

Description (last modified by aeichner)

Attempting to use TI USB JTAG debugger (MSP-FET430UIF) in a Windows XP 32-bit host running Virtualbox 3.1.6 r59338 on 64-bit Windows 7. IAR Embedded Workbench constantly reports that it's unable to connect to the device or locks hard.

This has been an issue since at least Virtualbox 3.1.2. The same debugger works using the USB host in VMWare Server.

Following are several links reporting similar issues:

http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/t/18554.aspx http://forums.virtualbox.org/viewtopic.php?f=8&t=23460

Change History (10)

comment:1 by Bob Barry, 14 years ago

Very similar problem: Attempting to use Atmel JTAGmkII debugger in a Windows XP guest on Linux 32-bit host, virtual box 3.2.0 thru 3.2.4: IAR AVR Embedded Workbench always reports unable to connect to the debugger via usb; XP hardware manager shows debugger and driver OK, and same debugger and usb work perfectly with Atmel AVR Studio 4.18 in the same XP guest. Same debugger and usb works fine with same IAR software and same Windows XP on real hardware.

comment:2 by Bob Barry, 14 years ago

VBox 3.2.6 behaves same in this respect: IAR EWB still won't connect to Atmel JTAGmkII debugger, but AVR Studio 4.18 does. VMplayer (3.1.0 build-261024) works fine on both IAR EWB and AVR Studio 4.18.

comment:3 by Marc Singer, 14 years ago

I've been looking into this as well. My host OS is Debian on AMD64. The install of the IAR compiler works fine. The licensing dongle works as well. The FET PRO drivers do install, though it requires a couple of tries, but the IDE will not download code to the target. The MSWindows device manager shows OK status of the FET drivers.

comment:4 by Bob Barry, 14 years ago

VBox 3.2.8 behaves same in this respect: IAR EWB still won't connect to Atmel JTAGmkII debugger, but AVR Studio 4.18 does. VMplayer (3.1.0 build-261024) works fine on both IAR EWB and AVR Studio 4.18.

comment:5 by konrada, 14 years ago

My setup: host MacOS 10.6, VBox 3.2.8, guest Ubuntu 10.04/x86. When I plug in the MSP-FET430UIF which came with the Chronos watch, the host recognizes it (as verified in USB Prober.app). I have created a USB filter for the MSP-FET430UIF in the virtual machine configuration. With or without the filter, the MSP-FET430UIF appears in the list of USB devices in the running VM's menu, but it is always grayed out.

comment:6 by Bob Barry, 13 years ago

VBox 3.2.10 works with JTAGICEmkII. This issue can be closed.

comment:7 by Marc Singer, 13 years ago

Just tried. No luck.

I'm using VBox 3.2.10-r66523, Windows 7-32 on a Debian Linux w/64bit kernel. The USB device for the FET Pro is listed in the attached devices, but it never communicates with either the IAR compiler or the Elpotronic FET-Pro flash utility.

I'm not sure what the mkII device is. Can you tell us your SW configuration?

comment:8 by Bob Barry, 13 years ago

I'm using:

VBox 3.2.10 r66523

IAR EWB 5.3:

IAR Embedded Workbench IDE 5.3.6.927 (5.3.6.927) C:\Program Files\IAR Systems\Embedded Workbench 5.3\common\bin\IarIdePm.exe 3/27/2009 2:45:10 PM, 487424 bytes

Atmel JTAGICEmkII

(see http://www.atmel.com/dyn/Products/tools_card.asp?tool_id=3353)

Windows XP Version 2002 Service Pack 3

I'd been able to compile. but not debug, on each previous version of VBox; all works fine on 3.2.10. Suggest you try an XP virtual machine.

comment:9 by DM, 13 years ago

I have the same problem as the O.P. Trying to use MSP-FET430UIF JTAG debugger in XP guest / Linux (ubuntu, debian, fedora host). Vbox v 3.2.10 and have tried last few versions.

I do believe the USB device in question is "double enumerated" - not sure if that's the accurate term. I.e. there are two devices in one. I think one is a virtual serial port and the other is some sort of admin channel, possibly to bootload the device itself.

If you plug it into native windows, the device connected sound plays twice.

comment:10 by aeichner, 8 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use