New update available for Clonix & NoVs users.

[Allen]

Sylvain, Diego,

Thank you for your help! I think I have it working, after several hours!

Ah, I think part of the reason I THOUGHT the modules were loading correctly:

When I selected the ROMS (from a sub directory) in the Clonix Config seems to make a 0-byte file in the working directory (if it does not exist) with the same name, then tries to load the 0-byte file into MPASMWIN.

It's clear a zero byte file is being created with the same name. Would it be possible to actually have Clonix Config read read the ROM file that was selected (from same directory or from elsewhere?) and make a copy of that in the local "working" directory if that's what is required by the MPASMWIN.EXE? It seems that is what ClonixConfig is trying to do?

Attachment:
I didn't notice until this evening that these files were all zero-byte files I was trying to load, that were created by the Config utility in the working directory.

[Sylvain Cote]

Allen,
I got bitten by the same mistake when I configured my first Clonix module in 2012.
I thought that you knew, sorry for not mentioning it, having the ROMs in the same folder as ClonixConfig has always been a requirement.
Even thought the NoV-64(d) configuration seems to works the Clonix-D configuration does not and my ROMs are in the same folder as CC.
I am stopping testing for now, I will do more testing tomorrow before and after HPCC mini-conference.
Sylvain

[Allen]

ironically I used to have all the roms in the right place, but with the October 2020 update, I took the opportunity to "clean" up my directories, which had various Clonix versions of software ( and ROMS) for:

1. 2011
2. 2014
3. 2020-08
4. 2020-09
5. 2020-10
   

and I think a 2008 Version also??

Thank you again for your help, my mistake not keeping the ROMS where they were before my cleaning!

[Diego Diaz]

Hi,

Good to know you've managed to find the problem. ;-)

All the best from Dominican Republic.

Diego.

[Sylvain Cote]

Hello Diego,
I still have issue in ClonixConfig v6.1 when I program a NoV-64d module with the Clonix-D option.
When I program the NoV-64d module with the NoV-64(d) option, HEPAX 1D and PPC ROM, I see the ROMs when plugged into an HP-41.
When I program the NoV-64d module with the NoV-64(d) option, HEPAX 4H and PPC ROM, I see the ROMs when plugged into an HP-41.
When I program the NoV-64d module with the Clonix-D option, PPC ROM, I do not see the ROMs when plugged into an HP-41.
I have taken screen shots and the support files for each options.
The files are available HERE
Sylvain

[Diego Diaz]

Hi Sylvain,

I've checked your files and they're correct.

Please remember that Clonix-D is natively port-sensitive, therefore if you're about to use ROMs in one block only you should mark the Join Blocks box when programming a NoV-64d or repeat the ROMs selection in the other block when using an older NoV-64.

I've also checked with my own NoV-64d and found PPC on CAT 2 as expected.

Hope this helps.

Best wishes.

Diego.

[Sylvain Cote]

Thanks for trying on your side.

(01-09-2021 04:09 PM)Diego Diaz Wrote:  Please remember that Clonix-D is natively port-sensitive ...

Yes, I know and that is why I tried the module in odd and even ports.

It turn out that I have a hardware problem with the module I was using for testing.
I try the same thing with my other NoV-64d modules and it works.

I will do more tests with this seemingly defect module and will be back with the results.

Sylvain

[Sylvain Cote]

(01-09-2021 04:52 PM)Sylvain Cote Wrote:  It turn out that I have a hardware problem with the module I was using for testing.
I try the same thing with my other NoV-64d modules and it works.
I will do more tests with this seemingly defect module and will be back with the results.

First, my module is perfectly working, the problem was related to a special configuration that I did to test something for the HPCC presentation.

I spent most of the day doing all kind of tests with three NoV-64d modules, three ClonixConfig versions (4.2 2015, 4.2 2020 & 6.2 2020) and tested on two HP-41 (CX HN & CL FN MMU disabled).
And it turn out that something got broken with the 2020 releases. (4.2 & 6.1)
A NoV-64d programmed as NoV-64d ...

• The default 4100 configuration is now at 000 instead of 100.
• More importantly, the 000 configuration is now equivalent to 200, meaning that there is no way to disable the Flash block mapping anymore.
  

I have not finished the tests for the NoV-64d programmed as Clonix-D, so the results will come later this week.

Sylvain

[Sylvain Cote]

Still testing three NoV-64d modules with three ClonixConfig versions (4.2 2015, 4.2 2020 & 6.2 2020) and on two HP-41 (CX HN & CL FN MMU disabled).

