Hi,
We can not verify the wiring as long as you don't show it to us.
What is your power supply and what voltage? Did you check stable voltage during programming?
What clock source do you use at the target device?
Klaus
Hi,
A microcontroller needs some basics to operate correctly.
Read the datasheet, because it differs from type to type.
* all power supply pins connected? Including the Analog section?
* ceramics capacitor close at each VCC pin?
* Reset circuit?
* others?
* clock circuit / clock source? I assume the factory setup is to operate from internal clock...but as soon as you modify the fuses to any other clock source it may refuse to respond.
Use a new microcontroller and manage to get a valid communication. Reading only. Chip ID...memory contents...
With this you can verify that all your connections are correct.
Be careful with programming clock fuses or brown out fuses....
Klaus
Post your procedure you are done . the image didint shows Crystal. So what type of clock you are done ?
The USBASP uses the ISR recording interface of the AVR, which has serious issues with regard to some Fuses, namely the inability to reprogram them. In case, if in the first recording you had for example setting in the program "External Oscillator", you will not be able to carry out a new update in the firmware if using in the actual hardware a "Crystal" unless inserting an external signal in the clock pin, but this was somehow already mentioned before by others.
What I mean is that without showing the screen of the program software with what was actually set there, and without detailing the hardware, it will not be possible to determine if your uC has already become unusable in the current configuration.
As you should know by reading datasheet, CKSEL=0001 means "reserved", which is hard to know which configuration will be set by default on this case (perhaps this information is also on datasheet)
Below attached are screenshots of Atmel studio showing error and progisp showing Fuse and lock. The settings of fuse and lock are default values, I haven't changed any of them.
When I click on detect uC, it gives the above error.View attachment 144264View attachment 144263
In case, if in the first recording you had for example setting in the program "External Oscillator", you will not be able to carry out a new update in the firmware if using in the actual hardware a "Crystal" unless inserting an external signal in the clock pin, but this was somehow already mentioned before by others.
I might be wrong but I remember that I solved this problem several time by inserting a random 8-20MHz (any of 8MHz, 10MHz, 12MHz, 16MHz, 20MHz or similiar) crystal between the OSC/crystal pins of Atmega. So it does not have to be the exact crystal used for the previous configuration...
I had a similar problem a while back - in my case it was a USB driver problem, I used https://zadig.akeo.ie/ and that helped to resolve the issue.
0xE1, 0x99 is 1Mhz only
for 8Mhz you should use 0XE4 ,0X99.
LCD works according to the command with specific time as in data sheet ,if you use 1Mhz it might be not correct ,(assumption only )
https://www.engbedded.com/fusecalc/
A crystal oscillator is no RC.like Ext RC 8-12Mhz (x CLK + y ms) and
- - - Updated - - -
Hi
When I connect my usvasp to PC, it is not displayed in zadig. When I check with the user manual it suggested that, if a device is not displayed it means it already has driver and I can see the device under options. It further stated that I must be careful if I want to Replace driver.
Should I go ahead and replace the driver?
- - - Updated - - -
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?