My program runs fine on uvision simulation (nothing to do with Silab peripherials). Same program shows (long multiplied by long) calling C:0000 My tool integration shows both, uvision and Silab are using same programs. Silabl people could not help.
Tools do not belong to silab. Only IDE belongs to silabb. But tools used under silab IDE is from Keil. When you configure keil tools in keil environment, its more user friendly, but silab environment is not. So I am in trouble. If a person knows Keil well and looks in silab environment, he can understand faster.
"When you configure keil tools in keil environment, its more user friendly, but silab environment is not." So, in summary: * Keil IDE works, Si Labs doesn't; * Keil IDE is nice, Si Labs isn't. The answer seems very simple to me: use the Keil IDE, throw away the Si Labs! Or am I still missing something?
Have you used Silab chips? If yes, you also will know that Keil simulator do not support all Silab processor peripherial. You have to use Silab IDE and integrate Uvision tools and JTAG debugging tools. I think I was here to get help from a bit more experianced person. I am running out of time.