|ARM Technical Support Knowledge Articles|
Applies to: MON390 Target Monitor
Information in this article applies to:
I would like to run MON390 on a PhyCORE-390 board from Phytec that I have. I'm using the Mon390 project located at C51MON390PhyCore390mon390.uv2 to build my monitor. I can load the monitor's HEX file into the board without problems, and I see LEDs blinking during the monitor's initialization as described in the mon390 release notes.
My problem appears when I try to connect to the monitor using the example project called DEG.UV2 under Keil's C51MON390PhyCore390ExamplesDEBUG subfolder. I can't get the uVision Debugger to connect with MON390 using this example. An error message appears aying "CONNECTION TO TARGET SYSTEM LOST". What is wrong?
This example originally selects a Baud rate of 38400 BPS under Options for Target - Debug - Monitor-390 Driver Settings. Due to hardware settings particular to the PhyCORE-390 board, the proper BAUD rate must be 19200 BPS.
In uVision, go to Options for Target - Debug - Monitor-390 Driver Settings and change the BAUD rate from 38400 to 19200 BPS.
If this modification still doesn't work, read the troubleshooting section of Mon390 release notes.
Article last edited on: 2004-04-22 20:40:22
Did you find this article helpful? Yes No
How can we improve this article?