felezjoo PI(the best pulse induction metal detector that I made until now)

[eclipse]

If you're burning chips PROBABLY the connections from your programmer to your Atmega chip are wrong.
Even if you don't succeed in programming the chip it should not burn, it will only show you that there's an error and ask you to remove the programmer and try again.

What Windows version are you using? I've used Windows 7 (wasn't easy to install) at first but since couple of weeks I've upgraded to Windows 10 and Extreme Burner doesn't seems to be working, so I've installed virtual Windows XP (Oracle VM Box) and worked like a charm.

There's a new version of the hex 3.05 here it is:

FelezJoo_PI_v3_05.rar

[bernte_one]

what my Buddy Nick means, is that we beed a step by step tutorial for dummies how to Flash these µControllers
with a Software we all can download and use and with a common programmer

i know there was something totally different in ponyprog and avr dude if you set the markings for fuse bits or so in ponyprog it is the total Opponent of the Settings in avr dude

if i find my last order of atmel Chips i will try this finally too at the next Weekends
but as i remember from past i got more error Messages and Driver Problems than any succes

there are some good instructions here in Forum, like " tgsl coil building" or "building a fast pi mono coil", now we Need "how to burn atmels without Magic smoke for dummie metal detector ethusiats"

[eclipse]

I don't know about a complete guide but here's what you can do:

1.Read this tutorial:
http://www.learningaboutelectronics....-pin-cable.php
It explains how to connect your USBasp programmer to Atmega328 chip (there are 2 versions with 6 or with 10 pin cable). Mine is with 10 pin connector.

2. Install Extreme Burner ( you need to connect your programmer before that)
http://extremeelectronics.co.in/avr-...r-programmers/

If you have Windows 7,8,10 it may not work correctly (shows missing DLL files, etc.) - in this case find Windows XP PC or install XP on virtual box to save a lot of headaches,
the software is not optimized under newer OS, it's free software so no complains.

Disconnect the programmer from the PC, and connect the Atmega328 chip to the programmer, then connect the programmer again back onto the PC, now with the chip in place.

3. Open Extreme Burner go to Chip -> and select Atmega328P
4. Click Open and load the hex file
5. Go to Fuse Bits and select like on the shown photo
6. Click Write All

That's all. It's not that hard, probably you have wrong connections.

I have 2 blank Atmega328P chips I can upload the file and post it to you, it will be around 8-9$ with shipping.

[Funfinder]

The problems here reminds me on my older satellite days with cards and firmware updating etc.
Homebrewed chipcards as the magic key to all the beautiful sexy girls etc. A fascinating time!


Usually there would be no chip-writing problems if everyone uses
the same programmer and computer-system!
In earlier times those programmers worked via the good old RS232 serial-port.

Now with USB you have to check out which programmer with what firmware works on what Windows version etc.

If someone buys such programmable uC chips he should be shure to have already or get directly a working
programmer for it. And those who sell these ICs usually know which programmer works and with what OS-version.


I'm using some of the following stuff (see pix) but this is for chipcards.
The CAS Studio (made in Italy) also can flash common access-modules for sat-receivers but no socket chips.
It works with USB like all the newer programmers.

Of course its also possible to buy some smartcard-slot (if the atmega328 is available on smartcard)
and solder the usually 7-8 used pins onto the metal detectors PCB. This way the chip is
updatable super easy and fast without opening the detector. By an usual smartcards-programmer.
And the MD only works if the keycard is inserted, which could be pretty cool to show around.

If the connection: computer <--> programmer is up, the writing itself should be super simple:

Selecting first the hex file for the internal flash with eeprom memory and if available the hex or bin for the
ext. eeprom and writing it with fuses not set (or as described in the manual) so the chip remains reflashable.

[scrungy_doolittle]

