If you are unable to use the tools or make this determination, you should probably call Keil technical support and work through it with them.
You should be able to compile/debug directly into the board via JTAG if you have the project/memory set up correctly. The AXF file contains a lot more information beyond the executable code. If you download the AXF directly into the STM32's memory space you might well have a problem as it is not native binary. I wish you'd stick to one thread rather than opening a new one every time you have a thought.
Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
It seems to me that the problem is that you are trying to run a marathon before learning to crawl - let alone walk. Do you have any prior programming experience in general? Do you have any prior programming experience with small embedded microcontrollers in particular?
Have you taken any time to study the Keil documentation, and familiarise yourself with the tools and their use? Have you taken any time to study the GUI library documentation, examples, etc, and familiarise yourself with the tools and their use?
A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
If your're running the actual code on the actual target, then that's not simulating - is it?! That's the Real Thing - not a simulation!
A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Your Keil IDE probably has an option to generate a map file. This is a text file with usually a .map extension that can be viewed with the IDE editor. It identifies how much RAM and flash your code requires and is therefore much more useful than the size of an AXF file. Compare the .map information with the processor's 64KB of RAM and 256 KB of flash.
The Keil IDE in simulation mode executes your code entirely within the PC. Special software included with the IDE replaces target hardware with software functions. When you download your code into the EVAL board or any other processor, you are in target mode where your code is interacting with real, not simulated hardware. All of this information is available in the materials provided with the EVAL board and Keil IDE. If you are have a language problem, get someone to help you. Cheers, Hal