• AVR Freaks

Hot!BAD CPU

Author
charleskerr
Junior Member
  • Total Posts : 103
  • Reward points : 0
  • Status: offline
2019/09/26 11:22:37 (permalink)
0

BAD CPU

I have a MPASM project (PIC12F1572) that in MPLAX 5.25 now gives me this when I try to build it:
 
Bad CPU type in executable
 
I haven't seen any add on packs to install (I vaguely recall an older version of MPLABX it gave me an option to install some add on device packs).  Anyone have any idea?
#1

15 Replies Related Threads

    charleskerr
    Junior Member
    • Total Posts : 103
    • Reward points : 0
    • Status: offline
    Re: BAD CPU 2019/09/26 11:34:38 (permalink)
    0
    Just to help, I created an empty project, and did a new file with one o the sample asm template options.
     
    It gives this error:
     
     
    ake -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
    /bin/sh: /Applications/microchip/mplabx/v5.25/mplab_platform/platform/../mplab_ide/modules/../../bin/mplabwildcard: Bad CPU type in executable
    /bin/sh: /Applications/microchip/mplabx/v5.25/mplab_platform/platform/../mplab_ide/modules/../../bin/mplabwildcard: Bad CPU type in executable
    make[1]: Entering directory '/Volumes/CodeNoCase/MPLABXPROJECTS/NewTstFix.X'
    make -f nbproject/Makefile-default.mk dist/default/production/NewTstFix.X.production.hex
    make[2]: Entering directory '/Volumes/CodeNoCase/MPLABXPROJECTS/NewTstFix.X'
    /bin/sh: /Applications/microchip/mplabx/v5.25/mplab_platform/platform/../mplab_ide/modules/../../bin/fixDeps: Bad CPU type in executable
    make[2]: *** [build/default/production/tstfix.o] Error 126
    make[1]: *** [.build-conf] Error 2
    make: *** [.build-impl] Error 2
    nbproject/Makefile-default.mk:108: recipe for target 'build/default/production/tstfix.o' failed
    make[2]: Leaving directory '/Volumes/CodeNoCase/MPLABXPROJECTS/NewTstFix.X'
    nbproject/Makefile-default.mk:91: recipe for target '.build-conf' failed
    make[1]: Leaving directory '/Volumes/CodeNoCase/MPLABXPROJECTS/NewTstFix.X'
    nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
    BUILD FAILED (exit value 2, total time: 281ms)
     
     
    I have reinstalled MPLABX to no avail.
    #2
    jtemples
    عُضْوٌ جَدِيد
    • Total Posts : 11430
    • Reward points : 0
    • Joined: 2004/02/13 12:31:19
    • Location: Southern California
    • Status: offline
    Re: BAD CPU 2019/09/26 15:19:21 (permalink)
    +3 (3)
    I'm pretty sure "Bad CPU type in executable" has nothing to do with what PIC you're using, but rather the CPU in your PC.  Have you tried Googling for "Bad CPU type in executable"?
    #3
    dan1138
    Super Member
    • Total Posts : 3290
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: BAD CPU 2019/09/26 19:47:47 (permalink)
    +2 (2)
    @jtemples,
     
    It looks like the OP is running on linux and some distributions no longer have support for 32-bit application.
     
    Java is just grand, write once run "almost" anywhere.
    #4
    jtemples
    عُضْوٌ جَدِيد
    • Total Posts : 11430
    • Reward points : 0
    • Joined: 2004/02/13 12:31:19
    • Location: Southern California
    • Status: offline
    Re: BAD CPU 2019/09/26 20:47:35 (permalink)
    +2 (2)
    linux

     
    I'm going to be contrary and wager on Mac OS.
    #5
    JPortici
    Super Member
    • Total Posts : 851
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: BAD CPU 2019/09/27 01:11:40 (permalink)
    +2 (2)
    correct, that's OSX folder structure (/Applications/)
     
    so one of two things happened here,
    either
    - OP purchased a brand new macbook and he's SOL
    or
    - OP has keeps ignoring what every software developer company has been telling since forever, IF YOU NEED TO USE YOUR SOFTWARE NEVER UPDATE TO THE LATEST OSX VERSION BECAUSE THEY ARE ALWAYS CHANGING SOMETHING FUNDAMENTAL TO THEIR OS,API,LIBRARIES... BUT WAIT UNTIL WE CONFIRM IT'S COMPATIBLE.
     
    because you can't just flip the switch on 64bit and expect that the compiler will behave the same. Extensive tests needs to be done and they are never done before it's mandatory
     
    Revert to a previous version of osx if you can and ask support when exactly the 64bit binaries for the compilers are being released, because we don't know.
    #6
    meyerjoh
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2016/07/15 14:33:40
    • Location: 0
    • Status: offline
    Re: BAD CPU 2019/11/15 13:40:44 (permalink)
    0
    Just "confirmed" that this is a problem with OS X Catalina and MP_LAB version 5.30.
     
    This is my fault, for buying a newer faster computer. :(
     
    Is there any light at the end of the tunnel? Is there is a fix in development? Or is this the right time to by a Windows box.
     
    //John
    #7
    NorthGuy
    Super Member
    • Total Posts : 5810
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: BAD CPU 2019/11/15 15:41:17 (permalink)
    +3 (3)
    OS X only supports true fans. If you're in doubt, you must leave.
    #8
    NKurzman
    A Guy on the Net
    • Total Posts : 18046
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: BAD CPU 2019/11/15 21:31:03 (permalink)
    0
    I think they are promising 64 bits by year end.
    #9
    mpgmike
    Super Member
    • Total Posts : 332
    • Reward points : 0
    • Joined: 2014/01/23 17:27:06
    • Location: NJ
    • Status: offline
    Re: BAD CPU 2019/11/16 03:57:40 (permalink)
    0
    NKurzman
    I think they are promising 64 bits by year end.

    "They" meaning Microchip?  Love 'em to death, and loyal like a spouse, but not enough to hold my breath.

    I don't need the world to know my name, but I want to live a life so all my great-grandchildren proudly remember me.
    #10
    NKurzman
    A Guy on the Net
    • Total Posts : 18046
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: BAD CPU 2019/11/16 09:04:59 (permalink)
    +1 (1)
    Yes microchip, and I agree they are often late.
    #11
    MisterHemi
    Senior Member
    • Total Posts : 178
    • Reward points : 0
    • Joined: 2017/11/02 12:24:21
    • Location: Commerce, CA USA
    • Status: offline
    Re: BAD CPU 2019/11/17 23:38:15 (permalink)
    +1 (1)
    meyerjoh
    Just "confirmed" that this is a problem with OS X Catalina and MP_LAB version 5.30.
     
    This is my fault, for buying a newer faster computer. :(
     
    Is there any light at the end of the tunnel? Is there is a fix in development? Or is this the right time to by a Windows box.
     
    //John


     
    I suppose if you're desperate you could use VMWare or Parallels (i've used both but currently using VMWare) and run an older version of Mac OSX in a virtual machine.
     
    I have some older professional music equipment that has software that only runs on Mac OS X 10.6 and I run it using VMWare and it works fine.

    I haven't had any issues running older versions of Mac OS when needed and presently I have virtual machines for Mac OS 10.6, Windows 10, Linux Mint, and Ubuntu - no problems.
     

    My configuration:
    MacBook Pro (Retina, 15-inch, Mid 2015) with MacOS High Sierra (10.14.5) and MPLAB X IDE v5.20
     
    Curiosity PIC32MZ EF, PIC24F Curiosity, XPRESS EVAL BOARD (PIC16F18855), SAMA5D3 Xplained and various custom boards.
    #12
    BMD
    Super Member
    • Total Posts : 434
    • Reward points : 0
    • Joined: 2003/12/02 21:42:52
    • Location: UK
    • Status: online
    Re: BAD CPU 2019/11/18 05:59:25 (permalink)
    +3 (3)
    Hi,
    In the IDE Release notes...
     

    2.4      Unsupported Configurations

    MPLAB X IDE does not support Virtual Machines.
     
     

    Regards

    Brandon
    #13
    MisterHemi
    Senior Member
    • Total Posts : 178
    • Reward points : 0
    • Joined: 2017/11/02 12:24:21
    • Location: Commerce, CA USA
    • Status: offline
    Re: BAD CPU 2019/11/18 10:48:49 (permalink)
    +2 (2)
    BMD
    Hi,
    In the IDE Release notes...
     

    2.4      Unsupported Configurations

    MPLAB X IDE does not support Virtual Machines.
     
     




    Interesting.... but i'm wondering if it's similar to what Microsoft says.
     
    They say they don't support virtualization of Windows 10 also but it works fine running on VMWare but they won't help (support) you should you have any technical issues.
     
    I may boot up Windows 10 and/or Linux try installing MPLAB X in it and see if it works.
    post edited by MisterHemi - 2019/11/18 11:30:43

    My configuration:
    MacBook Pro (Retina, 15-inch, Mid 2015) with MacOS High Sierra (10.14.5) and MPLAB X IDE v5.20
     
    Curiosity PIC32MZ EF, PIC24F Curiosity, XPRESS EVAL BOARD (PIC16F18855), SAMA5D3 Xplained and various custom boards.
    #14
    crosland
    Super Member
    • Total Posts : 1696
    • Reward points : 0
    • Joined: 2005/05/10 10:55:05
    • Location: Warks, UK
    • Status: offline
    Re: BAD CPU 2019/11/18 11:50:18 (permalink)
    0
    BMD
    Hi,
    In the IDE Release notes...
     

    2.4      Unsupported Configurations

    MPLAB X IDE does not support Virtual Machines.

     
    It may be something to do with the tool drivers. Then again, USB support in VMs is so much better than it used to be.
    #15
    mlp
    boots too small
    • Total Posts : 825
    • Reward points : 0
    • Joined: 2012/09/10 15:12:07
    • Location: previously Microchip XC8 team
    • Status: offline
    Re: BAD CPU 2019/11/18 20:25:29 (permalink)
    +2 (2)
    meyerjoh
    Is there any light at the end of the tunnel? Is there is a fix in development?

    A full 64-bit toolchain is in the works, I've heard.
    Many in the dev team use Macs so they've got incentive to get this fixed.
     
    Or is this the right time to by a Windows box.

    It's never the right time for that.
     
    MisterHemi
    I suppose if you're desperate you could use VMWare or Parallels (i've used both but currently using VMWare) and run an older version of Mac OSX in a virtual machine.

    I am partial to VirtualBox (it works well with OSX as both host and guest, and it has some little features that VMware lacks or at least doesn't make easily visible), but since it's owned by Oracle you may want to avoid it even though it's "free". (Oracle salescritters started breathing very heavy on my current boss's neck about our completely-legit use of the free license for vbox, demanding vast amounts of annual license payments. He told them to pound sand and paid for VMware instead.)
     
    MPLAB X and the XC compilers work fine running inside a virtual machine.
    I have used all 3 supported OSes as both host and guest with no problems at all beyond those that everybody sees.
    post edited by mlp - 2019/11/18 20:28:44

    Mark (this opinion available for hire)
    #16
    Jump to:
    © 2019 APG vNext Commercial Version 4.5