| ??? 01/21/10 23:34 Read: times |
#172656 - Sounds like hardware again Responding to: ???'s previous message |
Louis S said:
Is there an advantage to explicitly writing the code into an assembly file as opposed to emulator stepping? No - I think Richard was worried that you might just be stepping at the 'C' level... I've noticed that when the emulator uses its internal clock at 12 MHz the loop "never" (haven't caught it yet) hangs. When I set the internal emulation clock to 11.059MHz or use my target hardware clock (also 11.059MHz) than the hang comes back. If tweaking the clock causes it to hang or not, that again sounds like a hardware fault - probably a timing issue. Bit odd that it works at the higher frequency and not the lower, though! On the scope, the target hardware clock signal looks stable and clean. I think it's the memory timing that you need to be looking at... Have you run a thorough memory test yet? I'm not too sure on how the emulator POD generates multiple clock frequencies and will look into that. As Jez says, emulator pods can introduce a whole load of unwanted effects all of their own...! This is one of the reasons why JTAG was invented... |
