Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
05/15/09 19:29
Read: times


 
#165391 - Keil + Easy-Downloader : Large programs do not work !!
Hi

Request some help from the experts on this forum

1. I am using the Keil Evaluation Software
2. 89C52 and the Easy Downloader Ver 2.1 (Thats what it shows when connected to Hyperterminal)
3. Some simple programs for Hello worlds, UART sample etc work fine.
The Keil IDE generates the Hex80 files
4. I have progressed on the software development. The program has grown larger, it compiles very well, and works perfectly in the simulation mode. I am successfully able to even simulate the UART by toolbox of the Keil IDE
5. When compiled, here is the Keil output
Program Size: data=95.0 xdata=52 code=1938
Looking at the size of the output.hex file, it shows 6KB on my windows filesystem.
6. I am using EZ Uploader V3.1 on my Windows Xp to burn the hex file into the target.
Here is the output
Connecting ...
Identify your Chip...
Filename : output.hex Used Memory : 2383
Erasing(1/10) ...
Writing ...
Verify ...
Complete!

So the problem is why is the size 2383 when the code itself 1938 ?? When this chip is tested on the hardware the program obviously does not run.

7. If I try to burn the firmware file, here are the results
Filename : ez52.hex Used Memory : 3587
Erasing(1/10) ...
Writing ...
Verify ...
Complete!

So step #7 is working fine.

This makes me point that there is something to do with whole memory address space setup from the Keil side and something getting messed up for larger programs.

While I continue to investigate, any pointers in the right direction would be of great help.




List of 15 messages in thread
TopicAuthorDate
Keil + Easy-Downloader : Large programs do not work !!            01/01/70 00:00      
   Evaluation Limitation            01/01/70 00:00      
      Yes, you are wrong!            01/01/70 00:00      
   Remember that the evaluation also adds an offset            01/01/70 00:00      
      but code starts at 0x2000            01/01/70 00:00      
         Reading is Fundamental            01/01/70 00:00      
   Keil Eval is indeed the problem !            01/01/70 00:00      
      I don't think that's true            01/01/70 00:00      
         Seems to be common to simulate with more memory            01/01/70 00:00      
            why 380 bytes when code is 1900 ?            01/01/70 00:00      
               problems            01/01/70 00:00      
                  it starts at 2000 !!            01/01/70 00:00      
                     of course it does - kind of            01/01/70 00:00      
                     RE: it starts at 2000 !!            01/01/70 00:00      
            Keil simulator            01/01/70 00:00      

Back to Subject List