• AVR Freaks

Hot!XC8 v2.10: error: 141 can't open chip info file [SOLVED]

Page: 123 > Showing page 1 of 3
Author
GlennP
Super Member
  • Total Posts : 858
  • Reward points : 0
  • Joined: 2009/03/29 15:04:55
  • Location: El Paso County, CO, USA
  • Status: offline
2020/04/24 22:16:06 (permalink)
0

XC8 v2.10: error: 141 can't open chip info file [SOLVED]

XC8 v2.10 (1st try): error: (141) can't open chip info file "(null)"

See this post for the partial resolution: https://www.microchip.com/forums/FindPost/1137660

I'm attempting to use the XC8 assembler for the first time and have hit this wall.  I'm sure this is a cockpit error but I just don't know what I did / am doing wrong.  Complete build output is below along with a listing of the location of the files I believe should be used, but the short version is:

This is my first serious attempt to use the XC8 assembler and I'm on MpLabX v5.35.  I installed XC8 v2.10 (free) just to get the assembler as the mpasmx seems to be losing support.  [I have no other reason to move.]

I've done the usual dance: XC8 (install, remove, re-install), try MpLabX 5.30, ... - all to no avail.

I've read https://www.microchip.com/forums/m1060549.aspx and https://www.microchip.com/forums/m1058617.aspx and tried the C99 -> C90 -> C99 technique with no success.  I am using xc8-cc as can be seen in the build output.

For a while, there were preprocessor errors due to my use of possessives in comments (such as "; Check Library's contents").  Processing of comments for quote balance seems strange, but whatever.  But that implied I was at least using the xc8-cc.  It was only after I fixed those issues that the compiler/assembler decided the "chip info file" is an issue.

Any suggestions would be welcome.  Thanks.

GlennP

Here is the output of the make attempt and what might be a relevant directory list looking for info files for the PIC16LF1776:

BUILD (note - Trigger Expressions removed or modified):

CLEAN SUCCESSFUL (total time: 59ms)
make -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
make[1]: Entering directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'
"--------------------------------------"
"User defined pre-build step: ["C:\Program Files\Trailing Edge Technology\MicrochipSupport\TimeStamp" >BuildTimeStamp.inc]"
"--------------------------------------"
make -f nbproject/Makefile-default.mk dist/default/production/StarterBooster.X.production.hex
make[2]: Entering directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'
"D:\Program Files (x86)\Microchip\xc8\v2.10\bin\xc8-cc" -c -mcpu=16LF1776 -LOTSOFOPTIONSREMOVED -o build/default/production/StarterBooster.o StarterBooster.asm
make[2]: *** [nbproject/Makefile-default.mk:134: build/default/production/StarterBooster.o] Error 1
make[1]: *** [nbproject/Makefile-default.mk:105: .build-conf] Error 2
make: *** [nbproject/Makefile-impl.mk:39: .build-impl] Error 2
2:1:: error: (876) syntax error
2:3:: error: (141) can't open chip info file "(null)": Invalid argument
(908) exit status = 1
make[2]: Leaving directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'
make[1]: Leaving directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'

BUILD FAILED (exit value 2, total time: 1s)

 

DIRECTORIES:
D:\Program Files (x86)\Microchip\xc8\v2.10>dir /s 16lf1776*.*

 Directory of D:\Program Files (x86)\Microchip\xc8\v2.10\docs\chips
07/31/2019 01:14 AM 13,789 16lf1776. h t m l
               1 File(s) 13,789 bytes

 Directory of D:\Program Files (x86)\Microchip\xc8\v2.10\mpasmx\LKR
07/30/2019 06:15 PM 7,360 16lf1776_g.l k r
               1 File(s) 7,360 bytes

 Directory of D:\Program Files (x86)\Microchip\xc8\v2.10\pic\dat\cfgdata
07/31/2019 01:14 AM 6,679 16lf1776.cfg data
               1 File(s) 6,679 bytes

 Directory of D:\Program Files (x86)\Microchip\xc8\v2.10\pic\dat\cfgmap
07/31/2019 01:14 AM 2,700 16lf1776.cfg map
               1 File(s) 2,700 bytes

 Directory of D:\Program Files (x86)\Microchip\xc8\v2.10\pic\dat\ini
07/31/2019 01:14 AM 99,691 16lf1776.i n i
               1 File(s) 99,691 bytes

post edited by GlennP - 2020/04/28 14:49:02
#1

