New update available for Clonix & NoVs users.

[Diego Diaz]

Hi Allen,

According to your screenshots, it seems that the Config (v6.1) is effectively producing the proper .HEX file under MPASMWIN.EXE compiler.

In order to confirm that this is the file your're loading into the PicKIT2 programmer SW please scroll down in the bottom window "EEPROMdata". You should see a list if the ROM files and Page/Bank configuration mapping for the module to be programmed with.

Also the timestamp at the top of this very window must match with your file.

In case you find any mismatch in these records, chances are that you're loading a previous Clonix-D.HEX file from a different directory.

Note that the compiled file is placed in the same directory where the MPASMWIN.EXE is. Advisably you should keep all files in the same directory and as close as possible to your 'root' (C:, D:...)

For practical convenience, the PicKIT2 SW inlcudes an "Auto Import HEX + Write device" button.

If you use this accordint to the ClonixConfigv6.1 manual (last page) you should be loading the AutoImprt.HEX file wich is updated on every compilation instance by the Config utility hence ensuring you're loading the latest .HEX file you've created.

The Warning list on the .ERR file is not relevant and can be ignored.

Hope this helps.

Look forward to reading from you.

Best from Caribbean.

Diego.

PS: Not really relevant for the case but it would be advisable to load PPC .ROM files in the Even&Odd pages of the same port.