Please read - I wish to help with the development of this product.I am experienced with Linux, Windows & macOS, I have no problem understanding concepts such as "$PATH", "ls", I am VERY much a command line person in regards to Unix OS' specifically.
Okay, I have Windows 7 and I have installed WINAVR, and I have also gone to:
https://www.mikrocontroller.net/svnbrowser/transistortester/Software/trunk/ and clicked
"Download GNU tarball" - I have it downloaded and extracted with 7-zip etc...
#1 I know what a "Makefile" is, in essence, but...
#2 Once unarchived, which DIR do I go into, and which file do I edit for my customisations, please?
#3 From which folder do I run "make", once I have edited my "Makefile", and saved it, from the above?
If you'd give me a "starters guide" (I tried searching this thread, it's a NIGHTMARE to find what I need!) I would very much appreciate it, and can then start helping people. I am a VERY fast learner, I just need a "kick start" guide to what DIR, what commands etc - I know how to flash the firmware etc, it's just the configurations I need explained to me, and how to "make".
WINAVR is in my "PATH" by the way, so that's all setup as default.
Thanks so much!
<UPDATE>
I think I've worked it out:Say I want to edit the options and compile the firmware for the "mega328_T3_T4_st7565" variant, I simply:
1/ Go to where that folder is, in my case
"C:\Users\Myname\Desktop\transistortester-trunk.tar\transistortester-trunk\trunk\mega328_T3_T4_st7565" and edit the "Makefile" for the options I want.
2/ Open a CMD window in that
"C:\Users\Myname\Desktop\transistortester-trunk.tar\transistortester-trunk\trunk\mega328_T3_T4_st7565" DIR, and run "make" ... right?
3/ Flash the freshly built .eep and .hex into my T4 and test, rinse and repeat until it works as desired.
Ah, once I had worked that out, I went to:
https://github.com/svn2github/transistortester/tree/master/Software/trunk... and read:
This directory contains the program source for all TransistorTester versions.
To build the programming files for your ATmega microcontroller
please change to one of the following subdirectories:
mega8, default, mega328, mega168_strip_grid, mega328_strip_grid, mega328_dogm and mega328_strip_grid_dogm
The mega8 subdirectory contains the Makefile to build the programming data for a ATmega8 microcontroller.
The default subdirectory contains the Makefile to build the programming data for a ATmega168 controller.
The mega328 subdirectory contains the Makefile to build the programming data for a ATmega328 controller.
The subdirectories with the _strip_grid ending contains the Makefiles for the different connection
of the LCD used for the strip grid board and can not be used with the normal connection of the LCD.
You can find the programming data and the matching Makefile for the DOGM style LCD in the subdirectories
with dogm ending (mega328_dogm and mega328_strip_grid_dogm).
All subdirectories hold the Makefile the compiled data TransistorTester.hex and TransistorTester.eep!
The .hex data must be loaded to the flash memory and the .eep data must be loaded to the EEprom memory.
With the Linux operating system or with WinAVR the data can be loaded with the program avrdude to the
memory of the ATmega, controled with the Makefile. The connected ISP programmer must be supported by the program avrdude.
The data can also be loaded with any other program to the ATmega without control of the Makefile.
You can also create a own subdirectory and copy any of the Makefiles of the other directories to this
own subdirectory. Now you can set other options in this Makefile copy in your directory and try to build
your own TransistorTester programming data in this directory.
Please tell me, if you have problems with my software or if you have found errors.
You can send me a Email to kh_kuebbeler@web.de or answer to my www.mikrocontroller.net thread.
Good luck
Karl-Heinz KübbelerSo it seems I was on the right track?
I did a test "make" from the folder named above, and also saw the "107%" error for the main .hex, which was mentioned elsewhere due to inefficiencies in a new(?) toolchain, etc, as seen here:
How do I fix that? Clearly I can't fit 107% of something into 100% of program space, hah!
I saw "AVR Studio" mentioned somewhere - I take it that is not a pre-requisite? Not a problem if it is, but I get a hunch it's not needed.
See, I am a fast learner!
Cheers for your assistance, take it easy, I'll come back in about 10 hours or so. Sleep time now... zzzzzz