First of all, if you are using an arduino the programming part is done by downloading from the IDE.
That being said, there is an arduino sketch that lets you turn an arduino uno into a programmer to program other ATMEL parts. It actually comes with the Arduino IDE.
Now, if the guy making the detector, just used a bare part, without the programming interface, then converting an arduino to a programmer is a cheap way of doing it.

[nick holas]

hi all
thanks all for replys (bernt for better explanation of my problem)
i m lost!!! i read "satelite","arduino" ,"IDE" ( martian's name??? )hey guys!! i don t want to to go on Mars!!! just burning a little chip!! (joking!!).

eclipse ,my chip are not broken but after burning them ,when i try to reconnect them on usbasp,avrdudess it say "unable to recognise chip"(first time it recongnise them as atmega328p)
i think ,i ve made a wrong setting fuse
i m going to try your method but i m not at home so i can t now but during next week will do it and keep you up to date.
thanks again

[ivconic]

IDE is here: https://www.arduino.cc/en/Main/Software
...
Simplest way i can figure is using "Arduino UNO Programmer Tools".
Obtain Arduino UNO or clone and burn hex file using it and "Arduino UNO Programmer Tools" software.
So far i tested it with original UNO Rev3, NANO, MINI Pro and some cheap UNO clone made in China.
It's a simple GUI for avrdude. Everything is easier with it.
Tracing it's actions you can also learn a lot on avrdude params and how to invoke them manually later, if you want that.

[ivconic]

And another tip; how to "catch" HEX file from a sketch in IDE?
(these are elementary things, yet no harm to remind on them)
Just open any sketch in IDE and hit "verify" option.
IDE will generate temporary folder in %temp%, including all the object files and ... HEX file too.
Sweet. Just open %temp% folder and copy hex file to another desired location.
On closing IDE; temporary files from that folder will be deleted, so don't close IDE until you "catch" desired hex file.


P.S.
In Win7; open Start and type %temp% and hit enter.
You will see the content of hidden folder. Search subfolders by date and time.
Latest folder is containing your present IDE actions as well as hex file.

[ivconic]

Playing with Arduino is FUN!
I got time today to put all the things together and test this for the first time.
Wanted to keep things simpler as possible, used tiny bench power supply 12v and "ultra large heavy duty" coil... obtained from old 5.25" floppy!!!
Ok, this thing is working. Having indeed very interesting behavior. Worth to be made on regular pcb with Nano or Mini Pro... or bare Atmega328P.
Everything works just nice on the bench.
I picked up one of several tones available. Each one of those is acting different and interesting.
All other adjustments are working too, making differences in behavior.
So, this is checked. What's next? Making it on regular pcb and making real coil for it.

https://youtu.be/8aIkRmQEcfE

[ivconic]

If you're burning chips PROBABLY the connections from your programmer to your Atmega chip are wrong.
Even if you don't succeed in programming the chip it should not burn, it will only show you that there's an error and ask you to remove the programmer and try again.

What Windows version are you using? I've used Windows 7 (wasn't easy to install) at first but since couple of weeks I've upgraded to Windows 10 and Extreme Burner doesn't seems to be working, so I've installed virtual Windows XP (Oracle VM Box) and worked like a charm.

There's a new version of the hex 3.05 here it is:

[ATTACH]33951[/ATTACH]

Seems the author is following these forums...
I noticed changes in eeprom data manipulation on latest version!
Now those counter bytes are stored in different format than on earlier versions.
Earlier there were 3 eeprom locations holding 3 bytes for program counter and now there are only two bytes there.
First one is now in hexadecimal format. Though; i made several checks and it is the same value, earlier decimal and now hexadecimal.
For example; 300 power ups earlier was "224" and now is "E0" value on 4-th eeprom location.
On fifth eeprom location still is (also was earlier) value "7" and not changing.
299 power ups is now "E1", 298 power ups is now "E2"... etc
So main "mathematics" on counter seems not changed. Only the form of data stored in eeprom.
Second byte never changes though. And third byte disappeared in latest version (was present on 15-th location).
This also could be a smart trick from the author, in case of /int variable/ (it must be stored in 2 bytes).
So there you go... which one of two cases is? Two single bytes or one int variable holding 2 memory locations?
Ha!

