r0bbie wrote:Thank you for the reply Dmitri,
I have changed a few things, like new firmware for pic and Atmega,new USB connector and cable, plus an extended display + keyboard, inspired by the latest treads in the Megadrum gallery with the Nintendo controller.
First thing I noticed after the changes and firmware update was that, first lcd contrast was not right, so I adjust, save changes, set auto load to yes, cycle power, and have to adjust contrast again!!! After repeating this 3 more times it was finaly stored. Then I came to MaxInputs setting, I became more aware that something was not working right.
The conclusion up til now is that, storing various settings in non-volitile memory is not consistand, using the keyboard or MDM.
I wil revert hardware changes I have made and try to find what is causing this problem and wil report.
Regards,
Rob
Hi Dmitri,
I have reverted all changes exept the new USB connector, still have the problem saving to non-volitile memory.
I have checked the voltage and it is 4,75 Volts at the PCB, shouldn't be a problem.
I have put in my old "non encrypted bootloader" Atmega and have kind of the same promlem,for instance;
-power up MD
-change contrast to the lowest visable setting
-save changes to slot 1
-make sure Autoload Conf =Yes
-cycle power
Contrast is not the same as saved.
but other changes I have made like Altencoders or ChainID and more are still correct.
I am puzzled what could be causing this?
Hope you can help.
Regards,
Rob
If it ain't broken try to improve it.