2004-08-23 09:57 PM
2004-08-20 07:52 AM
I am using inDart with St72F63 (a flash device). It is a very limited tool to begin with. Anytime I set the a break point, the code is not running in real time. Since I am working on USB code, it mess all the timings. It is almost useless.
Does the ST's emulator have the same problem? Thanks in advance, Dong2004-08-20 11:22 AM
The work around to running realtime and using breakpoints on this device is to use the trap instruction.
It not ideal as you have to rebuild your code/etc but it does work. It is mentioned in the indart errata sheets. Hope this helps. sjo2004-08-23 02:30 AM
DVP and EMU don't have this limitation
Best Regards2004-08-23 02:30 AM
DVP and EMU don't have this limitation
Best Regards2004-08-23 07:24 AM
I am using ST7263 with Indar now, which is not very helpful. So I am think of changing to DVP or EMU? And what is the main difference? Which one shall I use?
Thanks, Dong2004-08-23 09:47 PM
Your only choice is the emulator, the dvp3 series does not support usb devices - and the emulator is very expensive.
Regards sjo2004-08-23 09:57 PM
This happens when working with HDFlash target devices (such as ST72F63) and one or more breakpoints are set. Since the device hasn't got any debug peripheral and it has a very small number of programming cycles, inDART technology has this limitation. On the other hand, all microcontroller's peripherals are not reconstructed or simulated by an external device. Besides the inDART-STX debugging approach makes sure that the target microcontroller's electrical characteristics (pull-ups, low-voltage operations, I/O thresholds, etc.) are 100% guaranteed.
As Sjo said, the work around to running realtime and using breakpoints on this device is to use the TRAP instruction. It's true that EMU doesn't have such a limitation, but it's also true that it is much more expensive than inDART, which is an in-circuit debugger. Luca [ This message was edited by: Luca_Defend on 24-08-2004 10:35 ]