So, it looks like I have what I need, Ardunio uno, breadboard , Ardunio IDE which also installed Avrdude. But I still do not understand how to get the Hex and eprom file into the ardunio world? Like I keep trying to get across , all the tutorials on using the arduinio as a ISP, show loading the blink sketch into a blank micro which is already in the sketch folder and it's a INO type. I need to know how to get a non INO file into (I guess) the sketch folder, is this right? Also what is this Makefile thing? Does it have to be loaded into the sketch too. And how do load/start Avrdude, which you guys say is included in the Ardunio IDE, I didn't see it anywhere in the menu's? Totally frustrated! Why can't this stuff be drag and drop!
"Just get the compiled files and use them", could you clarify that statement-How do you do that?, I don't understand. How do I upload the bin files to the Arduino IDE? Where do I put them in the Arduino IDE? I have downloaded the file folder called Component-tester 1.34m, there are tons of files, which files do I use? There is a ton of .c ,.h, files, I see no .eep files. Am I to assume that the .h is the .hex files? I have the M328kit as shown in the previously posted PDF.
The one with the black PCB seems to be pre-assembled (?), since it mostly uses SMD parts.
You might want to check whether it also uses a SMD version of the ATmega328P microcontroller, or if it still uses the more conventional DIP version.
If it's the SMD version, you might find it harder to flash new firmware onto it via SPI compared to just removing the DIP package from its socket and plugging it into a breadboard.
I own the red AY-AT variant.
Both are AY-AT based clones. There are also a few testers with ATmega 644 (more flash) but they don't use the additional I/O pins for hardware options. At the moment the AY-AT is still the best choice when buying. If you want all the cool stuff you have to DIY.
Both are AY-AT based clones. There are also a few testers with ATmega 644 (more flash) but they don't use the additional I/O pins for hardware options. At the moment the AY-AT is still the best choice when buying. If you want all the cool stuff you have to DIY.
The differences are explained in the m-firmware's README file. The m-firmware doesn't support the SamplingADC, but it offers an IR RC decoder, IR RC sender, dedicated optocoupler check, servo check, OneWire (DS18B20), touchscreen, remote control interface via serial port, and some measurements/checks are done a little bit different.
I have several questions because I'm really confused now:
I found this link with great resources about this tool ( probably most of you know this link ):
https://yadi.sk/d/yW8xa5NJgUo5z
There is two jpg, one is labeled with:
LCR-T4(T3)NoStripGreed ( actually this is my hardware )
And one is labeled with:
LCR-T4(T3)StripGreed
So, what this means "StripGreed" & "NoStripGreed" ?
Which version of firmware is maybe better? Or how to determine the right version?
1.13K or 1.13M ?
Or even can I mix up the versions?
Now I have an 8MHz oscillator on my pcb, is it prefferable to change it to 16MHz?
I can see there is the same unit with 8 and 16MHz osc...
/*
* power control
*/
#define POWER_PORT PORTD /* port data register */
#define POWER_DDR DDRD /* port data direction register */
#define POWER_CTRL PD6 /* controls power (1: on / 0: off) */
/*
* test push button
*/
#define BUTTON_PORT PORTD /* port data register */
#define BUTTON_DDR DDRD /* port data direction register */
#define BUTTON_PIN PIND /* port input pins register */
#define TEST_BUTTON PD7 /* test/start push button (low active) */
#define ENCODER_PORT PORTD /* port data register */
#define ENCODER_DDR DDRD /* port data direction register */
#define ENCODER_PIN PIND /* port input pins register */
#define ENCODER_A PD1 /* rotary encoder A signal */
#define ENCODER_B PD3 /* rotary encoder B signal */
#define HW_ENCODER
#define ENCODER_PULSES 4 /* usually 4 pulses per step */
#define ENCODER_STEPS 20 /* usually 20 detents */