I've got the same (Banggood) version, the original fuse settings were...
L 0xFF
H 0xD9
E 0x04
LB 0x3F
I enabled the brownout detection using...
(I know that there have been problems reported when using brownout detection but if the power glitches I'd prefer to know and fix it - No problems so far.)
L 0xFF
H 0xD9
E 0x07
LB 0x3C
I used the precompiled .hex & .eep files.
Jim
Would you mind attaching the .hex & .eep files here?
Thanks, I tried FW1.11M328 but it displays rubbish after the power on screen? Could this be because of incorrect fuse settings? Seems the Flash and eprom program fine.
Thanks, I tried FW1.11M328 but it displays rubbish after the power on screen? Could this be because of incorrect fuse settings? Seems the Flash and eprom program fine.
Thanks, I tried FW1.11M328 but it displays rubbish after the power on screen? Could this be because of incorrect fuse settings? Seems the Flash and eprom program fine.
Flashed a firmware with a language that your display does not support?
Why would you want to do that? Simply try flashing a different firmware.
I'd like to suggest two things. First, if you don't have much money to put into a decent AVR ISP programmer, just get the cheapest one from eBay. There is no need for HV to program fuses unless your chip refuses to be programmed via ISP, and it beats trying to get Arduino to do something that it doesn't like doing. Second, "garbage text" doesn't tell much. Images could help a bit in such cases.
Here's the rub, there are several modifications to the original design, crystal, LCD- GLCD display, voltage reference, HV zener, rotary encoder, Mega8, 168, 328... the list goes on. This makes it a little daunting to anyone unfamiliar with AVR programming.
I simply want to upgrade a banggood clone to 1.11k or possible 1.17m (is one better than the other?).
Seems I'm not the only person that had problems upgrading the firmware on an MK168. Based on this thread alone looks like most folks don't get it working without some help.
I've flashed pretty much any firmware I could find including the eeprom. Some power up with a bat & test screen but subsequent screens are garbage text. This is on a new ATMega328p, I didn't refresh the original with 1.05.
I've flashed pretty much any firmware I could find including the eeprom. Some power up with a bat & test screen but subsequent screens are garbage text. This is on a new ATMega328p, I didn't refresh the original with 1.05.
For a brand new ATmega you have to set the fuses, since the default setting is to use the internal RC as clock source and the 1:8 prescaler, resulting in an 1MHz MCU clock.
I've flashed pretty much any firmware I could find including the eeprom. Some power up with a bat & test screen but subsequent screens are garbage text. This is on a new ATMega328p, I didn't refresh the original with 1.05.
For a brand new ATmega you have to set the fuses, since the default setting is to use the internal RC as clock source and the 1:8 prescaler, resulting in an 1MHz MCU clock.
I got it working, it's an excellent bit of kit and I'm gobsmacked that you're the Markus that designed the thing
Nice going.
As far as my project I have given up on it for the moment.
Just do not know much about AVR programming and got to see if I can find a better noob training video.
I do know I was not sending anything to my chip. Read somewhere on this thread about the file size was too large. So that is most likely my problem.
So think mine in blank and giving me just a bar when the test button is pressed.
Not sure if I even have the correct programmer
Nice going.
As far as my project I have given up on it for the moment.
Just do not know much about AVR programming and got to see if I can find a better noob training video.
I do know I was not sending anything to my chip. Read somewhere on this thread about the file size was too large. So that is most likely my problem.
So think mine in blank and giving me just a bar when the test button is pressed.
Not sure if I even have the correct programmer
I got it working, it's an excellent bit of kit and I'm gobsmacked that you're the Markus that designed the thing
Great! And nope, I'm the Markus who does the m-firmware. The Markus who did the original design abandoned the project. Karl-Keinz (k-firmware) took over and I joined in.