A problem of similar nature is troubling me. whenever the ball hits the walls the x coordinates starts from 2 or 3 instead of zero.therefore my 4*4 ball is partially visible. Is this a perennial problem or can be rectified? I am not interested in shifting the coordinates as it will affect the disappearance of the top blocks. also to make a variable(say var) negative I am using var=0-var; which I think is not working. Please help
i also wanted to know that as the flsh memory size is of 8kb only, while programming if our program exceeds the given space how will we come to know.Is it the EEP file tat tells us this??
Blaster Game
A problem of similar nature is troubling me. whenever the ball hits the walls the x coordinates starts from 2 or 3 instead of zero.therefore my 4*4 ball is partially visible. Is this a perennial problem or can be rectified? I am not interested in shifting the coordinates as it will affect the disappearance of the top blocks. also to make a variable(say var) negative I am using var=0-var; which I think is not working. Please help
RE: Query
The LCDs zeroeth page (if broken) appears as three pixel column after the fifth row and addressed by y address equal to 6.
The three pixels in each column are the LSBs
X address always starts with 0 and there is no error in any of the LCDs
Hope this helps
The competition deadline is approaching 15th august 11:59 p.m.
So speed up your process
@nehul sir
thanks nehul sir!!
i also wanted to know that as the flsh memory size is of 8kb only, while programming if our program exceeds the given space how will we come to know.Is it the EEP file tat tells us this??
Reply to program size
If you use WinAVR
During Compiling the program see the output tab and a section called .text . This is the size of the program in bytes.
If you use Studio
During Build Process it is shown in the output tab as program size.
I hope this clears the doubt
@nehul sir
thanks sir!!