HP Forum Archive 18

[ Return to Index | Top of Index ]

NoV-64 is ready! :-) Preliminary info. Message #1 Posted by Diego Diaz on 21 Sept 2008, 6:12 p.m. Hi all, Finally, NoV-64 is fully operative. Main features: - 48K (12pages) Flash ROM distributed as follows: ... 4 pages (block 0) holding Advanced HEPAX emulation. ... 4 pages (block 1) to load primary user selected ROM images. ... 4 pages (block 2) to load secondary user selected ROM images. Block 0 is always active providing HEPAX functionality. Block 1 is active by default when the module is plugged. (uses ports 1 or 2) Block 2 can be swaped with Block 1 by means of control word at address H'4100 (explained below) Allowed pages for ROM blocks are #C to #F Also both blocks can be disabled by means of such control word. - 64K (16 pages) non volatile RAM. ... 4 blocks of 4 pages each, addressed to pages #8 to #B, can be used as HEPAX RAM or to hold ROM images the way Advanced HEPAX does. Active RAM block is also selected by means of control word at H'4100. There always be an active RAM block. Control word usage: HEXEDIT command allows direct access to any memory position. Enter: 4100 at the [ADR: _ _ _ _ ] prompt. You'll see [4100 100 _ _ _ ] Bits meaning of control word: b9: 1=ROM block 2 enabled, 0=ROM block 2 disabled. b8: 1=ROM block 1 enabled, 0=ROM block 1 disabled. b7-b2: Not used. b1-b0: 00=RAM block 0 enabled, 01=RAM block 1 enabled, 10=RAM block 2 enabled, 11=... mmm, sure you can guess that one... :-) Example 1: To enable ROM block 2 and select RAM block 3, write 203 into H'4100, then turn your HP-41 OFF and ON again. Example 2: To Disable both ROM blocks and select RAM block 0, write 000 into H'4100, then turn your HP-41 OFF and ON again. ROM block 1 has precedence over block 2. In case bits 9 & 8 were both set to 1 bit 9 will be erased leaving only ROM block 1 enabled. Clearing bits 9 & 8 will disable both ROM block allowing the use of ports 3 and 4 to plug physical ROM modules in. Changing the RAM block will be effective inmediately. To swap or disable ROM blocks power cycling the HP-41 is obviously needed. It'll still take a few days to update my web page with fully detailed info, and include NoV-64 into the new Windows Configuration Utility, however any comments, questions and/or suggestions will be welcome. Best wishes from the Canary Islands in this last Summer day. Diego.

Re: NoV-64 is ready! :-) Preliminary info. Message #2 Posted by PeterP on 21 Sept 2008, 10:13 p.m., in response to message #1 by Diego Diaz cant wait to play with one of these babies! Great stuff Diego!!

Re: NoV-64 is ready! :-) Preliminary info. Message #3 Posted by Les Wright on 21 Sept 2008, 11:19 p.m., in response to message #1 by Diego Diaz Looks great. I am glad I have held off placing my order with you. Looks like this is the thing I want, when I get it.... Les

Re: NoV-64 is ready! :-) Preliminary info. Message #4 Posted by Diego Diaz on 22 Sept 2008, 1:47 a.m., in response to message #3 by Les Wright Thank you both... A little bit more info and a couple of pics at my site. Best wishes for the upcomming Fall. Diego.

Re: NoV-64 is ready! :-) Preliminary info. Message #5 Posted by PeterP on 22 Sept 2008, 1:55 a.m., in response to message #4 by Diego Diaz Diego, One more thing. As you know, I think I have the same USB burner as you but I remember that you said something about certain modifications necessary to use it. I really do not want to buy another USB programmer so if you could be so kind and enlighten me on what I need to do to use the programmer I have with your Nov64, that would be awesome. Thanks! Peter

Re: NoV-64 is ready! :-) Preliminary info. Message #6 Posted by Diego Diaz on 22 Sept 2008, 2:39 a.m., in response to message #5 by PeterP Hi Peter, Currently only K149-BC USB programmer is supported. Most USB small programmers out there are of this kind. These programmers use a PIC micocontroller to program the rest of PIC's, you'll see it in a socket beside the ZIF. It's a PIC16F628. The program supplied with the origional programmers, does not include the protocol to handle the NoV-64 processor (PIC18F2620), further more, the device list does no includes the PIC18F2620 parameters definition either. So you'll need a new 16F628 to burn the new protocol in it. I upgraded the 16F628 on every USB programmer I supply, and obviously a modified chip definition file including PIC18F2620 parameters is attached to the mini-CD. However, there is no way I can guarantee the proper operation of your USB programmer. Or the steps required to upgrade PIC16F628 with your current sowtware. Please mail me to see how can we find a suitable work-around. Cheers. Diego. Edited: 22 Sept 2008, 5:41 a.m.

[ Return to Index | Top of Index ]

Go back to the main exhibit hall