43 Replies Related Threads

    jtemples
    عُضْوٌ جَدِيد
    • Total Posts : 12032
    • Reward points : 0
    • Joined: 2004/02/13 12:31:19
    • Location: Southern California
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/24 23:54:27 (permalink)
    0 (2)
    Try installing the compiler in the default directory.
    #2
    GlennP
    Super Member
    • Total Posts : 858
    • Reward points : 0
    • Joined: 2009/03/29 15:04:55
    • Location: El Paso County, CO, USA
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 01:02:26 (permalink)
    0
    Good idea, but no difference.
     
    Here's the full make output.  I had modified the earlier one in a fight to avoid "Access Denied".
     
    make -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
    make[1]: Entering directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'
    "--------------------------------------"
    "User defined pre-build step: ["C:\Program Files\Trailing Edge Technology\MicrochipSupport\TimeStamp" >BuildTimeStamp.inc]"
    "--------------------------------------"
    make -f nbproject/Makefile-default.mk dist/default/production/StarterBooster.X.production.hex
    make[2]: Entering directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'
    "C:\Program Files (x86)\Microchip\xc8\v2.10\bin\xc8-cc.exe" -c -mcpu=16LF1776 -fno-short-double -fno-short-float -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-3 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-osccal -mno-resetbits -mno-save-resetbits -mno-download -mno-stackcall -std=c99 -gdwarf-3 -mstack=compiled:auto:auto -o build/default/production/StarterBooster.o StarterBooster.asm
    make[2]: *** [nbproject/Makefile-default.mk:134: build/default/production/StarterBooster.o] Error 1
    make[1]: *** [nbproject/Makefile-default.mk:105: .build-conf] Error 2
    make: *** [nbproject/Makefile-impl.mk:39: .build-impl] Error 2
    2:1:: error: (876) syntax error
    2:3:: error: (141) can't open chip info file "(null)": Invalid argument
    (908) exit status = 1
    make[2]: Leaving directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'
    make[1]: Leaving directory 'C:/Users/Glenn/Documents/MPLabProjects/StarterBooster.X'

    BUILD FAILED (exit value 2, total time: 972ms)

    #3
    Jim Nickerson
    User 452
    • Total Posts : 6912
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 06:04:35 (permalink)
    0
    what happens if you disable the user pre build step ?
    #4
    NorthGuy
    Super Member
    • Total Posts : 6525
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 06:12:20 (permalink)
    0
    I had a similar error with PIC18F25K43 (mine said "bad address" instead of "invalid argument"). Turned out, it is not supported by XC8 at all. I ended up selecting PIC18F27K43 and restricting memory area.
     
    On the same note, try if you can get away with PIC16F1776 instead of PIC16LF1776.
    post edited by NorthGuy - 2020/04/25 06:13:56
    #5
    GlennP
    Super Member
    • Total Posts : 858
    • Reward points : 0
    • Joined: 2009/03/29 15:04:55
    • Location: El Paso County, CO, USA
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 07:13:26 (permalink)
    0
    I tried the plain F, same result.
     
    There seems to be a support file - I showed a search in the OP.  Since the filename seems to be (null), I think the issue is more fundamental.
     
    I will try this evening (it's ~8a here now) with a simpler file with other chips and see if any work.  I did try a P16LF18855 - same result.  I'm tending to think it's something universally wrong.
     
    Thanks,
    GlennP
    #6
    GlennP
    Super Member
    • Total Posts : 858
    • Reward points : 0
    • Joined: 2009/03/29 15:04:55
    • Location: El Paso County, CO, USA
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 07:19:36 (permalink)
    +1 (1)
    JANickerson
    what happens if you disable the user pre build step ?


    The prebuild doesn't run and output gets shorter by three lines, but the error is the same.
    #7
    du00000001
    Just Some Member
    • Total Posts : 4119
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 07:24:45 (permalink)
    0
    I can't see an .h nor an .inc file in the dir /s list  :(
    What might be worth trying: the last XC8 1.xx version.
    post edited by du00000001 - 2020/04/25 09:27:29

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #8
    Jerry Messina
    Super Member
    • Total Posts : 668
    • Reward points : 0
    • Joined: 2003/11/07 12:35:12
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 07:37:14 (permalink)
    0
    After reading through the XC8 asm users guide and the MPASM to XC8 migration guide you'll begin to wonder
    what idiot thought that getting rid of MPASM was a good idea.

    http://ww1.microchip.com/...0Guide%2050002974A.pdf
    http://ww1.microchip.com/...0Guide%2050002973A.pdf


    #9
    GlennP
    Super Member
    • Total Posts : 858
    • Reward points : 0
    • Joined: 2009/03/29 15:04:55
    • Location: El Paso County, CO, USA
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 13:41:08 (permalink)
    0
    du00000001
    I can't see an .h nor an .inc file in the dir /s list  :(
    What might be worth trying: the last XC8 1.xx version.



    I think that's because the .inc and .h files start with pic.  Here's a more inclusive listing (see "dir" command, first line) and note the last three files listed:
     
    C:\Program Files (x86)\Microchip\xc8>dir /s *16lf1776*.*
     Volume in drive C ...
     Volume Serial Number is ...

     Directory of C:\Program Files (x86)\Microchip\xc8\v2.10\docs\chips

    07/31/2019 01:14 AM 13,789 16lf1776.html
                   1 File(s) 13,789 bytes

     Directory of C:\Program Files (x86)\Microchip\xc8\v2.10\mpasmx

    07/30/2019 06:15 PM 188,358 p16lf1776.inc
                   1 File(s) 188,358 bytes

     Directory of C:\Program Files (x86)\Microchip\xc8\v2.10\mpasmx\LKR

    07/30/2019 06:15 PM 7,360 16lf1776_g.lkr
                   1 File(s) 7,360 bytes

     Directory of C:\Program Files (x86)\Microchip\xc8\v2.10\pic\dat\cfgdata

    07/31/2019 01:14 AM 6,679 16lf1776.cfgdata
                   1 File(s) 6,679 bytes

     Directory of C:\Program Files (x86)\Microchip\xc8\v2.10\pic\dat\cfgmap

    07/31/2019 01:14 AM 2,700 16lf1776.cfgmap
                   1 File(s) 2,700 bytes

     Directory of C:\Program Files (x86)\Microchip\xc8\v2.10\pic\dat\ini

    07/31/2019 01:14 AM 99,691 16lf1776.ini
                   1 File(s) 99,691 bytes

     Directory of C:\Program Files (x86)\Microchip\xc8\v2.10\pic\include

    07/31/2019 01:14 AM 1,959 16lf1776.cgen.inc
    07/31/2019 01:14 AM 1,800 as16lf1776.h
    07/31/2019 01:14 AM 2,417,398 pic16lf1776.h
    07/31/2019 01:14 AM 1,295,628 pic16lf1776.inc
                   4 File(s) 3,716,785 bytes

         Total Files Listed:
                  10 File(s) 4,035,362 bytes
                   0 Dir(s) 186,209,939,456 bytes free

    C:\Program Files (x86)\Microchip\xc8>

     
    I'll try an earlier xc8 later tonight.
     
    GP
    post edited by GlennP - 2020/04/25 13:43:23
    #10
    mlp
    boots too small
    • Total Posts : 1005
    • Reward points : 0
    • Joined: 2012/09/10 15:12:07
    • Location: previously Microchip XC8 team
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 14:00:29 (permalink)
    +1 (3)
    Jerry Messina
    you'll begin to wonder what idiot thought that getting rid of MPASM was a good idea.

    That would be the maybe-not-an-idiot who had to deal with the aftermath of an earlier good idea: get rid of, or fail to replace, the staff who wrote/supported MPASM (written in a PC-specific Pascal dialect), and hand responsibility for that fustercluck to the XC8 team (highly skilled in platform-independent C).

    Mark (this opinion available for hire)
    #11
    GlennP
    Super Member
    • Total Posts : 858
    • Reward points : 0
    • Joined: 2009/03/29 15:04:55
    • Location: El Paso County, CO, USA
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 14:06:17 (permalink)
    +1 (1)
    No comment.
    post edited by GlennP - 2020/04/25 14:07:24
    #12
    jtemples
    عُضْوٌ جَدِيد
    • Total Posts : 12032
    • Reward points : 0
    • Joined: 2004/02/13 12:31:19
    • Location: Southern California
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 14:24:23 (permalink)
    0
    written in a PC-specific Pascal dialect

     
    Seemed like a good idea at the time?
    #13
    NorthGuy
    Super Member
    • Total Posts : 6525
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/25 15:06:36 (permalink)
    0
    mark.pappin
    That would be the maybe-not-an-idiot who had to deal with the aftermath of an earlier good idea: get rid of, or fail to replace, the staff who wrote/supported MPASM (written in a PC-specific Pascal dialect), and hand responsibility for that fustercluck to the XC8 team (highly skilled in platform-independent C).



    So it's been written in Delphi originally and they re-wrote it in C? But this should make porting to 64-bit easier.
    #14
    Jerry Messina
    Super Member
    • Total Posts : 668
    • Reward points : 0
    • Joined: 2003/11/07 12:35:12
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/26 06:07:54 (permalink)
    +2 (2)
    I know this is marketing hype, but
    Delphi is the fastest way to write, compile, package and deploy cross-platform native applications on Windows, macOS, iOS, Android and Linux

     
    I'm sure MPASM is ancient, and I'm not trashing the skills of the XC8 team, but before replacing an existing tool with a new one that requires the user to completely review/rewrite their code line by line using a new syntax (if possible since there are many "No equivalent" statements in that porting guide), I think a lot more consideration should have been given for what effect this would have on the customer and not for the poor support staff saying "gee, this is too hard".
     
    If I did that to my customers they would be (rightly) teed off. I would expect many of them not to return.
     
    #15
    mad_c
    Super Member
    • Total Posts : 1289
    • Reward points : 0
    • Joined: 2010/12/12 17:48:27
    • Location: Brisbane, Australia
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/26 22:44:20 (permalink)
    +1 (1)
    Hi,
     
    I'm not certain what is going on here, but I would rename the source files to use the .s or .S extension, and check what is causing the syntax error produced first. Does the source file need preprocessing?
     
    And just a heads up: look out for the 2.20 release, which is due out Real Soon Now*. It has a few 'new things' for those of you wanting to use XC8 for assembly-only projects. I'd say more, but I'd hate to be the one to spoil everyone's surprise.
     
    Jeff.
    #16
    ric
    Super Member
    • Total Posts : 29944
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: online
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/26 22:50:14 (permalink)
    +1 (1)
    mad_c
     I'd say more, but I'd hate to be the one to spoil everyone's surprise.
     
    Jeff.

    Tease!

    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!
    #17
    GlennP
    Super Member
    • Total Posts : 858
    • Reward points : 0
    • Joined: 2009/03/29 15:04:55
    • Location: El Paso County, CO, USA
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/27 04:10:28 (permalink)
    0
    Renaming the source file had no significant effect.  It did, of course, change the invocation line but nothing else - same syntax error and same missing info file.
     
    I think there is a clue in that xc8-cc seems to have a "(null)" name for the info file.  But my secret decoder ring is missing.
     
    I'd love to fix the syntax error but have no idea what is causing it.  Can you offer any hints?  Is the clue somewhere in the invocation line?  Here's the output:
     
    "C:\Program Files (x86)\Microchip\xc8\v2.10\bin\xc8-cc.exe" -c -mcpu=16LF1776 -fno-short-double -fno-short-float -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-3 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-osccal -mno-resetbits -mno-save-resetbits -mno-download -mno-stackcall -std=c99 -gdwarf-3 -mstack=compiled:auto:auto -o build/default/production/StarterBooster.o StarterBooster.s 
    2:1:: error: (876) syntax error
    2:3:: error: (141) can't open chip info file "(null)": Invalid argument
    (908) exit status = 1

     
    I'll try 2.20 when it comes out, but if it doesn't at least try to assemble the source then I'm giving up on XC8's assemblers and will stay in the MPASMX world or go elsewhere for MCUs.
    #18
    ric
    Super Member
    • Total Posts : 29944
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: online
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/27 04:17:30 (permalink)
    0
    Can you hang on for the 2.20 release?
    If you hadn't noticed, mad_c is one of the XC8 authors, and he is heavily hinting at some major changes in a version about to come out...
     

    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!
    #19
    du00000001
    Just Some Member
    • Total Posts : 4119
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: XC8 v2.10: error: 141 can't open chip info file 2020/04/27 04:33:57 (permalink)
    0
    glennp17321
    Renaming the source file had no significant effect.  It did, of course, change the invocation line but nothing else - same syntax error and same missing info file.
     
    I think there is a clue in that xc8-cc seems to have a "(null)" name for the info file.  But my secret decoder ring is missing.
     
    I'd love to fix the syntax error but have no idea what is causing it.  Can you offer any hints?  Is the clue somewhere in the invocation line?  Here's the output:
     
    "C:\Program Files (x86)\Microchip\xc8\v2.10\bin\xc8-cc.exe" -c -mcpu=16LF1776 -fno-short-double -fno-short-float -O0 -fasmfile -maddrqual=ignore -xassembler-with-cpp -mwarn=-3 -Wa,-a -DXPRJ_default=default -msummary=-psect,-class,+mem,-hex,-file -ginhx032 -Wl,--data-init -mno-keep-startup -mno-osccal -mno-resetbits -mno-save-resetbits -mno-download -mno-stackcall -std=c99 -gdwarf-3 -mstack=compiled:auto:auto -o build/default/production/StarterBooster.o StarterBooster.s 
    2:1:: error: (876) syntax error
    2:3:: error: (141) can't open chip info file "(null)": Invalid argument
    (908) exit status = 1

     
    I'll try 2.20 when it comes out, but if it doesn't at least try to assemble the source then I'm giving up on XC8's assemblers and will stay in the MPASMX world or go elsewhere for MCUs.

     
    Dug a bit in the net: according to some other source, the chip info file should translate to
    C:\Program Files (x86)\Microchip\xc8\v2.10\pic\dat\ini\16LF1776.ini
     
    Have you already tried to open this file with some editor ?

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #20
    Page: 123 > Showing page 1 of 3
    Jump to:
    © 2021 APG vNext Commercial Version 4.5