[greylourie]

As it stands, the schematics and hex are available free for anyone. And a reflash when the 300 limit is reached, is a small thing to do. I'm probably seeing shadows where there aren't any, but a Geotech member pm'd asking me to be a proxy and open a user account on the Iranian forum.

The only possible disadvantage of the power-up limit is it makes it hard for any Tom, **** or Harry to churn these out and badge and sell them as their own work. The purpose of the use limit counter is to stop commercial cloning.
I don't see a problem with trying to decipher and understand the functions of the code, and how it makes the detector work. It reminds me a little, of a schematic 1843 posted.

[ivconic]

As it stands, the schematics and hex are available free for anyone. And a reflash when the 300 limit is reached, is a small thing to do. I'm probably seeing shadows where there aren't any, but a Geotech member pm'd asking me to be a proxy and open a user account on the Iranian forum.

The only possible disadvantage of the power-up limit is it makes it hard for any Tom, **** or Harry to churn these out and badge and sell them as their own work. The purpose of the use limit counter is to stop commercial cloning.
I don't see a problem with trying to decipher and understand the functions of the code, and how it makes the detector work. It reminds me a little, of a schematic 1843 posted.

Reasons to protect code are obvious and understandable, no problem with that.
But it's a "hobby on it's own" to be curious and try to nick out an information more than available.
It's just a curiosity with no bad background intentions. At least from my side.
Though there are other kind of people too. That's why i understand author's reasons and am not complaining much.
But curiosity will remain...

[greylourie]

Reasons to protect code are obvious and understandable, no problem with that.
But it's a "hobby on it's own" to be curious and try to nick out an information more than available.
It's just a curiosity with no bad background intentions. At least from my side.
Though there are other kind of people too. That's why i understand author's reasons and am not complaining much.
But curiosity will remain...

Its a good and useful to work out how it all goes together.

[Funfinder]

This checking out what the counter does reminds me on savestate hacking!

Play Gameboy "Legend of Zelda" via emulator, open the savestate file with a hex-editor
and change your 1 coin to 999 coins for being able to buy all the expensive stuff!

If you can change the felezjoo PI counter value from 300 to 9999 or to FF FF ...
To avoid annoying reprogramming.

And of course its important for tech-geeks to know how the rabbit runs.
At least for being able to repair this stuff if it doesn't work as it should.

[ivconic]

This checking out what the counter does reminds me on savestate hacking!

Play Gameboy "Legend of Zelda" via emulator, open the savestate file with a hex-editor
and change your 1 coin to 999 coins for being able to buy all the expensive stuff!

If you can change the felezjoo PI counter value from 300 to 9999 or to FF FF ...
To avoid annoying reprogramming.

And of course its important for tech-geeks to know how the rabbit runs.
At least for being able to repair this stuff if it doesn't work as it should.

Author of code is smarter than that. I am not absolutely sure; but it seems it is not simple "savestate" routine.
Somewhere in the code there is a condition which is limiting range of such numbers.
So it's something like; x number from eeprom can be ONLY in range zz to yy.
If number is out of range; call "DEMO!" ending.
So i guess you can only pick number from that range, in this particular case range is 0 to 300.
I tested this several times; instead regular count number, for example let's take 288, i wrote 290 in eeprom on 4th location.
And code accepted it naturally.
But than next time i wrote 301 and code rejected it producing "DEMO!" and instant ending of processing further.
So hacking eeprom content will not solve the problem.
Yet there is another solution; instead common Atmega328P bootloader (optiboot) certain custom bootloader can be flashed.
Such custom bootloader firstly will "reset" eeprom location to "300" and after that let the code to run.
So each time you turn ON the detector; number "300" will appear and code will run correctly.