Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 8 of 8

Thread: USB device descriptor request failed Custom Board

  1. #1
    Junior Member
    Join Date
    Feb 2017
    Posts
    4

    USB device descriptor request failed Custom Board

    Hello. We are working on using the Fadecandy bootloader (which is largely based on Paul's work) and are having trouble getting it to work on a MK20DX256VLH7. This is a modification of the fadecandy bootloader with the right IRQs and memory sizes. https://github.com/DavidMenting/fade...256-bootloader

    When we plug in the board to USB we get a device descriptor request failed.

    It is on a custom board. The schematic is attached. (Note: pin 8, vregin, has been jumped to the vusb)

    We have been troubleshooting this for weeks with little success. I suspect that it is a hardware problem. Any help is appreciated.

    Thanks,
    Eric
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	sch - p1.jpg 
Views:	38 
Size:	84.2 KB 
ID:	9707   Click image for larger version. 

Name:	sch - p2.jpg 
Views:	36 
Size:	71.4 KB 
ID:	9708  

    Click image for larger version. 

Name:	sch - p3.jpg 
Views:	31 
Size:	74.3 KB 
ID:	9709   Click image for larger version. 

Name:	sch - p4.jpg 
Views:	44 
Size:	102.6 KB 
ID:	9710  

    Click image for larger version. 

Name:	brd.png 
Views:	33 
Size:	196.9 KB 
ID:	9705  
    Last edited by ericsims; 02-16-2017 at 01:58 AM.

  2. #2
    Moderator Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,346
    Vbat is not connected(?)
    And im not sure about vregin. Doesnt it need a connection, too ?
    Last edited by Frank B; 02-16-2017 at 06:28 AM.

  3. #3
    Junior Member
    Join Date
    Feb 2017
    Posts
    4
    Hi Frank, Thanks for the reply. No, vbat is not connected. I thought/think that it is only for the RTC module. I hooked it up to 3v3 just now, but had no luck.
    Vregin has actually been jumped to vusb (5v). In the datasheet or reference manual it says that vreg in is required for the usb module to work, but I still can't find anything about vbat.

    -Eric

  4. #4
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    169
    Eric,

    See this page and search for "VBAT":
    https://www.pjrc.com/store/ic_mkl02.html

  5. #5
    Junior Member
    Join Date
    Feb 2017
    Posts
    4
    Ah that's quite interesting. I tried with both vbat connected and with the RTC init commented out with no luck. Same issue.

    On that same page I see that "VREGOUT on the MK20 must be connected, even if you are supply 3.3V without using the MK20's built in voltage regulator.", but this thread doesn't make much sense to me. It seems that Scott had his vregin powered incorrectly and a fried MK20.

  6. #6
    Update all your drivers.
    Disable fast boot from power options in Control Panel.
    Make sure all your ports works fine. Also, you can check this post which shows all the solutions for your problem: device descriptor request failed

  7. #7
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    15,711
    Quote Originally Posted by ericsims View Post
    On that same page I see that "VREGOUT on the MK20 must be connected, even if you are supply 3.3V without using the MK20's built in voltage regulator.", but this thread doesn't make much sense to me.
    It means you must connect 3.3V power to VREGOUT, even if not using the regulator.

    I've edited the web page. Hopefully this longer version will make more sense?

    VREGOUT on the MK20 must be connected, even if you are supply 3.3V without using the MK20's built in voltage regulator. The USB tranceiver power connects only to VREGOUT. Your board will fail to communicate over USB if VREGOUT does not have 3.3V power.
    Connect 3.3V to VREGOUT out, and of course also VBAT. Hopefully those will bring your board to life?

  8. #8
    Junior Member
    Join Date
    Feb 2017
    Posts
    4
    Thanks Paul,

    Ok, so I still haven't solved the problem.
    I put a ZIF socket on some protoboard to debug.
    I have 3v3 on pins 3,7,21,30,48. I have gnd on 4,31,47.
    There is a jtag connector on pins 22,23,24,25,34.
    USB is connected with the 5v line floating, and the D+ and D- connected to pins 5 and 6 through 33ohm resistors, and gnd, is connected to gnd.
    16 Mhz Crystal tied to 32 and 33 with caps to ground.

    Other than that, there is nothing connected. Same problem.

    Am I missing something? The board only has like a dozen wires. I am thinking that it might be a code problem(?)
    Anyways, if no one has any more ideas, I am going to switch to an ST chip instead.

    Thanks for all the help!
    -Eric
    Last edited by ericsims; 05-10-2017 at 10:59 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •