Nov64d & PicKit 2

[Papymouzot]

Hello,

I am running into an issue with my first tests of the Nov64d module I received from Diego a couple of weeks ago.

I first tried to create a service module, and it didn't compile correctly, I had an issue with the path being too long...

when I solved this, The created "module" hex file got created I I could write to the module, but when I plugged it in my calculator nothing happened... When I looked in cat 2 the module was invisible

I reprogrammed the module with the default hepax hex and the module seems to have been programmed again and the program I had in ram was still there and I could run it.

Today I tried again...

I used Clonix config utility v6.1 to create a Hepax 1D module plus the advantage module, nothing extraordinary, it seems to be working and PicKit 2 is launched, and this is when I have issues.

I get PicKit 2 VPP voltage level error, check target and retry operation" from time to time, and otherwise I get for the device "unsupported part (ID=3FED)" most of the time. it is impossible to write to the module, although the first time, a few weeks ago, it seems to run fine

When I try the module in the calculator, it still sees the hepax module. and my program

what am I doing wrong ?

what could I test ?

[Hiwi]

Try a different USB port.
Same issue?
Nov64d module connected correct? position , direction?
Nov64d module should be connected before programming/ compiling.
Ralf

[Papymouzot]

Hello, I have tried different USB ports, same punition.

The Picket 2 programmer actually stayed in the usb port since my first attempts.

When I do check communication, it seems that the software of picket sees the module, and when I try to read or write I get errors like if the module could not be found. I have tried both ides of the module...

Do you think the Picket programmer could be faulty ?

An error with a parameter of the Picket software ?

[Sylvain Cote]

There are several rules that you must follow with Clonix configuration software if you do not want to have problems.

Some of these are:

• ROM files must be in the same directory as the ClonixConfig61 software.
• ROM filename must follow the old 8.3 naming with no space in it.
• In PicKit 2 programming software, the hex firmware must be loaded manually.
  • click on the "Auto Import Hex + Write Device" push button to bring up the "Import Hex File" dialog.
  • make sure the current directory is the same as the ClonixConfig61 currently running. (I have been bitten several times on this one)
  • select the "AutoImprt.HEX" file in the file list (date and time should not be older than a minute)
  • press the "Open" push button to load the file and start the programming session.
    

edit: typos

[Diego Diaz]

Hi there,

All of the previous advices are correct.

In most cases the PicKit2 'Vpp' or 'not device recognition' warnings are due to poor connection between the module and the programmer's edge pads.

Cleaning the pads with a soft pencil eraser is often enough to recover good connectivity though, eventually, prying the module contacts a bit (with a wooden toothpick) may help.

If you cannot get a reliable and consistent programming process please let me know to check for other possible causes.

Best wishes from the Canary Islands.

Diego.

[teenix]

It is interesting in a nostalgic way to see K149/K150 listed as a programmer choice in screen shot 3.

I designed the original hardware and wrote the PIC programming software for that kit along with the K128 and K150 PIC programmers for Peter Crocroft when he was running KitsRUs.

Things do seem to run in circles

cheers

Tony

[Papymouzot]

Thanks,

I will try to follow these advice and come back to you

Charles