Amicus 18 FTDI driver on W10?


Closed Thread
Results 1 to 23 of 23

Hybrid View

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

    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

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

    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.

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

    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.

  4. #4
    Join Date
    Aug 2011
    Posts
    453

    Default Re: Amicus 18 FTDI driver on W10?

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

  5. #5
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,612

    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.

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

    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

  7. #7
    Join Date
    May 2013
    Location
    australia
    Posts
    2,640

    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.
    Warning I'm not a teacher

  8. #8
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,612

    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.

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 : 1

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