Basic test setup:

Code:

Software      : ClonixConfig 6.1 2020
Module used   : NoV-64d
Module type   : Clonix-D
Programmer    : PicKit2
Flash Block 0 : MATH-1D [1-8] : STAT-1B [1-9] 
Flash Block 1 : PPCL    [1-8] : PPCU    [1-9]

Testing NoV-64d Module #1 → Success

Code:

Calc   : CX         : CX         : CL         : CL         : 
Port   : #1 Odd     : #2 Even    : #1 Odd     : #4 Even    : 
CAT 2  : -MATH 1D   : C PPC 1981 : -MATH 1D   : C PPC 1981 : 
       : STAT 1B    :            : STAT 1B    :            :

Testing NoV-64d Module #2 → Failed

Code:

Calc   : CX         : CX         : CL         : CL         : 
Port   : #1 Odd     : #2 Even    : #1 Odd     : #4 Even    : 
CAT 2  : C PPC 1981 : C PPC 1981 : C PPC 1981 : C PPC 1981 : 
       :            :            :            :            :

Testing NoV-64d Module #3 → Success

Code:

Calc   : CX         : CX         : CL         : CL         : 
Port   : #1 Odd     : #2 Even    : #1 Odd     : #4 Even    : 
CAT 2  : -MATH 1D   : C PPC 1981 : -MATH 1D   : C PPC 1981 : 
       : STAT 1B    :            : STAT 1B    :            :

Sadly it does seems that my NoV-64d module #2 is defective after all.
I have made sure that all the connector pins do make contact.

Diego, do you have some idea on the source of this problem ?

Best regards,

Sylvain

edit 1: typo

edit 2: I just tried with ClonixConfig 4.2 2015 with the three modules and module #2 is still problematic.

[Diego Diaz]

Hi Sylvain,

Seems you've properly identified the source of the problem; most likely a cold solder joint failure.

I'll send you a new NoV-64d as soon as I get back home by early Feb.

Will mail you to arrange timely shipping of the defective one for service.

Best wishes from Dom. Rep.

Diego.

[Sylvain Cote]

Hello Diego,

(01-12-2021 08:42 PM)Diego Diaz Wrote:  Seems you've properly identified the source of the problem; most likely a cold solder joint failure.
Will mail you to arrange timely shipping of the defective one for service.

Thank you, take your time when you are back, there is no rush, it's not like I do not have spare modules here.
Let me know when you want me to send you my defective module.

The issue regarding the 4100 configuration value is still opened thought.
NoV-64d module Flash block mapping behaves correctly with the 2015 4.2 version and behaves incorrectly with the 2020 4.2 & 6.1 versions.
Again, no rush.

Best regards,

Sylvain

[PeterP]

(10-16-2020 07:27 AM)Diego Diaz Wrote:  Hi all,

I've made a new archive, updating all the latest changes and improvements, removing some old files no longer required and several minor bugs.

The link can be found at the bottom of my web:

Clonix41.

Since the most comprehensive ROMs collection is now mantained and regularily updated at Systmeyde site, a link to the coresponding page is also provided and the ROM files are no longer included in the Clonix upgrade archive.

Hope you find it useful.

Let me know of any issue you may find.

Best wishes and keep safe.

Diego.

Diego, amazing, as always. Quick question - is it possible to program the original Clonix/Nov/Nov32 etc with your new fancy programmer? Or would I have to use the old one?

[Diego Diaz]

Hi Peter,

The programer itself is fully capable of handling all the modules including the previous 32K ones (Clonix-41, NoVRAM & NoV-32); although the current utility Ver.6.1 only configures the current 64K ones: Clonix-D, NoV-64(d) and USB-41.

In order to use the new programmer with these previous modules you'll need to configure them using the Ver.4.2 utility; this will create a .HEX file (Clonix-41.HEX, NoVRAM-H.HEX or NoV-32-H.HEX) which you can then open using the new programmer's SW and load into the module at will.

Hope you find this useful.

Best wishes.

Diego.

[PeterP]

Thanks Diego, I *think* I understand what you say and will try and iterate and report back if I cant figure it out!

Thank you so much!

[Diego Diaz]

Hi Peter,

I remember I made this video back in August to cover this specific issue.

https://www.youtube.com/watch?v=RPTLk71u-OM

Hope this may help to clarify the steps. (Forgive my English... ;-)

Best.

Diego.

[PeterP]

wonderful!

Thank you Diego, very much appreciated!