??? 08/04/10 15:23 Read: times |
#177654 - I have to agree Responding to: ???'s previous message |
Erik Malund said:
I think you may be biased by your lack of experience with powerful debug monitors
yes, I had the displeeasure of speding, I do not know how long, trying to reformat the actual code to run with a monitor. I totally, absolutely, completely detest anything that requires that your actual code has to be modified for debugging. Leaving the monitor in is NOT an option. You'll get no argument from me there. I use a debugger that doesn't require any reformatting. There are many more SFR's that have to be understood and manipulated in order to run a program on the SiLabs boards
BALONEY, male cow manure, ridiculous if a chip has e.g. an A/D that you do not need/use then you do not need to "understand and manipulate" the associated SFRs, just leave them in the reset state. As you know, I'm a cycle-counter. The SiLabs guys wouldn't tell me how long it takes their PLL to acquire, and how close to the desired rate I could get, since I had to have precise timing in my executable. While I agree that, for a beginner, learning the SiLabs on-chip debug tool is probably on the same order of difficulty as learning a particular debug monitor, I doubt it's as easy to get a SiLabs chip going as it is to get a classic 80C31 going.
I think you may be biased by your lack of experience with SiLabs chips Yes, that's likely. After several conversations with the SiLabs folks, I concluded that there was too much stuff that had to be done with my particular EVK, in order to get it to run code already funcitonal on another MCU. That was based on their comments. I had asked them how to configure the device to run at a particular rate, with a particular external addressing scheme. At the time they had no help to offer. Erik
RE |