infineon4engineers Facebook

infineon@google+ Google+

infineon@linkedin linkedin

infineon4engi@twitter twitter

infineon@youtube youtube

Dave

+ Reply to Thread
Results 1 to 10 of 10

Thread: Crash on DAS (Device Access Server) in Virtual Machines.

  1. #1
    PE1PUP is on a distinguished road
    Join Date
    Nov 2011
    Location
    The Netherlands
    Posts
    15
    Points
    70

    Crash on DAS (Device Access Server) in Virtual Machines.

    Hello all,

    I use (VMware) Virtual Machines in order to install and run all my tools. This enables me to use tools in such a way that they can't interfere with each other. I tried to do this for an XC838 environment. DAVE and DAVE-Bench run fine in a WIndows-XP Virtual Machine. But as soon as I try to start the UDAS (as part of the installed DAS Servers) with actual XC836-EK hardware connected over USB, then my (virtual) machine crashes....

    It doesn't matter if I start UDAS from the DAS Server Control Panel or from the Keil uVision4 environment.

    If no (USB linked) hardware is connected, and I try to reprogram the device, then I get the proper error message (because of the missing hardware) as follows:...
    Build target 'MyTest'
    compiling HELLO.C...
    linking...
    Program Size: data=30.1 xdata=0 code=1096
    "HELLO" - 0 Error(s), 0 Warning(s).
    Load "C:\\Keil\\C51\\Examples\\Hello\\HELLO"
    Searching for DAS Server 'UDAS'...
    DAS Server 'UDAS' is installed.
    DAS Server 'UDAS' is not started yet. Trying to start it now...
    DAS Server 'UDAS' has been started successfully.
    Warning: Unknown JTAG ID=00000000. Assuming an XC866-4FR device with 16K flash
    So then I plugin the USB of my KIT_XC836_EK and give the same command.
    I see the same text appearing in the output window until the line "DAS Server 'UDAS' is not started yet. Trying to start it now..."
    And then I have a hard crash causing the (virtual) machine to reboot.....
    This is fully reproducable....

    Does anybody have any clue why invoking UDAS causes such a hard crash???
    Can UDAS handle USB 1.0 ports? (These are the virtual USB ports under VMware...)
    Or are USB 2.0 ports required as minimum????

    I'm looking forward to any reaction on this odd issue...
    Thanks in advance & best regards from the Netherlands,
    Johan.

    Update (18-jan-2012): In the meanwhile I'm getting the idea that the problem is caused by the fact that my virtual machine only has USB 1.0 ports while the UDAS tooling requires USB 2.0 for pushing the connection into SPD mode. I only do not understand why that makes the whole machine crash so hard. I would expect a failure message or warning. Not a full system crash.... Any ideas...????
    Last edited by PE1PUP; Jan 18th, 2012 at 07:13 AM. Reason: Updated based on further experiences.

  2. #2
    Beginner Beginner alexshao1978 is on a distinguished road
    Join Date
    Nov 2011
    Location
    ShangHai
    Posts
    31
    Points
    51.875
    I use VM to debug XBOARD-XC2265N, it work OK.
    My host OS version is Windows 7 Ultimate, 64-bit (Build 7600) 6.1.7600.
    My VM version 7.0.1 build-227600.
    Someone tell me I must use 32Bit OS(Like WINXP) in VM and 64Bit OS(Like WIN7) in host to avoid address overflow.

    Further more, do you notice any other features of VM? For example, have enable ACE? Have you connect device before you debug(click status bar in VM window below, connect and you will find a VM usb device in your host hardware managerment and a infinoen usb hardware in your VM OS)?

  3. #3

    Infineon Employee
    Infineon Employee
    Juergen is on a distinguished road
    Join Date
    Sep 2011
    Location
    Singapore
    Posts
    37
    Points
    52.3046875
    Hi Johan,

    I have passed this to our DAS expert who will reply to this thread.
    I myself also experienced this problem with XC836EK on an older laptop running on Windows2000. I had a few system hard crashes until I was told then that it is necessary to have USB 2.0
    The probelm in my case was overcome by using a powered USB hub. Since I upgraded to a new laptop and Windows 7, I have not had this kind of problem anymore.

    Best Regards
    Juergen

  4. #4

    Infineon Employee
    Infineon Employee
    Albrecht is on a distinguished road
    Join Date
    Jan 2012
    Posts
    3
    Points
    17.5

    SPD requires USB 2.0 + DAS on virtual machines is slow

    Hi Johan,

    an SPD connection requires a USB 2.0 connection, so your setup with a virtual USB 1.0 port can't work.

    Why it crashes is another issue. We know that there are problem with the USB drivers of FTDI on XP.
    E.g. you can get on XP a blue screen when you do a hot unplug of the USB.
    We also know from own experiments that a virtual machine makes the USB interaction much slower.
    And there is a lot of USB interaction. So it worked for DAP/JTAG but it was no fun to work with it.

    I just added the release notes of the upcoming DAS V4.0 point 3:

    2. For SPD a device connection is only established if the miniWiggler is using a high speed USB
    port, hub and quality cables.

    3. It is discouraged to run DAS on a virtual machine when the Access HW (miniWiggler etc.) is
    connected via USB. The performance of such a setup is very low. In particular it is not
    possible to have a reliable SPD connection if possible at all (refer to point 2).

    I would be interested whether the following setup is possible:
    Start UDAS in the regular OS of your computer
    Start your tool e.g. DAS Device Scanner within a Virtual Machine and use a socket connection to the UDAS on your host.
    However I don't know the Host Computer address you need to use in such a case and whether it's possible at all.

    -- Albrecht
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

  5. #5
    PE1PUP is on a distinguished road
    Join Date
    Nov 2011
    Location
    The Netherlands
    Posts
    15
    Points
    70
    Hello Alex,

    Thanks for your feedback that it should be possible what I try to do. Your comment enabled me to search deeper, and that way I found that my specific VMware image running XP inside was generated with an older VMware tool. This caused the image to only have USB 1.1 virtual ports connected to my real hardware USB 2.0 ports. The way to solve this is to migrate my VMware image of XP with the newest VMware tools to the latest version. In that latest version it's possible to determine the USB versions which will be emulated; so USB 2.0 can be selected for use inside the Virtual Machine. However, if it really would work has to be checked, because to the speed warnings Albrecht added... ;-)

    Best regards from the Netherlands, Johan.

  6. #6
    PE1PUP is on a distinguished road
    Join Date
    Nov 2011
    Location
    The Netherlands
    Posts
    15
    Points
    70
    Hello Albrecht,

    Thanks for your feedback. Good to know for sure that USB 1.1 can't work.
    It a clever step to add the "discouragement" to use VM's in the DAS 4.0 release notes. Using Virtualisation is becoming ever more popular, so any guidance is helpfull.

    And your suggestion to start UDAS in the regular OS on my host and start DAS Device Scanner within a Virtual Machine and use a socket connection to the UDAS on my host is a very clever one...!!!
    I tried it, and I can indeed make a logical connection that way. I just have to enter the IP address of my host into the proper Host Computer line in the DAS Device Scanner. (Where by default "localhost" can be found) And indeed I can see the UDAS running with the same PID as the UDAS I started in my host OS. So that looks very promising.
    However, I did not manage to use such a socket connection for FLOADing from within my VM to my host where the XC836 is connected to the USB 2.0 port, but I will try that a bit more, just out of own personal interest.....

    Best regards, Johan.

  7. #7
    Beginner Beginner kamikaze is on a distinguished road kamikaze's Avatar
    Join Date
    Nov 2011
    Location
    /Europe/Germany/Karlsruhe
    Posts
    94
    Points
    119.1015625
    I was thinking about running DAS in VirtualBox on a FreeBSD Host, exactly for the reason that I cannot run DAS on FreeBSD.

    Too bad that won't work. Or is anyone working on a DAS version for FreeBSD?
    [ kamikaze@bsdforen.de - XC878 libraries (GitHub) - XC878 ECU project stub (GitHub) - High Speed Karlsruhe ]
    - - - -
    Primary platform: XC878CM-16FFA
    Custom library: ~10k lines of code, ~300 pages of documentation

  8. #8
    Beginner Beginner kamikaze is on a distinguished road kamikaze's Avatar
    Join Date
    Nov 2011
    Location
    /Europe/Germany/Karlsruhe
    Posts
    94
    Points
    119.1015625
    I can offer you a little success story here.

    VirtualBox OSE on a FreeBSD 9/amd64 Host
    Windows 7/i386 VM

    Installed into the VM:
    DAS 3.3.1
    XC800 Fload 5.3.4

    Hardware passed through from host:
    XC800 Starter Kit

    The following things work:
    Fload: erase, flash, verify
    MCD Basic Client: run, stop, step, reset

    VirtualBox OSE only supports USB 1.0, but the throughput is not limited to USB 1 speed, as far as I know.
    Next week I will test it with a DAP miniWiggler (I don't have the 16pin cable at home).
    [ kamikaze@bsdforen.de - XC878 libraries (GitHub) - XC878 ECU project stub (GitHub) - High Speed Karlsruhe ]
    - - - -
    Primary platform: XC878CM-16FFA
    Custom library: ~10k lines of code, ~300 pages of documentation

  9. #9
    hsiva is on a distinguished road
    Join Date
    Nov 2012
    Posts
    1
    Points
    12.5

    das v3.3.1

    Does anyone have DAS v3.3.1 setup files that you can send to me? If so, please email to harish.siva@gmail.com.

    I am having issues with DAS 4.0.5 and FLOAD v5.3. When I try to connect to the micro, I get a message stating 'UDAS/JTAG server cannot be found'.
    I would like to try DAS v3.3.1 just to see if I have similar issues...

    Thank you very much.

  10. #10
    Beginner Beginner kamikaze is on a distinguished road kamikaze's Avatar
    Join Date
    Nov 2011
    Location
    /Europe/Germany/Karlsruhe
    Posts
    94
    Points
    119.1015625
    Last edited by kamikaze; Feb 19th, 2013 at 05:10 PM.
    [ kamikaze@bsdforen.de - XC878 libraries (GitHub) - XC878 ECU project stub (GitHub) - High Speed Karlsruhe ]
    - - - -
    Primary platform: XC878CM-16FFA
    Custom library: ~10k lines of code, ~300 pages of documentation

+ Reply to Thread
Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.