cant find 32 bit version of jvm.dll

[Ttelmah]

As I already said, you needed to install MPLAB, _not_ MPLAB-X.
MPLAB 8.92, sets up the JVM in the way required.
Your '5.5', and '6.2', are MPLAB-X versions.
It has been a curse for ages, that the releases of MPLAB-X do not include
this component properly set up.

[jimzum]

OK
I Found and downloaded and installed MPLAB 8.92. This is the last version of MPLAB
I then reinstall the 3 MPLAB Plugs in

I press the PROGRAM Button on the CCS compiler version 5.117
I get the error
"ERROR: Download Failed"

Running the Diagnostic

The Target ID is all zeros

Target voltage is correct 5 Volts
Everything is the same as in my last post
Loading MPLAB 8.92 changed nothing

As far as MPLAB-X 6.02 I am able to compile the C code using the CCS compiler loaded into MPLAB-x 6.2 and burn the PIC24FV32KA302 chip with no problems. I had to upgrade to the latest CCS compiler to get it to work

[temtronic]

OK, in MPLAB, what have you chosen for the 'build configuration' ?
The default is 'debug'.....

Have you tried another series of PIC ?

I use PICkit3 and burned lots of 18F46K22 pics over the years with MPLAB v8.92. Zero issues. I do however dedicate the ICSP pins ONLY for ICSP.

[jimzum]

based on your last comments this is what I thought you were going with this discission.

I want to use the CCS C Compiler (PCWHD version 5.11 package) to code, build, load and troubleshoot my project, use a PICKIT 3 to program not the ICD-U64 programmer. My PC boards are verry small less than 5 sq inches in area, and the ICD-U64 programming connector is to big.
I have tried to adapt the ICD-U64 to use the micro programming cables I use with mixed results. The PICKIT micro cables work fine.

If I wanted to use a MPLAB I would use the MPLAB-X 6.2 since it is new and it works. I have been using the MPLAB-X since version 1 to program pic processor using the CCS compiler over many, many years.

I would like to be able to program the PIC24FV32KS302 USING a PIKKIT programmer USING the CCS C Compiler suite package not a MPLAB package.

and yes I have used MPLAB 6 to the last one 8.92 before moving to the MPLAB-X programs

[temtronic]

curious, when you goto 'device' can you select the 24FV32KS302 for the list ?
if so, can you read it ? can you erase it ?

[Ttelmah]

I think three things may apply:
Firmware
Power
MCLR

Now I know the PK3 (and the ICDU64), are both fussy about the firmware
version loaded when using the CCS interface. If I remember correctly, I had
to download the PicKit3 programmer application. This then allowed the
firmware to be updated. You must select 'revert to MPLAB mode' before
exiting.
On power, I remember having issues, because the CCS setup defaults to
using a different algorithm to detect if the programming voltage is adequate.
Key was to ensure that short USB cables are used, and the device supplying
the power genuinely gives 5v. I think this is actually the one that is
probably causing the issue (it caused real grief for me). The voltage at
the PK3 has to be over 4.5v, to work with the firmware used when
programming from CCS. The code used by MPLAB is slightly more
lenient on the power requirements.
MCLR is also fussy. The PK3 had problems programming quite a few
chips if NOMCLR was selected, Again these programmed OK from MPLAB.

[jimzum]

temtronic Yes I see the PIC24FV32KA302
The status is GOOD

In the CCS Device Programmer when I click on diagnostic
Software 5.085
Firmware BLANK
Hardware: Rev 0 (PID 0)

Clicking on the Firmware update button
CCS ICDS for PIC16 targets v01.39 OR
CCS ICDS for PIC18 targets v01.39
Nothing else

[temtronic]

some PICkit3 comments

1) cable length is real important, shorter is better ! I added a 6pin M-F 'header' to the PK3 connector as an 'extension'. This allows it to nicely fit the 6 pins on the PIC PCB. ZERO issues with 'lack of communication'.....

2) PIC power can be from PK3 or the 'project'. The PK3 can only supply MINIMAL current,which can cause 'issues'.

3) Which PK3 version ? Older ones had a 'power' issue, which I think was solved by bypassing a resistor ? I remember seeing the bulletin on it,thinking, right...SMD are really ,really small..ain't no way I can do that !

[jimzum]

Yes I have been using a PICKIT's for about 20 years. The cable from the PICKIT 3 cable is about 4 inches in length. Been working on the current project for 3 years (home project retired) and until my computer failure, I was programming and burning the picks from MPLAB-X 5.5 with no problem.
I am going back to PMLAB-X 6.2 for the project.

Note I like the CCS debugger better than the MPLAB debugger, which is why I wanted to use the CCS C Compiler program.

I found using the ICD-U64 with a similar cable, the cable length has to be less than 4 inches for it to work reliably
the Firmware Suite Version.....01.56.09 on the PICKIT 3

point 2: the power to the chip comes from the PC board 5 V 300ma supply


I also have a PICKIT 4, and have tried to use it, but get the same results
point 3 the pic is BUR195068601 which I purchased from Microchip back in 2017, 2018 time period

[jeremiah]

[diode_blade]

Just a quick note on this.
I found that under windows 10 I had to install MPLAB and CCSC software inc debugger drivers as administrator, otherwise nothing would work.

Also be warned, I had just bought a 16 channel strain measurement test kit, second one I have done.
Got the kit everything worked fine, then both my PC and laptop did windows auto updates. The kit stopped working, uninstalled and re-installed the software, result was the same.
Sent the hardware back to the manufacturer, they checked it out and it was working fine.
Kit was sent back, in the meantime another windows update had happened, plugged the kit back in, bingo it was working again.

Should mention that the above kit is nothing to do with CCSC or Mplab hardware or software.

[temtronic]

Ah yes, the magical, mysterious automatic updates of Windows OS and programs.....
I got stung years ago, cutting PC host program in DELPHI.No formal training, no books, just 'cut and try', got it to work, then couldn't find the PIC on the USB port one day. After 2-3 days of 'it HAS to be ME'.. I went into 'DOSmode' (go back to basics,look at 'low level' stuff. USBVIEW found the port in question and the power level had been changed ! So PIC PCB didn't get all the current it needed. Sigh. Change the power register, it's alive! Since then I've disabled every program and OS from 'auto updating.
I'd like to go back to Windows98SE and PIC with quartz windows please. Life was much better then !

[dyeatman]

I have all my development PCs (including my Delphi system) in the Microsoft
Beta channel. This way I get a heads up when an update is going to break
something... and it has quite a few times.
_________________
Google and Forum Search are some of your best tools!!!!

[temtronic]

The best protection against unwanted updates.... do NOT have the PC connected to the Internet !
Frankly PCs are so dang cheap you should have a DEDICATED PC for PICwork. Can't think of any good reason why not.

[Ttelmah]

One question.

What is your Windows version????.

There are reports that the CCS plug-in with both the Pickit3 and Pickit5
fails under Win11. Same hardware works under Win10 or Win7.

Errors are the same as you are reporting.