Connect with us

Nano no longer working

Discussion in 'Microcontrollers, Programming and IoT' started by bigone5500, Oct 5, 2014.

Scroll to continue with content
  1. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    I used my nano yesterday and loaded a sketch to it. The sketch worked but I wanted to make a change. When I tried to upload the changes, I got the error that the serial port 'COM4' is already in use. I checked in device manager and found FT232R USB UART with an exclamation point stating The drivers for this device are not installed. (Code 28).

    I went to FTDI and got the latest drivers and loaded them. Didn't work. I have tried everything I can think of...but surely I have not thought of everything. I can load drivers for FTDI serial port and it says in device manager USB Serial Port (COM4). Alas, I cannot get past that.

    Arduino Problem.jpg
     
  2. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    This is just great! I can't upload to my Pro Minis either. My USB to 232 adapter is not recognized now. It also uses the FTDI 232RL chip.
     
  3. Gryd3

    Gryd3

    4,098
    875
    Jun 25, 2014
    Looks like windows 8...
    Are there any drivers specifically for your USB to RS232 adaptor that you have tried? Have you made any restore points you can try?

    Driver problems can be problematic, especially if windows decides it can take care of things itself... (*bluetooth, and USB tablets for example)
     
  4. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    I will try a restore point. Stay tuned...
     
  5. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    Tried restore point with no luck. I also hooked it up to my uno and successfully programmed it that way. This sucks bad.
     
  6. (*steve*)

    (*steve*) ¡sǝpodᴉʇuɐ ǝɥʇ ɹɐǝɥd Moderator

    25,418
    2,788
    Jan 21, 2010
    I find that removing and reinstalling the USB adapter often fixes this. Or changing the port you plug it into.

    However if you are able to program one device and not the other then you need to consider that you may have somehow corrupted the bootloader.

    Fixing that is an interesting and useful skill to have.

    (assuming it is this problem) There are several methods to fix it.

    One is to use a sketch which comes as part of the environment which allows you to use one arduino to program another. Beware that this requires that you disable the reset of the programmING arduino in such a way that the interface from the PC to the arduino DOES NOT reset it as the serial port connects. It also requires about 6 connections from one arduino to the other.

    An alternate means is to use a USB-ISP adapter which is essentially an interface between your USB and the 6 pin header on most arduino boards. In the absence of this 6 pin connector, you can also just connect it to the appropriate 6 pins.
     
    KrisBlueNZ likes this.
  7. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    I am leary of trying this but at this point I will try anything to get this thing back to working.
    Have done this with my UNO attached. It worked.
    I have one of these. It has an FTDI chip and is not recognized just the same as my nano.
    (Quoting fixed -- KrisBlueNZ)
     
    Last edited by a moderator: Oct 6, 2014
  8. Gryd3

    Gryd3

    4,098
    875
    Jun 25, 2014
    Perhaps step one should be getting this adaptor to work again before flashing the bootloader on your arduino.
    (Or try the arduino on a different machine)
     
  9. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    I have done more troubleshooting. I found that FTDI has a USB View utility and I also have read the installation guide. From there I found that there could be some issue with the PID and VID. These are programmed into the EEPROM and if the inf files do not match then there will be a problem. I think I am looking at this right but the VID for the chip is 0x0403 and the PID is 0x0000. There should be something different than all 0s in the PID according to the inf file.

    When I connect my usb to serial converter or my nano, they both have the same information in the usb view utility aside from having a different address.

    I am attaching a screen shot of the usb view utility and code from the inf for ftdibus.inf.

    FTDI USB View.jpg

    Code:
    [Version]
    Signature="$Windows NT$"
    DriverPackageType=PlugAndPlay
    DriverPackageDisplayName=%DESC%
    Class=USB
    ClassGUID={36fc9e60-c465-11cf-8056-444553540000}
    Provider=%FTDI%
    CatalogFile=ftdibus.cat
    DriverVer=07/12/2013,2.08.30
    
    [SourceDisksNames]
    1=%DriversDisk%,,,
    
    [SourceDisksFiles]
    ftdibus.sys = 1,i386
    ftbusui.dll = 1,i386
    ftd2xx.dll = 1,i386
    FTLang.Dll = 1,i386
    
    [SourceDisksFiles.amd64]
    ftdibus.sys = 1,amd64
    ftbusui.dll = 1,amd64
    ftd2xx64.dll = 1,amd64
    ftd2xx.dll = 1,i386
    FTLang.Dll = 1,amd64
    
    [DestinationDirs]
    FtdiBus.NT.Copy = 10,system32\drivers
    FtdiBus.NT.Copy2 = 10,system32
    FtdiBus.NTamd64.Copy = 10,system32\drivers
    FtdiBus.NTamd64.Copy2 = 10,system32
    FtdiBus.NTamd64.Copy3 = 10,syswow64
    
    
    [Manufacturer]
    %Ftdi%=FtdiHw,NTamd64
    
    [FtdiHw]
    %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6001
    %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_00
    %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_01
    %USB\VID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6011&MI_00
    %USB\VID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6011&MI_01
    %USB\VID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6011&MI_02
    %USB\VID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6011&MI_03
    %USB\VID_0403&PID_6014.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6014
    %USB\VID_0403&PID_6015.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6015
    
    [FtdiHw.NTamd64]
    %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6001
    %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_00
    %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_01
    %USB\VID_0403&PID_6011&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6011&MI_00
    %USB\VID_0403&PID_6011&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6011&MI_01
    %USB\VID_0403&PID_6011&MI_02.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6011&MI_02
    %USB\VID_0403&PID_6011&MI_03.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6011&MI_03
    %USB\VID_0403&PID_6014.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6014
    %USB\VID_0403&PID_6015.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6015
    
    [ControlFlags]
    ExcludeFromSelect=*
    
    [FtdiBus.NT]
    CopyFiles=FtdiBus.NT.Copy,FtdiBus.NT.Copy2
    AddReg=FtdiBus.NT.AddReg
    
    [FtdiBus.NTamd64]
    CopyFiles=FtdiBus.NTamd64.Copy,FtdiBus.NTamd64.Copy2,FtdiBus.NTamd64.Copy3
    AddReg=FtdiBus.NT.AddReg
    
    [FtdiBus.NT.Services]
    AddService = FTDIBUS, 0x00000002, FtdiBus.NT.AddService
    
    [FtdiBus.NTamd64.Services]
    AddService = FTDIBUS, 0x00000002, FtdiBus.NT.AddService
    
    [FtdiBus.NT.AddService]
    DisplayName = %SvcDesc%
    ServiceType = 1 ; SERVICE_KERNEL_DRIVER
    StartType = 3 ; SERVICE_DEMAND_START
    ErrorControl = 1 ; SERVICE_ERROR_NORMAL
    ServiceBinary = %10%\system32\drivers\ftdibus.sys
    LoadOrderGroup = Base
    AddReg = FtdiBus.NT.AddService.AddReg
    
    [FtdiBus.NT.AddReg]
    HKR,,DevLoader,,*ntkern
    HKR,,NTMPDriver,,ftdibus.sys
    HKR,,EnumPropPages32,,"ftbusui.dll,FTBUSUIPropPageProvider"
    
    [FtdiBus.NT.AddService.AddReg]
    ;HKR,Parameters,"LocIds",1,31,00,00,00,32,00,00,00,00
    ;HKR,Parameters,"RetryResetCount",0x10001,50
    
    
    [FtdiBus.NT.Copy]
    ftdibus.sys
    
    [FtdiBus.NT.Copy2]
    ftbusui.dll
    ftd2xx.dll
    FTLang.dll
    
    [FtdiBus.NTamd64.Copy]
    ftdibus.sys
    
    [FtdiBus.NTamd64.Copy2]
    ftbusui.dll
    ftd2xx.dll,ftd2xx64.dll
    FTLang.dll
    
    [FtdiBus.NTamd64.Copy3]
    ftd2xx.dll
    
    [Strings]
    Ftdi="FTDI"
    DESC="CDM Driver Package - Bus/D2XX Driver"
    DriversDisk="FTDI USB Drivers Disk"
    USB\VID_0403&PID_6001.DeviceDesc="USB Serial Converter"
    USB\VID_0403&PID_6010&MI_00.DeviceDesc="USB Serial Converter A"
    USB\VID_0403&PID_6010&MI_01.DeviceDesc="USB Serial Converter B"
    USB\VID_0403&PID_6011&MI_00.DeviceDesc="USB Serial Converter A"
    USB\VID_0403&PID_6011&MI_01.DeviceDesc="USB Serial Converter B"
    USB\VID_0403&PID_6011&MI_02.DeviceDesc="USB Serial Converter C"
    USB\VID_0403&PID_6011&MI_03.DeviceDesc="USB Serial Converter D"
    USB\VID_0403&PID_6014.DeviceDesc="USB Serial Converter"
    USB\VID_0403&PID_6015.DeviceDesc="USB Serial Converter"
    SvcDesc="USB Serial Converter Driver"
    ClassName="USB"
     
    Last edited: Oct 6, 2014
  10. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    This dilemma has been solved. I contacted FTDI support and sent them a screen shot of the usb view and they confirmed that the board contains a NON-GENUINE ftdi chip as does my non-working nano. Use their usb view software and send them a screen shot to us.support at ftdichip.com. They will respond promptly.

    Case solved with some hard feelings.

    This is what they replied to me:

    Code:
    Jared:
    
    
    Both of these devices are using non-genuine FTDI chips.  See if you can get a refund.
    
    
    Try Sparkfun or Adafruit as a source for  FTDI based hardware.
    
    
    
    Best Regards,
    
    
    Cameron Forbes
    Customer Support Engineer
    
    Description: Description: Description: cid:[email protected]
    
    Future Technology Devices International Limited
    
    7130 SW Fir Loop
    
    Tigard, OR 97223-8160
    
    Tel:   503.726.5415
    Fax:  503.547.0987
     
    Last edited: Oct 6, 2014
  11. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
    I said the Nano is no longer working. But it is. The ftdi is crap now but I can still program it by my UNO.

    The rat has clicked the like button...

    tmp_5166-20141006_212445-1261561315.jpg
     
  12. (*steve*)

    (*steve*) ¡sǝpodᴉʇuɐ ǝɥʇ ɹɐǝɥd Moderator

    25,418
    2,788
    Jan 21, 2010
    excellent :)
     
  13. Gryd3

    Gryd3

    4,098
    875
    Jun 25, 2014
    bigone5500 likes this.
  14. Arouse1973

    Arouse1973 Adam

    5,164
    1,081
    Dec 18, 2013
    Great news this could be my problem also. I have a sainsmart Nano that worked once and now I can't upload anything to the Nano using the IDE via FTDI USB. I can reprogram the boot loader using the USB ISP but if I upload a sketch this way the green LED goes out and nothing happens.
    Adam
     
  15. Gryd3

    Gryd3

    4,098
    875
    Jun 25, 2014
    Perhaps. I did a quick google search, and this seems to be hitting a lot of Arduinos more than others at the moment
     
  16. bigone5500

    bigone5500

    712
    120
    Apr 9, 2014
  17. (*steve*)

    (*steve*) ¡sǝpodᴉʇuɐ ǝɥʇ ɹɐǝɥd Moderator

    25,418
    2,788
    Jan 21, 2010
    Very good. I will take a look into that in more detail.

    FTDI bricking user's devices is a very baaad thing to do. I'd respond by using another manufacturer's products I'm afraid (if the story is true).
     
  18. Gryd3

    Gryd3

    4,098
    875
    Jun 25, 2014
    No prob.
    The scary part, is that I'm familiar with the 0403 VID, as I've seen it a number of times when looking for drivers... Does not mean the particular product is an FTDI FT232, but they have been used in tons of hardware. Known or not... this could screw a lot of people up.
    If you have the tools, I would love to know if the suggested fix works.
    "FT_PROG 2.8.2.0 - EEPROM Programming Utility" from
    http://www.ftdichip.com/Support/Utilities.htm

    Edit: More info from http://forum.arduino.cc/index.php?topic=270175.0
     
  19. Arouse1973

    Arouse1973 Adam

    5,164
    1,081
    Dec 18, 2013
    Ok get this, I ordered two Nano's from different people. One came in a kit with lots of other bits and the other was suppose to be a genuine Nano from Arduino. Both now bricked, both PID codes 0. Both parts had the same batch code, funny that!. If your Nano has batch code CN480661 then it's probably fake. I couldn't believe it's the same number as whats was on the link Gryd3 posted. I shall be having a little word with Amazon and the supplier of these parts in my usual diplomatic fashion :)
    Thanks
    Adam
     
    KrisBlueNZ likes this.
  20. Arouse1973

    Arouse1973 Adam

    5,164
    1,081
    Dec 18, 2013
    I can confirm the above post is correct. After getting the device replaced it now communicates with the PC and I can now programme the device. The next step is to get the code to run.

    I contacted the seller in China, Jackie Chan was his name I think :) And after asking him where he wanted me to stick his chop-sticks, I got a refund :)
    Thanks
    Adam
     
    Gryd3 and KrisBlueNZ like this.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Electronics Point Logo
Continue to site
Quote of the day

-