When I rebuild Mon51 using Keil's C51 tools, the resulting Mon51 won't run on the Cypress FX2LP dev kit - the green BKPT LED doesn't turn on.

The Cypress-supplied MON51 runs fine on the same setup. Using the mon-ext-sio1-c0.hex and mon-ext-sio0-c0.hex in the C:CypressUSBTargetMonitor directory, both .HEX files download using CyConsole and turn on the green BKPT LED on the Dev Kit and connect to the Keil debugger on their respective ports.

When I recompile the Keil-supplied INSTALL.A51 in the C:KeilC51MON51 directory, I don't get a Green BKPT LED on the dev kit and the Keil debugger doesn't connect. I verified that my resulting mon51.M51 file matches the Cypress mon-ext-sio1-c0 and mon-ext-sio0-c0 M51 files (except for a slight variation in code/data size by a few bytes) so I'm confident that the memory layout is identical and the linker parameters are identical. My build and the Cypress builds all use MON51DP2.LIB and there are no code/data overlaps.

Why would I want to recompile this? Because I want to get Mon51 running on my target PCB with a slightly reconfigured WR_CODE function that asserts a port pin to Von Neumann-ize code memory (i.e., allow data-write access to code ram). I'd do this following instructions here: http://www.keil.com/support/docs/2279.htm. Before I do that, I'd like to get something simpler - unmodified - to run on a known platform.

A few questions I have:
* Any suggestions to recompile Mon51 to run on Cypress FX2 for FX2LP? I don't think my rebuilt Mon51 is running because the green BKPT LED doesn't turn on and it doesn't connect to the Keil debugger.
* Has anybody found the Cypress source for INSTALL.A51 or equivalent for Mon51? I've seen several posts from people looking for this source but the only answers are Keil pointing to Cypress and vice-versa. I could disassemble the working .HEX file but I'd guess that somebody has already done this over the last 10 years or so.
* Should I skip Mon51 and try the Raisonance monitor or ISD51? Would those be compatible with the Keil debugger?

Where I've looked for answers:
* http://www.keil.com/support/m...ll_a51.htm, MON51: CONFIGURING FOR TARGET, setting INT_ADR_OFF
* Keil Application Note 152: Installing and Using the Keil Monitor-51.
* Mon51.hlp file and user's guide.
* I followed instructions here to initialize the serial port: http://www.keil.com/forum/2033/. This post, from 2002, is very descriptive. It omits some register defs (T2CON for example) but those defs were easy to add.
* Web searches using terms such as Cypress, Mon51, Mon-51, Source, INSTALL.A51
* http://www.keil.com/support/docs/2354.htm - µVISION DEBUGGER: KEIL MON51 CONFIGURATIONS FOR EZUSB FX
* http://infocenter.arm.com/help/inde...phtCj.html - µVISION DEBUGGER: KEIL MON51 CONFIGURATIONS FOR EZUSB FX
* http://www.cypress.com/?docID=4629, AN42499, Setting Up, Using, and Troubleshooting the Keil™ Debugger Environment
* http://www.cypress.com/?docID=20336, Debugging FX1/FX2LP using Internal Monitor Code
* http://www.keil.com/forum/5978/ - Humorous post: guy says "Cypress told to ask ... Keil" and Reinhard Keil sends him back to Cypress.

Thanks!
-Jim

http://www.keil.com/forum/2033/
http://www.keil.com/support/docs/2279.htm
http://www.keil.com/support/man/docs/mon51/mon51_install_a51.htm
http://www.keil.com/forum/2033/http://www.keil.com/forum/5978/