Hi, i'm using MCB167-Net board with uvision2. I want to connect a serial printer to this board. But since this board uses the same port to download monitor 166 and my code in the RAM, how should I test my printer? Regards Sonali
You can test the port by two methods; 1) Use a simulated serial port for the monitor/debugger. Details are in the documentation somewhere. 2) Use the port by not reserving it's vector space (under L166 misc. tab in the project) and disabling it as a control in the Debug/driver/settings sub-window of the project. You then have to use \NMI to stop the program. It works best if the settings for the monitor communications match the settings the target program is using. Otherwise, you may have to restart it from the beginning after stopping since the settings can be corrupted. Best luck
Hi, I went through the documents you have mentioned, but they dont seem to throw much light on the details of this mode. Can you help me with the following : 1] Where will I find a step by step documentation for implementation of simulated serial mode? 2] Where will I find the hex code for monitor to be burned in flash? 3] How do I simulate a serial interface? 4] What data should I send to this serial interface and in what sequence? Regards Sonali
The configuration of the Monitor-166 is described in detail in the file Keil\C166\Monitor\Readme.TXT.
See Keil\C166\Monitor\Readme.txt as suggested in Keil Support response. 1] Where will I find a step by step documentation for implementation of simulated serial mode? In readme.txt. As for burining it into your target flash, you will have to use the flash tools provided with the board. These will require the use of the bootstrap mode and the internal UART. You can also try 'memtool.exe' which is downloadable from the Infineon website. 2] Where will I find the hex code for monitor to be burned in flash? You create it in a build - see readme.txt. 3] How do I simulate a serial interface? You select it by setting a define - see readme.txt. 4] What data should I send to this serial interface and in what sequence? The actual format of the command/data/status transmissions are proprietary to Keil in UV2. The monitor source is not distributed, just the configuration portion. Best luck
Thanks for clearing all my doubts.