Hi All,
Microchip can't close IDE
Reason: a MCC close will produce [ mcc closing native project ] runs for ever and disallow to terminate IDE.


Looking at Internet and all reported problems with MCC I will Not try to use it anymore.(Time consuming sh*t)
I will keep my way of working.

This MCC program looks nice however, it seem to be useless .......>no way to get it to work.

Any people using this MCC software if so is it working?


Regards,
Picbuster
Running linux mint V22.02 & IDE V6.20

 

Works for me across the product line. IDE V6.25 with updates. I use it for boilerplate setup and then customize the code for the specific application.

 

You can try deleting you local (home directory) MPLabX config folders and let it recreate from scratch. That worked a couple of times for me on various issues.

 

Hi All,
Microchip can't close IDE
Reason: a MCC close will produce [ mcc closing native project ] runs for ever and disallow to terminate IDE.


Looking at Internet and all reported problems with MCC I will Not try to use it anymore.(Time consuming sh*t)
I will keep my way of working.

This MCC program looks nice however, it seem to be useless .......>no way to get it to work.

Any people using this MCC software if so is it working?


Regards,
Picbuster
Running linux mint V22.02 & IDE V6.20

Have you tried running this whole setup on Windows?

 

The IDE will choke if there is low memory <16G and it needs to run chromium (internal version in the user home IDE cache directories) during MCC. To the OP, what are the spec's on your Linux Machine and what else is running on it?

 

You can try deleting you local (home directory) MPLabX config folders and let it recreate from scratch. That worked a couple of times for me on various issues.

Somebody ask me did you install IDE in windows answer is no I did not. I might be able to find somewhere a disk or PC with Win2000 or winxp in the pile of obsolete material.

I did reinstalled the lot on mint V2.03 then on V2.00 no change.

The old way making my own .H, port-settings, drivers and other pic settings works for me.
I was investigating the possibilities of MCC.
Question: should it bring me any advantage?
I am not convinced yet.

Regards,
Picbuster

 

...Win2000 or winxp in the pile of obsolete material.

The most modern obsolete OS ever.

I was investigating the possibilities of MCC.

Ha ha ha.

I was avoiding them.

Question: should it bring me any advantage?

Not if you're a mediocre or better programmer.

The old way making my own .H, port-settings, drivers and other pic settings works for me.

That's almost sacrilege in these parts.

It's far better to do things fast than to do them right.

And there is always time to do them over.

 

Somebody ask me did you install IDE in windows answer is no I did not. I might be able to find somewhere a disk or PC with Win2000 or winxp in the pile of obsolete material.

I did reinstalled the lot on mint V2.03 then on V2.00 no change.

The old way making my own .H, port-settings, drivers and other pic settings works for me.
I was investigating the possibilities of MCC.
Question: should it bring me any advantage?
I am not convinced yet.

Regards,
Picbuster

Depends. I use both methods in projects. The MCC is only for basic configuration at best, with lots of limitations. The trick is knowing when there is an advantage and when it's a liability.

With a new uC device, I use it to see what works for basic operation and then write a custom init for what I need, as needed for the task.

volatile uint8_t iss_adc_write[8] = {0x02, 0x00, 0x00, 0x00}; // 1024 bytes in each address page for sequential writes
uint8_t sram_adc_write[8];
volatile uint32_t total_sample_triggers = 0;
volatile uint16_t sram_addr = 0, *sram_addr_ptr = (volatile uint16_t *) & iss_adc_write[2];  // pointer to address bytes
volatile uint16_t adc_result[NUM_ADC] = {0, 0};


/*
* setup the iss66 command buffer and DMA the data to the chip
*/
void ADC_DMA_write(void)
{
#ifndef USE_SRAM
    /*
     * trigger both ADC's
     */
    AD1SWTRGbits.CH6TRG = 1;
    AD2SWTRGbits.CH4TRG = 1;
    while (AD1STATbits.CH6RDY == 0 && AD2STATbits.CH4RDY == 0); // conversions complete on both
    adc_result[ADC1_D] = (uint16_t) AD1CH6DATA; // save as uint16_t data
    adc_result[ADC2_D] = (uint16_t) AD2CH4DATA;
    memcpy((void *) &iss_adc_write[4], (const void *) &adc_result[ADC1_D], 4);

    /*
     * swap address bytes for serial SRAM addressing and update address bytes
     */
#if defined __has_builtin
#if __has_builtin (__builtin_bswap16)
    *sram_addr_ptr = __builtin_bswap16(sram_addr);
#else
    *sram_addr_ptr = htons(sram_addr);
#endif
#else
    *sram_addr_ptr = htons(sram_addr);
#endif
    if ((sram_addr += 4) >= MAX_ISS66_SAMPLES) {
        sram_addr = 0;
        total_sample_triggers++;
        //        TP0_Toggle();
    };

    /*
     * make sure DMA is ready for next sequence
     */
    while (DMA_ChannelIsBusy(DMA_CHANNEL_5)) {
    };
#ifndef USE_SRAM
    SRAM_CS_Clear(); // CS will bet set in DMA complete ISR
#endif
    /*
     * write sram chip data address and two 16-bit ADC results to chip for later processing
     */
    DMA_ChannelTransfer(DMA_CHANNEL_5, (const void *) iss_adc_write, (const void*) &SPI2BUF, (size_t) 8);
#endif
};

 

Somebody ask me did you install IDE in windows answer is no I did not. I might be able to find somewhere a disk or PC with Win2000 or winxp in the pile of obsolete material.

I did reinstalled the lot on mint V2.03 then on V2.00 no change.

The old way making my own .H, port-settings, drivers and other pic settings works for me.
I was investigating the possibilities of MCC.
Question: should it bring me any advantage?
I am not convinced yet.

Regards,
Picbuster

Take a look at this option:

https://visualgdb.com/tutorials/pic32/

 

https://www.microchip.com/en-us/tools-resources/develop/mplab-tools-vs-code

https://developerhelp.microchip.com/xwiki/bin/view/software-tools/ides/extensions/get-started/

 

https://www.microchip.com/en-us/tools-resources/develop/mplab-tools-vs-code

https://developerhelp.microchip.com/xwiki/bin/view/software-tools/ides/extensions/get-started/

"...no more heavy IDE overhead."

While I agree with your post in principle, I had to chuckle a bit when I read the text at the link.

 

The standalone MCC version: https://www.microchip.com/en-us/tools-resources/configure/mplab-code-configurator#downloads

 

"...no more heavy IDE overhead."

While I agree with your post in principle, I had to chuckle a bit when I read the text at the link.

Me too

MPLAB X IDE is based on Apache Netbeans.

talk about a steam engine...

 

Nuclear power (fission and fusion) still uses steam. The modern world still relies on steam. Nothing wrong with steam or Apache Netbeans or vi(m). They all get the job done.

 

vi(m)

The world needs only one.

 

Nuclear power (fission and fusion) still uses steam. The modern world still relies on steam. Nothing wrong with steam or Apache Netbeans or vi(m). They all get the job done.

Watch out Harley Davidson.

 

......... ahhhhhh, ......... digging really deep in my memory .........

There is some file that is updated upon closing. Anyway, it is copied from the distribution medium during installation, and, of course, it is read-only. MCC blocks on the failure to write. The solution is to delete that file, and MCC will create a new one with read/write permission.

Another poster said that deleting some folders worked. So, yeah, delete something...