|Re: NoVRAM Module|
Message #2 Posted by Vieira, L. C. (Brazil) on 6 June 2007, 10:18 p.m.,
in response to message #1 by Jeff Davis
please, forgive me if I am heading the answer prior to wait for Diego´s post. I have both NoVRAM and NoV32 modules, and I have programmed them many times. Some days ago I reprogrammed my NoV32 a few times prior to match my needs.
Quote:Yeap! Just configure the ICPROG to work with the 18F252 and, after reading (there is a button to read contents, too) you'll see the current configuration (.ROM file names) in the lower, small window.
Can I use the icprog software and use the F8 function to read the existing contents of the NoVRAM module?
Quote:I use the programmer sold by Diego, and had no problems so far. It is a good idea to read all documents related to both Clonix and NoVRAM. The procedures explained in the Clonix manual apply to the NoVRAM as well, added the complementary explanations found in the NoVRAM manual.
I wanted to ask before trying this so I do not damage the NoVRAM Module.
Quote:What I actually do is to prepare the configuration with the novram-h.exe, save it and wait till the ICPROG opens automatically. Then I have the NoVRAM programmed. You see, the 16KRAM only make sense when you use some sort of software to handle it, like HEPAX, David Assembler... You probably know about this, sorry, just to make sure. I configured my NoV32 to run HEPAX and David Assembler with the additional label ROM, and it works fine (I cannot access the second 16KRAM page, though, but this is another story...) So, when I want to use the HEPAX emulation with NOVRAM, novram-h.exe must be used to create the necessary files. I think that some of the files you mention are used as temporary buffers (the H might be related to hex coded data), because only the NOVRAM-H.HEX file seems to be used. As mentioned in the Novram manual, it is possible to invoke the ICPROG with a command line that specifies the .HEX file you want to use instead of the default NOVRAM-H.HEX. I have also executed ICPROG directly and then I explicitly opened another .HEX file and programmed the module. Worked fine as well.
When I tried the NoVRAM-h.exe I end up with 4 different files. romimg0H, roming1H, mappingH and sgnaturH. How do these files work with the icprog software?
I hope I did not miss anything. Anyway, it would be wise to wait for some extra help.
(Tomorrow is a Holliday here, so I found some time to write a few words in some posts today. Feels good....)
Edited: 6 June 2007, 10:21 p.m.