Remove Text Formatting
Loading...

+ Reply to Thread
Results 1 to 18 of 18
  1. #1
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Amicus 18 FTDI driver on W10?

    Hi,
    So I've got myself a new PC (with Window 10) and I'm slowly setting everything up.

    I'm now at the point where I need to get the Amicus 18 bootloader to work. Plugging an Amicus 18 board in to the PC makes it show up in the device manager but no driver is installed. So I installed Proton IDE (2.0.3.3 with Proton compiler 3.5.9.2) but no dice.

    I tried to manually install the driver by pointing the driver wizard to the Amicus18 USB Driver folder within the ProtonIDE installation but it complains about a missing hash value.

    Tried downloading the generic FTDI CDM driver (2.12.26) and pointed it to that but no go.

    I've Googled for a while and found an [urllhttp://www.protonbasic.co.uk/archive/index.php/t-75562.html]archived thread[/url] on the Proton forum where someone apparently provides a solution but I can't seem to find the attachment anywhere.

    So, anyone knows how to get the Amicus Loader to work on Win10? I use that board extensively when trying and debugging quick things when helping out her on the forum, I'd hate to see it not working on W10.

    I'd appreciate any pointers, thank you!

    /Henrik.

  2. #2
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    BTW, plugging in a generic USB to UART board based on the FTDI FT232RL (same chip as on the Amicus 18) works just fine.

  3. #3
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    More info:
    On the Proton forum I found a thread with links showing how to install unsigned driver so I followed that and was able to install the Amicus 18 serial port driver (which again is nothing other than the standard FTDI driver as far as I understand) and it shows up correctly in device manager. But when rebooting into normal mode and plugging in the Amicus 18 it again refuses to use the driver.

    For reference, here's the thread on the Proton forum.

    /Henrik.

  4. #4
    Join Date
    Sep 2009
    Posts
    616

    Default Re: Amicus 18 FTDI driver on W10?

    That is new "state of art" way to protect user from malicious drivers. Or to be honest, very good way to get more money. Because certificates have expiration date. You know, after some period drivers turn bad....
    And you pay about 200-500$ per year to maintain drivers signed and to redistribute new signed driver every 1 to 3 years.
    You have option to get 32bit version, and then it shouldn't disable unsigned drivers, go back to win 7, or pay to sign driver...
    Even if original driver is signed, they probably changed PID and VID for Amicus, so that render driver useless.

    There is one more option, but probably wont work.
    You can try to manually force FTDI driver to Amicus.
    1. Uninstall all drivers for Amicus.
    2. When you plugin USB cancel automatic search.
    3. Go to device meager right click properties, go to driver tab, click update driver
    4. Let me browse option, Then select from list, or what ever is called on win10
    5. Then click to have disk, select FTDI signed drives files.
    6. Click what ever is needed to install it. You should get some errors that driver isn't compatible, etc...
    This you may expect with all drivers stored on disc. So you need always to have new signed driver. Or at least every couple years.
    I have this issue with microchip drivers for my devices. I have CDC on couple devices and just changer PID and VID to match with PID and VID in device, and that makes driver unsigned. And you also need to pay VID to USB...
    Also there is some changes in CE certification for EU. So it seems that small manufacturers have no chance....
    Hope that this help you.

  5. #5
    Join Date
    Aug 2011
    Posts
    93

    Default Re: Amicus 18 FTDI driver on W10?

    Even though the chip on the amicus18 board is an FT232RL, the USB PID has been changed so that it appears as an "Amicus18 Serial Port" (USB\VID_0403&PID_AC75). Once that was done it required the use of a modified INF driver file.

    There is (at least was) a utility on the FTDI site called FT_PROG that would let you change the PID back to the standard FTDI PID for the FT232RL, and that would let you use the standard FTDI driver. I don't know if there are any issues with that (like a loader program looking for the old AC75 PID), but hardware-wise that should work fine.

    I've only used FT_PROG on win7 so I have no idea if/how it works on win10.

  6. #6
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,014

    Default Re: Amicus 18 FTDI driver on W10?

    Yes, In fact I recently purchased a few Amicus18 boards for a development program. I switched out the processor for an 18F26K22 and used the FT_PROG program from FTDI to set the PID to a default state. This however can only be done after the board is found and connected by the operating system which requires the Amicus software to be loaded on the computer you are using to do the reprogramming. I then use the PBP3 with the MCSPX boot loader for all program development. Works a treat...
    Dave Purola,
    N8NTA
    EN82fn

  7. #7
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    Thank you all for your input!
    Forcing the standard FTDI USB serial port driver onto the "Amicus serial port" does "work" in that it shows up as a COM-port (instead of under "other devices") in the device manager but obviously the Amicus Loader application isn't looking for a "generic" COM port, it's looking for the "Amicus serial port" - which sucks.

    In the Proton forum thread I linked to previously there appears to be a special version of the Amicus loader application (in post #8). I've registred and got my account activated but I'm not allowed to post or download so I can't try it and it doesn't really say what the purpose of that version is.

    I guess since Windows now sees the board as a normal COM port using FT_Prog to get rid of the Amicus stuff all together is the best thing to do and the way forward.

    Dave, are you using the standard MCSPX bootloader or the "UMC" one. I can't seem to find a prebuilt loader .hex file for either 25K20 or the 25/26K22 and I've never used the UMC one.

    /Henrik.

  8. #8
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,014

    Default Re: Amicus 18 FTDI driver on W10?

    Henrick, I have used the UMC Loader since it came out and have worked with David Barker on a few bug's I found in it. In fact as far as the Boot Loader goes, you have to manipulate some of the registers of the newer 16F & 18F parts before the Boot Loader will work. That is why David has allowed you to generate an .ini file to configure the Boot Load Builder for your particular processor.
    Dave Purola,
    N8NTA
    EN82fn

  9. #9
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    Thanks Dave,
    Guess it's time to figure that UMC loader out, never had the need before.

    /Henrik.

  10. #10
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    Dave,
    If you don't mind me asking, are you using the UMCBuild application to create your bootloader .hex files or are you building them manually in MPLAB?

    I've just read thru the documentation and have attempted to create a .hex file using the UMCBuild application but needless to say I'm struggling. The application says it can't find the MPASM executable, something the docs says it should be able to do if I have a working environment (which I do). I suspect the issue is that it's looking for MPASM.exe while it's now called MPASMX.exe.

    I tried adding the path to MPASMX in the [PATH] section of the UMCBuild.ini but I get either Can't find MPASM executable or Can't find MPASM path. I tried making a copy of MPASMX.exe, renaming it to MPASM.exe but still can't make it work.

    Would you mind sharing some of your knowledge regarding the UMC?

    /Henrik.

  11. #11
    Join Date
    Aug 2011
    Posts
    93

    Default Re: Amicus 18 FTDI driver on W10?

    Try renaming mpasmx.exe to MPASMWin.exe. That's the name of the old assembler.

  12. #12
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    Well of course it is! Thank you for reminding me!
    Making progress but still not all the way. Placing a copy of MPASMX with its name changed to MPASMWIN.exe and adding the following line to the UMCbuild.ini file made THAT error go away
    Code:
    MPASM=C:\Program Files (x86)\Microchip\MPLABX\v3.55\mpasmx
    It then complained it couldn't find the MPLAB device path so I added the following:
    Code:
    DB=C:\Program Files (x86)\Microchip\MPLABX\v3.55\mpasmx
    (Because, just as with the assembler, that's where all the device specific assembler .inc files are located - which I assumed was what it's looking for...)

    But now it says No device file found for "18F452"

    Anyone have any ideas?

    /Henrik.

  13. #13
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,014

    Default Re: Amicus 18 FTDI driver on W10?

    Henrick, I have my "Mecanique" directory mounted off my root directory on "C:/" drive. I have never used the "PATH" directives since I have mounted it on my Windows 8 machine about 3 years ago. Even when I had my Windows "XP" machine I had it mounted in the same way. Make sure the device you are trying to program in in the devices.ini file located under "Mecanique/MCSPX/MCLoader/umc/src/18F/". For new devices you will have to make new entries into this .ini file.
    Dave Purola,
    N8NTA
    EN82fn

  14. #14
    Join Date
    May 2013
    Location
    australia
    Posts
    1,181

    Default Re: Amicus 18 FTDI driver on W10?

    hi Henrik
    I do it this way , it may not be the best way but it works for me

    created folded
    c:\myBOOTLOADER
    made a subdir for each chip i use
    c:\myBOOTLOADER\16f1825
    c:\myBOOTLOADER\18f25k22
    in each folder the modified config.ini file to suit that chip

    to compile loader
    copy chosen config.ini to c:\myBOOTLOADER
    then using dos shell
    cd to working dir
    CD C:\Program Files\Mecanique\MCSPX\MCLoader\umc\build
    run compiler
    umcbuild.exe "c:\myBOOTLOADER\config.ini"

    output is in c:\myBOOTLOADER\"chosen pic folder"

    note
    C:\Program Files\Mecanique\MCSPX\MCLoader\umc\src has two sub dirs
    16f and 18f , in these are the device.ini files you may need to add your chips to these files if they are not included


    16f1825 ini
    Code:
    ; optional path information - default output folder is 
    ; user documents -> umcbuild... 
    [PATH] 
    Output=C:\MYBOOTLOADER
    [TEMPLATE] 
    ;PIC18=..\src\18F\umc_loader.asm 
    PIC16=..\src\16F\umc_loader.asm 
    ; device name and OSC... 
    [MCU] 
    Device=16F1825 
    OSC=32000000 
    [USART] 
    BAUDRATE = 19200 ; initial startup baudrate (default is 19200) 
    BRGH16 = 1 ; 16 bit SPBRG support (default is OFF) 
    ; device configuration settings... 
    [CONFIG] ;----- CONFIG1 Options -------------------------------------------------- 
     __config        _CONFIG1,    _FOSC_INTOSC & _CP_OFF & _WDTE_OFF  &  _PWRTE_ON  &  _MCLRE_ON  & _CLKOUTEN_OFF
     __config      _CONFIG2, _PLLEN_OFF & _LVP_OFF
    ; place startup code in here... 
    [USERCODE] 
    
     movlb 1
     BCF TRISC,4
     BSF TRISC,5
     ;movlb 1
     movlw 0xF0 ; 32 MHz
     movwf OSCCON
     btfss OSCSTAT,6
     goto $-1
    1825k22 ini

    Code:
    ; optional path information - default output folder is 
    ; user documents -> umcbuild... 
    [PATH] 
    Output=C:\MYBOOTLOADER
    ; source code files... 
    [TEMPLATE] 
    PIC16=..\src\16F\umc_loader.asm 
    PIC18=..\src\18F\umc_loader.asm 
    [USART] BAUDRATE=19200 BRGH=1 BRG16=1 
    ; device name and OSC... 
    [MCU] 
    Device=18F25K22 
    OSC=64000000 
    ; device configuration settings... 
    [CONFIG] 
    config FOSC = INTIO67
    config PLLCFG = OFF
    config PRICLKEN = ON ; Primary clock Enabled 
    config FCMEN = OFF ; Fail-Safe Clock Disabled 
    config IESO = OFF ; Oscillator Switchover Disabled 
    config PWRTEN = ON ; Powerup Timer Enabled 
    config HFOFST = OFF ; HFINTOSC delayed until oscillator stable 
    config BOREN = ON ; Brown Out Detector Enabled 
    config BORV = 250 ; VBOR set to 2.50 V nominal 
    config WDTEN = OFF ; WDT Enabled; SWDTEN bit has no effect 
    config WDTPS = 512 ; WDT = 1:512 = 2048 ms 
    config CCP2MX = PORTB3 ; CCP2 i/o is multiplexed with RB3 (not RC1) 
    config CCP3MX = PORTB5 ; P3A/CCP3 i/o is multiplexed with RB5 (not RC6) 
    config T3CMX = PORTB5 ; T3CKI is on RB5 (not RC0) 
    config P2BMX = PORTC0 ; ECCP2 P2B is on RC0 (not RB5) 
    config PBADEN = OFF ; PORTB<5:0> pins configured as digital i/o (not analog) 
    config MCLRE = EXTMCLR 
    config STVREN = ON ; Stack Overflow Reset Enabled 
    config XINST = OFF ; Extended Instructions Disabled 
    config LVP = OFF ; Low-Voltage-Programming Disabled 
    config CP0 = OFF ;Code Protect 00800-03FFF 
    config CP1 = OFF ;Code Protect 04000-07FFF 
    config CP2 = OFF ;Code Protect 08000-0BFFF 
    config CP3 = OFF ;Code Protect 0C000-0FFFF 
    config CPB = OFF ;Code Protect Boot 
    config CPD = OFF ;Data EE Read Protect 
    config WRT0 = OFF ;Table Write Protect 00800-03FFF 
    config WRT1 = OFF ;Table Write Protect 04000-07FFF 
    config WRT2 = OFF ;Table Write Protect 08000-0BFFF 
    config WRT3 = OFF ;Table Write Protect 0C000-0FFFF 
    config WRTC = OFF ;Config. Write Protect 
    config WRTB = OFF ;Table Write Protect Boot 
    config WRTD = OFF ;Data EE Write Protect 
    config EBTR0 = OFF ;Table Read Protect 00800-03FFF 
    config EBTR1 = OFF ;Table Read Protect 04000-07FFF 
    config EBTR2 = OFF ;Table Read Protect 08000-0BFFF 
    config EBTR3 = OFF ;Table Read Protect 0C000-0FFFF 
    config EBTRB = OFF ;Table Read Protect Boot 
    ; place startup code in here... 
    [USERCODE] 
    movlb 0x0F ; MANDATORY: BSR set to SFR bank 
    movlw b'00000000' 
    movwf ANSELC ; MANDATORY: analog off on port C 
    movlw 0x70 
    movwf OSCCON
    bsf   OSCTUNE,6
    BTFSS OSCCON2,7
    BRA $-2
    Last edited by richard; - 14th April 2017 at 13:49.
    This is more entertaining than Free to Air TV

  15. #15
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    Thanks guys!

    Are you both using MPLABX/MPASMX or do you also have an older version of MPLAB installed? I thought I'd try to bloat this new computer down with all sort of software but that seems impossible to avoid. Microsoft won't properly support Win7 on new generation CPU(s), the Amicus loader doesn't work on Win10, the UMC loader doesn't work with MPLABX....it just never ends :-(

    I'm trying to build a bootloader .hex for the 18F452 - which is what the default .ini file is configured to do. As far as I can see it's one of the default devices but I may be wrong. I thought I'd get that going first before trying to configure it for other chips.

  16. #16
    Join Date
    Aug 2011
    Posts
    93

    Default Re: Amicus 18 FTDI driver on W10?

    I've never tried building the bootloader using mplabx, and I only have the UMC stuff from swordfish and proton so take this with a grain of salt...

    Some of the [PATH] options in the umc.ini file specify the MPASM and DB paths. You can fool it to use mpasmx.exe as the assembler, but if umcbuild is looking for the old *.dev files from MPLAB you might be SOL trying to use mplabx.

    On my system I have
    Code:
    DB=d:\program files\microchip\mplab IDE\device
    which is where the old mplab *.dev files were/are located on my setup. MPLABX doesn't have these files anymore, or if it does they're buried deep inside some .jar file that I've never found.

    You might just be forced to install MPLAB.
    Last edited by tumbleweed; - 14th April 2017 at 16:17.

  17. #17
    Join Date
    May 2013
    Location
    australia
    Posts
    1,181

    Default Re: Amicus 18 FTDI driver on W10?

    Are you both using MPLABX/MPASMX or do you also have an older version of MPLAB installed?
    I have mplab and mplabx installed on win10 , its the only way I could make it work
    This is more entertaining than Free to Air TV

  18. #18
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,129

    Default Re: Amicus 18 FTDI driver on W10?

    Thank you guys,
    Installed MPLAB 8.92 and I'm now able to build the default bootloader file for the 18F452 - that's progress. Next I'll look at adding a device of my own.
    I wonder if there are any plans to switch the UMC stuff to MPASMX as no new devices (like the 26K40) are available for the old assembler (I think I know the answer to that....)

    I guess it should be possible to "manually" build the bootloader files using MPLABX instead of the UMC builder application. But, one step at a time.

    /Henrik.

Similar Threads

  1. Amicus shields
    By Bruce in forum PBP & Amicus18
    Replies: 33
    Last Post: - 30th July 2011, 22:06
  2. AMICUS 18 Section
    By charudatt in forum Forum Requests
    Replies: 26
    Last Post: - 17th July 2011, 10:03
  3. Amicus Name
    By Charles Linquis in forum PBP & Amicus18
    Replies: 12
    Last Post: - 31st May 2011, 05:01
  4. Amicus 18 Review
    By lester in forum General
    Replies: 0
    Last Post: - 10th June 2010, 07:58

Members who have read this thread : 17

You do not have permission to view the list of names.

Posting Permissions

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