Cool. Would it be possible to show the current value of the parameter being changed?
Retro Canada any idea what could cause the color issue described here?
Cool. Would it be possible to show the current value of the parameter being changed?
next time but it will be probably a progress bar
Done. Now you have a nice progress bar.
OK, cool. I loaded the new firmware. I like it, for the most part. I'd like to see a longer timeout on the display of the current parameter. Also a number value instead of or along with the progress bar would be nice. It's difficult to remember the position of the progress bar, making it hard to repeat results. I wish the adjustments could be saved so that when the power is turned off, it would remember its last settings. Maybe the firmware could be reprogrammed once one finds the ideal settings for a particular setup so that the device defaults to those settings.
Thanks Again
Greg
Thanks for the reply, I am using a board from dreamblaster - he assembled it and with a visual inspection it looks fine - it's all smd as you'll see when you get yours.
I also tested a different EGA card and a different lcd monitor , still the same results. It almost seems to me that something is going on with the intensity pins?
printing numbers would be much more complicated and I am not planning it soon...
OK, cool. I loaded the new firmware.............
OK, understood. What about my other suggestions?
1. I'd like to see a longer timeout on the display of the current parameter.
2. I wish the adjustments could be saved so that when the power is turned off, it would remember its last settings.
3. If number 2 is not feasible, Maybe the firmware could be reprogrammed once one finds the ideal settings for a particular setup so that the device defaults to those
settings. Could you give some pointers here. I'm not much of a programmer, but I think I could make the adjustments needed if pointed in the correct direction.
Best Regards,
Greg
...For 1: in the Quartus II code there is a module callled ctrl_params.vhd there is a
peak: integer range 0 to 128*1024*1024 := 0;
make it to 256*1024*1024 in both lines (it sets the value after)
I'm a little confused here. I can only find one line in cntrl_params.vhd with the exact string "peak: integer range 0 to 128*1024*1024 := 0;"
you say to change "in both lines". Where is the other line?
Yeah, the ones that came with some of the kits, give my computer a BSOD! I used one like THIS.