• AVR Freaks

Hot!Compilation fthat works last december doesn't anymore

Author
edube
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2019/07/23 11:12:04
  • Location: 0
  • Status: offline
2020/05/19 19:55:52 (permalink)
0

Compilation fthat works last december doesn't anymore

I can't longer compile code with HITECH V9.66; it worked in last decembre; and now it does not work. here are errors:
 
 
make -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
make[1]: Entering directory 'C:/Users/Proprietaire/Documents/MPLab/test.X'
make -f nbproject/Makefile-default.mk dist/default/production/test.X.production.hex
make[2]: Entering directory 'C:/Users/Proprietaire/Documents/MPLab/test.X'
"C:\Program Files (x86)\HI-TECH Software\PICC-18\PRO\9.66\bin\picc18.exe" --pass1 main.c -q --chip=18F4520 -P --outdir="build/default/production" -P -N255 --warn=0 --runtime=default,+clear,+init,-keep,-download,+stackwarn,+config,+clib,-plib --opt=default,+asm,+asmfile,-speed,+space --cp=16 -Blarge --double=24 --mode=pro -g --asmlist "--errformat=%f:%l: error: (%n) %s" "--warnformat=%f:%l: warning: (%n) %s" "--msgformat=%f:%l: advisory: (%n) %s" 
"C:\Program Files (x86)\HI-TECH Software\PICC-18\PRO\9.66\bin\picc18.exe" -odist/default/production/test.X.production.cof -mdist/default/production/test.X.production.map --summary=default,-psect,-class,+mem,-hex --chip=18F4520 -P --runtime=default,+clear,+init,-keep,-download,+stackwarn,+config,+clib,-plib --opt=default,+asm,+asmfile,-speed,+space -P -N255 --warn=0 --cp=16 -Blarge --double=24 --mode=pro --output=default,-inhx032 -g --asmlist "--errformat=%f:%l: error: (%n) %s" "--warnformat=%f:%l: warning: (%n) %s" "--msgformat=%f:%l: advisory: (%n) %s" build/default/production/main.p1 
HI-TECH C PRO for the PIC18 MCU Family (Lite) V9.66
Copyright (C) 1984-2011 HI-TECH SOFTWARE
(1273) Omniscient Code Generation not available in Lite mode (warning)
:: advisory: (1233) Employing 18F4520 errata work-arounds:
:: advisory: (1234) * Corrupted fast interrupt shadow registers
make[2]: *** [dist/default/production/test.X.production.hex] Error 1
make[1]: *** [.build-conf] Error 2
make: *** [.build-impl] Error 2
:0: error: (593) can't find 0x15A words (0x15a withtotal) for psect "text24" in segment "CODE"
:0: error: (593) can't find 0x11E words (0x11e withtotal) for psect "text12" in segment "CODE"
:0: error: (593) can't find 0x112 words (0x112 withtotal) for psect "text18" in segment "CODE"
:0: error: (593) can't find 0xD0 words (0xd0 withtotal) for psect "text29" in segment "CODE"
:0: error: (593) can't find 0xCC words (0xcc withtotal) for psect "text26" in segment "CODE"
:0: error: (593) can't find 0xB0 words (0xb0 withtotal) for psect "text27" in segment "CODE"
:0: error: (593) can't find 0xAA words (0xaa withtotal) for psect "text15" in segment "CODE"
:0: error: (593) can't find 0xA6 words (0xa6 withtotal) for psect "text6" in segment "CODE"
:0: error: (593) can't find 0x94 words (0x94 withtotal) for psect "text10" in segment "CODE"
:0: error: (593) can't find 0x92 words (0x92 withtotal) for psect "text2" in segment "CODE"
:0: error: (593) can't find 0x7E words (0x7e withtotal) for psect "text14" in segment "CODE"
:0: error: (593) can't find 0x74 words (0x74 withtotal) for psect "text28" in segment "CODE"
:0: error: (593) can't find 0x66 words (0x66 withtotal) for psect "text11" in segment "CODE"
:0: error: (593) can't find 0x54 words (0x54 withtotal) for psect "text19" in segment "CODE"
:0: error: (593) can't find 0x50 words (0x50 withtotal) for psect "text8" in segment "CODE"
:0: error: (593) can't find 0x3A words (0x3a withtotal) for psect "text7" in segment "CODE"
:0: error: (593) can't find 0x2C words (0x2c withtotal) for psect "text5" in segment "CODE"
:0: error: (593) can't find 0x28 words (0x28 withtotal) for psect "text20" in segment "CODE"
:0: error: (593) can't find 0x24 words (0x24 withtotal) for psect "text22" in segment "CODE"
:0: error: (593) can't find 0x12 words (0x12 withtotal) for psect "text23" in segment "CODE"
nbproject/Makefile-default.mk:130: recipe for target 'dist/default/production/test.X.production.hex' failed
make[2]: Leaving directory 'C:/Users/Proprietaire/Documents/MPLab/test.X'
nbproject/Makefile-default.mk:90: recipe for target '.build-conf' failed
make[1]: Leaving directory 'C:/Users/Proprietaire/Documents/MPLab/test.X'
nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
BUILD FAILED (exit value 2, total time: 2s)
 
Please help.
 
 
#1

