Keil Logo

Troubleshooting

If MON166 does not start correctly, the problem typically lies with the CPU Startup Code or with the Monitor code and data locations. Carefully check these settings in the CONFIG.INC file to be sure they are correct.

In Bootstrap Mode, µVision verifies that the monitor downloaded correctly. If the monitor does not start, check to see that the Write Configuration Control bit _WRCFG matches your target hardware configuration.

If the Monitor stops working during the C startup code, you most likely have specified different settings in the CPU parameter section. Carefully verify that the settings of your startup code (STARTUP.A66 or START167.A66) match the settings in CONFIG.INC.

Note

  • In many cases it is possible to get a program working with the monitor but not without it. In these situations, the most likely cause is that the startup code in the monitor is correct, but the startup code in the program is not. If you encounter this situation, carefully compare the settings in the CONFIG.INC to the settings in your startup code (STARTUP.A66 or START167.A66).
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.