Hi, I'd like to know how uVision2 finds the Monitor when it is in ROM. Does the address where it stands have to be specified somewhere ? thx, julien
I'd like to know how uVision2 finds the Monitor when it is in ROM. Does the address where it stands have to be specified somewhere ? When the C16x monitor is loaded into ROM, the starting address (reset vector) must reside at 000000h. The actual monitor program can reside anywhere in memory. The monitor communicates with the PC using a serial port. The way that uVision2 "finds" the monitor is by sending a special command over the serial interface. The Monitor will respond in a certain way and that is how uVision2 knows it is talking to the monitor. Obviously, if there are serial port problems, uVision2 may not recognize the monitor. Keil Support
I wanted to know how uVision2 "finds" the monitor, because we would like it to communicate through the serial 2 in simulated serial mode (we are using the serial 1 for hardware debugging). But we'd still like to install the Monitor in RAM. So we'd like to load the monitor in a HEX file into the RAM, and then use uVison2 to load our application as if the monitor was in ROM, but for that we have to tell uVision where to find the monitor. Is there some way (no doubt it must be tricky)to do that ?
Actually, what you would have to do is: 1. Connect to the C16x using the standard serial port (that's what the bootloader uses), 2. Download the monitor BOOT to RAM (This program loads the real monitor), 3. Just after the monitor is loaded, you'll have to unplug your serial cable from the C16x serial port and plug it into the simulated serial port. I don't know if anyone has tried this or even if it will work. I'm pretty sure that uVision2 will probably complain that it has lost communication with the monitor. As soon as you connect up the simulated serial port, MAYBE uVision2 will be able to continue. If you get this to work, please let the rest of us know. Keil Software