| ??? 05/16/09 04:40 Modified: 05/16/09 04:42 Read: times |
#165403 - but code starts at 0x2000 Responding to: ???'s previous message |
Andy Neil said:
Girish Nikam said:
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 ?? Remember that the evaluation also adds an offset to the code. It says "used memory" - not "code size" - so maybe the "used memory" includes the gap...? Even for the smallest small program like hello.c, the size of the program in the hex file detected by the programmer is around 0x2200 so looks like 0x2000 is the starting point. I was expecting the programmer to detect that the size of my program in the hex file close to 0x2000 + 1938 + some offset. However, here it is 0x2383 i.e 899 (decimal)so there is something terribly wrong out there. I cannot suspect the programmer because when I try to burn the Ez52.hex file (8.45Kbytes on WinXP filesystem), it does detect its size close to 0x3857 which is 6237 decimal. This Ez52.hex file is NOT generated by my Keil evaluation version but downloaded from the internet. So the problem lies with some setting or usage of Keil and I am trying to find that out. |
| Topic | Author | Date |
| 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 |