We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I'm having some turkey a day early this year. I say again BS !! I've got the folloing ini file: Func void Hey() { printf("*****\n"); } pc=0x003 bs 0x06,1,"Hey();" bs 0x07 g pc=0x003 g pc=0x003 g // This is the end of my file Problem is simulator locks up. PROBLEM is this occurs on your example program BLINKY !!! My typical situation: I want to verify some(~15-20) calculations under the simulator. Easiest thing to do set the pc at begining of function, set a bs in the middle somewhere check value before clamp set bs at the end check a value after the clamp - easy enough. Then I want to check for a range of inputs, invalids ranges etc. so I want to run this several times. So I tried something similair to above which didn't work. Your simulator kept locking up so I reproduced it under your Blinky sample program sorry turkey no application specific thing that were doing which is the cause of this one. I just simply want your simulator to do something everytime I reach a breakpoint like run a function evaluate a variable I'm not asking for much. This counter thing is intriguing but I don't have much confidence in it. Seems like your having problems with 1. So I do an "include XXX.ini" and see: Func void Hey() { printf("*****\n"); } pc=0x003 bs 0x06,1,"Hey();" bs 0x07 g ***** pc=0x003 g ***** pc=0x003 g ***** and the simulator is locked up. Oh by the way uVision 2.31 under Windows 2000 PRO. So it seems this did what I expected but your simulator being locked up and having to end the task to get it to close is a real downer. So what's going on?
Sorry guys, this ones on me. I had a problem the other day which occurred and which I also reproduced on Blinky or so I had thought. I sent that one into you about the simulator not allowing modifications(via debug commands in the output window) to variables after the code had done a write to external memory(i.e., "MOVX @DPTR,A"). This latter one just made me start spinning and I looked at it really good and realized my so called Blinky was not your Blinky. I'm pretty convinced our specific settings are causing both of the issues I have raised. FYI they are: Our settings are: Silicon Labs C8051F021 Use Simulator Dialog DLL parameter -pyCYGF021 Xtal: 24 MhZ