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

[AurumKid]

i was able to decompile or disassembled the hex using a windows decompiler program but i dont know how to edit the program. i think i was written in C language.

[eclipse]

If you decompile the hex file the result will be pseudo code at best, if your compiler is even capable of doing that.
You can't expect to edit & recompile it. I've done the same, just out of curiosity, with Hex-Rays, but this is as far as you could go.
Advanced knowledge is required from this point on, so my advice is don't waste your time.

[jladre]

If you decompile the hex file the result will be pseudo code at best, if your compiler is even capable of doing that.
You can't expect to edit & recompile it. I've done the same, just out of curiosity, with Hex-Rays, but this is as far as you could go.
Advanced knowledge is required from this point on, so my advice is don't waste your time.

exactly!!

[ivconic]

Not really though!
With strong nerves and lot of patience; something can be done.
I will not disclose final solution here, simply because it would not be a fair towards the author.
But i will put a bit oil on fire here and also provoke you to start working something.
If not in course to achieve final solutions than at least for educational purposes.
Each similar code is having certain rules. Certain procedure and certain repeatings.
Things were being complicated further because of the relative addresses, so you can't rely exactly on fixed addresses here.
But you can try to locate blocks of code, their repeatings and relative jumps.
Some procedures are common and the main trick is to recognize them in the code.
For example; the procedure of displaying a text string on LCD. Or to store a byte in eeprom.
Or to wait key stroke. Or this and that...
To be sure in what are you doing; knowing Atmega architecture is MUST!
Before starting anything else; first download Atmega's datasheet and start reading.
I will give here my first initial dump file and lot of useful comments i added later in process of analyzing it.
That's as far as i can help here.
But as i said; this is only for educational purposes!
Please don't ask me questions, i will not be in position to answer.

[jladre]

Not really though!
With strong nerves and lot of patience; something can be done.
I will not disclose final solution here, simply because it would not be a fair towards the author.
But i will put a bit oil on fire here and also provoke you to start working something.
If not in course to achieve final solutions than at least for educational purposes.
Each similar code is having certain rules. Certain procedure and certain repeatings.
Things were being complicated further because of the relative addresses, so you can't rely exactly on fixed addresses here.
But you can try to locate blocks of code, their repeatings and relative jumps.
Some procedures are common and the main trick is to recognize them in the code.
For example; the procedure of displaying a text string on LCD. Or to store a byte in eeprom.
Or to wait key stroke. Or this and that...
To be sure in what are you doing; knowing Atmega architecture is MUST!
Before starting anything else; first download Atmega's datasheet and start reading.
I will give here my first initial dump file and lot of useful comments i added later in process of analyzing it.
That's as far as i can help here.
But as i said; this is only for educational purposes!
Please don't ask me questions, i will not be in position to answer.

This is really helpful for disabling counter but it cannot be used to edit the source code.

[AurumKid]

Not really though!
With strong nerves and lot of patience; something can be done.
I will not disclose final solution here, simply because it would not be a fair towards the author.
But i will put a bit oil on fire here and also provoke you to start working something.
If not in course to achieve final solutions than at least for educational purposes.
Each similar code is having certain rules. Certain procedure and certain repeatings.
Things were being complicated further because of the relative addresses, so you can't rely exactly on fixed addresses here.
But you can try to locate blocks of code, their repeatings and relative jumps.
Some procedures are common and the main trick is to recognize them in the code.
For example; the procedure of displaying a text string on LCD. Or to store a byte in eeprom.
Or to wait key stroke. Or this and that...
To be sure in what are you doing; knowing Atmega architecture is MUST!
Before starting anything else; first download Atmega's datasheet and start reading.
I will give here my first initial dump file and lot of useful comments i added later in process of analyzing it.
That's as far as i can help here.
But as i said; this is only for educational purposes!
Please don't ask me questions, i will not be in position to answer.

exactly! atmega328p datasheet will be our bestfriend to re-write the program.

[scrungy_doolittle]

