| ??? 05/15/09 21:26 Read: times |
#165395 - Remember that the evaluation also adds an offset Responding to: ???'s previous message |
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...? |
| 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 |