This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

monitor51 problem

Hi there, i've got a project realizing mc8051 on a FPGA board and using mon51 of keil uvision3 for debugging. I got my VHDL code implemented and tested the functionality, the UART interface of the MC is working correctly, memory space is also von neuman wired, but the communication between my MC and the keil uvision is always wrong. I used the baudrate 9600 for the mon51 program. Is there any way to look inside what is going on? I mean is there any way to see if the mon51 on the ROM of my MC is working and is receiving some data from uvision?
p.s. i used a new setting for mon51. For example i changed the starting address of xdata and code, excuted the install-batch with proper parameter, and generated a new hex file for mon51 of keil uvision. But the keil uvision always seems to be working with the old mon51 setting. Why?

thanks & regards
chris

Parents
  • As Erik says, JTAG really is de rigueur these days - why would you choose a core without it?

    Because i don't have any choice, that all i've got. My job is to implement this 8051 ipcore into my fpga board, connect it with keil uvision's monitor program. We don't have jtag debugger.

Reply
  • As Erik says, JTAG really is de rigueur these days - why would you choose a core without it?

    Because i don't have any choice, that all i've got. My job is to implement this 8051 ipcore into my fpga board, connect it with keil uvision's monitor program. We don't have jtag debugger.

Children
  • I trust you have fed-back to the person who did make the choice, and ensured that they are aware of the implications...

    "My job is to ... connect it with keil uvision's monitor program"

    Are you familiar with doing that on a standard 8051 chip?

    If not, that would probably be the place to start. Then you will have a reference point for your FPGA implementation...