|ARM Technical Support Knowledge Articles|
Applies to: MON166 Target Monitor
Information in this article applies to:
I'm using the CAN peripherals in my application and must set the XPEN: XRAM & XBUS Peripheral Enable Control Bit (SYSCON.2) in the START167.A66 file. Everything works fine in the real hardware, but when I test my application with the Keil Monitor-166 it does not work. How can I solve this problem?
The Monitor-166 initializes the CPU and executes the EINIT instruction before your program loads and executes. On most 166/ST10 variants it is not possible to modify the SYSCON register after execution of EINIT.
For this reason, the monitor's startup code (in CONFIG.INC) must match that of your target program. If you use the Monitor in bootstrap mode you may modify the Monitor using the uVision2 projects in the KEILC166MONITOR folder.
Article last edited on: 2007-07-27 08:30:12
Did you find this article helpful? Yes No
How can we improve this article?