• AVR Freaks

Hot!MPLABX is a steaming pile of sh@t

Author
gottliebgreg
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2020/01/28 10:50:54
  • Location: 0
  • Status: offline
2020/05/18 21:37:37 (permalink)
3.5 (8)

MPLABX is a steaming pile of sh@t

rant
I've had it with MPLABX and Microchip in general. I have been using MPLAB since 5.35 and it has done nothing but go down hill. MPLABX is just an embarrassment. I'm tired of going over page after page of errata to solve their latest 'issues', and a wildly unstable IDE. And now the newest issue, Pickit3 will program the pic and then immediately message that the pic is disconnected. Sometimes relaunching IDE solves, not always. Not interested in the Microchip apologists telling me to read the compiler users guide. I don't expect anybody to show me a solution to this. I have come to the conclusion that using pic's and MPLABX is a fool's errand and it's time to move on.  
/rant
#1

11 Replies Related Threads

    katela
    Super Member
    • Total Posts : 1753
    • Reward points : 0
    • Joined: 2013/06/11 05:25:18
    • Location: South Africa
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/19 08:10:11 (permalink)
    +5 (5)
    Many people can feel your frustration.

    Free online Microcontroller Tutorials and Projects for Hobbyists and students. From beginners to advanced. Website: www.studentcompanion.co.za
    YouTube Tutorials: https://www.youtube.com/StudentCompanionSA
    #2
    Judy
    New Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2012/02/02 15:39:09
    • Location: 0
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/19 08:55:02 (permalink)
    +1 (1)
    I've been using MPLAB since '94 but have been away from it for awhile. Now have a new project that requires MPLABX. I'm really struggling with learning it. I had the wrong Device ID code come up when I tried to program a 16F1509 with an existing .hex file that was good.  I ended up ignoring the error message and programmed anyways. Everything worked well. I'm adding more features to an existing product so we've respun the board to add more I/O. The old firmware works well in the new board even with the error message. I had a case opened on this. Sent pictures of the top of the PIC's for both boards. Nothing was resolved. I suspect V5.35 has bugs.
    #3
    katela
    Super Member
    • Total Posts : 1753
    • Reward points : 0
    • Joined: 2013/06/11 05:25:18
    • Location: South Africa
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/19 09:11:33 (permalink)
    0 (6)
    I see MPLAB X v5.40 has been released, maybe you can try it to see if it will solve your problem: https://www.microchip.com/forums/m1140504.aspx

    Free online Microcontroller Tutorials and Projects for Hobbyists and students. From beginners to advanced. Website: www.studentcompanion.co.za
    YouTube Tutorials: https://www.youtube.com/StudentCompanionSA
    #4
    _dex
    Junior Member
    • Total Posts : 102
    • Reward points : 0
    • Joined: 2008/03/19 13:57:34
    • Location: 0
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/21 00:29:28 (permalink)
    +1 (3)
    I am wondering how advanced and experienced person musty be any developer who want to develop anything reliable with MCHP products, just look at that:
    this is unbelievable!

    18.10   IDE Specific Issues

    The following are issues for the MPLAB X IDE.
    SSR
    Description
    Device(s) Affected
    MPLABX-5003
    BOOTSIZE and CODESIZE fuses for AVR-DA are missing in MPLAB X IDE v5.30.
     
    MPLABX-4965
    In some code execution a Break Instruction is not being shown as executed when it should.
     
    MPLABX-4901
    If the configuration bit RSTPINCFG in an UPDI interface is configured as GPIO or as RST, the debug tool will have to be configured to simple high voltage mode to be able to read/program the device again. On the first try a "PDI enable failed (27)" message may be observed. Try a second time and the operation will succeed.
    AVR
    MPLABX-4880
    The IDE displays incorrect value for stack pointer for devices with 127 stack levels.
     
    MPLABX-4772
    The Breakpoint Type 'Function' only shows and accepts 'main' function
     
    MPLABX-4737
    HVP/LVP cannot be selected for PIC18F26K22 with MPLAB ICD 3/ PICKIT3/ REAL ICE.
    Workaround: Use MPLAB ICD 4, MPLAB PICkit 4 In-Circuit Debuggers.
    PIC18F26K22
    MPLABX-4736
    Code Coverage does not support Macros in all cases at this time. It highlights a blank line in place of the Macro. Please review the program memory window for true accuracy.
     
    MPLABX-4626
    The visualization of the debugging variables doesn't fit with the flow of the program.
     
    MPLABX-4583
    Stopwatch display is not scaling its output using the simulator's input frequency project setting. Work around is to change simulator settings, then stop and restart MPLAB X IDE.
     
    MPLABX-4543
    IDE misrepresents REPEAT instruction in the disassembly for dsPIC33E/dsPIC33C devices. The #lit15 value instruction is being decoded as a maximum #lit14.
    dsPIC33E/dsPIC33C devices
    MPLABX-4506
    Peripheral freeze is broken for PIC18F46Q10 on MPLAB ICD 4, MPLAB PICkit 4 and MPLAB Snap tools.
    PIC18F46Q10
    MPLABX-4454
    MPLAB X IDE v5.15 installer may sometimes hang when installing drivers.
     
    MPLABX-4297
    Lubuntu 18.04 LTS: Install/Uninstall Problems of MPLAB X IDE.
     
    MPLABX-4296
    SAME54 XC32 (MPLABX 5.15) fails to step through instructions in RAM while debugging
    SAME54 MCUs
    MPLABX-4255
    Links in the final screen don't open in the browser on a 64-bit Linux system.
     
    MPLABX-4206
    Keyboard shortcut description on menus disappears after using it once.
     
    MPLABX-4131
    When using MPLAB XC32 v2.15 (Windows and Linux installations only), ATSAM devices that have 32-bit wide configuration (config) fields will have incorrect config values programmed into the device when their pragmas are added to the source code. This is not an issue when using the Mac installation of MPLAB XC32 v2.15.
    The work around for ATSAM devices will be to use the Configuration bits window to directly program the values, instead of including config pragmas in the source code.
    ATSAM MCUs
    MPLABX-4129
    Auto-complete does not work for bit fields using ATSAM MCUs and ARM_GCC
    ATSAM MCUs
    MPLABX-4027
    For ATSAM devices the datasheet link does not access the datasheet, but a product page.
    ATSAMS70Q20B and other ATSAM
    MPLABX-4014
    Address breakpoints in the Disassembly window are not recognized by the "Step Over" function
     
    MPLABX-4008
    AVR-GCC Toolchain on a mounted drive in Linux does not get discovered with correct version information in MPLAB X IDE.
    AVR MCUs
    MPLABX-3991
    Const declared variables display incorrect addresses in the watch window for AVR devices
    atmega324pb
    MPLABX-3894
    AVR STS instruction displayed incorrectly in multiple MPLAB X IDE displays:
    • Program memory view
    • Disassembly listing view
    • Trace
    AVR
    MPLABX-3870
    Using the IDE to move a project which has an associated Git repo leaves behind a copy of the Git repo after the move
     
    MPLABX-3840
    BOOTEND and APPEND configuration values are not in the configuration window
    ATmega4809
    MPLABX-3839
    Error in disassembly of rcall/call AVR instructions
    AVR 4809
    MPLABX-3836
    When launching a Debug Wire debug session and the device signature is wrong, the launch is aborted. However, a dialog pops up asking if you want to disable Debug Wire even though you never entered a Debug Wire session.
    ATmega328PB, other AVR debugWIRE devices
    MPLABX-3833
    Undocked window is resized to its default size when a new file is opened in the undocked pane. Default NetBeans behavior.
     
    MPLABX-3832
    MPLABX START project import: EDBG selected does not stay selected.
     
    MPLABX-3773
    'parallel make' causes compiler errors.
     
    MPLABX-3725
    LDS instruction generated has wrong operands in Disassembly view.
    ATmega324pb
    MPLABX-3710
    Underscore in project name causes dual-core device debug failure
    dsPIC33CH128MP508 family
    MPLABX-3687
    "Software Breakpoint Preference" prompt ignores user response if "don't show this message again" is checked
     
    MPLABX-3678
    On some projects, when first using MPLAB XC8 2.00 in MPLAB X v5.00, the build fails with No Chip name.
    The interim fix is to change the compiler drivers manually, under Tools>Options>Embedded>Build Tools>XC8 v2.00, C Compiler = xc8-cc, Assembler = xc8-cc, and then click OK.
    8-bit MCUs
    MPLABX-3657
    Adding Library project for MPLAB XC8 v2.00 changes makefile to search for .hex/.elf in library project dist folder instead of .a file
    8-bit MCUs
    MPLABX-3653
    Step-out fails to halt at the next statement after the function call
     
    MPLABX-3615
    The AVR-GCC installed with the Arduino IDE does not work with MPLAB X IDE
    AVR devices
    MPLABX-3595
    Memory notification not occurring when notification happens on a config mem change for AVR devices.
    AVR devices
    MPLABX-3508
    Renaming project & project folder causes subsequent debug attempts to fail
     
    MPLABX-3489
    When trying to add a library project to an application project, the IDE does not include the just closed project unless it is opened in the same session.
    PIC32MZ1025W104132
    MPLABX-3433
    SAM E70 TCM_CONFIGURATION fuse shown as a 1-bit field rather than 2-bit.
    ATSAME70
    MPLABX-3390
    Menu Entry Window > Web > Web Browser brings up browser with Netbeans.org
     
    MPLABX-3376
    ADPCH register missing from the IO View window
    PIC16F19155
    MPLABX-3358
    Step over(F8) doesn't work properly during debugging with MPLAB XC32 MIPS16 mode.
    PIC32 MCUs
    MPLABX-3349
    SKDE Memory missing configuration options.
    All Serial devices supported by Serial Memory Starter Kit
    MPLABX-3294
    When MPLAB X IDE is open and a project that was checked out from SVN is loaded, it may not be possible to work with other tools like TortoiseSVN because MPLAB X IDE may lock the SVN database. MPLAB X IDE may need to be closed to unlock this. Workaround: Select Tools > Options > Team > Versioning > Subversion, select CLI and put in the path of TortoiseSVN. This provides MPLAB X IDE and TortoiseSVN with the same client and will not lock the SVN database.
     
    MPLABX-3290
    TMR0 missing from IO view for PIC16F18875
    PIC16F18875
    MPLABX-3170
    Red bangs in MPLAB X IDE when C code has an ASCII char "Vertical Tab"
     
    MPLABX-3161
    When using the GIT plugin and cloning the project from GIT, the new project is not recognized within MPLAB X IDE
     
    MPLABX-3155
    Unable to "Download Latest" MPLAB XC8 installer (v1.45) from MPLAB X IDE on MAC OSx
     
    MPLABX-3116
    This occurs when using two editor Frames: Toggling a bookmark in the second view of a code file window toggles the bookmark on the cursor position in the first file window
     
    MPLABX-3115
    When you try to access RAM that does not exist using a hex file project only and no source files, such that the target silicon goes into an exception, the IDE becomes unresponsive.
     
    MPLABX-2993
    Using RTW on SFRs seems to apply but do not update when using a 16-bit device.
    PIC24HJ128GP306A
    MPLABX-2985
    Debugger is dereferencing pointer incorrectly; specifically, instead of showing the value at the address pointed to, it is showing the value at the address of the pointer.
     
    MPLABX-2944
    Disassembly listing view for 16-bit devices using MPLAB XC16 is missing some instructions when compared to the Assembler listing file for some sections of code.
     
    MPLABX-2911
    Parser does not recognize legal C syntax of defining an enum inside an object typedef. This could be C99 we are looking into it.
    PIC32MZ
    MPLABX-2880
    Unable to resolve an Identifier that appears with the structure bit field that is nested inside the structure.
     
    MPLABX-2874
    The package project does not include scripts that are referenced in the pre/post steps.
     
    MPLABX-2853
    "No source code lines found at PC 0x2b6" while stepping over assembly macros in a PIC24FJ device; Simulator/MPLAB ICD 3 used as debugger
    PIC24FJ
    MPLABX-2830
    Register Trace "Add/Remove variable" window does not size correctly
     
    MPLABX-2797
    When using microMIPS code - A General runtime MCU exception is caused when invoking a __builtin_software_breakpoint() function either by running to it or single-stepping on it.
    MEC devices
    MPLABX-2791
    Attempting to remove auto-indenting by making the value 0 results in non-functional tab capability
     
    MPLABX-2790
    On some occasions the debug (elf) file gets locked by MPLAB X IDE when doing a build / debug-build. The current workaround is to click the performance monitor to force a GC collection
     
    MPLABX-2789
    When using the compiler built in halt macro the software shows you are halted on the line prior to the Macro.
    dsPIC33EP128GS804
    MPLABX-2785
    Unable to resolve identifier appearing with legacy plib for PIC32MX device of MPLAB XC32.
    PIC32MX
    MPLABX-2779
    When switching from MPLAB XC16 to MPLAB C30, the XC16 Global options "Define common Macros" and "Common Include Directories" are not persisted in C30 Global Options causing build failure.
     
    MPLABX-2746
    IDE does not handle cases when 2 files in the same folder have same name and different extensions, which are both accepted as source files by the compiler. Building such a project will fail.
     
    MPLABX-2742
    User is not prevented from invoking the clean and build action multiple times before it has completed. This invokes the compiler many times and can cause issues
     
    MPLABX-2721
    For some files ‘unexpected token’ (Red circle bang in gutter of editor) messages in the code, when the code is on a Network drive
    PIC32
    MPLABX-2701
    "PC=" trigger in the Stimulus Register Injection tab has disappeared. We need to investigate what happened and bring it back.
     
    MPLABX-2664
    Not all the CPU registers are being read up from the target and updated in the core displays
     
    MPLABX-2639
    Pointer to ROM objects shows incorrectly in the Watches window. The MPLAB C18 C compiler only supports COFF debug format. Unfortunately, the COFF specification does not provide sufficient detail to describe pointers to ROM memory. The MPLAB XC8 C compiler supports ELF/DWARF debug format which provide sufficient detail in the debug information for the debugger to properly decode the address and data in this case.
    PIC18F
    MPLABX-2608
    When using full line indent on braces the text stays in line with the braces.
     
    MPLABX-2596
    Live parser shows unresolved identifier for structure nested in structure without name. This results from NetBeans native CND not supporting anonymous field declarations. The workaround is to specify an identifier for the field. The downside is that you will have to specify that field name everywhere you use it in code.
     
    MPLABX-2565
    For the PIC32MM device the option to Enable App IO on the MPLAB XC32 compiler is not grayed out, as it is not available.
    PIC32MM
    MPLABX-2564
    Response file support in MPLAB XC16 may not work if the linker gld name is stored in a file with spaces. If you want to use a gld as is (without modification), you do not need to specify a file in the Linker Files node. The MPLAB XC16 will pick the correct file. If you do need to specify a gld of your own: 1) Do not include spaces in the path where you put it 2) Preferably put it in the MPLAB X project directory. Even if not using response files, the advice above still holds true.
     
    MPLABX-2525
    On some occasions when opening a project, the files will show gray, which is indicative that they are excluded from the project. In this case the build will fail because the system thinks the project is empty. Closing and re-opening the project should rectify the issue.
     
    MPLABX-2514
    On some midrange devices the breakpoint will miss and not stop after stopping several times. Once paused then restarted the BP will continue to work for while then again not stop. There is no definitive count on how many times it will stop until the halt fails.
    PIC16F877A, PIC16F887
    MPLABX-2481
    Starting debug before Hold in Reset completes causes out of sync issues with toolbar
     
    MPLABX-2475
    Value of assembly symbols do not show in the Watch or variables window for relocatable code
    PIC18F26K22
    MPLABX-2455
    When using loadables, the ImagePath macros do not use the unified image
     
    MPLABX-2454
    Problems using "/" for pre-post-steps of a build under Windows OS.
     
    MPLABX-2449
    Incorrect disassembly of CP instruction for dsPIC33E devices.
     
    MPLABX-2428
    Generic plugin has some issues with command execution using Wine for Mac. So generic plugin will not work on MAC OS using MPLAB X IDE.
     
    MPLABX-2425
    DisAssy column of Program Memory View displays incorrect code for movpag, call.l , computed branch (eg. bra w3), cpseq, cpsgt, cpslt, cpsne ,cpbeq, cpbgt , cpblt , cpbne
    dsPIC33EVXXXGM00X/10X
    MPLABX-2408
    Attempting to cancel project file deletion using keyboard navigation will fail (the file will be deleted). Selecting a project file and then hitting the Delete key will pop up a "Confirm Object Deletion" dialog. Using the Tab key to select "No" and hitting Enter will still result in the file being deleted. Using the mouse to click "No" will cancel the deletion.
     
    MPLABX-2368
    Labels are not loaded in Program memory window of Partition 2 in dual partition devices
     
    MPLABX-2250
    PICkit 3 fails to connect and/or program a 12F629 when powering from the tool using 5.0 volts
    PIC12F629
    MPLABX-2247
    A frozen peripheral can unfreeze when single stepping at or immediately after instructions that perform a read-modify-write on the peripheral's control register.
    Workaround: Either use atomic set/clear registers such as T1CONSET or do not single step too close to instructions that modify xCON registers.
    PIC32MZ family
    MPLABX-2069
    Code folding does not work for inline asm code in MPLAB C18 when _asm and _endasm directives are used. The work-around is to put the code block near the end of the code/file.
     
    MPLABX-2034
    The correct 'Firmware Suite Version' is not being displayed after recovery from a 'Connection Failed' error.
    PIC16F1939-ME2; may affect other parts
    MPLABX-2026
    Named elements in C99 structure initializers are incorrectly flagged as errors
     
    MPLABX-2022
    When hexmate reports a conflict, the reported address does not always reflect the address in MPLAB X IDE. For example, on a 16-bit device, 0x1000 is address 0x800 in MPLAB X IDE.
     
    MPLABX-2004
    An array residing in the external memory may not be displayed properly in the watch window.
    PIC24FJ128GA010
    MPLABX-1971
    When importing an MPLAB C18 project, an exception occurs in the MPLAB X IDE, although the import happens correctly.
     
    MPLABX-1969
    In the Project Properties dialog, for any MPLAB XC assembler, adding “ASM include dirs” results in .d files contain in this path.
     
    MPLABX-1962
    Cannot communicate with AC162055 below 3.375 volts and cannot erase USER ID below 4.5v
    PIC16F684-ICE
    MPLABX-1778
    Start page links do not work if installed in the 64-bit OS default directory 'Program Files(x86)'
     
    MPLABX-1727
    Highlighted selection (SFR/bit) in watch window gets deselected if stepping through project too fast.
    All
    MPLABX-1414
    "New File" option appears twice in the Toolbar customize menu. This is a NetBeans issue (Bug 162385):
    https://netbeans.org/bugzilla/show_bug.cgi?id=162385
     
    MPLABX-1170
    The MPLAB XC32 compiler might place a function parameter in a CPU register so it does not update in the watch. Define variable as volatile for debugging.
    PIC32 MCUs
    MPLABX-752
    When Find... or Find In Projects... is used to search for text, the resulting display in the Search Results output window does not display tab characters that were in the original text file. For example, searching for latt_kesk in the line movf latt_kesk will display movflatt_kesk
     
    MPLABX-651
    Project properties for MPLAB ICD 3 do not show User ID memories for PIC32 devices.
    PIC32
    MPLABX-303
    Mac OS 10.5 (32 bit) seems to think REALICE was ICD3 and PICkit 3 was PICkit 2. If the tool is plugged into the SAME USB port, then this problem can occur.
     
    MPLABX-180
    SKDE PIC32: Calling DBG_PRINTF back to back can lock up MPLAB X IDE and MPLAB IDE v8.
    PIC32

    18.11   UDBC Issues

    The following are enumerated issues for the device data base incorporated into MPLAB X IDE.
    SSR
    Description
    Device(s) Affected
    UDBC-1421
    For the below listed devices, POR and MCLR masks for SFR ADCON1 are defined as “00qqqq". However, the datasheet states that the mask should be "000qqq". PIC18(L)F2221 PIC18(L)F2321 PIC18(L)F2410 PIC18(L)F2420 PIC18(L)F2423 PIC18(L)F2450 PIC18(L)F2455 PIC18(L)F2458 PIC18(L)F2510 PIC18(L)F2515 PIC18(L)F2520 PIC18(L)F2523 PIC18(L)F2525 PIC18(L)F2550 PIC18(L)F2553 PIC18(L)F2610 PIC18(L)F2620 PIC18(L)F4221 PIC18(L)F4321 PIC18(L)F4410 PIC18(L)F4420 PIC18(L)F4423 PIC18(L)F4450 PIC18(L)F4455 PIC18(L)F4458 PIC18(L)F4510 PIC18(L)F4515 PIC18(L)F4520 PIC18(L)F4523 PIC18(L)F4525 PIC18(L)F4550 PIC18(L)F4553 PIC18(L)F4610 PIC18(L)F4620
    PIC18(L)F2/4xxx
    UDBC-1408
    MCP19126 device PIC file has incorrect SFR names
    MCP19126
    UDBC-1405
    ECH option should be changed to "ECH, External Clock, High Power Mode (4-32 MHz): device clock supplied to CLKIN pins" from "ECH, External Clock, High Power Mode (4-20 MHz): device clock supplied to CLKIN pins" in all the devices belonging to PIC16F161x family.
    PIC16F161x device family.
    UDBC-1404
    MCP19214 doesn’t support UART
    MCP19214
    UDBC-1386
    SPI6TXIF is not defined in the header file of PIC32MZ2048EFG144.
    PIC32MZ2048EFG144
    UDBC-1304
    Incorrect device ID in PIC files for MCP19214 and MCP19215.
    MCP19214, MCP19215
    UDBC-1292
    The Config bit setting for FOSC contains 3 fields as per data sheet: FOS FPR FCKSMEN But X IDE merges FOS and FPR as FOSFPR and this does not set the FPR bits. So this does not support #pragma config, Please use __FOSC syntax.
     
    UDBC-1225
    Missing definition of the SFRs in the header files: USBIE0CSR0 USBIE0CSR2 USBIE0CSR3
    PIC32MZ device family
    UDBC-1159
    IEC3 and IFS3 should not exist for PIC24EPxxxGP20x devices
    PIC24EPXXXGP20X
    UDBC-1014
    Per datasheet, table 25.2 FNOSC<2:0> FOSCSEL- 111 = Internal Fast RC (FRC) oscillator with postscaler In MPLAB X and the compiler device header file, this bit is named as LPRCDIVN and description for the bit is- Oscillator Mode (Internal Fast RC (FRC) with divide by N) Using the configuration bits feature from MPLAB X v2.30 for PIC24HJ128GP502 device, when selecting 'Fast Internal oscillator with postscaler N' the generated code is 'LPRCDIVN'. From the datasheet the bit name is 'FRCDIVN'.
    PIC24HJ family
    UDBC-1007
    OCFLT<2:0> bits of OCxCON1 register in PIC24F/FV32KA304 family devices are Hardware Settable/Clearable bits, but shouldn't be able to set them in software. Currently they are selectable in software.
    PIC24F/FV32KA304 family
    UDBC-988
    TMR1, TMR2, TMR3, TMR4, and TMR5 registers should be set to 0 for all resets (also tested with real device, and they did get cleared after reset), but currently may get set to any value.
    PIC24FV32KA304 Family
    UDBC-950
    Some ADC registers are not showing up in the SFR peripheral display.
    PIC18F97J94
    UDBC-924
    The SFR registers QEI2ICL and QEI2ICH have been removed from 33EP devices.
    dsPIC33EPxxxGMxxx , dsPIC33EPxxxMU8xx
    UDBC-922
    There may be some default values of the configuration registers that are not correct for the PIC24FV32KA304 family.
    PIC24FV32KA304 Family
    UDBC-884
    Reset value of CORCON is incorrect in MPLAB X
    All 16-bit devices
    UDBC-881
    [PIC32MX1xx/2xx]ODCB bit implementation for r/w operation doesn't match the datasheet
    PIC32MX1xx/2xx
    UDBC-867
    Linker error "Settings in '__FBS.sec' are not valid for target device PIC24F04KL101 " though valid settings are made for the device. A workaround is to define this way: #pragma config BWRP = OFF, BSS = OFF
    PIC24F04KL101
    UDBC-863
    In dsPIC33EP256MU806.h, SFR blocks are missing for UART3, UART4, SPI3 and SPI4.
     
    UDBC-858
    Unrecognized macro value generated for configuration bit settings for BORV with PIC24F04KA201.
    PIC24F04KA201
    UDBC-846
    RETCFG is missing description in the support header files.
    PIC24F16KM204 family
    UDBC-821
    Description of BORV in incorrect and is similar to BOREN. The description of BORV needs to be "Brown-out Voltage Level".
    PIC24F16KM204 family of devices.
    UDBC-711
    RJPU bit is not defined in PIC18F97J94 datasheet but is included in PIC18F97J94.h header file of XC8
     
    UDBC-672
    The CiFEN1 register default value may not match the default value as mentioned in the datasheet.
    dsPIC33F, PIC24H
    UDBC-670
    PMMODE- Bit16 (Busy) is implemented as r/w bit for PIC32MX devices.
    PIC32MX Family
    UDBC-664
    Not enough FUID macros, highest byte not handled by FUID macros.
    dsPIC30F
    UDBC-515
    Configuration bit name is PLL_96MHZ_ON, should be PLL96MHZ_ON
    PIC24FJ128GB106, PIC24FJ128GB108, PIC24FJ128GB110, PIC24FJ192GB106, PIC24FJ192GB108, PIC24FJ192GB110, PIC24FJ256GB106, PIC24FJ256GB108, PIC24FJ256GB110, PIC24FJ64GB106, PIC24FJ64GB108, PIC24FJ64GB110
    #5
    NorthGuy
    Super Member
    • Total Posts : 6085
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: online
    Re: MPLABX is a steaming pile of sh@t 2020/05/21 07:37:38 (permalink)
    +5 (5)
    _dex
    I am wondering how advanced and experienced person musty be any developer who want to develop anything reliable with MCHP products, just look at that:
    this is unbelievable!



    Most of the issues you quote are local and small. You may work for a long time and never encounter any of these.
     
     
    #6
    JPortici
    Super Member
    • Total Posts : 1017
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/21 07:58:00 (permalink)
    +5 (7)
    As i never did in 10 years of working with microchip parts, but hey, endless complaining is fun!
     
    #7
    nigelwright7557
    Super Member
    • Total Posts : 424
    • Reward points : 0
    • Joined: 2006/11/06 08:15:51
    • Location: 0
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/21 08:01:36 (permalink)
    +2 (2)
    I have just started a new project with atsame70j21
    Looked through datasheet to make sure it had all the peripherals I wanted and it did.
    It had higher speed usb which is great.
    I had trouble finding pin out for cortex and programming pins but eventually found a diagram.
    I managed to program the IC once and then it wouldnt program again.
    So  I had an IC that flashed a LED but otherwise useless.
    SO put in a ticket to Microchip for help.
    Turned out the Snap connections I used had reset on pin 6 instead of pin 1.
    However the also looked at my circuit and told me the USB doesnt work on that IC anyway.
    They say before designing in IC's read datasheet but also any errata.
    Good clear information on connecting to atsame70 is not good.
    Even the power supplies took a long time to work out which is 3v3 and which is VDDCORE.
    The VBUS signal needs to be on a I/O pin too which was buried in datasheet.
     
    I can see two sides here.
    1/ Microchip spending an absolute  fortune on dev software/hardware.
    2/ Trying to use that software/hardware in the real world.
     
    A previous project I worked on I moved up to the next faster IC and used same port pins.
    When I got the pcb up and running portb,4 was no longer an output ! they had changed it to be input only despite Harmony pin settings showing it can be an output too.
     
     
    post edited by nigelwright7557 - 2020/05/21 08:04:13
    #8
    Tim Cruise
    Senior Member
    • Total Posts : 158
    • Reward points : 0
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/21 09:36:57 (permalink)
    0
    Their IDE and libraries are very HUGE!!!  Just install and load what you need.  Do not load every plug-in.  Unload MCC and MHC if you don't need them.
     
    Concentrate on your best known MCUs and their libraries.
     
    There is a plug-in called USB Connection Diagnostics inside MPLAB X.  Run it to test your USB cable connection.
     
    Command console is also available.  They are under mplab_platform\mplab_ipe\.
     
    Also, choose Microchip's recommended MCUs and platforms.
     
    Upgrading your computer to accommodate MPLABX and Netbean.
     
    If you are in a hurry, open a ticket with US$100.00.
    #9
    NKurzman
    A Guy on the Net
    • Total Posts : 18667
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/21 09:58:00 (permalink)
    +3 (3)
    ALWAYS Read the Errata before making a final chip selection.  Words to live by.
     
    This Forum has very power SAM and AVR Coverage.  Have you tried the Atmel Forums?
    #10
    ric
    Super Member
    • Total Posts : 27022
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/21 13:42:46 (permalink)
    +2 (2)
    NKurzman
    This Forum has very power SAM and AVR Coverage.  Have you tried the Atmel Forums?

    Typo. "power" -> "poor".
     

    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!
    #11
    _dex
    Junior Member
    • Total Posts : 102
    • Reward points : 0
    • Joined: 2008/03/19 13:57:34
    • Location: 0
    • Status: offline
    Re: MPLABX is a steaming pile of sh@t 2020/05/22 01:12:25 (permalink)
    +2 (2)
    It is extremely challenging for not an advanced user ( as I am) to work with their Product, you never know if this is a IDE problem, debugger or your hardware. Cost time and time. The only one thing what user expect is that when you halt debugger, the register values are true!
    Are this minor problems?:

     
    MPLABX-4626
    The visualization of the debugging variables doesn't fit with the flow of the program.
     
    MPLABX-2944
    Disassembly listing view for 16-bit devices using MPLAB XC16 is missing some instructions when compared to the Assembler listing file for some sections of code.
    MPLABX-2449
    Incorrect disassembly of CP instruction for dsPIC33E devices.
    MPLABX-4014
    Address breakpoints in the Disassembly window are not recognized by the "Step Over" function
    UDBC-884
    Reset value of CORCON is incorrect in MPLAB X
    All 16-bit devices
     

    I would never release new version until the old KEY Issues are fixed. And these were only issues for PICs which I  am interested in.
    Motor control chip which has 6 or 8 bugs in QEI encoder and the solution is to make software workaround. Or chip with fancy I2C hardware which is not to use. Joke! If the task or amount of work overload the company, then reduce number of Products and make less but full functional.
    In such way all the electronics around us live by their own live.. And we will have every month new firmware update due to old bugs. Developer things something and the hardware is doing something else..
     
    How they could get TUV certificate? For what ?For a management and bureaucracy, for sure not for the reliability..
    Complaining is not just to  complain and waste a time but to make it better, if I really believe in that, perhaps some day smart or clever person will make order in this company.
    post edited by _dex - 2020/05/22 01:30:02
    #12
    Jump to:
    © 2020 APG vNext Commercial Version 4.5