• AVR Freaks

Hot!(902) no chip name specified; use "PICC --CHIPINFO" to see available chip names

Author
orchardaudio
New Member
  • Total Posts : 14
  • Reward points : 0
  • Joined: 2018/03/07 07:46:31
  • Location: 0
  • Status: offline
2018/07/20 13:00:27 (permalink)
0

(902) no chip name specified; use "PICC --CHIPINFO" to see available chip names

Hello,
 
I upgraded to MPlab X 5.00, and when I opened my 4.XX project it asked to upgrade. Now the project will not compile in the new version.
 
I keep getting the following error:
(902) no chip name specified; use "PICC --CHIPINFO" to see available chip names
 
Thanks for your help.
#1

10 Replies Related Threads

    qɥb
    Monolothic Member
    • Total Posts : 3332
    • Reward points : 0
    • Joined: 2017/09/09 05:07:30
    • Location: Jupiter
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/07/20 14:48:27 (permalink)
    +1 (1)
    Which compiler are you using?
    (Type and version)
    That error message has been asked about before, and it was to do with changes from XC8 1.xx to 2.00
     

    This forum is mis-configured so it only works correctly if you access it via https protocol.
    The Microchip website links to it using http protocol. Will they ever catch on?
    PicForum "it just works"
    #2
    orchardaudio
    New Member
    • Total Posts : 14
    • Reward points : 0
    • Joined: 2018/03/07 07:46:31
    • Location: 0
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/07/20 14:57:19 (permalink)
    0
    With mplabx 4.15 was using XC8 1.45, and now using XC8 2.00
    #3
    qɥb
    Monolothic Member
    • Total Posts : 3332
    • Reward points : 0
    • Joined: 2017/09/09 05:07:30
    • Location: Jupiter
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/07/20 14:59:04 (permalink)
    +1 (1)
    Please show the actual lines from your build log where the compiler was run and produced that error.
     

    This forum is mis-configured so it only works correctly if you access it via https protocol.
    The Microchip website links to it using http protocol. Will they ever catch on?
    PicForum "it just works"
    #4
    orchardaudio
    New Member
    • Total Posts : 14
    • Reward points : 0
    • Joined: 2018/03/07 07:46:31
    • Location: 0
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/07/20 15:23:08 (permalink)
    0
    qɥb
    Please show the actual lines from your build log where the compiler was run and produced that error.




    Is this what you are looking for?
     
    CLEAN SUCCESSFUL (total time: 15ms)
    make -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
    make[1]: Entering directory 'E:/Documents/MPLABXProjects/Volume-Clocker.X'
    make -f nbproject/Makefile-default.mk dist/default/production/Volume-Clocker.X.production.hex
    make[2]: Entering directory 'E:/Documents/MPLABXProjects/Volume-Clocker.X'
    (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names
    (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names
    "D:\Applications\MP-LAB\xc8\pic\bin\xc8.exe" -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/adc.p1 mcc_generated_files/adc.c 
    (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names
    "D:\Applications\MP-LAB\xc8\pic\bin\xc8.exe" -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/mcc.p1 mcc_generated_files/mcc.c 
    "D:\Applications\MP-LAB\xc8\pic\bin\xc8.exe" -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/spi1.p1 mcc_generated_files/spi1.c 
    "D:\Applications\MP-LAB\xc8\pic\bin\xc8.exe" -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/pin_manager.p1 mcc_generated_files/pin_manager.c 
    D:\Applications\MP-LAB\xc8\pic\bin\picc -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/adc.p1 mcc_generated_files/adc.c
    D:\Applications\MP-LAB\xc8\pic\bin\picc -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/mcc.p1 mcc_generated_files/mcc.c
    "D:\Applications\MP-LAB\xc8\pic\bin\xc8.exe" -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/main.p1 main.c 
    D:\Applications\MP-LAB\xc8\pic\bin\picc -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/spi1.p1 mcc_generated_files/spi1.c
    D:\Applications\MP-LAB\xc8\pic\bin\picc -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/mcc_generated_files/pin_manager.p1 mcc_generated_files/pin_manager.c
    D:\Applications\MP-LAB\xc8\pic\bin\picc -mcpu=16F15313 -c -fno-short-double -fno-short-float -fasmfile -maddrqual=ignore -xassembler-with-cpp -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/main.p1 main.c
    (908) exit status = 1
    (908) exit status = 1
    (908) exit status = 1
    make[2]: *** [build/default/production/mcc_generated_files/spi1.p1] Error 1
    make[2]: *** Waiting for unfinished jobs....
    nbproject/Makefile-default.mk:154: recipe for target 'build/default/production/mcc_generated_files/spi1.p1' failed
    make[2]: *** [build/default/production/mcc_generated_files/mcc.p1] Error 1
    nbproject/Makefile-default.mk:140: recipe for target 'build/default/production/mcc_generated_files/mcc.p1' failed
    nbproject/Makefile-default.mk:133: recipe for target 'build/default/production/mcc_generated_files/adc.p1' failed
    make[2]: *** [build/default/production/mcc_generated_files/adc.p1] Error 1
    (908) exit status = 1
    (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names
    nbproject/Makefile-default.mk:147: recipe for target 'build/default/production/mcc_generated_files/pin_manager.p1' failed
    (908) exit status = 1
    (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names
    nbproject/Makefile-default.mk:161: recipe for target 'build/default/production/main.p1' failed
    make[2]: *** [build/default/production/mcc_generated_files/pin_manager.p1] Error 1
    make[2]: Leaving directory 'E:/Documents/MPLABXProjects/Volume-Clocker.X'
    make[2]: *** [build/default/production/main.p1] Error 1
    nbproject/Makefile-default.mk:90: recipe for target '.build-conf' failed
    make[1]: Leaving directory 'E:/Documents/MPLABXProjects/Volume-Clocker.X'
    make[1]: *** [.build-conf] Error 2
    nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
    make: *** [.build-impl] Error 2

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

    #5
    aschen0866
    Super Member
    • Total Posts : 4434
    • Reward points : 0
    • Joined: 2006/01/08 22:18:32
    • Location: San Diego
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/07/20 15:28:15 (permalink)
    +2 (2)
    #6
    orchardaudio
    New Member
    • Total Posts : 14
    • Reward points : 0
    • Joined: 2018/03/07 07:46:31
    • Location: 0
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/07/20 15:40:27 (permalink)
    0
    aschen0866
    Ran into the same problem.
     
    https://www.microchip.com/forums/m1058617.aspx




    Thanks, using the XC8-CC fixed the issue.
    #7
    JamesN
    Starting Member
    • Total Posts : 62
    • Reward points : 0
    • Joined: 2014/08/06 07:18:54
    • Location: 0
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/08/07 07:31:49 (permalink)
    0
    I got the same problem updating to MPLABX 5.0 from 4.00 (XC8 1.38). I changed to XC8-CC and still have the problem. Please help.
    #8
    JamesN
    Starting Member
    • Total Posts : 62
    • Reward points : 0
    • Joined: 2014/08/06 07:18:54
    • Location: 0
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/08/07 07:33:33 (permalink)
    0
    Last week, I updated to MPLABX 5.0 on another project and got no issue.
     
    #9
    JamesN
    Starting Member
    • Total Posts : 62
    • Reward points : 0
    • Joined: 2014/08/06 07:18:54
    • Location: 0
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2018/08/07 08:03:41 (permalink)
    +1 (1)
    In Project Properties, XC8 Global Options, Global Options, C standard, I changed to C90, then issue went away.
    In Embedded,Build Tools, I changed XC8-cc.exe back to XC8.exe, I got no error, but it still uses xc8-cc.exe.
    What is the deal?
     
    "C:\Program Files (x86)\Microchip\xc8\v2.00\bin\xc8-cc.exe"  -mcpu=16F1713 -c  -fno-short-double -fno-short-float -O0 -maddrqual=ignore -xassembler-with-cpp -I"src" -I"mcc_generated_files" -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=c90 -gdwarf-3 -mstack=compiled:auto:auto     -o build/default/production/mcc_generated_files/mcc.p1 mcc_generated_files/mcc.c
    ...
    post edited by JamesN - 2018/08/07 09:01:12
    #10
    Picmad
    New Member
    • Total Posts : 20
    • Reward points : 0
    • Joined: 2018/01/24 23:52:28
    • Location: 0
    • Status: offline
    Re: (902) no chip name specified; use "PICC --CHIPINFO" to see available chip names 2019/06/13 06:20:06 (permalink)
    -1 (1)
    I had a similar problem went back to v1.45 of xc8 and it complied ok then went back to v2.00 and that worked weird that is
    #11
    Jump to:
    © 2019 APG vNext Commercial Version 4.5