Main Site Documentation

Cannot attach my Quail to WINUSB port


#1

Sorry this is VERY longwinded but I wanted to give all the information I have.

Using Windows 10 Pro with all known updates.
Using TinyCLR 0.6.0

Quail is marked: Rev 2.01 - Original code Mountaineer Prime Firmware.

Using the STM32 bootloader to generate and load a DFU firmware file.
Update of Quail Firmware v0.6.0.hex to file QUAIL6.dfu said that it was loaded successfully.

Device Manager shows:
Universal Serial Bus devices
MikroE.Quail (Win Usb Device) Device status: This device is working properly.)

Device USB\VID_0483&PID_A08A\6&ab382be&0&3 was not migrated due to partial or ambiguous match.
I do not know what this means… I found some notes that it may be because of a Windows10 update?

TinyCLR Config does not find the Port: device

Upon power up of the Quail board the three led’s blink in sequence and the Red led remains on.

FEZ Config shows MikroE.Quail_v2.0
Ping returns Pinging… TinyCLR

Check device for update returns:
Firmware (TinyCLR) version information:
4.3.1.0 on this device.
Please wait for the device to reboot… Done.

Build a small app and start debugging returns:

In Output window I receive:
Show output from: TinyCLR Device Deployment
Looking for a device on transport ‘USB’.
Found device port ‘USB’ with ID ‘4d3c4ddc-9d96-4d39-95d0-1e64df0a8e15’ for transport ‘Usb’.
Starting device deployment.
Attempting to connect to device ‘USB:’: iteration 0.

Fails! TinyCLR Error dialog popup shows
An exception occured while attempting to launche the debugger:
DebugPort.GetDeviceProcess()called with no argument

Application used for test:

using System;
using System.Collections;
using System.Text;
using System.Threading;
using System.Diagnostics;

namespace TinyCLR_Test
{
class Program
{
static bool isattached;

    static void Main()
    {
        isattached = Debugger.IsAttached;

        if(isattached)
        {
            Debug.WriteLine("Is Attached");
        }

        if (!isattached)
        {
            Debug.WriteLine("Is NOT Attached");
        }

        Thread.Sleep(20);
    }
    // End main
} // End class

} // End namespace

Yes It’s me and in trouble AGAIN!

My G400 developer board using TinyCLR ver 6 runs fine winusb.


#2

Did you try to remove the driver and scan your hardware again ? I have latest Windows 10 and do not have any issue with Quail and TinyCLR 0.6.0 (at least regarding the connection to the PC :wink: )

Also, could you post your Device.h file, please ? Perhaps there is something wrong in it ?


#3

Did you try to remove the driver and scan your hardware again

I wanted to avoid that because my other boards work with the current driver but I will do so.

As to the Device.h file. I do not have. (That I know of)

I was using GHI Quail Firmware v0.6.0.hex converted to .dfu


#4

Please give me your email address so that I can send my .dfu file (I cannot attach it to my message here :frowning: )


#5

will_george@sbcglobal.net

I uninstalled the driver with same results.

Uninstalled the winUSB driver (Uninstall Device)
Power off my PC
Restart PC with Quail attached to usb port

Used Search automatically and Browse my computer for driver
Both tell me
Device USB\VID_0483&PID_A08A\6&ab382be&0&3 was not migrated due to partial or ambiguous match.

Thanks for the help!


#6

I received the DFU file from Bec_a_Fuel and I can now attach to the USB port.

MY HERO!

I do not know if I did something wrong but I do not think so (But with me you can never tell).

From Quail DFU I received by email: The DFU file size is 435 KB

From Quail Firmware v0.6.0.hex I made: The DFU file size is 434 KB

Anyway I am now up and able to debug.
(As a note I still see the Device not migrated so I assume it is not a problem)

Output for my little test application:
The debugging target runtime is loading the application assemblies and starting execution.
Ready.

‘GHIElectronics.TinyCLR.VisualStudio.dll’ (Managed): Loaded ‘C:\Users\Will George\Documents\Visual Studio 2017\Projects\TinyCLR_Test\TinyCLR_Test\bin\Debug\pe…\TinyCLR_Test.exe’, Symbols loaded.
Done.

Waiting for debug commands…

The thread ‘’ (0x2) has exited with code 0 (0x0).
Is Attached (<< Debug message from my app)
The thread ‘’ (0x1) has exited with code 0 (0x0).
The program ‘[1] TinyCLR application: Managed’ has exited with code 0 (0x0).


#7

I have just sent to you the Device.h and Scatterfile.gcc.ldf files so that you can try to build the same dfu as me.


#8

Received… And thanks again.


#9

[quote=“willgeorge, post:1, topic:21054”]
FEZ Config shows MikroE.Quail_v2.0
Ping returns Pinging… TinyCLR
Check device for update returns:
Firmware (TinyCLR) version information:
4.3.1.0 on this device.
Please wait for the device to reboot… Done.[/quote]

FEZ Config is no longer to work with with TinyCLR OS.
Try to build the original version provided by Ghi to see if it work on your PC?
Usually you don’t have to but for your case, uninstall NetMF 4.3.1.0 to see what happen.


#10

I used FEZ Config and TinyCLR Config only to see if there was any difference in the USB connection.

The dfu file sent to me by Bec_a_Fuel: is allowing me to attach to the Quail.

Thanks for the information.

EDIT:
I forgot to mention that NetMF 4.3.1.0 was/is not on my PC.