11 Replies Related Threads

    NKurzman
    A Guy on the Net
    • Total Posts : 18860
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: Compilation fthat works last december doesn't anymore 2020/05/20 08:13:39 (permalink)
    +1 (1)
    (1273) Omniscient Code Generation not available in Lite mode (warning)
    Were you using Pro or Lite in December? On the same computer?
    If you were using Eval, Then it expired.
    If you have a License, then check the Optimization level it should be on PRO.
     
    #2
    jtemples
    عُضْوٌ جَدِيد
    • Total Posts : 11937
    • Reward points : 0
    • Joined: 2004/02/13 12:31:19
    • Location: Southern California
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/20 09:27:29 (permalink)
    +2 (2)
    Licensing/registration no longer works in Windows 10.  It does work in Linux.
    #3
    ric
    Super Member
    • Total Posts : 28026
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: online
    Re: Compilation fthat works last december doesn't anymore 2020/05/20 13:26:21 (permalink)
    +1 (1)
    If you're only using free mode, why not use XC8?
    Even the latest version is very compatible with HiTech code (when XC8 is in C90 mode).
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #4
    edube
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2019/07/23 11:12:04
    • Location: 0
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/21 07:23:50 (permalink)
    +1 (1)
    I use the PRO version it is configure in PRO mode; I changed nothing there.
     
    Licensing/registration no longer works in Windows 10.  It does work in Linux.
    Does that mean it is Windows 10 that makes it does not work????
     
    Thanks all,
     
    Eric
    #5
    edube
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2019/07/23 11:12:04
    • Location: 0
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/21 07:26:56 (permalink)
    0
    ric
    If you're only using free mode, why not use XC8?
    Even the latest version is very compatible with HiTech code (when XC8 is in C90 mode).
     




    I tried XC8; first, it does not compile strait foward. There is many errors. The eeprom_read and write don't compile. They say to try with MCC; I did and the PIC I use is not supported with MCC; So it is a mess a very big mess to migrate to XC8 for this particular project.
     
    post edited by edube - 2020/05/21 07:31:00
    #6
    mbrowning
    USNA79
    • Total Posts : 1791
    • Reward points : 0
    • Joined: 2005/03/16 14:32:56
    • Location: Melbourne, FL
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/21 07:43:15 (permalink)
    +2 (2)
    edube
    I tried XC8; first, it does not compile strait foward. There is many errors. The eeprom_read and write don't compile. They say to try with MCC; I did and the PIC I use is not supported with MCC; So it is a mess a very big mess to migrate to XC8 for this particular project.

    A bigger mess than dealing with ancient licensing?
    Did you set XC8 to C90 mode? Versions 2.xx default to C99 mode which will generate errors on older code.
    I say don't bother with MCC for most things. It's better to read the datasheet, errata, and appnotes.
    I believe that eeprom functions are included in XC8 for PIC16, but I've never used them and don't know if they differ from HTC.
    Newer version of XC8 (after 2.05 I think) allow 2 levels of optimization for free, which may be enough to match PRO mode for you.
    #7
    edube
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2019/07/23 11:12:04
    • Location: 0
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/21 07:55:06 (permalink)
    0
    mbrowning
    edube
    I tried XC8; first, it does not compile strait foward. There is many errors. The eeprom_read and write don't compile. They say to try with MCC; I did and the PIC I use is not supported with MCC; So it is a mess a very big mess to migrate to XC8 for this particular project.

    A bigger mess than dealing with ancient licensing?
    Did you set XC8 to C90 mode? Versions 2.xx default to C99 mode which will generate errors on older code.
    I say don't bother with MCC for most things. It's better to read the datasheet, errata, and appnotes.
    I believe that eeprom functions are included in XC8 for PIC16, but I've never used them and don't know if they differ from HTC.
    Newer version of XC8 (after 2.05 I think) allow 2 levels of optimization for free, which may be enough to match PRO mode for you.


    Ok first I will update the XC8; I have now the V1.41. and let you know.
     
    Thanks
     
    Eric.
    #8
    NKurzman
    A Guy on the Net
    • Total Posts : 18860
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: Compilation fthat works last december doesn't anymore 2020/05/21 08:15:34 (permalink)
    0
    So you updated to a Windows 10 PC?
    Going to XC8 will Not solve your Problem, unless you either license it , or use the Evaluation.
    #9
    rpg7
    Super Member
    • Total Posts : 1405
    • Reward points : 0
    • Joined: 2003/11/07 12:47:35
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/21 08:22:13 (permalink)
    0
    I'm running my hitech compilers in an XP vm hosted on Win10. Also wouldn't work in native win10.
    edit: (Oracle VM Virtual Box)
    post edited by rpg7 - 2020/05/21 08:25:03
    #10
    jtemples
    عُضْوٌ جَدِيد
    • Total Posts : 11937
    • Reward points : 0
    • Joined: 2004/02/13 12:31:19
    • Location: Southern California
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/21 12:50:43 (permalink)
    +1 (1)
    The eeprom_read and write don't compile.


    The source code for those functions is included with the compiler.  You should be able to copy those into your XC8 project without changing your source code.
    #11
    edube
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2019/07/23 11:12:04
    • Location: 0
    • Status: offline
    Re: Compilation fthat works last december doesn't anymore 2020/05/22 07:58:38 (permalink)
    0
    I taking out my old portable computer; all still working on it. So I'm resigned to still using this old computer for this project.
     
    #12
    Jump to:
    © 2020 APG vNext Commercial Version 4.5