But when I tried to run the demo, it pop up target device ID was not matching with the expected device ID. Hence, in the MPLAB IDE, I went Configuration -> Select Device. I found the preset device was wrong and I changed to the correct MCU, which was PIC32MX765F512L. But after changing, the IDE pop up the device was unloaded and then the IDE crashed.
Sorry to hear you are having a problem. It sounds like the part number used on the kit has changed. I will open one up and adjust the project accordingly, then post back here.
I have looked at the kits I have open, from an older batch, and they definitely have the PIC32MX795F512 part on them. Also, the cover of the kit box (current batch) shows a picture that has the PIC32MX795 partnumber written on its silk screen. The Microchip site is also still showing the part as a PIC32MX795: http://www.microchip.com/stellent/images/mchpsiteimages/PIC32%20USB%20Starter%20Kit%20II.gif
It is possible that the latest batch have a different part, but before I take the cellophane off a new kit to see what is in side I would like to ask that you double check what is written on the chip - just in case you were mistaken. I cannot see that there is a PIC32MX765F512L device listed.
Also, is the kit you have a USB Starter Kit II that you actually purchased through the FreeRTOS shop?
Sorry, It was my typo. The MCU is PIC32MX795F512L as the .gif you attached. I did try to choose the correct MCU, PIC32MX795F512L, in the MPLAB Configuration since the default MCU of the RTOSDemo.mcw was PIC32MX360F512L and this lead to the device mismatched. Please see my screenshot.
But after I chose PIC32MX795F512L, the IDE crashed.
And I did purchase the USB Starter Kit II from the FreeRTOS shop.
The files that are sent with the education kit documents are set for the PIC32MX795F512L to target the USB-II starter kit hardware (I just checked), but the project that comes in the main FreeRTOS .zip file download targets the much older MX360 part on the Explorer16 PIM.