This is really helpful for disabling counter but it cannot be used to edit the source code.

I'm swamped at the moment, but I have reverse engineered many binaries. All of microsofts 6800, 8080, z80,6502 basic interpreters, code from russian instrument, etc.
It is not that bad, just a bit time consuming and if you have an emulator, much easier.

The code does not look like it was generated from C. Might be either assembler or basic.
It does terminate strings with a Null, so that is consistent with C.
Not familiar enough with the Mega to understand this to much, but I don't see local variables being held on the stack in this.
Of course, you don't see that with the Keil 8051 C compiler either, because they do overlays.

[Geo]

Not really though!
With strong nerves and lot of patience; something can be done.
I will not disclose final solution here, simply because it would not be a fair towards the author.
But i will put a bit oil on fire here and also provoke you to start working something.
If not in course to achieve final solutions than at least for educational purposes.
Each similar code is having certain rules. Certain procedure and certain repeatings.
Things were being complicated further because of the relative addresses, so you can't rely exactly on fixed addresses here.
But you can try to locate blocks of code, their repeatings and relative jumps.
Some procedures are common and the main trick is to recognize them in the code.
For example; the procedure of displaying a text string on LCD. Or to store a byte in eeprom.
Or to wait key stroke. Or this and that...
To be sure in what are you doing; knowing Atmega architecture is MUST!
Before starting anything else; first download Atmega's datasheet and start reading.
I will give here my first initial dump file and lot of useful comments i added later in process of analyzing it.
That's as far as i can help here.
But as i said; this is only for educational purposes!
Please don't ask me questions, i will not be in position to answer.

I have many years ago that i stoped the programming and cracking.
From what i remember, a jump command at "wrong password" message and we are ok .
But now i don't know what is happening with new technologies...

[Altair]

Not really though!
With strong nerves and lot of patience; something can be done.
I will not disclose final solution here, simply because it would not be a fair towards the author.
But i will put a bit oil on fire here and also provoke you to start working something.
If not in course to achieve final solutions than at least for educational purposes.
Each similar code is having certain rules. Certain procedure and certain repeatings.
Things were being complicated further because of the relative addresses, so you can't rely exactly on fixed addresses here.
But you can try to locate blocks of code, their repeatings and relative jumps.
Some procedures are common and the main trick is to recognize them in the code.
For example; the procedure of displaying a text string on LCD. Or to store a byte in eeprom.
Or to wait key stroke. Or this and that...
To be sure in what are you doing; knowing Atmega architecture is MUST!
Before starting anything else; first download Atmega's datasheet and start reading.
I will give here my first initial dump file and lot of useful comments i added later in process of analyzing it.
That's as far as i can help here.
But as i said; this is only for educational purposes!
Please don't ask me questions, i will not be in position to answer.

I am play some with AVR Simulator (same as Owosuma) trying to simulate and study felezjoo coding. I have seen the hint you posted some time ago (attached jpeg) and I wonder how you have set the virtual LCD to work.
I tried some LCD setting and confirm it but when start simulation nothing happen on virtual LCD!
An help shall be appreciated!

[ivconic]

Forget that simulator and learn Proteus.

[basellafe]

toros acicriut u put in this thread (usb avr progremer) does it work perfectly with this project

[mrtronik]

As ivconic suggested Proteus is the best tool for changing the code.
It is very easy to find the command than increase the counter variable
stored in microprocessor's eeprom and change the hex using a hex editor
with nop command.

[Geo]

Yes but why to changing the code????
300 times are enough, and after it you can reprogram the chip and have other 300 etc....

[mrtronik]

Just because it can be done.
But you are right.Its unnecessary.
Especially if there are often firmware updates.

[ivconic]

Yes but why to changing the code????
300 times are enough, and after it you can reprogram the chip and have other 300 etc....

I made one copy and sent it to a friend, 700km away, across the 2 borders, 2 customs.
A friend is not in position to reprogram it after the counter reaches 300 power ons.
Quite decent excuse for me!