No, my display is working fine for everything on the transistor tester...only the function menu Frequency blanks after a second or 2 into the menu and then the tt is frozen...only way to get it back to work is to unplug battery.
When I unplug battery and start the tt, it works just fine. Can't get the function Frequency to work however.
As I wrote above, everything works normally.
The attached file contains the software that I tested:
Thank you Tom..I'll give it a try and let you know if all is fine.
... My version of avr-gcc is 4.8.1
So I wonder why I don't compile to the same file size as yours and why some functions (like frequency) don't work properly? ...
Both eep files are 56 bytes. My version of avr-gcc is 4.8.1
So I wonder why I don't compile to the same file size as yours and why some functions (like frequency) don't work properly?
Hi Scott,
I also have both Pis : model B and Pi2. They can write .hex files in Atmega, with or without bootloader. The 'gpio' programmer makes bit-banging on 4 serial lines, simply flashing an .hex file. You can afterwards use the bootloader with an ordinary serial interface, but with little or no interest as you're obliged to have the previous programmer to flash the bootloader the first time.
If the lock bits are set, only 'parallel' programmers can reset the device. In all other cases you can re-flash the fuses.
Out of factory the Atmega are configured with internal RC oscillator. You can then put the device on a breadboard without any crystal circuit. If you then configure the fuses to crystal oscillator, further programming will require the crystal on the breadboard (or on the target board if you're using ISP).
Denis
I also noticed that IDE on the Mac is using AVRDude in the background for the programming, so IDE is just a sketch editor, compiler and AVRDude does the flashing?
So what is the advantage (if any) of running the full raw AVRDude over using IDE besides being able to use some switches like -F for ignoring the signature of a chip? And even that could be fixed in the conf file.
Yep, avrdude is the common tool to program AVR's fuses, flash and EEPROM. It doesn't matter if you run it directly in a shell or via the IDE. I prefer a simple "make upload" to program flash and EEPROM , or "make fuses" to set the fuse bits. Someone else might prefer a fancy GUI. Another useful option for avrdude is "-B <bitclock>" in case you have to deal with a clock problem. I don't know if most IDEs support that option.
... My version of avr-gcc is 4.8.1
So I wonder why I don't compile to the same file size as yours and why some functions (like frequency) don't work properly? ...
Try my updated WinAVR-20100110 - link expires after 48 hours.
Where can one find the changelog for the different revisions of version 1.12k (508, 509 and now 510) ?
... What is confusing, is that the already compiled version of the hex file in the directory mega328_t3_t4_St7564 (compiled by Karl Heinz I think?) for release 508 is 81 304 bytes ?? ,,,
Where can one find the changelog for the different revisions of version 1.12k (508, 509 and now 510) ? ...
I found these boards on banggood and I'm thinking to buy one of these.
Which one should I prefer? 16x2 or 128x64 screen? Which one has the latest firmware and which one follows the original schematic with good quality components? Could I reflash the firmware by downloading the latest one from Karl-Heinz's repo?
The quality of the components is the same. In principle, no matter which device you buy, because the only difference is in the used type of LCD and control. Both devices are identical to the basic schematic diagram and can therefore use the official software from Mr. Karl-Heinz.
Hi, I recently purchased the newer DIY kit from Banggood:
http://www.banggood.com/DIY-M12864-Graphics-Version-Transistor-Tester-Kit-LCR-ESR-PWM-p-986954.html
...
My questions is which branch directory is the correct build for this board and LCD? The main /mega328, /mega328 GM328?
Hmm, didn't work the display is unreadable. Going to try some others.
mega328_wei_st7565/ Appears to display properly, but it's reporting the voltages wrong, looks like half.
Its data layout and font are much different than the original firmware, I am wondering if the creator wrote a custom firmware for these.
Thanks, will try it as soon as I get home.
I'm new to compiling, but I am going to try to get the make file to compile locally as well, figured it will be a good thing to know how to do.
Hi,
I finished my transistor tester. Sometimes when i test caps it shows me n-d-mos, between pin 1 and 2. Between 1 and 3 it's ok! Is this normal?
Sometimes when i test caps it shows me n-d-mos, between pin 1 and 2. Between 1 and 3 it's ok! Is this normal?